Ansicht
Dokumentation

RDDTLCK2 - XPRA for TLOCK Conversion (R3TR DSYS, R3OB CHDO)

RDDTLCK2 - XPRA for TLOCK Conversion (R3TR DSYS, R3OB CHDO)

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

Description

RDDTLCK2 is used to adjust the lock key table to the longer object names in Release 4.6. You can execute this program as many times as you want in an SAP system with longer object names.

If you execute the program in an SAP system where the longer object names for the object types R3TR DSYS or R3OB CHDO are not yet recognized, an internal check prevents the program from starting.

When you upgrade an SAP system from a release prior to 4.6 to Release 4.6 or later, then this adjustment report program has to run once without errors. If the program is not run, or if it is run with errors, then you risk problems with lock management for the object types mentioned above, and will not be able to coordinate development work.

Example
For the object types mentioned above, you can include objects and their sub-objects that are already locked in repairs or corrections, in other repairs or corrections. This prevents the original repairs or corrections from being released.

To adjust the lock key table, the existing entries for the object types R3TR DSYS or R3OB CHDO are split into the following groups. These groups are handled differently from each other:

  • Lock key with old syntax (old object name lengths)
  • Lock key with new syntax (new name lengths; often appear when the report is restarted)

The lock key entries are handled as follows:

  • The transport objects are determined for lock keys with old syntax, and then used to determine the lock keys with the new syntax.
  • If the conversion is successful, the new lock keys are flagged for insertion in the lock key table. The corresponding lock keys with the old syntax are flagged for deletion from the lock key table.

  • Lock keys for transport objects that can no longer be locked are also flagged for deletion from the lock key table.

  • Any lock keys with new syntax that already exist remain unchanged.

After all entries in the original lock key table have been handled in the same way, the flagged database actions are carried out:

  • Converted lock keys are copied to the lock key table.
  • The old lock key entries are deleted.

Requirements

The SAP system must recognize the new name lengths of the transport objects.

The report checks these system requirements and prevents execution if they are not met.

Output

The output of the report is sent using the log interface, where you can expand the display at different levels.






General Data in Customer Master   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2965 Date: 20240601 Time: 092829     sap01-206 ( 53 ms )