SAP PARTNER_IDENTIFICATION Proxy Structure (generated) Table data and field list

PARTNER_IDENTIFICATION 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 "Proxy Structure (generated)" 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_PARTNER_IDENTIFICATION TYPE PARTNER_IDENTIFICATION.

The PARTNER_IDENTIFICATION table consists of various fields, each holding specific information or linking keys about Proxy Structure (generated) data available in SAP. These include TASK_CODE (Change Indicator Role (I = Insert, D=Delete etc. )), IDENTIFICATION_DATA_KEY (), CONTROLLER (), IDENTIFICATION_CATEGORY_CODE ()... 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. .

PARTNER_IDENTIFICATION structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can Be Enhanced (Deep)


SAP PARTNER_IDENTIFICATION structure fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the PARTNER_IDENTIFICATION table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
CONTROLLER 0
TASK_CODEChange Indicator Role (I = Insert, D=Delete etc. ) PARTY_TASK_CODECHAR1
IDENTIFICATION_DATA_KEY 0
CONTROLLER 0
IDENTIFICATION_CATEGORY_CODE 0
PARTNER_ID 0
IDENTIFICATION_DATA 0
CONTROLLER 0
IDAGENCY_NAME 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEObject name within business partner data PARTY_NAME_CONTENTCHAR40
IDENTRY_DATE 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEProxy Data Element (Generated) GDT_DATEDATS8
IDVALIDITY_START_DATE 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEProxy Data Element (Generated) GDT_DATEDATS8
IDVALIDITY_END_DATE 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEProxy Data Element (Generated) GDT_DATEDATS8
IDVALID_COUNTRY_CODE 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEProxy Data Element (Generated) GDT_COUNTRY_CODECHAR3
IDVALID_COUNTRY_ISOCODE 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEProxy Data Element (Generated) GDT_COUNTRY_CODECHAR3
IDVALID_REGION_CODE 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUECode for a region name PARTY_REGION_CODE_CONTENTCHAR3

Key field Non-key field



How do I retrieve data from SAP structure PARTNER_IDENTIFICATION using ABAP code?

As PARTNER_IDENTIFICATION 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 PARTNER_IDENTIFICATION as there is no data to select.

How to access SAP table PARTNER_IDENTIFICATION

Within an ECC or HANA version of SAP you can also view further information about PARTNER_IDENTIFICATION and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).