Kontakt

Ansicht
Dokumentation

RPM_CHECK_DB_CONSISTENCY - Data Consistency Check Report

RPM_CHECK_DB_CONSISTENCY - Data Consistency Check Report

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The program checks the consistency of database entries for projects. Additionally it provides a repair option, which can correct inconsistencies.

Integration

Prerequisites

Features

Selection

Check mode:

  • Dependent table entries (CGPL -> RPM)
    In this check mode the program uses the CGPL tables as the source table and searches for related entries in the Pôrtfolio Management tables. This check mode finds the most critical errors and should be run prior to running the check 'Main table entries (CGPL -> RPM)'.
    Example: Project data in the Portfolio Management system is stored in tables CGPL_PROJECT and RPM_PROJECT. In check mode 'CGPL -> RPM' the program reads the entry in the CGPL table and tries to locate the matching entry in the Portfolio Management table. If not matching record can be found in the Portfolio Management table, then this represents a sever error, which will lead problems when processing this project.
  • Main table entries (RPM -> CGPL)
    This check mode uses the RPM tables as the source table and searches for related entries in the CGPL tables. Prior to running this mode you should execute in 'CGPL -> RPM' mode.

Project ID:
Select the projects you want to analyze. If no selection is made then all projects will be checked.
Objects, which can not be assigned to any project will only be detected by the program if you do not specify a project ID.

Repair errors:
This option allows for repair of inconsistencies. Click this checkbos to enable the repair functionality. See below for further details.

Objects:
Select, which object should be checked. Each object can be checked individually or in combination. To improve performance of the report, reduce the selection of objects.

Error log:
Here you can filter the kind of errors you want to see in the output. Furthermore you can specify a display variant for the log.

Standard Variants

Output

The list of errors is presented in an ALV list, where the columns have the following meaning:

  • Type: Severity of the error
  • Project ID: Indicates which project the record belongs to
  • If no project ID is displayed then this indicates that the object could not be properly linked to a project. A repair of the link to the project might be necessary.

  • If the ID displays 'Unrelated object' this means that this type of object usually is not stored with a link to a project and therefore no project ID can be provided.

  • Object: Object type
  • Table Name: Table where the error can be found
  • GUID: The key of the database record that is causing the error
  • Add. Key field: Additional key field to identify the record
  • Repair: Indicates whether a record can be repaired or not. If a repair can be performed the text 'Insert', 'Delete", or 'Modify' will be displayed. The repair has be be executed for each line and will be triggered when you click on the hotspot in the Repair column.
  • Message Text: Error message text

Activities

Repair mode:

  1. You have to activate the repair mode on the selection screen by clicking the checkbox 'Repair Errors'.
  2. The program output presents you with a list of all errors. The errors that are repairable can be identified by the Insert, Modify, or Delete option in the Repair column.
  3. Read the long text of the error message. This will provide you with information about the proposed repair. It is important to understand that the system proposes one method of repairing the problem. There might be other ways of correcting the error. You have to decide whether the proposed method meets your requirements.
  4. If so, then click on the text in the Repair column, which will initiate the repair. Depending on the type of repair, you will be presented with a list containing the record in question. The repair types include the following:
  • Insert: The system prefills all the key fields. It is your responsibility to enter data into the other fields to create a correct and complete data record. The list allows you to edit the presented record.

  • Modify: The system presents you the data of the record. From the error message you will know, which of the fields in the record is causing the problem. It is your responsibility to correct the data of those fields. The data in the list can be edited.
    In the case of PROJECT_GUID, the program tries to provide you with a proposal value if possible.

  • Delete: The system displays the record that will be deleted. It is your responsibility to verify that this record should really be deleted.

  1. Confirm by clicking the 'Save' button. Now the system executes the repair (insert, modify, delete). 'Cancel' if you do not want the repair to be executed.

Additional information about the repair functionality

  • A repair can only be executed once. The system prevents you from performing it a second time.
  • Keep in mind that performing one repair might actually fix other errors displayed in the error list. We therefore advise that you check the list carefully to verify if there are multiple error messages referring to the same object. If so, then choose the repair, which is likely to resolve all the problems.
  • Those records that cannot be repaired automatically have to be corrected manually by means of a custom report.

Example






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 6393 Date: 20240601 Time: 134717     sap01-206 ( 112 ms )