SAP ABAP Data Element EDIPTEST (Flag for test mode)
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 | EDIPTEST |
| Short Description | Flag for test mode |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_FLAG | |
| 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 | 4 | Test |
| Medium | 4 | Test |
| Long | 4 | Test |
| Heading | 0 |
Documentation
Use
If a message is to be sent via IDoc for test purposes, the test flag in the partner profiles should be set. Test messages cannot be posted 'live' in IDoc inbound processing. 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 three partner values (number, type and function) and the three "logical" message values (type, code and function). These seven fields therefore determine the dependent parameters, e.g. the port in outbound processing or the process code in inbound processing.
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
