Skip to end of metadata
Go to start of metadata
ReportDescriptionNote
RCUVT_AEBLIf changes are made to the contents and structure of a variant table, change documents should be displayed.1112786
RCUCONFCDWith the display of the change documents there are differences with the added values. It is possible to display different information for the added value depending on whether you start with or without user name.580394
RCU_FIND_STRING_IN_DEPThis report is used to find any character string in object dependencies.
Added functions:
-F4 Help for object dependencies
-Addition of the type of object dependencies to the selection criteria
-Checkbutton for the separate selection of released object dependencies

1972641
2053008

RCCTKNOWThis report program checks whether the characteristic contains dependency assignments that are no longer used. On the selection screen, you can define whether the dependencies that are no longer used are deleted.Start this program if you cannot delete characteristics or global object dependencies, even though they are apparently not in use. You can start this program multiple times without losing data. The result is a list of dependencies that are no longer used.63275
RCU_COMPILE_DEPENDENCYThe where-used list of objects (for example, characteristics) in the dependency may display incorrect results. To correct the display, you must retranslate the affected dependency using the report RCU_COMPILE_DEPENDENCY.

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.

1547233
RCUUPDMATVAR

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.

1548171 ,
1548289
RMCUINOBTOIBASEMARAThe performance for reports 'RMCUINOBTOIBASEMARA' and 'RMCUINOBTOIBASEPLKONET' used for converting the configurations into the new data storage (CBASE) can be improved.198651
RCU_COMPARE_CONFIGURATIONSThe report enables the comparison of two configurations that are stored on the database.1711419 
RIBCHECKIBINThe report can be used for the analysis and correction of the data storage for configurations and object structures.206766
RCUIB_DELETE_DUPLICATE_CFG

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

RCU_EXCL_CHARACTERISTICS

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

362438, 336842, 387001
RCU_EXCL_COMPARISONA change transaction checks whether a change has occurred in the configuration. When you execute the RCU_EXCL_COMPARISON report, the system excludes characteristics that should not be taken into account for this comparison. The characteristics that are excluded by this report apply to all materials in all plants. Characteristics that are saved in the CABN_EXCL table are not used later for the comparison, regardless of whether the configuration has changed.487886
RCU_CLEANUP_IBINOBSIn certain cases, entries remain in the IBINOBS table even though you have already deleted the corresponding "observer" of the configuration (for example a purchase requisition). As a result, the system does not delete configuration data from the database even hough it is no longer used.808683
RCU_CHECK_CONFIGURATION

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

RCU_CLEANUP_CONFIGS_IN_CBASE

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.

708094
RCU_CONFIG_PROFILE_40_TO_45

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.

585019 ,
587721 ,
301829
RCU_VC_PERFORMANCEPerformance is not optimal in variant configuration and long runtimes occur either during the actual value assignment or when you go to the configuration. The aim of this note is to support the user during analysis to find out in which area of the configuration model runtime improvements can be achieved or how to avoid characteristic errors when structuring the configuration model. As a general note, however, some of the unsatisfactory modelings shown here do not necessarily have a negative effect on performance and the overall modeling must always be taken into account during the analysis. On the other hand, even if you pay attention to all the criteria listed below, you cannot expect extremely fast runtimes (of around one second) in a very large configuration model with very complex object dependencies.926714 ,
917987
RCUKDUPD

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.

1693067 ,
700873
Z_MAINTAIN_MANUAL_CONDITIONS

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.

2053795
ZZ_CHECK_CONS_OF_CFG_OF_MATVARThe report ZZ_CHECK_CONS_OF_CFG_OF_MATVAR returns incorrect results if the modification from Note 128942 or 961910 is used: If there are required characteristics that are hidden using a precondition but that are not valuated, there should now be a complete configuration. However, due to the report, these configurations are still displayed as incomplete as in the standard system.579239
RCU_CREATE_SYMBOLINTERVALWith this report, you create an interval for the number range for object "IB_SYM_ID". You can also maintain this interval with Transaction "SNRO". Execute the report directly after migration. This report is not a check report.203446
ZM01INOBThe report checks in table INOB whether the PARENT and OBJEK columns of a record contradict each other. If this is the case, then the report determines the correct entry for the PARENT column using the bill of material information in the OBJEK column, if this is possible. If input parameter "pm_updat" is valuated with "Y", the corrections are carried out on the database. You can start the report directly in correction mode.105819
ZKMATNSTFor all objects with the setting sales order (SET), the report checks in the configuration profile whether all of their sub-components have the entry "VBPS" in column OBTAB of table INOB. If this is not the case, these records are corrected. (You should execute this report in the old Release (<4.5B), if possible.) (Caution the report corrects the database immediately; it has no test mode)102751
RCU_CHECK_INOB_CIRCLE

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.

