Difference between revisions of "SAP HCM POSTING"

From SapWiki
Line 2: Line 2:
 
In SAP HR/HCM, transaction PCP0 is used to display, edit, and manage payroll posting runs to accounting. The data associated with these posting runs is stored across several core database tables, primarily split between run administration, document details, and mapping data. [1, 2, 3]
 
In SAP HR/HCM, transaction PCP0 is used to display, edit, and manage payroll posting runs to accounting. The data associated with these posting runs is stored across several core database tables, primarily split between run administration, document details, and mapping data. [1, 2, 3]
 
Here is the breakdown of the critical PCP0-related tables:
 
Here is the breakdown of the critical PCP0-related tables:
−
#Run Administration Tables
+
##Run Administration Tables
 
* PEVST: Stores the main parameters and administration data for payroll posting runs (Posting Runs).
 
* PEVST: Stores the main parameters and administration data for payroll posting runs (Posting Runs).
 
* PEVSH: Stores the status history of the payroll posting runs.
 
* PEVSH: Stores the status history of the payroll posting runs.
 
* PEVAT: Stores background information and run control totals. [1, 2, 3, 4]
 
* PEVAT: Stores background information and run control totals. [1, 2, 3, 4]
−
#Document & Line Item Tables
+
##Document & Line Item Tables
 
* PPDHD: Document Header data for the payroll posting. Contains vital data like Run ID, Posting Date (BUDAT), Document Number (DOCNUM), and Company Code (BUKRS). [1, 2, 3, 4]
 
* PPDHD: Document Header data for the payroll posting. Contains vital data like Run ID, Posting Date (BUDAT), Document Number (DOCNUM), and Company Code (BUKRS). [1, 2, 3, 4]
 
* PPDIT: Document Item data. Contains the specific FI/accounting details, including the General Ledger Account (HKONT), Cost Center (KOSTL), Profit Center (PRCTR), and Amount (WRBTR). [1, 2]
 
* PPDIT: Document Item data. Contains the specific FI/accounting details, including the General Ledger Account (HKONT), Cost Center (KOSTL), Profit Center (PRCTR), and Amount (WRBTR). [1, 2]
−
#Wage Type & Component Tables
+
##Wage Type & Component Tables
 
* PPOIX: Stores the assignment of wage types and amounts mapped by Personnel Number.
 
* PPOIX: Stores the assignment of wage types and amounts mapped by Personnel Number.
 
* PPDIX: Contains the index for document items (useful for tying cluster data to FI documents).
 
* PPDIX: Contains the index for document items (useful for tying cluster data to FI documents).
 
* PPOPX: Stores the index and details for the personnel numbers involved in the posting run. [1, 2, 3]
 
* PPOPX: Stores the index and details for the personnel numbers involved in the posting run. [1, 2, 3]
−
#Cross-Reference to Financial Accounting (FI)
+
##Cross-Reference to Financial Accounting (FI)
 
* When a posting document is successfully transferred, it links directly to the Financial Accounting module.
 
* When a posting document is successfully transferred, it links directly to the Financial Accounting module.
 
* BKPF: Accounting Document Header (stores the FI Document Number based on PPDHD-DOCNUM).
 
* BKPF: Accounting Document Header (stores the FI Document Number based on PPDHD-DOCNUM).

Revision as of 21:54, 6 July 2026

Trn. PCP0

In SAP HR/HCM, transaction PCP0 is used to display, edit, and manage payroll posting runs to accounting. The data associated with these posting runs is stored across several core database tables, primarily split between run administration, document details, and mapping data. [1, 2, 3] Here is the breakdown of the critical PCP0-related tables:

    1. Run Administration Tables
  • PEVST: Stores the main parameters and administration data for payroll posting runs (Posting Runs).
  • PEVSH: Stores the status history of the payroll posting runs.
  • PEVAT: Stores background information and run control totals. [1, 2, 3, 4]
    1. Document & Line Item Tables
  • PPDHD: Document Header data for the payroll posting. Contains vital data like Run ID, Posting Date (BUDAT), Document Number (DOCNUM), and Company Code (BUKRS). [1, 2, 3, 4]
  • PPDIT: Document Item data. Contains the specific FI/accounting details, including the General Ledger Account (HKONT), Cost Center (KOSTL), Profit Center (PRCTR), and Amount (WRBTR). [1, 2]
    1. Wage Type & Component Tables
  • PPOIX: Stores the assignment of wage types and amounts mapped by Personnel Number.
  • PPDIX: Contains the index for document items (useful for tying cluster data to FI documents).
  • PPOPX: Stores the index and details for the personnel numbers involved in the posting run. [1, 2, 3]
    1. Cross-Reference to Financial Accounting (FI)
  • When a posting document is successfully transferred, it links directly to the Financial Accounting module.
  • BKPF: Accounting Document Header (stores the FI Document Number based on PPDHD-DOCNUM).
  • BSEG: Accounting Document Segment (stores the actual FI line-item details). [1, 2, 3, 4]

Tips for Custom Reporting When building custom ABAP reports or querying these tables, PPDHD acts as the primary connector. You can retrieve the RUNID or DOCNUM from PPDHD and pass it to PPDIT to extract exact financial results. Use the SAP Document Overview to check the completeness of postings in your S/4HANA system. [1, 2, 3]