Kontakt

Ansicht
Dokumentation

SOLMAN_CM_PRJ_LIFECY - Configure and Activate Cross-System Object Lock

SOLMAN_CM_PRJ_LIFECY - Configure and Activate Cross-System Object Lock

PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity you:

  1. Check the RFC connections required for using the cross-system object lock
  2. Activate the cross-system object lock for each satellite system
  3. Globally activate the cross-system object lock
  • The satellite systems have the following minimum Support Package level:
System Release Support Package Level
46C 51
46D 42
610 45
620 56
640 15
700 06

  • You have change authorization for the Transport Management System (TMS).
700

700
  1. Check the RFC connections.
Each satellite system involved in the cross-system object lock has to be able to communicate with a central Solution Manager system by means of an RFC connection. The central Solution Manager system manages the lock information. The default setting of the cross-system object lock is to use the Service Desk connection of each satellite system. This Service Desk connection is saved as OSS_MSG in the BCOS_CUST table of the satellite system and does not allow display interaction. For the cross-system object lock, you require either a trusted system connection, or you have to create an RFC connection with a special user of the type 'S' (Service). Assign the service user at least the SAP_SOLMANTMWCOL role. If you want to use a different Solution Manager system for the cross-system object lock than the Service Desk, you have to enter a new RFC connection in the BCOS_CUST table of the satellite system as follows:
  1. In the APPLI field, enter SOL_CONNECT.
  2. In the DESTINAT field, enter the new RFC connection.
  • Activate the cross-system object lock for each satellite system.
    • The cross-system object lock has to be activated at client level. To do so, proceed as follows:
    1. In transaction /TMWFLOW/CMSCONF, select the System Change Options tab page.
    2. In the System/Client column, select the relevant client.
    3. In the Cross Sys. Obj. Lock column, double-click inactive .
    4. If you are sure that you want to activate the cross-system object lock for the client that you selected, choose Yes.
    5. Repeat the procedure for all clients of all the development systems that are involved in a project.
  • Globally activate the cross-system object lock
    • To globally activate the cross-system object lock for all the systems and clients that you selected in transaction /TMWFLOW/CMSCONF, you have to execute the /TMWFLOW/CONFIG_SERVICES report (final activity for this IMG activity).
    On the ChaRM Services screen, select Cross-System Object Lock Active and then choose Execute.
    If the cross-system object lock is deactivated (Cross-System Object Lock Not Active is selected), cross-system object locks can no longer be performed. Note that the /TMWFLOW/CONFIG_SERVICES program always shows the current status (Cross-System Object Lock Active, for example).

    For more information about the cross-system object lock, see the Knowledge Warehouse documentation for Change Request Management.

    700






    CPI1466 during Backup   TXBHW - Original Tax Base Amount in Local Currency  
    This documentation is copyright by SAP AG.

    Length: 4557 Date: 20240523 Time: 161545     sap01-206 ( 77 ms )