Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
EHS-SAF (Application Component) Product Safety⤷
CBUI (Package) Company Environment Information System
Basic Data
| Data Element | ESESTGEN |
| Short Description | Generation Not Permitted |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ESDFLAG | |
| 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 | GenNotPerm |
| Medium | 15 | Gen. not perm. |
| Long | 20 | Generation not perm. |
| Heading | 20 | Generation not perm. |
Documentation
Definition
Specifies that generating the data that has the status is not permitted.
Dependencies
If the Status check indicator is set in the report geneneration variant header, or in the dialog box for the Report from template function, the status is checked for the current key date as follows:
- Preliminary check
The SAP System generates combinations of the leading validity area (in the report generation variant header) and the ratings of the highest priority.
The system checks whether in these combinations at least one status entry exists for the relevant specification for which the Generation not permitted indicator is set in the IMG activity Specify Statuses.
Here, a 1:1 check is performed for the validity areas, or in other words, the validity areas are not expanded to their countries and regions.
Note:
- If the exclusion indicator was set, this constitutes an exception whereby the validity areas are expanded to their countries and regions.
The following cases could occur:
- If the status for a usage does not permit generation, generation is canceled without any data being read.
- This ensures that system performance is not unnecessarily impaired. The report is assigned the status Generation failed.
- If no status forbids generation, the system runs the check between the usages that lead to the selection of the data records due to the set usage check, and the usages for the status entries of the specification status. There could therefore be usages for which data selection was successful, but for which there is a status entry that does not permit generation.
- Example:
- Usage check: 0 (subset)
- Status entry: PUBLIC/REG_EU/In process (this means generation is not permitted)
- Generation variant: PUBLIC/DE (=> preliminary check successful, since no status entry was found during the 1:1 check that does not permit generation)
- Value assignment instance: PUBLIC/REG_EU (=> data record is selected due to usage check (0)
- Data record is however rejected due to the status entry as this does not permit generation for PUBLIC/REG_EU.
- Check for selected data records
In this check the system decides for each data record (identifier or value assignment instance) whether the status entry for the relevant specification does not permit output of the data on reports.
This check includes all usages for the data record that lead to the data record being selected.
Example of selection:
Usage check: 0 (subset)
Report generation variant (RGV): PUBLIC/REG_EU
Value assignment instance:
- PUBLIC/DE
- PUBLIC/REG_EU
- PUBLIC/REG_WORLD
- INTERNAL/US
Due to the usage check (0), the comparison of the report generation variant usage and the value assignment instance usages leads to the value assignment instance being selected as valid using the usages PUBLIC/REG_EU and PUBLIC/REG_WORLD. (The expanded validity area PUBLIC/REG_EU for the report generation variant is a subset (with regard to rating PUBLIC) of the expanded validity areas REG_EU and REG_WORLD for the value assignment instance). These usages are transferred to the status check. The usages PUBLIC/DE and INTERNAL/US are not taken into account by the usage check because they did not lead to the value assignment instance being selected.
The SAP System uses the usages for a data record that lead to the data record being selected to check whether the status entries for the relevant specification "are appropriate" and therefore do not permit generation. Whether the status entries are appropriate depends on the usage check that was defined for the corresponding usage record. The usage check controls whether the check is performed for the intersection, subset or superset of the expanded validity areas, or whether it is performed to check that the validity areas correspond on a 1:1 basis without being expanded.
Only if no status entry is found that forbids generation can the data record appear on the report.
Example of "appropriate" status entries:
Status entries:
- PUBLIC/DE/Released (generation permitted)
- INTERNAL/US/In process (generation not permitted)
RGV usage
- PUBLIC/DE
Value assignment usages
- PUBLIC/DE (lead to selection of data record)
- INTERNAL/US
The value assignment data is output on the report because generation for the usage PUBLIC/DE is permitted and only the usage is taken into account on the basis of which the data record was selected as valid (PUBLIC/DE). The fact that the usage INTERNAL/US (for which generation is not permitted) is additionally assigned to the value assignment data is irrelevant.
Example of effects of the usage check in status checks
The status check is dependent on the usage check:
Usage check = 0
Value assignment instance: PUBLIC/DE
The system checks
- Whether there are status entries that do not permit generation
- Whether the value assignment instance validity area that was expanded to its countries and regions is a subset of at least one of the expanded validity areas for the status entries that do not permit generation (relating to the same rating)
The data record is not output on the report for the following status entries that do not permit generation:
- PUBLIC/DE
- PUBLIC/REG_EU
- PUBLIC/REG_WORLD
Instead, the following message is output on the report:
- For specification STOFF01, value assignment type State of matter and value assignment instance 1:
- {**Status of value assignment not permitted: STOFF01, SAP_EHS_1013_001, 1**}
- For specification STOFF01, identifier category = NAM, identification type = PROD and language = English:
- {**Status of identifier not permitted: STOFF01, NAM, PROD, [E]**}
Usage check = 1
Value assignent instance: PUBLIC/DE
The system checks
- Whether there are status entries that do not permit generation
- Whether the value assignment instance validity area that was expanded to its countries and regions has at least one intersection containing values with at least one one of the expanded validity areas for the status entries that do not permit generation (relating to the same rating)
The data record is not output on the report for the following status entries that do not permit generation. A corresponding message is output instead (see above):
- PUBLIC/DE
- PUBLIC/REG_EU
- PUBLIC/REG_WORLD
- PUBLIC/DE_BW (region of DE)
Usage check = 2
Value assignment instance: PUBLIC/DE
The system checks
- Whether there are status entries that do not permit generation
- Whether the value assignment instance validity area corresponds with one of the validity areas for the status entries that do not permit generation on a 1:1 basis (relating to the same rating)
The data record is not output on the report for the following status entries that do not permit generation. A corresponding message is output instead (see above):
- PUBLIC/DE
Usage check = 3
Value assignment instance: PULBIC/DE
The system checks
- Whether there are status entries that do not permit generation
- Whether the value assignment instance validity area that was expanded to its countries and regions is a superset of at least one of the expanded validity areas for a status entry that does not permit generation (relating to the same rating)
The data record is not output on the report for the following status entries that do not permit generation. A corresponding message is output instead (see above):
- PUBLIC/DE_BW (region of DE)
- PUBLIC/DE_WEST (region of DE)
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in |
