PAPARTNER SAP (SD partner that can be used in CO-PA) Structure details
Description: SD partner that can be used in CO-PA
Structure field list including key, data, relationships and ABAP select examples
PAPARTNER is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "SD partner that can be used in CO-PA" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_PAPARTNER TYPE PAPARTNER.
The PAPARTNER table consists of various fields, each holding specific information or linking keys about SD partner that can be used in CO-PA data available in SAP. These include KUNWE (Ship-to party), KUNRE (Bill-to party), KUNRG (Payer), SPDNR (Forwarding agent).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP PAPARTNER structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
KUNWE | Ship-to party | KUNWE | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
KUNRE | Bill-to party | KUNRE | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
KUNRG | Payer | KUNRG | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
SPDNR | Forwarding agent | SPDNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
VRTNR | Sales employee | VRTNR | NUMC | 8 | PERNR | PREMV | |||
PDUMMY | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
.INCLU--AP | 0 | ||||||||
HIE01 | Customer hierarchy Level 1 | HIEZU01 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE02 | Customer hierarchy Level 2 | HIEZU02 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE03 | Customer hierarchy Level 3 | HIEZU03 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE04 | Customer hierarchy Level 4 | HIEZU04 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE05 | Customer hierarchy Level 5 | HIEZU05 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE06 | Customer hierarchy Level 6 | HIEZU06 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE07 | Customer hierarchy Level 7 | HIEZU07 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE08 | Customer hierarchy Level 8 | HIEZU08 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE09 | Customer hierarchy Level 9 | HIEZU09 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIE10 | Customer hierarchy Level 10 | HIEZU10 | CHAR | 10 | KNA1 | ALPHA | KUNNR |
Key field | Non-key field |
How do I retrieve data from SAP structure PAPARTNER using ABAP code?
As PAPARTNER is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on PAPARTNER as there is no data to select.How to access SAP table PAPARTNER
Within an ECC or HANA version of SAP you can also view further information about PAPARTNER and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects