PC00 — Payroll Area Menu and Country Driver Entry Point
PC00 is the area menu that opens the Payroll folder tree in SAP Easy Access; it is not a payroll processing program itself. It branches by country grouping (molga) to the real payroll driver transactions, such as PC00_M99_CALC for the international version or PC00_M40_CALC for India. Confusion arises because people report 'running PC00' when they actually executed a country-suffixed transaction beneath it.
This page covers PC00 as the entry-point area menu for payroll execution transactions, organized by country grouping rather than being a single program. It focuses on the diagnostic confusion this causes in support tickets, authorization checks, and batch job variants, and points to the master data and time evaluation transactions that feed the actual payroll run.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,215 words
Purpose
PC00 is an area menu, not an executable payroll program. Running it opens a folder tree inside the SAP Easy Access menu grouping payroll-related activities: Payroll, Subsequent activities, Payroll supplement, Info System, and similar branches. Each branch is populated with country-specific transactions identified by their country grouping code (molga), because payroll logic, wage type catalogs, and legal reporting differ by country and cannot share one driver. The transaction a consultant actually executes to calculate payroll is always a suffixed variant, for example PC00_M99_CALC for the generic international schema or a country-specific equivalent. This is the structural fact behind most confusion: incident reports, chat threads, and even internal documentation frequently say 'PC00 failed' when the failing object was a specific country driver several folders deep, with its own selection screen, its own authorization checks, and its own program logic.
When it is used
PC00 is reached during initial exploration of the payroll module, during training, or when a consultant working across multiple country payroll implementations does not remember the exact suffixed transaction code for a given country grouping. It sits upstream of the actual payroll run in the business process: master data changes, time evaluation, and infotype maintenance all happen before someone drills into the PC00 tree to launch the calculation. In steady-state production, consultants bypass the tree and enter the fully qualified country transaction directly, or the transaction is called from a background job. PC00 itself is rarely referenced in a batch job step; the job variant points to the suffixed tcode. Fiori apps for payroll monitoring exist alongside this menu but do not replace the driver execution transaction reached through it.
How to use it in practice
- Enter PC00 in the command field and execute.
- The Payroll folder tree opens; identify the country grouping (molga) relevant to the personnel area or employee group under investigation.
- Drill into the corresponding country subfolder rather than assuming the first entry applies.
- Locate the payroll driver transaction for that country, typically named with a M<CC> suffix such as PC00_M40_CALC or the generic PC00_M99_CALC.
- Execute that transaction directly, entering payroll area, payroll period, and personnel number or selection criteria on its own selection screen.
- Record the exact suffixed transaction name used, since this is what any log, dump, or support ticket needs to reference.
Key data objects
- PCL2 - cluster table holding payroll results (retrieval cluster RT and related clusters) written when a country driver completes a run.
- PCL1 - cluster table holding retroactive accounting difference data used across payroll periods.
- T569V - payroll control record per payroll area, tracking status (released, exit, check, corrected) that the driver reads and updates.
- PA0003 - payroll status infotype, mirroring run date, earliest retroactive accounting date, and lock status per personnel number.
How to prove it in the data
PC00 itself leaves no trace because it performs no processing; to confirm what actually ran, check PA0003 via SE16 filtered on the personnel number in question, looking at the run date and status fields to see when payroll last executed and whether the record is locked for further changes. Cross-check T569V for the relevant payroll area to see the control record status (released versus exit) at the time of the run. If a batch job is suspected, check the job step definition in the job log rather than PC00, since the job step always names the country-specific suffixed transaction.
ECC vs S/4HANA
On S/4HANA on-premise using classic or Employee Central Payroll, the PC00 area menu structure and the country-suffixed driver transactions are unchanged; this part of payroll has not been redesigned. Some Fiori apps exist for payroll status monitoring and process oversight, but none of them replace the driver execution transaction itself. In a SuccessFactors Employee Central plus Employee Central Payroll landscape, the PC00 tree and its drivers still run inside the ECP system, separate from the S/4 core, and are invoked the same way as in a standalone HCM system.
Common pitfalls and how to diagnose them
- Wrong transaction assumption - a ticket or chat message says PC00 threw an error, but PC00 has no selection screen or processing logic of its own. Before investigating, ask which country grouping and which suffixed transaction (for example PC00_M10_CALC) was actually executed; the real error lives there, not in the menu node.
- Menu authorization gaps - a user cannot see a country folder under PC00 or the folder appears empty for them specifically. PC00 as an area menu carries no meaningful authorization object of its own; the visibility is driven by whether the underlying transaction codes in that branch are authorized in the user's role. Check the role's transaction authorizations and the payroll-related authorization objects for the country and payroll area in question rather than anything tied to PC00 itself.
- Missing country version - a folder is genuinely empty or a driver transaction does not exist because that country's payroll component was never activated or installed in the system. This shows up as a folder with no entries rather than an authorization error, and the fix is a functional and Basis conversation about country version activation, not a role change.
- Custom menu deviation - some implementations copy PC00 into a Z-area menu and prune or rearrange branches. A support message referencing 'PC00' from an end user may actually describe the customer's Z-copy. Confirm via the transaction's properties which object was actually launched before assuming standard SAP behavior applies.
- Batch variant mismatch - a scheduled job variant was built against one country's driver transaction but the payroll area assigned to it belongs to a different country grouping, producing calculation errors or empty results. Check the payroll area's molga against the variant's target transaction before assuming a data issue in infotypes.
Whose problem this is
Primarily a payroll functional consultant's territory, since the confusion and the fix both live in identifying the correct country driver and payroll area setup. Basis involvement is limited to authorization roles and background job scheduling infrastructure. ABAP involvement only arises if a custom country driver or Z-area menu is implicated. A good handover names the country grouping, the exact suffixed transaction executed, the payroll area, the period, and the precise error or log entry, not just 'PC00 failed'.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/pc00ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.