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_SNDPN3 |
| Short Description | Partner Number of Sender |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Sender no. |
| Medium | 15 | Sender number |
| Long | 27 | Partner Number of Sender |
| Heading | 27 | Partner Number of Sender |
Documentation
General
This field contains the partner number of the sender. The partner number and partner type identify the sender uniquely.
The partner number can be alphanumeric and must be filled for processing.
Applications
Outbound IDocs:
The application is identified in this field by means of its organization structure (e.g. the sales organization '0001').
Inbound IDocs:
The field contains the partner number of the business partner.
IDoc interface
Outbound IDocs:
No action required.
Inbound IDocs:
The field is used to determine the partner profile.
EDI subsystem
Outbound IDocs:
The field is part of the partner profile identification in the subsystem.
Inbound IDocs:
The EDI subsystem must fill the SNDPRN field. The information on the sender ID in the interchange file is used for this purpose. This information includes the sender address, forwarding address etc.
The field must be filled so that the partner profile in SAP can be found.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