200914
RCU_CHECK_INOB_CIRCLE_2

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.

200914
RMCUINOBTOIBASEMARA_PBKOReport RMCUINOBTOIBASEMARA_PBKO converts the data of characteristics planning to the new storage. However, you may only start it after the following reports have run without errors: RM60XPRA_STAMM, RM60XPRA_BEW and RM60XPRA_CLEAN.140639 ,
174061 ,
301829
RMCUINOBTOIBASEMARA and RMCUINOBTOIBASEPLKONET

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).

301829 ,
301305 ,
302033
RCU_INTERFACE_DESIGN_40_TO_45This report should be executed after the conversion of the configuration profiles.301829
RCUCHECK_VBAP_IBASEThis report finds VBAP-cuobj entries without entries in the IBASE (database tables IBIN, IBST, IBINOWN). For sales orders in the old database storage it checks database tables INOB, KSSK and AUSP. In addition, this report checks whether the VBAP-cuobj differs from the IBINOWN-cuobj for the same sales order (IBASE) or from the INOB-cuobj (old database storage).201591
RCUCHECK_VBBE_VBAPThis report finds different CUOBJs for the same sales order in database tables VBBE and VBAP.201591
RCUCHECK_MARA_IBASEThis report finds MARA-cuobj entries without entries in the IBASE.201591
RCUCHECK_MARC_IBASEThis report finds MARC-cuobj entries without entries in the IBASE (database tables IBIN, IBST, IBINOWN). For plant-specific material variants in the old database storage it checks database tables INOB, KSSK and AUSP.201591
RCUCHECK_STPO_CUOBThis report finds STPO-knobj entries without CUOB-knobj entries.201591
RCUCHECK_CUOB_CUKBThis report finds CUOB entries without entries in database table CUKB.201591
RCUCHECK_KDST_STKOThis report finds KDST-stlnr entries without entries in database table STKO.201591
RCUCHECK_DOUBLE_INOBThis report finds repeated entries in database table INOB (the same applies to OBTAB, OBJEK, PARENT, ROOT).201591
RCUCHECK_INOB_EQUIThis report finds incorrect IBINOWN or INOB entries with owner (OBTAB) EQUI.201591
RCUCHECK_DUPLICATE_IBSTThis report finds repeated IBST entries with different ROOT or PARENT.201591
Z_VARTAB_CHECKThe report Z_VARTAB_CHECK checks all of the variant tables within the range of the selection criteria you entered for the consistency of the derivations of values for the tables. All existing change states are taken into account for the analysis. At the same time, the system analyzes whether tables exist with interval values that must be manually checked for redundancy. The system then outputs all variant tables with inconsistencies and intervals, together with their internal number (VTINT) and change number (ECM_NO) in each case, if it exists. Using the list that is output, you can click the relevant variant table to navigate directly to transaction CU60 to change inconsistent values if necessary.1553307
RCU_CHECK_INOB_CIRCLE_1 and RCU_CHECK_INOB_CIRCLE_2

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.

200914
RCU_CHECK_OWNER_INOBReport RCU_CHECK_OWNER_INOB or ZZVBIBOW checks all SD documents which have a configuration for the correct owner of the configuration.200914
IBRT_STATISTICS_CREATEThe search via variant classes (find objects in classes) or the search for material variants takes very long. During the performance analysis, you found out that single Select statements take a very long time and that these Select statements consist of dynamic join conditions. For very complex searches with many characteristic values and a great number of hits, these SELECT statements can be accelerated if you select via less than 4 tables at the same time.301944 ,
309035 ,
356397

 

 

 

  • No labels