Ansicht
Dokumentation

SPROX_TADIR_CHECK - Check/Repair SPRX consistency in TADIR

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Logical Transport Object SPRX

The logical transport object SPRX was initially introduced with the global proxy check for duplicates. Duplicate means different ABAP keys (OBJECT/OBJ_NAME) for the same external key (type/name/namespace). See also checkman check Duplicate HashID

Until now the logical transport object SPRX object was not persisted in table TADIR and only visible in the transport request for proxy changes. Here it acts as a trigger for the after import method (SPRX_AFTER_IMPORT) that checks/repairs those duplicates. In the "before release step" of the transport request release it is checked that for each proxy a SPRX entry exists in the object list.

SPRX Key

The SPRX key is derived from the TADIR entry for a proxy by concatenating OBJECT and OBJ_NAME into the OBJ_NAME key field.

Example:

For a proxy structure TABL MYTABLE the TADIR key is R3TR TABL MYTABLE, hence the SPRX key is R3TR SPRX TABLMYTABLE.

With introduction of SCWB/SNOTE support for ABAP proxies the logical transport object has to be persisted in table TADIR because it is needed in the version database framework to get a version for a proxy object.

For already delivered proxies this means that no SPRX key is available in TADIR/GTADIR so far. To deal with this an XPRA SPROX_FILL_TADIR was delivered which automatically fills the tables when it is imported.

Relevant Types

SPRX entries are created for all proxies types except business object enhancements (ENHO):

• DTEL ,,,,Simple Data Types

• TABL ,,,,Message Types, Complex Data Types

• TTYP ,,,,Table Types

• CLAS ,,Client Proxies, Exception Classes, Event Provider

• INTF ,,,,Server Proxies, Service Variants

• COBO,,Business Objects

• PAIN,,,,Inbound Process Agents

• PAOT,,,,Outbound Process Agents

TADIR check

For TADIR to be consistent with respect to proxy objects it has to be checked that

• SPRX entry exists in TADIR

• The SPRX entry must have the same package ( TADIR-DEVCLASS ) and

• the same original system ( TADIR-SRCSYSTEM )

• the same author ( TADIR-AUTHOR )

• the same masterlanguage ( TADIR-MASTERLANG )

This is checked during

• load of proxy,

• checkman check PROXY_CHK and

• before release of a transport request

Inconsistencies can be repaired via report SPROX_TADIR_CHECK

General Material Data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3218 Date: 20240601 Time: 092748     sap01-206 ( 54 ms )