Get Import State Plugin for the ABAP Build Framework
Waits for the import process to complete and verifies the return code (RC).
This documentation refers to Release 2025/06 (SAP Note 3615638) of the ABAP Build Framework 750+.
If you’re using a different release, please note that the plugin may have undergone slight changes, and some parameters could differ from what is described here.
For an overview of the releases, please refer to Note 3141309 – ABAP Build Framework overview of released TCIs.
ABAP Class
/BUILD/CL_CTS_GET_IMPORT_STATE
Build Script Configuration Parameters
The parameters listed below should be maintained in Section CTS of the configuration area in the build script.
| Parameter | Description |
|---|---|
maxReturnCode | (Default = 7) The maximum return code that is considered successful. |
pollingIntervalInSeconds | (Default = 30) The interval, in seconds, to wait between each attempt to check the import’s completion. |
pollingItrations | (Default = 600) The maximum number of attempts to check the import’s completion before a timeout occurs. |
generateTransportLogLink | (Default = false) Specifies whether to always generate an SAPGUI link to the transport log. If set to false, the link is only generated if the max return code is exceeded or if the import results in an error (RC > 7). |
TRANSPORT_RUNTIME_ID | (Default = “CTS-SOURCE_TRANSPORT”) The Runtime Value ID used to specify the single transport ID. |
Runtime Values
| Direction | Parameter | Description |
|---|---|---|
| Input | CTS-SOURCE_TRANSPORT | This parameter specifies the Transport ID to be used. The name of the parameter can be configured through the Build Script Configuration Parameter TRANSPORT_RUNTIME_ID |
| Input | CTS-IMPORT_TRANSPORTS | Multiple Transport IDs can be provided, separated by a semicolon (‘;’). This setting takes precedence—if a single Transport ID is specified elsewhere, it will be ignored. |
| Input | CTS-IMPORT_START_DATE_TIME | (Optional) If transports are imported multiple times using this plug-in, previous cofile entries may interfere with the process. To avoid confusion, a date/time string in the format YYYYMMDDHHMMSS (e.g., 20371231172453) must be provided. This timestamp should represent a point in time when the previous import was completed, but the current import had not yet started. |
| Output | CTS-IMPORT_STATE | The state will be set to “IMPORTED,” regardless of the return codes, if the transport has been successfully imported. |
| Output | CTS-RETURN_CODE | The highest return code encountered during any of the transport import phases. |
Results
For all transports with errors, the framework generates a SAP GUI shortcut (MIME type: application/x-sapshortcut). The shortcut is named using the convention: transport_log_link_{TRANSPORT_ID}.sap
Example
The Import configuration can be defined in the build script as follows:
"CTS": {
"maxReturnCode": 3,
"pollingIntervalInSeconds": 1,
"pollingItrations": 1,
"TRANSPORT_RUNTIME_ID": "TRANSPORT"
}