Kontakt

Ansicht
Dokumentation

RDDTLCK1 - XPRA for TLOCK Conversion (for Namespace Extension)

RDDTLCK1 - XPRA for TLOCK Conversion (for Namespace Extension)

BAL Application Log Documentation   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Description

RDDTLOCK is used to adjust the lock key table in conjunction with the object name extension for Release 4.0. The program can be executed as often as required in an SAP System with extended object names (restart capability).

If the program is started in an SAP System that has not yet been supplied with extended object names, or in which tables with extended domains have not yet been converted, execution is prevented by internal checks. If the program is executed in such a system, this may result in the contents of the lock key table being lost completely.

When an SAP System is upgraded from a Release prior to 4.0 to Release 4.0 or later, this adjustment report must be run once successfully (without errors). If it is not executed or does not run correctly, there is a risk that problems will occur in the lock management of objects in repairs or corrections, therefore impairing regulated development coordination.

Example
Objects or related sub-objects that are already locked in repairs or corrections can be included in other repairs or corrections. This prevents the original repairs or corrections from being released.

To adjust the lock key table, the existing entries are divided into the following groups, which are treated differently:

  • Lock keys with old syntax (old name lengths of the objects)
  • Lock keys with new syntax (new name lengths, occur particularly when the report is restarted)
  • Other entries (incorrect - are marked for deletion, since they are not currently locking any objects)

The lock key entries from the first two groups are processed as follows:

  • The transport objects are determined for lock keys with the old syntax, and the appropriate lock keys then found with the new syntax.
  • If conversion is successful, the new lock keys are marked for insertion into the lock key table. The corresponding lock keys with the old syntax are marked for deletion from the lock key table.

  • Lock keys with the old syntax for which no transport objects can be determined - these lock keys are also marked for deletion, since they are no longer locking any objects.

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

  • Lock keys that already exist with the new syntax remain unchanged.

After all entries in the original lock key table have been processed in this way, the database actions only noted up till now are actually performed:

  • Transferring the converted lock keys to the lock key table
  • Deleting the old and the incorrect lock key entries

The incorrect entries that were deleted are then listed.

Requirements

The SAP System must know the new name lengths of the transport objects. The tables with extended domains have to be converted.

These system requirements are checked in the report; if they are not met, the report cannot be executed.

Output

The report output is shown with the log interface, which allows various expansion levels to be displayed.






TXBHW - Original Tax Base Amount in Local Currency   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3646 Date: 20240520 Time: 105833     sap01-206 ( 64 ms )