ABAP Test Cockpit Plugin for the ABAP Build Framework
The ATC Build Plugin is directly invoking ATC classes, so it’s important to ensure that the relevant ATC functionality in your SAP system is up to date.
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_ATC_PLUGIN
Build Script Configuration Parameters
The parameters listed below should be maintained in Section ATC of the configuration area in the build script.
| Parameter | Description |
|---|---|
code_inspector_check_profile | Specify the name of the code inspector check profile to be used. If provided, ATC will operate in the code inspector mode. Configuring exactly one check profile is required. |
checkman_profile | Specify the name of the checkman profile to be used. If provided, ATC will run in checkman mode. Configuring exactly one check profile is required. Experimental! |
evaluate_prio | (Optional: “1”, “2”, “3”, “4”) If this parameter is not set, the plugin will complete successfully even if issues are found, assuming the evaluation is handled by the caller based on the provided checkstyle result file. If the parameter is set, the plugin will check for any findings with the specified or higher priority. In such cases, the plugin will return a status of “errornous.” For example, if “2” is specified, the plugin will check for findings of priority 1 or 2 and ignore findings with priority 3 or 4. |
only_transport | (Default: “false”) If set to “true”, only the objects from the original source transport (specifically, the subset of objects related to the current build task) will be used as the object set, rather than the entire package, including subpackages. If the build was not initiated with a supplied transport, this parameter has no effect. |
result_also_in_plug_in_log | (Optional: positive number as a string) Specifies the number of findings to be written to the plugin log. This parameter is only required if the result checkstyle.xml file(s) cannot be processed. |
enforce_user_parameter | (Default: false) If set to true, and the required ATC flavor is not active in the system, it will be activated for the executing user as a user parameter and reset after execution. If set to false, the active ATC flavor is only checked, and if it’s not suitable, the execution will be aborted. |
evaluate_failures | (Default: false) If set to true, the plugin will check if ATC reported any failures. If failures are found, the plugin will end with an error. |
life_span_in_days | (Default 7) Specify the number of days the ATC results should be retained. After this period, the results will be automatically deleted. |
Runtime Values
| Direction | Parameter | Description |
|---|---|---|
| Output | ATC_AGGREGATES_<TASK_ID> | Aggregated Results as JSON |
Results
- One XML file (per build task) in Checkstyle format, containing potential findings.
- One SAP shortcut file (per build task) that can be used to display the ATC results via SAP Logon in the backend system. This will only work if the ATC flavor used is active in the system.
Example
The ATC configuration can be defined in the build script as follows:
"ATC":
{
"CODE_INSPECTOR_CHECK_PROFILE": "DEFAULT",
"EVALUATE_PRIO": "2",
"ONLY_TRANSPORT": "true",
"RESULT_ALSO_IN_PLUG_IN_LOG": "100",
"enforce_user_parameter": false,
}