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 | ESEESNTFLG |
| Short Description | Relevant Change Has Been Made |
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 | REL_IND | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Relevant |
| Medium | 15 | Relevant |
| Long | 20 | Relevant |
| Heading | 1 | R |
Documentation
Definition
Specifies that a relevant change has been made. The Relevant indicator can be set in the usage of an identifier or of a value assignment.
Use
The relevance indicator is taken into account for both manually and automatically generated reports and has the following functions:
- Relevant data changes are marked in the margin of the page when you print the report, if you have set the Change Marks indicator in the generation variant.
- Report bodies resulting from a relevant data change contain the Relevant indicator in the report header. It serves as the default value for version creation. You can deselect the indicator in the report header manually.
The SAP system automatically resets the relevance indicator when the value assignment is changed again. If required, you must set it again manually.
Dependencies
In version creation, the default value specifies:
- Whether the number of the main version of a report body is incremented due to a relevant change
- Whether the number of the sub-version of a report body is incremented due to a change of lesser importance
During version creation, you can manually change the default value.
Note:
A change to a data record is made within a day-long time window (accurate to one day). The determination of relevance and change marking is therefore also exact only to one day.
If the last change date of a data record is the same as or newer than the date of generation of the last report version, the system always interprets this as a change and creates a new main version or sub-version, depending on whether the change is relevant or not. In this way, no changes are overlooked, as owing to the fact that changes can be pinpointed only to one day, the system cannot decide whether the content of the data record has changed within that one day (before or after the last report generation).
To avoid unwanted main versions being created and to avoid any unnecessary subsequent shipping, we recommend you use either automatic worklist generation or generate the report manually on the day after the change.
Example:
The following example shows versioning as determined to be accurate to one day:
- 02/26/2003 Report generated manually: Version 1.0
- 02/27/2003 Relevant change to a value assignment
- 02/27/2003 New report generated manually: Version 2.0
- 03/04/2003 Report generated manually again: Version 3.0
- 03/04/2003 Report generated manually again: Version 3.1
On 02/27/2003, the report was given a new main version because the last generation date is the same as the change date. On 03/04/2003, the report was given another new main version because the system views this as the actual report generation. As no other relevant changes followed, the report was given a new sub-version in the second report generation on 03/04/2003.
For more information, see the SAP Library:
- For the Basic Data and Tools component under Relevance Indicator and Change Marking
- For the Product Safety component under Report Versioning
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
