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 | ESESTATABR |
| Short Description | Status of a document (language-dependent) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR2 | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ESI | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Status |
| Medium | 15 | Status |
| Long | 20 | Document Status |
| Heading | 4 | St. |
Documentation
Definition
This key shows the document status.
Procedure
When you create or change a document:
If a status network is defined for the document type, you can display a list of all the statuses you can set at the current processing stage, by selecting the possible entries button.
Dependencies
An indicator next to the status shows whether the current status is defined in customizing as a released status.
- If the current status is defined in customizing as a released status, you see the release date next to the status.
- If no change number is maintained, the release date is the date on which the status was set.
- If a change number is maintained, the release date is the valid-from date in the change master.
The document status abbreviation is language-dependent. The status network has the same structure in all languages.
Supplementary Documentation - ESESTATABR0001
Use
The initial status determines the status that a report has after being generated.
Procedure
Examples
Dependencies
The generation variant (SRGV) must be defined in the following way, so that a report has one of the following statuses after being generated either manually or automatically:
Status Prerequisites
RR - Manual report request
| - no indicator Manual report requests gen. automatically
| - Initial status = any
|
GS - Manual or automatic report request
| - Indicator Manual report requests gen. automatically
| - Initial status = GS
|
R1, R.. - Manual or automatic report request
| - Indicator Manual report requests gen. automatically
| - Initial status = R1, R2, R...
CO - Manual or automatic report request
| - Indicator Manual report requests gen. automatically
| - Initial status = CO
|
| Note:
| When converting status from CO -> RE, the version number of | the report is increased if you have set the
| Version requirement indicator. If there is no version
| requirement, the version remains as version V1.0.
|
RE - Manual or automatic report request
| - Indicator Manual report requests gen. automatically
| - Initial status = RE.
|
HI - Manual or automatic report request
- Indicator Manual report requests gen. automatically
- Indicator Set historical automatically.
- Initial status of newest report = RE
If a new report for the same specification, SRGV and
language is set to RE, the status of the older report
is automatically converted to status HI.
The following functions take you from a status reached to the next status:
Status Function
RR
| Generate
| => Conversion to initial status
GS
| Accept
R1
| Accept
R2,...
| Accept
CO
| Accept
|
| Note:
| the version number of the report is increased if you have set
| the Version requirement indicator. If there is no
| version requirement, the version remains as version V1.0.
|
|
RE
| Set to historical
|
| Note:
| The conversion to status HI is performed automatically if the
| the Set historical automatically indicator is set and
| a new report is subsequently generated to status RE.
|
HI
Supplementary Documentation - ESESTATABR0002
Use
Reports with release status must be accepted manually before they are versioned or finally released, until they have proceeded through all release statuses.
Procedure
Enter the release status for which you want to select the reports.
Examples
Dependencies
To enable a report to proceed through the release stages, you must enter a release status as initial status in the generation variant header.
The next status after release will be the versioning status CO only if the versioning indicator is set. Otherwise, the report is immediately assigned the status RE (released).
Supplementary Documentation - ESESTATABR0003
Use
You can only make changes to reports if they do not possess any of the following statuses:
- RR (report request)
- RE (released)
- HI (historical)
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in |
