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_TEST3 |
| Short Description | Test flag |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 flag |
| Medium | 16 | Test flag |
| Long | 20 | Test flag |
| Heading | 16 | Test flag |
Documentation
General
This field contains the indicator that specifies whether the EDI message that corresponds to the IDoc is a test message.
Applications
Outbound IDocs:
The selection module of the application receives the data via the PARTOUT (partner profile) parameter.
Inbound IDocs:
The posting module of the application must check whether an IDoc contains the test indicator. In this case, a 'productive' posting must not take place.
IDoc interface
Outgoing IDocs:
No action required.
Inbound IDocs:
The field is used to determine the inbound partner profile.
EDI subsystem
Outgoing IDocs:
The EDI subsystem is responsible for marking the generated EDI message as a test or productive message in accordance with this field.
Inbound IDocs:
The EDI subsystem must mark test messages by means of an 'X' in this field. The field must be filled so that the partner profile in SAP can be determined.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
