> ## Documentation Index
> Fetch the complete documentation index at: https://docs.luumen.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# SAP transports

> What SAP transports are, why operations teams care about them, and how Luumen tracks transport state across your landscape.

If your team is new to SAP, "transport" is the SAP term for a unit of change. This page explains the concept at the level a non-SAP infrastructure engineer needs to understand the rest of the Luumen platform. The next page, [Transports and compliance](/enterprise/integrations/sap-compliance), covers how transport state feeds Luumen's checks and scans.

## What an SAP transport is

A **transport** in SAP is a package of changes (code, configuration, customizing, data structures) that moves between SAP systems in a controlled order. The canonical pattern is:

```
Development (DEV)  →  Quality Assurance (QAS)  →  Production (PRD)
```

A change is built and tested in DEV, exported to a transport request, imported into QAS for validation, and finally imported into PRD. Each system in the chain has an **import queue** of transport requests waiting to be applied, and each transport that's been imported has a return code that indicates whether the import succeeded, partially succeeded, or failed.

This is similar in spirit to deploying a code change through environments, but it's specific to SAP and managed by SAP's own tooling rather than by general-purpose CI/CD.

## Why operations teams care

For an infrastructure or basis admin, transports matter for a few reasons:

* **Drift.** If a transport is imported in QAS but never makes it to PRD, the two systems are out of sync — a recurring source of "it worked in QAS" surprises.
* **Failed imports.** Transports that return errors leave the system in a known-bad state that needs investigation. Letting them pile up makes later imports riskier.
* **Audit trail.** Many compliance frameworks require evidence that production changes followed a documented promotion path. Transport history is the system-of-record for that evidence.
* **Coordinating with patches.** OS patches, kernel upgrades, and SAP kernel updates are often coordinated with transport activity to avoid interleaved changes that complicate rollback.

For a non-SAP team running this infrastructure on someone else's behalf, knowing the transport queue state is the difference between "we patched cleanly" and "we patched in the middle of a partial customizing rollout and now nothing works."

## What Luumen tracks

The agent collects transport-related properties from each SAP host during its normal data collection. The exact properties depend on the SAP system role, but typically include:

* **Import queue depth** — how many transports are waiting to be imported on this system.
* **Last import status** — return code of the most recent transport import (success, warning, error).
* **Outstanding error count** — transports in the queue that have failed and not been resolved.
* **Recent transport activity** — a window of recent imports for trending and audit context.

These properties show up on the host detail page in the UI like any other property the agent collects. They can be used in host group filters and in compliance checks — see [Transports and compliance](/enterprise/integrations/sap-compliance).

<Note>
  Luumen reads transport state through the same agent connection that collects everything else. It doesn't initiate or import transports. Promotion remains a deliberate operation your basis team controls.
</Note>

## Vocabulary cheat-sheet

For readers who aren't SAP-native:

| Term                  | Plain-English meaning                                                                                |
| --------------------- | ---------------------------------------------------------------------------------------------------- |
| **Transport request** | A change set, identified by a request number, that moves between SAP systems.                        |
| **Import queue**      | The list of transport requests waiting to be applied to a given system.                              |
| **Return code (RC)**  | The result of importing a transport. RC 0 is success; RC 4 is a warning; RC 8 or higher is an error. |
| **SID**               | System ID, a three-character identifier for an SAP system (e.g., `DEV`, `QAS`, `PRD`).               |
| **Basis**             | The SAP team responsible for installation, configuration, and operation of SAP systems.              |
| **Kernel**            | The compiled runtime SAP runs on. Kernel patches are a common change managed alongside transports.   |

If you want more depth than this overview, SAP's own documentation on Transport Management System (TMS) is the canonical reference.