Ansicht
Dokumentation

AGSGBC_UPDATE_REF_TEXT_SMUD - Repair description based on reference for Diagram usage report

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Purpose

When a reference is assigned to a diagram object, the user can decide to rename the diagram object based on the referenced object.

While doing so, if the description of the referenced object is changed in Solution Documentation, then the description of the diagram object is automatically adjusted to the new text.

This is working fine in the Diagramuser interface, but this is not the case for the Diagram Usage report.

There the user sees one of the following descriptions:

- The older description, which was retrieved from Solution Documentation when the referenced object was chosen

- The up-to-date description of the referenced object, even if renaming capability has not been chosen (if SAP Note 2965930 has been implemented on your system).

You can adjust the database, by using report AGSGBC_UPDATE_REF_TEXT_SMUD, to ensure that the renaming feature is handled in the Diagram Usage report similarly as in the Diagramuser interface.

Integration

Prerequisites

You have upgraded to Solution Manager SP13 or higher.

Features

Selection

Solution - This field is mandatory. If you have several solutions in your system, you should run the report for all of them to ensure all diagrams have been analyzed and eventually repaired.

Branch - You can select a Branch, belonging to the selected Solution or let the field empty to analyze all branches of the Solution.

Diagram ID - You can specify a Diagram ID (GUID). The report will then analyze and eventually repair the specified diagram within the specified Branch (or for all Branches of the solution if Branch has not been specified).

Test Mode - In test mode, the data will be analyzed, but no update will be done in the database.

Background Job - This option allows you to execute the report in background.

Standard Variants

Output

After the execution, you will see the results of the analysis.

When the report is executed for the first time, all diagram IDs and versions are collected in a specific table, that will be processed afterwards.

All diagrams created afterwards will be ignored by the repair report, as the database will be properly updated when the diagram is saved.

The header info will mention:

- the number of diagrams that still need to be analyzed in the system,

- the number of diagrams analyzed in the current run,

- the number of diagrams repaired during the current run,

- the number of diagrams in error for the current run. If an error prevents the update to be done when necessary (eg the diagram is already locked by another user), this will be mentioned. The repair report should then be executed again to complete the diagram processing.

For each execution run, the output list shows:

- the Diagram Id and description

- the Diagram version

- the Branch

- a link to navigate to the diagram in Solution Documentation

- the previous Diagram' status

- the current Diagram' status,

- the error text (if any).

All Diagrams/versions processed successfully in update mode, will not be analyzed again.

Activities

You should run the report in update mode for all Solutions in your system.

Remark - You may have obsolete diagram versions in your system. Meaning, version that does not show up anymore in Solution Documentation but are still available in the Diagram table. If you ran the repair report for all your solutions without issue in update mode, then you can ignore them.

Example

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4095 Date: 20240520 Time: 062325     sap01-206 ( 64 ms )