PERSON SAP (Standard Selection of Persons for Manpower Planning) Structure details
Description: Standard Selection of Persons for Manpower Planning
Structure field list including key, data, relationships and ABAP select examples
PERSON 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 "Standard Selection of Persons for Manpower Planning" 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_PERSON TYPE PERSON.
The PERSON table consists of various fields, each holding specific information or linking keys about Standard Selection of Persons for Manpower Planning data available in SAP. These include OTYPE (Object Type), BEGDA (Start Date), ENDDA (End Date), STATUS (Employment Status).. 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)
SAP PERSON 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 |
| PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
| OTYPE | Object Type | OTYPE | CHAR | 2 | T778O | OTYPE | POT | ||
| BEGDA | Start Date | BEGDA | DATS | 8 | DATUM | ||||
| ENDDA | End Date | ENDDA | DATS | 8 | DATUM | ||||
| STATUS | Employment Status | STAT2 | CHAR | 1 | STATA | ||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| WERKS | Personnel Area | PERSA | CHAR | 4 | Assigned to domain | PERSA | PBR | ||
| PERSG | Employee Group | PERSG | CHAR | 1 | Assigned to domain | PERSG | PRG | ||
| PERSK | Employee Subgroup | PERSK | CHAR | 2 | Assigned to domain | PERSK | PKR | ||
| KOKRS | Controlling Area | KOKRS | CHAR | 4 | TKA01 | CACCD | CAC | ||
| KOSTL | Cost Center | KOSTL | CHAR | 10 | CSKS | ALPHA | KOSTL | KOS | |
| ORGEH | Organizational Unit | ORGEH | NUMC | 8 | Assigned to domain | ORGEH | |||
| ORGEH_TXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
| PLANS | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
| PLANS_TXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
| STELL | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
| STELL_TXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
| ANRED | Form-of-Address Key | ANRDE | CHAR | 1 | Assigned to domain | ANRDE | |||
| ENAME | Formatted Name of Employee or Applicant | EMNAM | CHAR | 40 | TEXT40 | ||||
| NACHN | Last Name | NACHN | CHAR | 25 | NACHN | ||||
| VORNA | First Name | VORNA | CHAR | 25 | VORNM | ||||
| TITEL | Title | TITEL | CHAR | 15 | Assigned to domain | TITEL | |||
| GESCH | Gender Key | GESCH | CHAR | 1 | GESCH | ||||
| GBDAT | Date of Birth | GBDAT | DATS | 8 | PDATE | GBDAT | |||
| NATIO | Nationality | NATSL | CHAR | 3 | T005 | LAND1 | NAT | ||
| KONFE | Religious Denomination Key | KONFE | CHAR | 2 | Assigned to domain | KONFE | |||
| FAMST | Marital Status Key | FAMST | CHAR | 1 | Assigned to domain | FAMST | |||
| PSTLZ | Postal code | PSTLZ_BAS | CHAR | 10 | PSTLZ | ||||
| ORT01 | City | ORT01 | CHAR | 25 | TEXT25 | ||||
| STRAS | House number and street | STRAS | CHAR | 30 | TEXT30 | ||||
| LAND | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND | ||
| TELNR | Telephone Number | TELNR | CHAR | 14 | TELNR | ||||
| USRTY | Communication Type | USRTY | CHAR | 4 | Assigned to domain | SUBTY_591A | |||
| SYSID | Communication Identification/Number | SYSID | CHAR | 30 | CHAR30 | ||||
| .INCLU--AP | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PERSON using ABAP code?
As PERSON 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 PERSON as there is no data to select.How to access SAP table PERSON
Within an ECC or HANA version of SAP you can also view further information about PERSON 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