SAP SOLMAN is a tool used by organizations to manage their SAP landscapes effectively. One of the great features of SOLMAN is its Change Request Management (ChaRM), which provides a structured approach to managing transport requests (TRs) in SAP.
Since many clients and customers are using SOLMAN, and it will be supported until 2027, this blog will explore two special scenarios that often arise in SOLMAN.
Scenario 1: Handling Released Transport Requests in SOLMAN (when changes are not moved to PROD)
In certain situations, you may need to segregate objects from a released transport request. Since decoupling a released TR is not permitted, follow these steps:
- Create a New Change Document (CD): Create a new CD to manage the segregation process.
- Segregate Objects from the Older CD: Identify and segregate the objects from the existing CD.
- Lock Objects in a New TR of the New CD: Create a new transport request within the new CD and lock the segregated objects accordingly.
- CSOL Lock Management: If you're unable to lock the objects, it might be due to an active CSOL (Cross-System Object Lock). Use transaction code /N/TMWFLOW/LOCKMON or Administration Cockpit - CSOL in SOLMAN to remove the CSOL lock, allowing you to proceed with locking the objects in the new TR.
- Change the status of existing CD to WITHDRAWN: Forcefully change the status of an existing CD to "WITHDRAWN" using the report CRM_SOCM_SERVICE_REPORT.
Note: You might encounter a ToC (Transport of Copies) document somewhere, so proceed diligently with above steps.
Scenario 2: Managing TRs after QA Refreshes (when changes are not moved to PROD)
A common challenge during QA refreshes is that only changes made till the production system may be reflected in the QA environment. To address this, you can:
- Consolidate Changes: Instead of manually moving all the transport requests (TRs) of a change document (CD) one by one via STMS_IMPORT, include all objects from various TRs of the CD into a single TR. By doing this, all active versions of dependent objects will be locked in one TR. This approach is particularly helpful in implementation projects when you are building something from scratch.
- Move Consolidated TR via SOLMAN: Use SOLMAN to transport this consolidated TR and validate that all necessary changes are visible in the QA system.
By following the above actions for specific scenarios, we can efficiently handle CDs in SOLMAN with ease.
These insights are based on my experience. I recommend connecting with your Basis/Solman team for further guidance. I would greatly appreciate any additional details or new techniques you might have to offer. Your comments and feedback are welcome!
Bluesky
