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_SNDLAD |
| Short Description | Logical address of sender |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_LOGADR | |
| Data Type | CHAR | Character String |
| Length | 70 | |
| Decimal Places | 0 | |
| Output Length | 70 | |
| 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 | Log.addr. |
| Medium | 15 | Sender |
| Long | 0 | |
| Heading | 32 | Logical address of sender |
Documentation
Use
The logical sender address can be used for confirmations for IDocs received from an SAP system. The EDI partners must then agree on these logical addresses. The confirmations are like wise sent by IDoc.
The logical address of the internal organization is allocated by the sender. Choose Control -> Forward inbound from the initial screen of the IDoc interface. The table EDILOGADR maintained here must be analyzed by the application, so that inbound confirmations can be forwarded correspondingly.
IDoc interface
No action required.
EDI subsystem
Outbound IDocs:
No action required.
Inbound IDocs:
The EDI subsystem determines the logical address from the sender information in the interchange file and fills the field.
Example:
For the EDI standard EDIFACT, the logical address can be a combination of the sender address in the header segment UNB and the routing address in the UNG segment.
In the case of the EDI standard ANSI X.12, the logical address can be derived from the segments ISA and GS.
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
