Ansicht
Dokumentation

CNV_10020_ANALYSE - Analysis of object types and filling percentage of determination flds

CNV_10020_ANALYSE - Analysis of object types and filling percentage of determination flds

Vendor Master (General Section)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program analyzes all relevant fields as specified in table CNV_10020_DTFLD for a given package with regard to the degree to which the fields itself and the assigned determination object are filled. (Depending on the analysis type, the determination object is either the source or the target determination object.)

If the determination covers fields that contain an object number, the program also finds out how often the different object types occur.

Selection screen

On the selection screen, you define the package. You can specify the tables for which you want to run the analysis.

The parameter User mode can be used to enable the expert mode. Normally, the org package decides via an exit or parameter if the user is a standard user or not.

Analysis mode

The analysis type specifies if you want to consider priorities for DTFLD entries, if you want to find out about the filling percentage for source or target determination objects, or if you simply want to analyze the object numbers. If you do not enter a value, the default setting that is stored with the package parameters applies.
Note: Note that the analysis does not consider logical relationships. If you selected an analysis type with prioritization, the analysis for records with logical relationships is done without prioritization.

To determine the filling percentage of the target determination objects, the program needs a determination, which is normally not possible at this point because the object tables are probably not yet filled. In this case, you can override the determination type for the determination paths to enable determination at runtime.

If the indicator Filling percentage only for suggestions is set, the program analyzes only DTFLD entries that are suggested by the system, while the shipped DTFLD entries are not analyzed.

If no DTFLD entries were shipped for a field that is to be converted, the org. package suggests and stores exactly one entry. Often, however, there is more than one possible entry. If the indicator Analyze all suggestions is set, all possible suggestions are analyzed. If the filling percentage for the stored entry is lower than the corresponding percentage for another value, this other value is used instead of the originally stored one.

If the indicator Exclude already analyzed tables is set, tables for which an analysis has already been made are not analzed once again. This is helpful if you include an additional field in the conversion after the analysis has run and want to do an analysis for this additional field only.

Fields for which determination should not take place and tables that should not be analyzed (for example because it would take too long) are excluded from the analysis by the 'do not analyze' indicator in the related DTFLD entry if the indicator Only selected DTFLD entries is set.
Note: This applies only to the analysis of the fililng percentage. The analysis of different object types takes place for DTFLD entries with source determination object OBJNR or OBJNRD even if the 'do not analyze' indicator is set - as long as the package parameter DT_EXCLUDE_IRRELEVANT_OBART_GLOBAL is set (default setting).

Table ONR00 contains (almost) all object numbers that exist in the system. If the indicator Count object numbers in ONR00 is set, the system determines the number of occurrences for the different object types. This helps you to find out which object types might cause problems because they occur very often.

Mode for deleting analysis results

The analysis results are deleted for the (possibly limited) selection. This includes not only the analysis status, but also the underlying tables.

Execution type

If the indicator Schedule analysis jobs is set, the system schedules jobs for the individual tables. You can then execute these jobs in parallel in the background.
If the indicator is not set, the tables are analyzed sequentially.

If the indicator Start analysis jobs directly is set, the job starter is triggered, which means that all scheduled analysis jobs are started. If the analysis jobs have to be scheduled first, the job starter is triggered as soon as a few scheduled jobs are available.
If the indicator is not set, the analysis jobs are scheduled, but not started.

If the indicator Execute in background is set, the program is executed in the background with the current settings as specified on the selection screen.






ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4961 Date: 20240520 Time: 073856     sap01-206 ( 109 ms )