HCM Report Custom development ALV report

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

  • PA20 Display HR Master Data. Shows the infotypes of one employee; does no consistency check across the population.
  • PU03 Change Payroll Status. Changes the payroll status one by one; does not list employees that need correction.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
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, namePA0001-PERNR = PA0000-PERNRECC + S/4
PA0003HR Master Record: Infotype 0003 (Payroll Status)Payroll status: payroll lock, accounted-to date, earliest retro datePA0003-PERNR = PA0000-PERNRECC + S/4
PA0002HR Master Record: Infotype 0002 (Personal Data)Existence of the personal data recordPA0002-PERNR = PA0000-PERNRECC + S/4
PA0007HR Master Record: Infotype 0007 (Planned Working Time)Existence of the planned working time recordPA0007-PERNR = PA0000-PERNRECC + S/4
PA0008HR Master Record: Infotype 0008 (Basic Pay)Existence of the basic pay recordPA0008-PERNR = PA0000-PERNRECC + S/4
PA0009HR Master Record: Infotype 0009 (Bank Details)Existence of the bank details recordPA0009-PERNR = PA0000-PERNRECC + S/4
T001PPersonnel Area/SubareaCountry grouping of the personnel area/subareaT001P-WERKS = PA0001-WERKS AND T001P-BTRTL = PA0001-BTRTLECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_ABKRSPayroll areaRange / multiplePA0001-ABKRSYesTM
S_BUKRSCompany codeRange / multiplePA0001-BUKRSNo1000
S_WERKSPersonnel areaRange / multiplePA0001-WERKSNoIST1
S_PERNRPersonnel numberRange / multiplePA0000-PERNRNo00001024
P_KEYDTKey date (default: period end)Single valueSY-DATUMYes30.11.2026
P_CHKITCheck missing infotypesCheckbox—NoX
P_CHKACTCheck actions and organizational assignmentCheckbox—NoX
P_CHKPAYCheck payroll status (IT0003)Checkbox—NoX

Output columns

#ColumnSource
1Pers. no.PA0000-PERNR
2NamePA0001-ENAME
3Personnel areaPA0001-WERKS
4Payroll areaPA0001-ABKRS
5Employment statusPA0000-STAT2
6ActionPA0000-MASSN
7Action startPA0000-BEGDA
8Accounted toPA0003-ABRDT
9Check codeCalculated Check group and number (e.g. IT-01, ORG-02, PAY-03)
10InfotypeCalculated Infotype the finding refers to
11FindingCalculated Description from the check rule
12SeverityCalculated Stops payroll: error; may affect the result: warning

Sample output

Pers. no.NamePersonnel areaPayroll areaEmployment statusActionAction startAccounted toCheck codeInfotypeFindingSeverity
00001302Ozan TekinIST1TM30111/03/202610/31/2026IT-010009No bank details valid on the key dateError
00001288Selin ArıIST1TM30109/15/202610/31/2026PAY-020003Hire date before accounted-to date; September may not be calculatedWarning
00001140Burak ŞenANK1TM01011/01/202609/30/2026PAY-030003Leaving date passed, October payroll not completedError
00001255Ceren UçarANK130211/01/202610/31/2026ORG-010001Payroll area blank in the organizational assignmentError
A view built with fictional sample data; not real system data.

How does the report work?

  1. 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.
  2. 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’.
  3. 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.
  4. Action check: more than one action with the same start date in PA0000 (SEQNR > 0) and an active status again after a leaving action.
  5. 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

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.

Related report: Employee Master Data Consistency Check Before Payroll Report