- SAP Managed Tags
Objective: This blog aims to guide users through the configuration and execution of transport checks in SAP Cloud ALM, with a specific focus on Downgrade Protection (DGP) and Cross-Reference Checks. These checks help ensure that transports do not unintentionally overwrite newer objects (DGP) and that all dependent or referenced objects are correctly included (Cross-Reference Checks), thereby maintaining system integrity and minimizing post-deployment issues in S/4HANA Private Cloud environments. This blog aims to guide users through the configuration and execution of transport checks in SAP Cloud ALM, with a specific focus on Downgrade Protection (DGP) and Cross-Reference Checks. These checks help ensure that transports do not unintentionally overwrite newer objects (DGP) and that all dependent or referenced objects are correctly included (Cross-Reference Checks), thereby maintaining system integrity and minimizing post-deployment issues in S/4HANA Private Cloud environments.
Transport checks is one of the new features that SAP CALM is providing.
The Transport Checks are available for Features application in Cloud ALM, and you can check a CTS-managed transport set to evaluate the impact on your production tenant.
The checks include Downgrade Protection and a Cross-Reference Check. It’s possible to choose to perform an individual check or both.
Downgrade Protection (DGP) tracks objects in transport requests, and reports conflicts when different versions of the same object that is saved in two or more transport requests is imported.
- Predecessor Check (Sequence Violation)
The system can detect conflicting predecessors, that is, preceding transport requests containing conflicts, at the time of importing transport requests to the production.
- Imminent Check (Downgrade Situation)
The system can detect impending (imminent) downgrade conflicts when transport requests are imported. This kind of conflict would become an actual downgrade if you ignored the conflict.
Cross-reference Check can detect inconsistencies for objects that are referenced in transport requests, indicating object dependencies.
Objects in transport requests sometimes refer to other objects that are not included in the transport. The cross-reference check applies a where-used-analysis to check the referenced objects in transport requests. If a referenced object doesn’t exist in the target system or if the referenced object in the source system has a different version than in the target system, the check indicates a potential error. In addition, the check shows the last transport requests for the missing object versions.
Let me take you through how to configure these transport checks and perform them in SAP CALM.
The first step is to enable the use case Transports: Check in Production system during the registration of the systems while configuring SAP CALM for Implementation:
To configure SAP Cloud ALM for Implementation for your SAP S/4HANA Private Cloud, do check out my blog:
Re: How to Configure SAP Cloud ALM for Implementation for Your SAP S/4 HANA Private Cloud Landscape
Just enabling Transports: check is not enough to perform the checks; RFC destination needs to be maintained with the source tenant, if you do not maintain it, you will get the below error message:
To maintain the RFC destination, follow the below steps:
Step 1: Goto SAP Note: 2475591 and download the role: SAP_SDF_ALM_TRCHK.SAP from the Attachments section:
Now goto the Development system of your landscape and upload the downloaded role in the tcode PFCG-> Role->Upload:
Step 2: Now Goto tcode SU01 in the Development system of your landscape and create a user, for example: TRCHECK_CALM, give the initial password and give the same role that we uploaded in step 1 to this user and save the User.
Step 3: Now we need to create RFC in Development system of the landscape, to do so goto SM59 and click on create button:
Give the Destination name (For example: TRCHECK_CALM_RFC) and select the connection type as 3:
In the Technical settings tab give the target host and instance no:
In the logon & Security tab, give the user we created in Step 2 and the password and save the RFC destination:
Do the connection test and authorization test:
Step 4: Login to Production system 000 client in SM30 Table view: /SDF/CMO_TARGET and maintain the RFC destination just created in step 3:
Once all the steps are performed, login to SAP CALM tenant and click on perform all checks in the Feature when the Transports have target tenant as Production system:
The results for Transports check are then reflected:
After the transport checks are performed, you can now deploy your changes to Production system.
| User | Count |
|---|---|
| 10 | |
| 8 | |
| 7 | |
| 6 | |
| 6 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
