Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ALE (Application Component) ALE Integration Technology⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
| Data Element | EDI_ENDUNG |
| Short Description | Suffix for File for Ending Identification |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_CHAR6SEN | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| 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 | 6 | Ending |
| Medium | 6 | Ending |
| Long | 6 | Ending |
| Heading | 6 | Ending |
Documentation
Definition
If you want to generate a handshake file instead of starting a shell script, then this additional handshake file is given the name of the source file created, plus the ending entered in this field.
The default is: '.ready', but it can be overwritten.
Use
You can use the handshake file if you do not wish to start any further script from the SAP system and you want to determine the output IDoc files through a regular check of the output directory (polling).
Dependencies
Example
The output file created is called: '/usr/sap/4711'
If this file is complete and trigering is to take place by means of a handshake file, the empty file '/usr/sap/4711.ready' is created - provided the character string '.ready' has been defined as ending.
If the file '/usr/sap/4711.ready' exists, then you can be sure that the file '/usr/sap/4711' is fully filled with data and can be processed by the subsystem.
In this case, the subsystem should delete both files after processing.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 703 |
