Ansicht
Dokumentation

RDDTTADI - Process GTADIR Checks on Entries in the TTADIR

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Description

During a development project there may be times when the global object directory (GTADIR) is not available, usually because the GTADIR_SERVER is offline. You access the GTADIR every time you create or generate new objects, perform relocation transports, or make manual changes in the TADIR (transaction SE03). In these cases, you are allowed to proceed, however the necessary GTADIR checks need to be repeated later. This requires an asyncronous GTADIR adjustment that performs the checks.

The adjustment is implemented as follows:
1.) The entry that needs to be checked is flagged in the TADIR.
2.) The GTADIR action is written to a buffer table for each object.
3.) The report program RDDTTADI is started asynchronously (usually in
the background). Each entry in the buffer table is checked with the
GTADIR.
If the GTADIR is not available, the report cannot run and is
terminated.

Any buffer table entries that cause errors (double or meaningless entries) trigger an automatic mail to the responsible developer. This mail contains a description of the problem.

When the adjustment is complete, the report displays a short log
with all the completed actions.

Parameters:
The report has two parameters, which you must either enter online, or maintain in a report variant:

1.) Suppress mail
Enter an X to suppress the automatic mail.

2.) SUPERUSR
Enter the user who you want to receive the automatic mails.

You can only execute the report online in transaction SE38. Execute the report daily in the background.

Requirements

Output

Example

Addresses (Business Address Services)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 1842 Date: 20240601 Time: 103006     sap01-206 ( 32 ms )