SAP ABAP Data Element EDIUTEST (Test flag for IDoc)
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 | EDIUTEST |
| Short Description | Test flag for IDoc |
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 |
| Long | 20 | Test flag |
| Heading | 15 | Test flag |
Documentation
Use
When a message is to be sent via IDoc for test purposes, the test indicator in the partner profiles should be set. Test messages in IDoc inbound processing cannot be posted 'live'. In this case, the external system must maintain the field with 'X'.
The field is a key field in both the inbound and outbound partner profiles. The remaining key fields are the three partner values (number, type and function) and the three 'logical' message values (type, code and function). These seven fields provide a unique ID for the dependent parameters, i.e. the port in outbound processing or the process code in inbound processing.
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
