Introduction
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.
The system can detect conflicting predecessors, that is, preceding transport requests containing conflicts, at the time of importing transport requests to the production.
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.
ABAP repository data.
Dictionary objects
Customizing objects
Logical transport objects and SAP HANA objects are not supported.
Both checks identify conflicts with other transport requests by using the RFC connection you created in the production system that targets your development system. As a result, this checks all transports that are in the production system import buffer. This means that unassigned transports or transports assigned to another feature can also be conflicting entities.
Preparation
You can only perform checks for ABAP systems with CTC = 1 configuration
You’ve installed at least ST-PI 740 SP 27 and implemented the latest versions of SAP Notes 3497169 and 3497168
You’ve set up your RFC connection. For more information, see SAP Note 3447901
You created the role SAP_SDF_ALM_TRCHK for your RFC user as described in SAP Note 2475591
Your source tenant and target tenant reside on different physical systems.
In the production tenant for client 000, you’ve activated use case task Transports: Check. For more information, see Activating the Use Case Transports.
At least one CTS-managed transport is assigned to your feature.
Use
You can choose to perform an individual check or both. When you perform transport checks, all production tenants of all CTS-managed transports of your feature are checked.
You can start transport checks in the detail view of your feature in the Features app.
After a check has been successful and shows a warning or error, you can select a check to navigate to the Transport Checks app. The Transport Checks app provides more details about the checks and shows you what to do in case of critical results.
Check Statuses
Transport Checks can have the following statuses:
Scheduled: Transport check has been scheduled. Note that you can’t perform a check again as long as it’s in status Scheduled.
Completed: If your check passed, you can continue with deploying your feature. If your result shows a warning, you can select the check to navigate to the Transport Checks app to get more details.
Failed: If a check fails, follow the solution provided in the popover.
Canceled: If a transport check job hasn’t been picked up by the managed system within 8 hours, the transport check is canceled. In this case, perform the check again.
Notifications
You only receive an email notification for a completed transport check if you performed the check.
For more information about enabling notifications, see Working With In-App Notifications and Enabling Email Channel for In-App Notifications.
IntroductionThe 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.The cross-reference check can handle the following type of data:ABAP repository data.Dictionary objectsCustomizing objectsLogical transport objects and SAP HANA objects are not supported.Both checks identify conflicts with other transport requests by using the RFC connection you created in the production system that targets your development system. As a result, this checks all transports that are in the production system import buffer. This means that unassigned transports or transports assigned to another feature can also be conflicting entities.PreparationYou can only perform checks for ABAP systems with CTC = 1 configurationYou’ve installed at least ST-PI 740 SP 27 and implemented the latest versions of SAP Notes 3497169 and 3497168You’ve set up your RFC connection. For more information, see SAP Note 3447901 You created the role SAP_SDF_ALM_TRCHK for your RFC user as described in SAP Note 2475591Your source tenant and target tenant reside on different physical systems.In the production tenant for client 000, you’ve activated use case task Transports: Check. For more information, see Activating the Use Case Transports.At least one CTS-managed transport is assigned to your feature.Your transports are in the import queue of your production tenant, or are already deployed to production.UseYou can choose to perform an individual check or both. When you perform transport checks, all production tenants of all CTS-managed transports of your feature are checked.You can start transport checks in the detail view of your feature in the Features app. After a check has been successful and shows a warning or error, you can select a check to navigate to the Transport Checks app. The Transport Checks app provides more details about the checks and shows you what to do in case of critical results.Check StatusesTransport Checks can have the following statuses:Scheduled: Transport check has been scheduled. Note that you can’t perform a check again as long as it’s in status Scheduled.Completed: If your check passed, you can continue with deploying your feature. If your result shows a warning, you can select the check to navigate to the Transport Checks app to get more details.Failed: If a check fails, follow the solution provided in the popover.Canceled: If a transport check job hasn’t been picked up by the managed system within 8 hours, the transport check is canceled. In this case, perform the check again.NotificationsYou only receive an email notification for a completed transport check if you performed the check.For more information about enabling notifications, see Working With In-App Notifications and Enabling Email Channel for In-App Notifications. Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
