DIIHPA SAP (Partner PM/QM) Structure details
Description: Partner PM/QM
Structure field list including key, data, relationships and ABAP select examples
DIIHPA 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 "Partner PM/QM" 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_DIIHPA TYPE DIIHPA.
The DIIHPA table consists of various fields, each holding specific information or linking keys about Partner PM/QM data available in SAP. These include COUNTER (Counter for differentiation 6-digit), OBTYP (Object Category), PARVW (Partner Function), I_PARNR (Partner).. 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 DIIHPA 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 |
OBJNR | Object number | J_OBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
COUNTER | Counter for differentiation 6-digit | I_COUNT | NUMC | 6 | NUM6 | ||||
OBTYP | Object Category | J_OBTYP | CHAR | 3 | Assigned to domain | J_OBTYP | |||
PARVW | Partner Function | PARVW | CHAR | 2 | Assigned to domain | PARVW | PARVW | PAR | |
I_PARNR | Partner | I_PARNR | CHAR | 12 | ALPHA | I_PARNR | |||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
ERZEIT | Time, at Which Record Was Added | ERZEIT | TIMS | 6 | UHRZT | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
AEZEIT | Time of Change | AEZEIT | TIMS | 6 | UHRZT | ||||
AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
KZLOESCH | Delete Data Record | KZLOESCH | CHAR | 1 | CHAR1 | ||||
VTEXT | Name | VTXTK | CHAR | 20 | TEXT20 | ||||
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
NAME1 | Name 1 | AD_NAME1 | CHAR | 40 | TEXT40 | ||||
NAME2 | Name 2 | AD_NAME2 | CHAR | 40 | TEXT40 | ||||
NAME3 | Name 3 | AD_NAME3 | CHAR | 40 | TEXT40 | ||||
NAME4 | Name 4 | AD_NAME4 | CHAR | 40 | TEXT40 | ||||
CITY1 | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
CITY2 | District | AD_CITY2 | CHAR | 40 | TEXT40 | CITY_PART | |||
POST_CODE1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
POST_CODE2 | PO Box Postal Code | AD_PSTCD2 | CHAR | 10 | CHAR10 | ||||
COUNTRY | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND | ||
REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | T005S | REGIO | |||
STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
PO_BOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
LANGU | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
TEL_NUMBER | First telephone no.: dialling code+number | AD_TLNMBR1 | CHAR | 30 | CHAR30 | ||||
FAX_NUMBER | First fax no.: dialling code+number | AD_FXNMBR1 | CHAR | 30 | CHAR30 | ||||
TLX_NUMBER | Telex number | AD_TLXNMBR | CHAR | 30 | TEXT30 | ||||
TTX_NUMBER | Teletex number | AD_TTXNMBR | CHAR | 30 | TEXT30 | ||||
SORT1 | Search Term 1 | AD_SORT1 | CHAR | 20 | CHAR20 | ||||
NAME_LIST | Name for list displays | I_NAME_LST | CHAR | 35 | NAME | ||||
REMARK | Address notes | AD_REMARK1 | CHAR | 50 | TEXT50 | ||||
TZONSP | Time Zone for Partner | TZONSP | CHAR | 6 | TTZZ | TZNZONE | |||
DATUM | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
UZEIT | System Time | SYUZEIT | TIMS | 6 | SYTIME | ||||
HOUSE_NUM1 | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
TITLE | Title text | AD_TITLETX | CHAR | 30 | TEXT30 | ||||
DEPARTMENT | Department | AD_DPRTMNT | CHAR | 40 | TEXT40 | ||||
FUNCTION | Function | AD_FNCTN | CHAR | 40 | TEXT40 | ||||
NICKNAME | Nickname or name used | AD_NICKNAM | CHAR | 40 | TEXT40 | ||||
SEX | Gender key | AD_SEX | CHAR | 1 | AD_SEX | ||||
PAFKT | Contact person function | PAFKT | CHAR | 2 | Assigned to domain | PAFKT | |||
PARVO | Partner's Authority | PARVO | CHAR | 1 | Assigned to domain | PARVO | |||
PAVIP | VIP Partner | PAVIP | CHAR | 1 | Assigned to domain | PAVIP | |||
GBDAT | Date of Birth | GBDAT | DATS | 8 | PDATE | GBDAT | |||
FAMST | Marital Status Key | FAMST | CHAR | 1 | Assigned to domain | FAMST | |||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
ADRNR | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR |
Key field | Non-key field |
How do I retrieve data from SAP structure DIIHPA using ABAP code?
As DIIHPA 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 DIIHPA as there is no data to select.How to access SAP table DIIHPA
Within an ECC or HANA version of SAP you can also view further information about DIIHPA 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