Hierarchy

⤷

⤷

Basic Data
Data Element | EHSBE_RC_FIPARAM_CONSTR_USAGE |
Short Description | Usage of Constraints |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EHSBD_RC_TEXT_128 | |
Data Type | CHAR | Character String |
Length | 128 | |
Decimal Places | 0 | |
Output Length | 128 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | CONSTRAINT_USAGE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Usage |
Medium | 15 | Usage |
Long | 20 | Usage |
Heading | 30 | Usage |
Documentation
Definition
Use
In the compliance check, the system only takes constraints into account whose usage is within the usage specified here.
Dependencies
A constraint is implemented by means of a value assignment instance. The system only checks those constraints whose usage is part of the usage defined on the initial screen of the compliance check and whose value assignment instance is marked as active.
If you specified more than one usage on the initial screen, the system only takes those constraints into account that have all usages (AND operation).
Note
The system saves the usage defined on the initial screen of the compliance check in the result of the check. If you have already performed a check with the same parameters, the system overwrites the result of this check.
Example
You defined the usage PUBLIC REGION EU (EU stands for Europe) on the initial screen of the compliance check. The system determines all constraints with rating PUBLIC that are valid worldwide and for Europe and are defined in Customizing for EH&S, for example, REG_WORLD.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 700 |