Show TOC

Function documentationAutomatic and Manual Check

 

Based on when the checks are performed, there are mainly two categories: Automatic (dynamic) check and manual check (static).

Automatic Check

Automatic check applies to cases in which checks are performed automatically due to triggering a transport-related operation.

When automatic check is performed and if the system doesn’t detect any issues from the checks (for example, DGP, ATC), the user action continues; if some issues are detected by the checks, a unified issue result popup window appears displaying detailed result information for each check.

In the popup window, a result table provides an overall status of each check. Below this table, tab pages for the individual checks, for example downgrade protection check, display a detailed issue list.

There are two types of severity for each conflict:

  1. Warning: You can ignore the issue and the action continues.

  2. Error: You cannot ignore the issue and the action will be stopped.

The overall status for each check type reflects the highest severity of the issues detected. The yellow status icon stands for a warning. The red status icon stands for an error.

Activities

  • In case of warning instances only, the Ignore issues and continue pushbutton will be enabled so you can continue your action or you can choose Cancel to cancel your action.

  • In case of error detection, the Ignore issues and continue pushbutton is disabled. You can only choose Cancel to cancel your action. The error needs to be fixed first.

  • If neither warning nor error issues are detected from checks, no results are displayed for these checks. For example, you may only see the overall status and tab page for the downgrade protection check and ABAP test cockpit check on the UI because for other checks, no issues were detected or the check itself is not active.

  • For checks performed before saving objects in a transport request in the managed system, the check results are displayed in SAP GUI, which is different from the Web-based UI. Here, the CSOL check result, the critical object check result, and the custom-specific check result are shown side by side on the UI.

Manual Check

In the Transport-Related Checks assignment block of the overview pages for normal change, urgent change, defect correction, and cycles (phase cycle, release cycle, and continual cycle), you can choose Perform check to start an asynchronous job that performs various checks, for example a downgrade protection check, for the current document (a change document or a change cycle). This is called manual check.

The Transport-Related Checks assignment block displays the tab pages for all check types regardless of whether or not issues exist. Regarding the overall status, the following statuses exist:

  • Warning

  • Error

  • Passed: Green icon means that no issue has been detected so far

  • Inactive: Grey icon means that the check is switched off or not active

The following provides an overview of the rules on defining a check as inactive in the Transport-Related Checks assignment block:

  • Downgrade Protection Check

    Regard each case below as inactive, or else active:

    1. Global switch in Customizing is off.

    2. The switches of the all relevant systems are off. Relevant systems comprises (for a change document) all the development systems of the transport requests that it contains and all the target systems that these development systems can reach via transport tracks; for a cycle, all the systems on the transport tracks of its task list. If there is no relevant system (for example, for a change document, it doesn’t contain any transport requests), it also means off.

  • Critical Object Check

    Regard each case below as inactive, or else active:

    1. The global switch is off.

    2. The switches of all the relevant systems are off. Relevant systems comprises (for a change document) all the development systems of the transport requests that it contains; for a cycle, all the development systems on the transport tracks of its task lists. If there is no relevant system (for example, for a change document, it doesn’t contain any transport requests), it also means off.

  • ATC and Code Inspector Check

    Regard each case below as inactive, or else active:

    The switches of all the relevant systems are off. Relevant systems comprises (for a change document) all the development systems of the transport requests that it contains; for a cycle, all the development systems on the transport tracks of its task list. If there is no relevant system (for example, for a change document, it doesn’t contain any transport requests), it also means off.

  • Custom-Specific Check

    Regard each case below as inactive, or else active:

    There is no active BAdI implementation.

When you load the assignment block for the first time or choose Refresh manually, the cached check results of the checks performed in your last session (either by an automatic check from the WebClient UI or by manual check) are displayed.

For custom-specific checks, the system performs both check before release and check before import. This means that both methods CHECK_BEFORE_RELEASE and CHECK_BEFORE_IMPORT are called if the check is performed manually from the Transport-Related Checks assignment block. However, the following rules apply:

  • The system only performs check before release on the open transport requests that are in the change (manual check from the change) or in the cycle (manual check from the cycle).

  • Regarding the check before import, the system detects issues based on the transport tracks and gets all relevant target systems with possible importable transport requests (located in the buffer). Then, they are passed to the method CHECK_BEFORE_IMPORT of the BAdI to perform the check.

Determining Issue Severity (Warning or Error) for Checks
  • For CSOL and downgrade protection checks customized in SAP Solution Manager Configuration (transaction SOLMAN_SETUP):

    Stop means error, Warning means warning, and Silent / Off means passed.

  • For critical object check:

    Issues detected before saving objects on transport requests in managed systems are always categorized as a Warning, or else as an Error.

  • For ABAP test cockpit check and code inspector check:

    It is customized and controlled in the managed system (ATC settings Start of the navigation path Behavior on Release End of the navigation path configuration). If Block on any errors is selected, priority 1 and 2 issues are categorized as an Error, or else as a Warning.

  • For custom-specific check:

    It is determined and controlled by BAdI implementation.