PEOPLE_KEY SAP (OM: Overview Structure for Buffer_key of People List) Structure details
Description: OM: Overview Structure for Buffer_key of People List
Structure field list including key, data, relationships and ABAP select examples
PEOPLE_KEY 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 "OM: Overview Structure for Buffer_key of People List" 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_PEOPLE_KEY TYPE PEOPLE_KEY.
The PEOPLE_KEY table consists of various fields, each holding specific information or linking keys about OM: Overview Structure for Buffer_key of People List data available in SAP. These include STARTOBJEC (), PLVAR (Plan Version), OTYPE (Object Type), OBJID (Object ID).. 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: Not classified
SAP PEOPLE_KEY 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 |
HANDLE | 0 | ||||||||
STARTOBJEC | 0 | ||||||||
PLVAR | Plan Version | PLVAR | CHAR | 2 | PLVAR | POP | |||
OTYPE | Object Type | OTYPE | CHAR | 2 | OTYPE | POT | |||
OBJID | Object ID | PD_OBJID_R | NUMC | 8 | NUM08 | PON | |||
BEGDA | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
ENDDA | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
ISTAT | Planning Status | ISTAT_D | CHAR | 1 | ISTAT | PST | |||
HISTO | Historical Record Flag | HISTO | CHAR | 1 | CHAR1 | ||||
SHORT | Object Abbreviation | SHORT_D | CHAR | 12 | TEXT12 | ||||
STEXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
REALO | Extended Object ID | REALO | CHAR | 45 | CHAR45 | ||||
PLVAR | Plan Version | PLVAR | CHAR | 2 | Assigned to domain | PLVAR | POP | ||
OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
OBJID | Object ID | PD_OBJID_R | NUMC | 8 | NUM08 | PON | |||
C_OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
C_OBJID | Object ID | PD_OBJID_R | NUMC | 8 | NUM08 | PON | |||
KEYDATE | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
BEGDA | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
ENDDA | End Date | ENDDATUM | DATS | 8 | DATUM | END |
Key field | Non-key field |
How do I retrieve data from SAP structure PEOPLE_KEY using ABAP code?
As PEOPLE_KEY 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 PEOPLE_KEY as there is no data to select.How to access SAP table PEOPLE_KEY
Within an ECC or HANA version of SAP you can also view further information about PEOPLE_KEY 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