SAP ABAP Data Element EDI_TEST (Test Flag)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-ALE (Application Component) ALE Integration Technology
⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
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_TEST |
| Short Description | Test Flag |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_TEST | |
| 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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Test |
| Medium | 15 | Test Flag |
| Long | 20 | Test Flag |
| Heading | 4 | Test |
Documentation
Use
Like the logical message, the indicator belongs to the key fields in partner profiles. Thus in inbound processing for example, you can control separately whether IDocs are posted for test or productive purposes: Define via the process codes two different processing procedures for set and non-set indicators.
Applications
IDocoutbound
The application selection module receives the data via the parameter PARTOUT (partner profile).
EDI subsystem
IDoc outbound
The EDI subsystem must make sure that the EDI message generated is flagged as a test or productive message depending on the field.
IDoc inbound
The EDI subsystem must identify test messages by an 'X' in the field. The field must be filled to determine the correct partner profile in the SAP System.
Input values
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
