Hierarchy

⤷

⤷

Basic Data
Data Element | GLE_DTE_ECS_RUNID_EXT |
Short Description | Versioned Run ID |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | GLE_ECS_RUNID_EXT | |
Data Type | CHAR | Character String |
Length | 12 | |
Decimal Places | 0 | |
Output Length | 12 | |
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 | Ext.Run ID |
Medium | 18 | External Run ID |
Long | 37 | External Run ID |
Heading | 18 | External Run ID |
Documentation
Definition
Identifies an ECS posting run.
Use
The external run ID comprises the following:
- An unversioned run ID that contains 8 alphanumeric characters
- A 4-digit run version
You can enter the run ID. If you do not specify the version of the run, the system uses the next free number that is greater than 0000 as the run version.
The system uses the external run ID to find the application log and the auto correction trace for the posting run.
Dependencies
You can start posting runs as background jobs. In this case, you have to enter the run ID and the run version. This makes sure that the system can identify the run if the run needs to be restarted.
You can start an ECS run by calling the Batch Input Documents report or the Error Correction and Suspense Accounting (ECS) - Direct Input report.
In the Batch Input Documents report, you have to choose Error Correction and Suspense Accounting (ECS) - Direct Input for the type of data transfer in question.
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 600 |