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_SNDPT3 |
| 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 | CHAR2 | |
| 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 | 19 | Sender partner type |
| Long | 24 | Partner type of sender |
| Heading | 24 | Partner type of sender |
Documentation
General
This field contains the partner type of the sender which defines the business relationship between the sender and recipient. A list of the available partner types is provided in the TEDST table. SNDPRT must be filled.
SNDPRT and SNDPRN identify the sender uniquely.
Applications
Outbound IDocs:
The application is identified in this field by means of its application code (e.g. MM, SD etc.).
Inbound IDocs:
The field contains the partner type of the business partner.
IDoc interface
The system checks whether the field is filled and whether the value exists.
EDI subsystem
Outbound IDocs:
The field is part of the partner profile identification in the subsystem.
Inbound IDocs:
The EDI subsystem must fill the SNDPRT 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 determined.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
