Hierarchy

⤷

⤷

Basic Data
Data Element | SATC_CI_TRANSPORT_SETTING |
Short Description | ATC transport checking (together with transport tools) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SATC_CI_TRANSPORT_SETTING | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Transport |
Medium | 15 | Transp. Set. |
Long | 20 | Transport Settings |
Heading | 30 | Transport Settings ATC |
Documentation
Definition
Here, you can control whether and how the ATC checks transport requests. If this feature is activated, then the ATC checks all ABAP repository objects in a transport request when the request is released in transaction SE09
, the Transport Organizer.
You can use this feature to set up a 'Q-Gate' for repository objects leaving development systems.
You have these options:
- No ATC Check: The ATC does not check objects in transports.
- Inform on errors (priority 1 and 2): The ATC checks all repository objects in a transport request in this system when the request is released. The ATC reports to the user who released the transport if there are any findings.
The user can display the findings and work with them normally, as in the ATC Result Browser. But the user is allowed to complete the release of the transport without displaying or correcting the findings.
In effect, this setting sets up a 'soft' Q-gate in a development or consolidation system. The ATC checks transports and informs users, but users can still transport objects that have priority 1 or 2 errors.
- Block on any error (priority 1 and 2): The ATC checks all repository objects in a transport request in this system when the request is released. The ATC reports to the user who released the transport if there are any findings.
The user can display the findings and work with them normally, as in theATC Result Browser. The user cannot complete the release of the transport request and cannot transport the objects as long as any finding of priority 1 or 2 is open for any object in the request.
This setting sets up a 'hard' Q-gate in a development or consolidation system. A user cannot complete a transport without fixing or getting an exemption for all findings for objects in the transport request.
It's recommended in this case that you set field For Which Kind of Results? to For any results on this screen. That way, a user can request a local exemption if it is necessary to complete the release of a transport without fixing all ATC findings.
Notes:
- The ATC can check transport requests only if the transport system is also set to allow checks. See transaction SE03, section Administration > Global Customizing. (Transport tools authorizations are required.)
- The ATC uses the standard check variant set by the ATC administrator in this system. That way, the ATC uses the same checks for transports as it does for local and central checks.
If no standard check variant has been set, then the ATC looks for a check variant that has the name
DEFAULT
. If no check variant is found, then the ATC reports an error when a transport is released.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 732 |