In this blog we identify the most important SAP Human Capital Management (HCM) tables for users of:
HCM data covers the people side of your SAP system. Employee data is stored in infotypes (the PAnnnn series), organisational management is modelled through object-and-relationship tables (HRPnnnn), and payroll results are held in cluster tables. Together these tables support headcount and organisational reporting, absence and attendance dashboards, basic pay roll-ups, and payroll-to-FICO reconciliation. SAP Human Capital Management tables are found in the following SAP systems:
SuccessFactors Employee Central is a separate cloud product with its own data model and is not covered here. The on-premise HCM data model is broadly unchanged between SAP ECC and SAP S/4HANA. SAP HCM Personnel Administration InfotypesPersonnel Administration (PA) infotypes store the core employee record. Each infotype is time-sliced, with validity dates held in the BEGDA (start date) and ENDDA (end date) fields, so you can reconstruct the state of an employee record at any point in time. Every PA infotype is keyed on the personnel number (PERNR), which is the join key for building a complete employee dataset. PA0000 - Actions (Infotype 0000). Contains one row per personnel action, such as hire, transfer, promotion or termination. Key fields include PERNR, SUBTY, BEGDA and ENDDA. Reporting fields include MASSN (action type), MASSG (reason for action) and STAT2 (employment status). This is the starting point for joiner, mover and leaver analysis. PA0001 - Organisational Assignment (Infotype 0001). Contains the current and historical organisational placement of each employee. Key fields include PERNR, BEGDA and ENDDA. Reporting fields include BUKRS (company code), WERKS (personnel area), PERSG (employee group), PERSK (employee subgroup), KOSTL (cost centre), ORGEH (organisational unit) and PLANS (position). This is the primary infotype for headcount and org reporting. PA0002 - Personal Data (Infotype 0002). Contains the demographic data for each employee. Key fields include PERNR, BEGDA and ENDDA. Reporting fields include VORNA (first name), NACHN (last name), GBDAT (date of birth) and GESCH (gender). Use with caution and in line with your data privacy policies. PA0006 - Addresses (Infotype 0006). Contains one row per address type per employee (permanent, temporary, emergency, etc.). Key fields include PERNR, SUBTY (address type) and BEGDA. Useful for geographic and location-based reporting. PA0007 - Planned Working Time (Infotype 0007). Contains the work schedule rule and contracted working time for each employee. Key fields include PERNR, BEGDA and ENDDA. Reporting fields include SCHKZ (work schedule rule) and EMPCT (employment percent). Essential for full-time equivalent (FTE) calculations. PA0008 - Basic Pay (Infotype 0008). Contains the base salary and wage type assignments for each employee. Key fields include PERNR, BEGDA and ENDDA. Reporting fields include TRFAR (pay scale type), TRFGR (pay scale group), TRFST (pay scale level), BSGRD (capacity utilisation level), ANSAL (annual salary) and the LGA01 / BET01 wage type and amount pairs. This is the primary table for base pay roll-ups. PA0105 - Communications (Infotype 0105). Contains the communication identifiers held against each employee, one row per communication type. Key fields include PERNR, SUBTY and BEGDA. The USRID field often holds the employee email address or SAP user ID, depending on the SUBTY value. Useful for joining HR data to authentication and system-usage datasets. SAP HCM Time ManagementPA2001 - Absences. Contains one row per absence record, such as sickness, annual leave or unpaid leave. Key fields include PERNR, SUBTY, BEGDA and ENDDA. Reporting fields include AWART (absence type), STDAZ (absence hours) and ABWTG (absence days in calendar days). Primary source for absence and sickness dashboards. PA2002 - Attendances. Contains one row per attendance record, such as training, overtime or business trips. Key fields include PERNR, SUBTY, BEGDA and ENDDA. Structure mirrors PA2001 but is used for positive-time reporting rather than absence tracking. PA2006 - Time Quotas. Contains the leave and time-off entitlement balances for each employee. Key fields include PERNR and QUONR (quota number). Reporting fields include KTART (quota type), ANZHL (number of entitled days or hours) and KVERB (number used). Use to build leave balance and accrual reports. SAP HCM Organisational ManagementOrganisational Management (OM) in SAP HCM is modelled as a graph of objects (org units, positions, jobs, persons) linked together by relationships. The two central tables are HRP1000 and HRP1001. HRP1000 - Org Objects. Contains one row per organisational object. Key fields include PLVAR (plan variant, usually '01' for the active plan), OTYPE (object type, e.g. 'O' for org unit, 'S' for position, 'C' for job, 'P' for person), OBJID (object ID), BEGDA and ENDDA. Reporting fields include STEXT (short text). This is your master list of org objects. HRP1001 - Relationships. Contains one row per relationship between two org objects. Key fields include PLVAR, OTYPE, OBJID, RSIGN (direction 'A' or 'B'), RELAT (relationship type) and BEGDA. Reporting fields include SCLAS (related object type) and SOBID (related object ID). This is the self-joining table that builds the org structure. Use it to walk the hierarchy from position to org unit to parent org unit, and to link employees (via the P object type) to their position and cost centre. T527X - Org Unit Text. Contains language-specific descriptions for each organisational unit. Key fields include SPRSL (language) and ORGEH. Join to decode ORGEH values in PA0001 and OM reports. T528T - Position Text. Contains language-specific descriptions for each position. Key fields include SPRSL, PLANS (position) and MOLGA (country grouping). Join to decode PLANS values in PA0001. SAP HCM Payroll ResultsHCM payroll results are not stored in ordinary transparent tables. They are held in the PCL2 cluster table in binary format, grouped by cluster ID. For analytics, you should not attempt to read PCL2 directly. Instead, use the directory table HRPY_RGDIR as your entry point, along with the companion cluster tables HRPY_WPBP and HRPY_RT. Alternatively, use the standard ABAP report RPCLSTxx to unpack cluster data into a transparent structure that downstream tools can consume. PCL2 - Payroll Results Cluster. Key fields include MANDT (client), RELID (cluster ID) and SRTFD (sort field). Stores payroll and time evaluation results in binary form. Referenced here for completeness; not intended for direct extraction. HRPY_RGDIR - Payroll Directory. Key fields include MANDT, PERNR and SEQNR (sequence number). Contains one row per payroll run per employee and acts as the entry point for locating payroll results in the cluster. Use SEQNR to join to the other HRPY tables. HRPY_WPBP - Work Place / Basic Pay (from payroll cluster). Key fields include MANDT, PERNR and SEQNR. Reporting fields include BUKRS (company code), ORGEH (org unit), KOSTL (cost centre), PERSG (employee group) and PERSK (employee subgroup). Gives you the organisational and cost centre context of each payroll run, which is what you need for payroll-to-FICO reconciliation. HRPY_RT - Results Table (wage type results). Key fields include MANDT, PERNR, SEQNR and LGART (wage type). Reporting fields include BETRG (amount), ANZHL (number) and the associated time unit. This is where you pick up gross pay, deductions, tax, net pay and employer costs by wage type for payroll analytics. SAP HCM Configuration TablesConfiguration tables (also known as customising tables) hold the enterprise structure and HR code values used across the HCM module. They are small, slowly changing tables used to decode the identifiers stored in PA and OM tables. The configuration tables listed below apply to both SAP ECC and SAP S/4HANA. T001P - Personnel Subareas. Key fields include WERKS (personnel area) and BTRTL (personnel subarea). Join to PA0001 to group and decode personnel subareas in headcount and location reports. T500P - Personnel Areas. Key field PERSA. Contains the list of personnel areas defined in your system along with their address and country assignments. Join to PA0001 on the personnel area field to enrich employee records with location data. T503 - Employee Groups and Subgroups. Key fields PERSG and PERSK. Contains the employee group and subgroup combinations configured in your system (for example, active salaried employees, hourly workers, pensioners). Join to PA0001 to decode PERSG and PERSK in workforce segmentation reports. T529A - Personnel Action Types. Key field MASSN. Contains the list of personnel action types configured in your system (for example, hire, transfer, termination). Join to PA0000 on MASSN to decode action types in joiner, mover and leaver reporting. Explore SAP HCM Tables with a DVW ConnectorThe fastest way to explore SAP HCM tables is to connect directly to your SAP system from your preferred analytics platform. DVW Connectors let you browse available tables, preview fields and extract data without writing any ABAP code. All DVW products support both SAP ECC and SAP S/4HANA. To see how all 22 tables in this blog connect to each other, visit our SAP HCM Table Relationships page for an interactive data model diagram with join keys and ECC vs S/4HANA compatibility. All DVW products include a 30-day free trial with full functionality, so you can start working with these tables right away. Visit our Free Trial page to get started, or explore our Help Centre for detailed documentation on connecting to SAP HCM tables. Next StepsSee these SAP HCM tables in action. Register for a 30-day free trial and start extracting employee, organisational and payroll data from your SAP system today. Comments are closed.
|
Categories
All
Archives
May 2026
|
RSS Feed