Hierarchy

⤷

⤷

Basic Data
Data Element | /TDAG/CPE_INPUT_CHECK_VALID |
Short Description | Consistency Check: Indicates Use Record Is Consistent |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ESDBOOLE | |
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 | Consistent |
Medium | 15 | Consistent |
Long | 20 | Consistent |
Heading | 55 | Indicates Use Record Is Consistent |
Documentation
Definition
Indicates whether a use record is consistent based on the rules defined for the consistency check. If you have specified more that one rule for a combination of main user group and environmental release category, the consistency check is positive when at least one of the applied rules is fulfilled.
Use
The main user group (MUG) and environmental release category (ERC) are always mandatory. The system checks whether the sector of end use (SU), process category (PROC), product category (PC), and article category (AC) are forbidden, mandatory, or optional for each combination of main user group and environmental release category.
The consistency check fails if the MUG or ERC are not maintained, if a mandatory use descriptor is not maintained, or if a forbidden use descriptor is maintained.
Dependencies
You can save even if the check shows that the entries are not consistent. For more information, see the Specify Rules for Consistency Check Customizing activity.
Example
History
Last changed by/on | SAP | 20141109 |
SAP Release Created in | 110_600 |