Hierarchy
DMIS (Software Component) DMIS 2011_1⤷
CA-GTF-BS (Application Component) Business Application Support⤷
CNV_10020 (Package) CNV package 10020
Basic Data
| Data Element | CNV_10020_RELMIXED |
| Short Description | Mixed relevance |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CNV_10020_XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | MixedRel |
| Medium | 18 | Mixed relevance |
| Long | 20 | Mixed relevance |
| Heading | 8 | MixedRel |
Documentation
Definition
The system sets the indicator for mixed relevance automatically when maintaining relevant values for different main source package numbers for a given determination object. For a path determination, the relevance check has to be repeated at runtime.
Example
You blended packages for renaming cost elements and profit centers. The conversion of the cost elements takes place in controlling areas 1000 and 2000, the conversion of the profit centers in controlling areas 2000 and 3000.
If you maintained the settings accordingly, the information about the global relevance is stored in the corresponding object tables when the object tables are loaded. This means that the determination values 1000, 2000 and 3000 are flagged as relevant for determination paths that have KOKRS as determination object.
When reading a relevant controlling area in an object table at runtime, the system then determines the main source package to which the relevant field belongs, and a subsequent local relevance check takes place.
Notes
For performance reasons, try to avoid mixed relevance if possible. If, for example, the cost element and profit center conversion in the example given above was to take place in controlling areas 1000 and 2000 for both packages, it would be better to globally assign the relevant values in the relevance table.
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in |
