SAP ABAP Data Element EDI4SNDPRN (Partner Number of Sender)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-ALE (Application Component) ALE Integration Technology
⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
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 | EDI4SNDPRN |
| 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 | Sender |
| Medium | 15 | Sender |
| Long | 20 | Sender partner no. |
| Heading | 15 | Partner number |
Documentation
Use
Inbound processing (from SAP):
This field must contain the partner number of the sender, as entered in the SAP master data (via internal number assignment).
SNDPFC, SNDPRN and SNDPRT serve as a unique ID for the sender. They are assigned to the corresponding key fields of the (inbound) partner profile, which is used to determine the process code, and therefore the internal SAP processing. The external system must enter the 'appropriate' number in the field.
The sender is the SAP system. The value '<SID>CLNT<CLNT>' is entered in the field, e.g. C11CLNT003 for system C11, client 003.
History
| Last changed by/on | SAP | 19980116 |
| SAP Release Created in |
