Ansicht
Dokumentation

REPAIR_DOCU2 - Self-Explanatory Indicator: Consistency Between T100 / T100U / DOKIL

ROGBILLS - Synchronize billing plans   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Purpose

This report is used to restore the consistency between DOKIL, T100 and T100U tables regarding self-explanatory flag for objects belonging to documentation class 'Message' ('NA').

This reports also allows the comparison of the table entries between two systems. The system used for starting the actual report will also be called the 'current system'. The second system used as source, will be named 'reference system' in the further description.

Integration

Prerequisites

1. User needs to have authorization to use the transaction SE91.
2. The synchronization with a reference system is only possible, if the basis release of the reference system is 640 (or higher).
3. If the comparison with a reference system is required, you should clarify the following steps with the responsible system administrators:
1. The RFC destination pointing to the reference system must be created in transaction SM59 of the current system. The name of the RFC destination needs to be provided at the selection screen of the report.
2. As user for establishing the RFC connection between the systems 2 options would be possible:

Provide a specific dialog user within the RFC destination. Effect: If the report is started with this RFC destination, always the same user is taken for the building up the connection.

Select the option 'Current user' within the RFC destination. Effect: The user starting the report in the current system is taken for establishing the connection to the reference system.

Attention: For both options, the corresponding user must exist in the reference system to allow the comparison of the table entries.

1. Check that the function module 'INFO_DOKIL_T100U' exists in the reference system.

If report should be started in the 'change' mode, the transport request must be valid for the selected packages / message classes:

1. The user starting the report in the current system must have an unreleased task in this transport request.
2. The selected package(s) / message class(es) must lay in the same transport layer as the selected transport request.

The current system and all the target systems of the transport request must have at least the R3Trans version from January 5th 2006 (or newer) to avoid the problems during transport of docu objects.

Features

This report processes only the cases (processing types) described at the beginning of the output list (general text 'T100U_DOKIL').

Selection

Below you can find information about the selection options of this report.

Subscreen "Search parameters"

To reduce the runtime and the usage of the system resources, it's recommended to limit the amount of Repository objects via entering the package name or message class. If there is a mismatch between the selected package(s) and the transport request (transport layer), the affected message classes will be not processed by the report.

• Package

The system allows the usage of symbol '*' as placeholder.

• Application Area

The system allows the usage of symbol '*' as placeholder in the name of the message class.

Subscreen "Processing options"

• Transport request / task

This field can remain empty for the display / test mode ('T') of the report.

In the change / edit mode an entry is mandatory for this field. If the the report is started and the field is still empty, a popup for selecting a transport request appears automatically. The selected request must be valid for selected package(s) / message class(es), otherwise the process will be stopped or invalid package(s) / message class(es) will be excluded from processing.

• RFC Destination

This field must be filled, if the synchronization with a reference system is required.

• Display / Change mode

Symbol 'T' (default) means display / test mode. No changes to the content of the tables DOKIL / T100 / T100U are performed. Only a results list sorted by processing types is generated.

All other values (including no entry at all) for this field will start the report in change / edit mode. This means that table entries can be newly created / modified.

• Synchronisation

The field should be marked, if the content of the tables DOKIL / T100 / T100U needs to be synchronized within the current system.

Standard Variants

Output

As result, this report generates a list with several sections. The content of these depends on the mode (display / change), the report had been started with.

In both modes, the first section of the results list, contains all the possible processing types of the report, the reasons and the recommended follow up actions.

• Display / test mode:

The next section contains the objects, which would be processed automatically by the report, if started in 'Change' mode.

Afterwards, the section with cases, which would require manual processing, is displayed. This section can also contain a list of objects with inconsistencies between the tables T100 and T100U.

• Change / edit mode:

The next section contains the list of all objects, which could be processed automatically by this run of the report.

Afterwards the list of objects appears, which had been adjusted correctly on database level and inserted to a transport request.

The last section contains the problem cases, sorted by processing type. The description of the processing type is given at the beginning of the results list. The required manual activities should be defined individually by a docu-developer / user starting the report.

Attention:

Objects with processing type 0 (no synchronization is required) are not displayed in the output list.

Objects with processing type 40 (table entries are consistent for the Documentation Tool) could maybe processed automatically by the report, if a correct reference system is provided. If they still remain in the list of objects to be processed manually, the docu-developer needs to decide about the next actions.

The processing type 35 can help to find the docu objects with documentation class 'Message' without an entry in the table DOKIL with 'X' in the field 'MASTERLANG'.

Possible values for self-explanatory flag:

• Empty, no value in table DOKIL:

The documentation exists.

• Empty, no value in table T100U:

3 possible meanings:

• The documentation exists.

• The documentation does not exist.

• The synchronization is not done yet.

• 1:

The repository object does not appear on the screen.

• 2:

The repository object will be documented later.

• 3:

The repository object is described by its short text (no documentation is required).

Activities

If no reference system is provided, this report synchronizes the content of tables T100 / T100U / DOKIL regarding the value of self-explanatory flag, based only on information from the current system. The synchronization can include the recreation of entries in the tables DOKIL and T100U.

If a reference system is provided, this report tries to define the cases, which can be automatically processed, based on information received from tables of the reference and the current system. If the values are different (e.g. documentation exists in reference system, but a repository object is declared as not required documentation in the current system), the report performs no further automatical actions. The docu-developer / user has to decide (according to the results list) which actions should be performed to receive again a consistent state. For example: transport the object from the reference system, declare it is as self-explanatory in corresponding system, recreate the object from scratch.

Example

rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 9459 Date: 20240520 Time: 110035     sap01-206 ( 138 ms )