SAP ABAP Data Element EDI4TEST (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 | EDI4TEST |
| 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
If a message is to be sent via IDoc for test purposes, the test indicator should be set in the partner profiles. Test messages in IDoc inbound processing cannot be posted 'live'. The external system must therefore enter 'X' in the field.
The field is a key field in the partner profile for both inbound and outbound processing. The remaining key fields are the partner values (number, type and function) and the "logical" message values (type, code and function). These 7 fields determine the dependent parameters: the port in outbound processing or the process code in inbound processing.
History
| Last changed by/on | SAP | 19980202 |
| SAP Release Created in |
