Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-EHS (Application Component) Environment, Health and Safety: Master Data⤷
CBEHS_BAS (Package) Common EH&S Objects
Basic Data
| Data Element | ESERVLID |
| Short Description | Validity Area |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ESDRVLID | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | TCG91 |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ESJ | |
| Default Component name | VAL_AREA | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Val. Area |
| Medium | 15 | Validity Area |
| Long | 20 | Validity Area |
| Heading | 10 | Val. Area |
Documentation
Definition
Specifies the validity area.
Supplementary Documentation - ESERVLID 0001
Definition
Specifies the area for which the data record has legal validity, for example, European Union, South America.
Dependencies
The rating, together with the validity area, forms the value assignment usage.
If you specify a value assignment usage during a search for specifications, this only has an effect on the search result if you specify search criteria at the same time for at least one of the following extended search functions:
- <Specification> with values assigned
- <Specification> contains components
- <Specification> with phrases assigned
Supplementary Documentation - ESERVLID 0010
Dependencies
In the inheritance template, you can:
- Specify value assignment types and identifiers independent of the usage (meaning the All usages indicator is set)
- Specify identifiers and value assignment types combined with a specific usage
When you choose the value assignment types, you can change to another property tree and specify other value assignment types. You can choose whether you want to replace the value assignment types you chose first with the new value assignment types, or extend your selection.
If you have defined individual usages in the inheritance template, only the data whose active usage matches the prerequisites is passed on (meaning, linked by reference).
In Customizing for Basic Data and Tools in the IMG activity Specify Environment Parameters, you can use the environment parameter INH_RESOLVE_STATUS_CONFLICT to set whether the status of the target specifications is taken into account.
The system checks that the line content does not overlap:
- Identifiers with the same category must either have a different language or different type.
An example of a combination that is not permitted:
- NUM/CAS und NUM/<generic>.
- Usages that have the same rating are not permitted to contain validity areas with shared countries or regions. Validity areas are broken down into countries and regions.
Some examples of combinations that are not permitted:
- PUBLIC/DE and PUBLIC/REG_WORLD
- INTERNAL/DE and INTERNAL/DE_BW (DE_BW is a region in DE)
- PUBLIC/DE and PUBLIC/<generic>
- Usages with the same validity area are not permitted to have generic ratings.
An example of a combination that is not permitted:
- PUBLIC/De and <generic>/DE
Processing inheritance templates already in use
If you have used an inheritance template in an inheritance relationship, the inheritance template can be changed only in that data already passed on cannot be deleted. If an inheritance template is already in use, the system displays a warning. Any changes to the inheritance template that are not permitted are rejected by the system.
You can therefore add new identifiers because the target specifications inherit a higher number of identifiers. Deleting existing identifiers is not, however, permitted.
You can:
- Change usages in the inheritance template subsequently if this does not restrict the data.
Example:
Instead of the validity area DE you can define the following:
- All validity areas
- A region of DE, for example, DE_BW
- All data records that are valid for DE_BW are also valid in every case for DE because DE_BW is included in DE.
- Delete individual usages.
Example:
You can delete the usage INTERNAL/US from the usages PUBLIC/DE and INTERNAL/US. The AND logic operation linking usages within an inheritance template does not restrict the inheritance template as much.
You must not:
- Replace an individual usage with another (for example, change PUBLIC/DE to PUBLIC/FR)
- Deactivate one of the set indicators All usages, All identifiers, or All value assignment types
Data inheritance
The system passes on data of the source specification whose usage concurs with that of the template, and displays the usage for the target specification correspondingly.
Example (for correct display, set SAPscript in the SAP system):
Usage in source Usage in template Usage in target
INTERNAL/REG_EU ALL/DE INTERNAL/DE
PUBLIC/US PUBLIC/REG_EU
Note: DE is contained in REG_EU, filter effect of validity area
INTERNAL/REG_EU ALL/US PUBLIC/US
PUBLIC/REG_WORLD
INTERNAL/REG_EU ALL/DE INTERNAL/DE
PUBLIC/DE PUBLIC/REG_EU PUBLIC/DE
History
| Last changed by/on | SAP | 20041223 |
| SAP Release Created in |
