9. Correction Reports

1972641
2053008

Constraints and simple dependencies (procedures, selection conditions, and so on) are processed separately by the report.

The report displays the deleted and generated database records if required. This output can also be carried out in test mode for simple dependencies. In test mode however, only the records to be deleted can be displayed for constraints. The newly created records are displayed only in update mode.

The status of the retranslation (showing whether this was successful or whether syntax errors occurred) is also determined in test mode. In this respect, we recommend that you execute this first in test mode.

For the usage of materials and characteristics or characteristic values in the variant configuration, statistics can be recorded that support faster access to material variants (for example).

You use the report RCUUPDMATVAR to update material variants.  If a lot of material variants are processed in one run, a lot of V2 updates and deadlocks on the tables IBINVALST_SYM and/or IBINST_OBJ may occur. This note creates the prerequisites to enable the alternative methods of statistic determination that are described in Note 1548171.

The RCUIB_DELETE_DUPLICATE_CFG correction report deletes the duplicate configurations that are no longer used. Used configurations are marked for deletion, so that the system deletes these configurations as soon as the last user is deleted.

Use the following selection criteria: External object type = VBPS

You can run the program in the test mode first (leave the 'Execute Correction' field empty). After checking the data, you can correct the inconsistencies by selecting the field 'Execute Correction'.

608229 , 575221 , 558812 ,
901893

This report excludes characteristics that should not be taken into account during the variant matching or during the comparison of configuration results of the serial number processing. You can either restrict the exclusion to one material or apply it to all materials. Using this report, you can exclude certain characteristics for specific materials only or for specific materials in specific plants.

Use the following selection criteria:
Material number = Material number for which the characteristics are to be excluded
Characteristic name = Characteristic to be excluded

This report excludes characteristics that should not be taken into account during the variant matching or during the comparison of configuration results of the serial number processing. You can either restrict the exclusion to one material or apply it to all materials. Using this report, you can exclude certain characteristics for specific materials only or for specific materials in specific plants.

This report also searches for sales items whose VBAP-CUOBJ field that refers to configuration data that does not exist. The report deletes these references. Afterwards, you must configure the item again. The previous configuration value assignment is unfortunately lost and cannot be recovered.

Use the following selection criteria:

Find wrong vbap CUOBJ = X SELVBELN = Interval for sales documents to be checked

You can run the program in test mode first (leave the 'Update Database' field empty). After checking the data, you can correct the inconsistencies by selecting the field 'Update Database'. The reference is then deleted from the VBAP table. However, you must then maintain the configuration of the relevant document items manually.

To improve the performance of the report, you can create an additional index for the MANDT and CUOBJ fields in the VBAP table before you execute the report. After the execution, you can delete this index again.

200914

It can happen that configuration data in the IBase (CBase) remain on the database although no corresponding owner or observers exist. Due to these remnants usages are displayed in configurations which should not exist anymore.

The report RCU_CLEANUP_CONFIGS_IN_CBASE deletes configuration data from the CBase (IBase) only if this data no longer has an owner or observers. The scenario in which there is no owner but there are still observers is not taken into consideration here.

In this scenario, the owner of the configuration is now flagged for deletion. In IBINOWN, DELFLAG is set to X.

The configuration profiles are converted with report RCU_CONFIG_PROFILE_40_TO_45.  This report should be executed after migration to the higher release but before executing correction reports and data conversion reports.

This report program checks the syntax of the selected set of dependencies and lets you update the compilation of corrupt dependencies in the database. The check does not include constraint nets. It is possible to change compilations in the database for dependencies that are released and compilable if the compilation in the database is different from the compilation currently generated.
Output: List of checked dependencies. You can go to the detail screen and where-used list.
Example: We advise you to follow these steps when you use this report program:
1. Test run without changing the database to find which dependencies contain errors and determine the quantity structure.
2. Live run to change corrupt dependencies in the database.
We advise you to run the program in the background. You can define relevant restrictions for the dependencies to be changed (for example, using the internal number).
For information on selection options, see report program RCUKDCHK.

Up to now, it was possible to maintain the manual variant conditions on the characteristic value only in a very complicated way using transaction CU50. The report Z_MAINTAIN_MANUAL_CONDITIONS simplifies this.

As the selection criteria, you can specify the material and the validity date of the displayed characteristic values. On an ALV grid, the system then displays all of the relevant configurable characteristics and their values, and manual maintenance of the relevant variant conditions is possible.

Each characteristic value can be assigned exactly one variant condition.

This direct assignment of variant conditions to characteristic values, without having to enter a procedure or an action, is only possible for characteristics that have the format CHAR. For numeric characteristics, this option is not available.

The report checks the link of the instances within the structure of a configuration for any available links that are closed in a circular form. The report only takes into account entries from table INOB that have value "KMAT_NST" in column OBTAB. The following input options are available:

•  P_ROOT :Restriction of the analysis to certain ROOT-CUOBJs 
•  P_UPDATE  : If this parameter is valuated with any character, then the database is corrected.

Expected runtime: Short to average runtime Interpretation of the result: Action carried out: For any instance within a circle reference, column PARENT is occupied with the CUOBJ of the instance. You might have to execute this report several times in correction mode because it can only correct one error per object in a run.

The report checks the concatenation of the instances within the structure of a configuration for any possible concatenations that are closed in a circular form. The report only takes into account entries from table INOB that have value "VBPS" in column OBTAB.

P_UPDATE : If you assign any character to this parameter, then the database is corrected.

Expected runtime: Short runtime Interpretation of the result: Action carried out: For the owner instance of a circle reference column PARENT and ROOT are set to initial.

These two reports convert the configuration data from the old storage to the new storage.

Report RMCUINOBTOIBASEMARA is used to convert the configuration data for materials.

Report RMCUINOBTOIBASEPLKONET is used to convert the configuration data for standard networks.

Note 301305 delivers additional selection options for report RMCUINOBTOIBASEMARA. Using Note 302033, the data of characteristics planning in reports RMCUINOBTOIBASEMARA and RMCUINOBTOIBASEPLKONET is taken into account and no longer converted. It is essential to implement this note because otherwise data of characteristics planning might be lost during conversion of the configuration data. However, you can also use these reports as check reports. To be able to find the optimum length of the interval block size, you can determine it for the material number using report ZZ_FIND_ROOT_MATERIALS (Note 200914).

Reports RCU_CHECK_INOB_CIRCLE_1 and RCU_CHECK_INOB_CIRCLE_2 check the concatenation of instances for circle reference within the structure of a configuration.