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_SNDPRN |
| 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 | EDI_PARNUM | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | EDPP1 |
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 | Partn.no. |
| Medium | 15 | Sender |
| Long | 20 | Sender partner no. |
| Heading | 15 | Partner number |
Documentation
General
The field contains the partner number of the sender. The partner number and the partner type uniquely identify the sender.
The partner number can be alphanumeric and is a mandatory field.
Applications
Outbound IDocs:
The application is identified in this field by its organizational structure (for example, 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 identification of the partner profile of the subsystem.
Inbound IDocs:
The EDI subsystem must fill the field SNDPRN from the information on the sender ID in the interchange file. This includes, for example, the sender address, routing address, etc.
The field must be filled to determine the partner profile in the SAP System.
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
