PMID1 SAP (HR-ID:Structure for usage in feature IDPEN) Structure details
Description: HR-ID:Structure for usage in feature IDPEN
Structure field list including key, data, relationships and ABAP select examples
PMID1 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 "HR-ID:Structure for usage in feature IDPEN" 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_PMID1 TYPE PMID1.
The PMID1 table consists of various fields, each holding specific information or linking keys about HR-ID:Structure for usage in feature IDPEN data available in SAP. These include STAT2 (Employment Status), PERNR (Personnel Number), BUKRS (Company Code), WERKS (Personnel Area).. 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 PMID1 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 |
MOLGA | Country Grouping | MOLGA | CHAR | 2 | T500L | MOLGA | MOL | ||
STAT2 | Employment Status | STAT2 | CHAR | 1 | STATA | ||||
PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
WERKS | Personnel Area | PERSA | CHAR | 4 | T500P | PERSA | PBR | ||
PERSG | Employee Group | PERSG | CHAR | 1 | T501 | PERSG | PRG | ||
PERSK | Employee Subgroup | PERSK | CHAR | 2 | T503K | PERSK | PKR | ||
VDSK1 | Organizational Key | VDSK1 | CHAR | 14 | T527O | VDSK1 | |||
GSBER | Business Area | GSBER | CHAR | 4 | TGSB | GSBER | GSB | ||
BTRTL | Personnel Subarea | BTRTL | CHAR | 4 | T001P | BTRTL | PBS | ||
JUPER | Legal Person | JUPER | CHAR | 4 | JUPER | ||||
ABKRS | Payroll Area | ABKRS | CHAR | 2 | T549A | ABKRS | ABK | ||
ANSVH | Work Contract | ANSVH | CHAR | 2 | T542A | ANSVH | |||
KOSTL | Cost Center | KOSTL | CHAR | 10 | CSKS | ALPHA | KOSTL | KOS | |
ORGEH | Organizational Unit | ORGEH | NUMC | 8 | T527X | ORGEH | |||
PLANS | Position | PLANS | NUMC | 8 | T528B | PLANS | |||
STELL | Job | STELL | NUMC | 8 | T513 | STELL | |||
MSTBR | Supervisor Area | MSTBR | CHAR | 8 | MSTBR | ||||
SACHA | Payroll Administrator | SACHA | CHAR | 3 | T526 | SACHA | |||
SACHP | Administrator for HR Master Data | SACHP | CHAR | 3 | T526 | SACHA | |||
SACHZ | Administrator for Time Recording | SACHZ | CHAR | 3 | T526 | SACHA | |||
SNAME | Employee's Name (Sortable by LAST NAME FIRST NAME) | SMNAM | CHAR | 30 | CHAR30 | ||||
ENAME | Formatted Name of Employee or Applicant | EMNAM | CHAR | 40 | TEXT40 | ||||
OTYPE | Object Type | OTYPE | CHAR | 2 | T778O | OTYPE | POT | ||
SBMOD | Administrator Group | SBMOD | CHAR | 4 | CHAR4 | SGR | |||
KOKRS | Controlling Area | KOKRS | CHAR | 4 | TKA01 | CACCD | CAC | ||
FISTL | Funds Center | FISTL | CHAR | 16 | Assigned to domain | FISTL | FIS | ||
GEBER | Fund | BP_GEBER | CHAR | 10 | Assigned to domain | BP_GEBER | FIC | ||
FKBER | Functional Area | FKBER | CHAR | 16 | Assigned to domain | FKBER | FBE | ||
GRANT_NBR | Grant | GM_GRANT_NBR | CHAR | 20 | ALPHA | GM_GRANT_NBR | GM_GRANT_NBR | GRANTS_GENERIC | |
SGMNT | Segment for Segmental Reporting | FB_SEGMENT | CHAR | 10 | Assigned to domain | ALPHA | FB_SEGMENT | ||
BUDGET_PD | FM: Budget Period | FM_BUDGET_PERIOD | CHAR | 10 | Assigned to domain | FM_BUDGET_PERIOD | BUDPER |
Key field | Non-key field |
How do I retrieve data from SAP structure PMID1 using ABAP code?
As PMID1 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 PMID1 as there is no data to select.How to access SAP table PMID1
Within an ECC or HANA version of SAP you can also view further information about PMID1 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