Employee Master Data Consistency Check Before Payroll Report
Short answer: A custom ALV report that shows, before the payroll run, missing mandatory infotypes, gaps in the organizational assignment, overlapping actions on the same day and payroll status (infotype 0003) inconsistencies for active and recently terminated employees in one list. Payroll errors and the need for recalculation are caught before the payroll runs.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
PA20 shows one employee; inconsistent actions or missing infotypes are usually noticed when the payroll driver (PC00_M99_CALC) fails. PU03 corrects the payroll status one by one but does not list which employees need it. There is no single list that lets teams check the whole population before the payroll cutoff.
Who uses it? Payroll specialists, personnel master data owners and HCM consultants.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| PA0000HR Master Record: Infotype 0000 (Actions) | Actions: action type, reason, employment status, sequence number (driving table) | — | ECC + S/4 |
| PA0001HR Master Record: Infotype 0001 (Organizational Assignment) | Organizational assignment: company code, personnel area, payroll area, cost center, name | PA0001-PERNR = PA0000-PERNR | ECC + S/4 |
| PA0003HR Master Record: Infotype 0003 (Payroll Status) | Payroll status: payroll lock, accounted-to date, earliest retro date | PA0003-PERNR = PA0000-PERNR | ECC + S/4 |
| PA0002HR Master Record: Infotype 0002 (Personal Data) | Existence of the personal data record | PA0002-PERNR = PA0000-PERNR | ECC + S/4 |
| PA0007HR Master Record: Infotype 0007 (Planned Working Time) | Existence of the planned working time record | PA0007-PERNR = PA0000-PERNR | ECC + S/4 |
| PA0008HR Master Record: Infotype 0008 (Basic Pay) | Existence of the basic pay record | PA0008-PERNR = PA0000-PERNR | ECC + S/4 |
| PA0009HR Master Record: Infotype 0009 (Bank Details) | Existence of the bank details record | PA0009-PERNR = PA0000-PERNR | ECC + S/4 |
| T001PPersonnel Area/Subarea | Country grouping of the personnel area/subarea | T001P-WERKS = PA0001-WERKS AND T001P-BTRTL = PA0001-BTRTL | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_ABKRS | Payroll area | Range / multiple | PA0001-ABKRS | Yes | TM |
| S_BUKRS | Company code | Range / multiple | PA0001-BUKRS | No | 1000 |
| S_WERKS | Personnel area | Range / multiple | PA0001-WERKS | No | IST1 |
| S_PERNR | Personnel number | Range / multiple | PA0000-PERNR | No | 00001024 |
| P_KEYDT | Key date (default: period end) | Single value | SY-DATUM | Yes | 30.11.2026 |
| P_CHKIT | Check missing infotypes | Checkbox | — | No | X |
| P_CHKACT | Check actions and organizational assignment | Checkbox | — | No | X |
| P_CHKPAY | Check payroll status (IT0003) | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Pers. no. | PA0000-PERNR |
| 2 | Name | PA0001-ENAME |
| 3 | Personnel area | PA0001-WERKS |
| 4 | Payroll area | PA0001-ABKRS |
| 5 | Employment status | PA0000-STAT2 |
| 6 | Action | PA0000-MASSN |
| 7 | Action start | PA0000-BEGDA |
| 8 | Accounted to | PA0003-ABRDT |
| 9 | Check code | Calculated Check group and number (e.g. IT-01, ORG-02, PAY-03) |
| 10 | Infotype | Calculated Infotype the finding refers to |
| 11 | Finding | Calculated Description from the check rule |
| 12 | Severity | Calculated Stops payroll: error; may affect the result: warning |
Sample output
| Pers. no. | Name | Personnel area | Payroll area | Employment status | Action | Action start | Accounted to | Check code | Infotype | Finding | Severity |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 00001302 | Ozan Tekin | IST1 | TM | 3 | 01 | 11/03/2026 | 10/31/2026 | IT-01 | 0009 | No bank details valid on the key date | Error |
| 00001288 | Selin Arı | IST1 | TM | 3 | 01 | 09/15/2026 | 10/31/2026 | PAY-02 | 0003 | Hire date before accounted-to date; September may not be calculated | Warning |
| 00001140 | Burak Şen | ANK1 | TM | 0 | 10 | 11/01/2026 | 09/30/2026 | PAY-03 | 0003 | Leaving date passed, October payroll not completed | Error |
| 00001255 | Ceren Uçar | ANK1 | 3 | 02 | 11/01/2026 | 10/31/2026 | ORG-01 | 0001 | Payroll area blank in the organizational assignment | Error |
How does the report work?
- For the selected payroll area and company code, PA0000 and PA0001 records valid on the key date are read; employees with an active employment status (STAT2) and those who left in the selected period are included.
- Missing infotype check: for active employees a PA0002, PA0007, PA0008 and PA0009 record valid on the key date is required; missing ones are reported as ‘mandatory infotype missing’.
- Organizational assignment check: PA0001 records with a blank payroll area or cost center and date gaps between hire date and today; an error if the personnel area/subarea has no country grouping (MOLGA) in T001P.
- Action check: more than one action with the same start date in PA0000 (SEQNR > 0) and an active status again after a leaving action.
- Payroll status check: PA0003 records with the payroll lock (ABRSP) set; new hires whose hire date is before the accounted-to date (ABRDT), meaning a past period may not be calculated; leavers whose leaving date has passed but whose accounted-to date is still before it. Each finding is listed with a check code, description and severity.
Performance notes
Read all infotypes in one go with the personnel number list and a key date filter; a direct selection is much faster than using a logical database. The report can run as a background job one day before the payroll cutoff.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking a line opens the relevant infotype in PA20.
- Export to Excel
- Runs as a background job
- Send the result by email Can be sent to master data owners per personnel area before the payroll cutoff.
Authorization objects
- P_ORGINRead authorization for infotypes 0000, 0001, 0002, 0003, 0007, 0008, 0009
- P_ABAPSimplified authorization check for the report (optional)
Frequently asked questions
Can the check list be extended?
Yes. Checks are designed like a rule table; country-specific infotypes (for example tax and social insurance data) or company-specific rules can be added as extra checks.
Does the report correct the data?
No, it only reads. Corrections are made by an authorized user in PA30 or PU03; you can jump to the relevant transaction from a line.
Does it run on S/4HANA?
Yes. HCM on S/4HANA (including H4S4) uses the same PA infotype tables, so the report runs unchanged.
Related reports
Employee Bank Details Changed Since Last Payroll Report
A custom ALV control report that lists employees whose bank details (infotype 0009) were created or changed after the last payroll run or within a …
Employees Missing Cost Center or Organizational Assignment Report
A custom ALV check report that finds, before payroll runs, active employees with an empty or invalid cost center, assignments left on the default …
Payroll Wage Type Period Comparison and Variance Report
A custom ALV report that compares the payroll results of one period with the previous period per employee and wage type, and lists variances above a …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.