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_SNDLA3 |
| 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 | CHAR70 | |
| 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 | SenderAddr |
| Medium | 19 | Sender log.address |
| Long | 30 | Logical address of sender |
| Heading | 30 | Logical address of sender |
Documentation
General
The logical addresses must be defined between the EDI partners and are used to forward IDocs within the SAP application system.
Applications
Outbound IDocs:
No action required.
Inbound IDocs:
The logical sender address can be used for confirmation replies between SAP systems.
The logical address is assigned to the internal organization via the EDI interface, EDILOGADR table.
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 then fills the field.
Example:
The logical address for the EDI standard EDIFACT can be a combination of the sender address in the header segment UNB and the forwarding address in the UNG segment.
The logical address for the EDI standard ANSI X12 can be derived from the ISA and GS segments.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
