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_SNDPRT |
| Short Description | Partner type of sender |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_PARTYP | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Partn.Type |
| Medium | 15 | Sender type |
| Long | 20 | Sender partner type |
| Heading | 10 | Partn.Type |
Documentation
General
This field contains the partner type of the sender, which defines the commercial relationship between the sender and receiver. The partner types possible can be found in table TEDST. SNDPRT is a mandatory field.
SNDPRT and SNDPRN identify the sender uniquely.
Applications
Outbound IDocs:
The application is identified in this field by its application code (for example, MM, SD, etc.).
Inbound IDocs:
The field contains the partner type of the business partner.
IDoc interface
It checks whether the field is filled and the value exists.
EDI subsystem
Outbound IDocs:
The field is part of the ID of the partner profile of the subsystem.
Inbound IDocs:
The EDI subsystem must fill the field SNDPRT. It uses the information on the sender ID in the interchange file. This includes, for example, the sender address, the routing address, etc.
The field must be filled to determine the partner profile in the SAP System.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
