Hierarchy
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
Data Element | EDI_FILSTA |
Short Description | File name for status records |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EDI_FILENA | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | File |
Medium | 15 | Status file |
Long | 20 | Status file name |
Heading | 20 | Status file name |
Documentation
Use
Here you can specify a fixed name for the file, in which the status records from external systems (for example EDI subsystem) are transferred. SAP however recommends that the external system starts the status processing in the SAP system and notifies what the transferred file is called (Parameter from startrfc). In this case the field is ignored.
In general SAP recommends using dynamic file names, that is to say variable file names generated at runtime, in order to prevent the overwriting of non-processed files.
Dependencies
When you have entered the existing file port in the tab page Test in IDoc administration, the settings for inbound, outbound and status files are copied as default values in the test programs. When testing it is sensible to use fixed file names.
History
Last changed by/on | SAP | 19970221 |
SAP Release Created in |