SAP Hire to Retire (HCM) – Realistic HR Lifecycle & Payroll Integration Hands‑On Tutorial | Part 10 | FreeLearning365

 

SAP Hire to Retire (HCM) – Realistic HR Lifecycle & Payroll Integration Hands‑On Tutorial

So far, you’ve sold, bought, closed the books, and manufactured. Now ask yourself: who made that possible? The most valuable asset of any company – its people – is managed and paid through SAP HCM. The Hire to Retire cycle is the backbone that ensures the right person is in the right job, paid accurately, and that every rupee of payroll cost finds its way to the correct general ledger account. If you skip this module, you’re leaving a massive blind spot in your ERP knowledge.

In this part of the Business Process First series, we step into GlobalTech Innovations (Company Code 1000) as an HR consultant. We will build the organizational structure, hire a production operator, run time management, execute payroll, post the results to FI, and finally process a full termination and settlement. Every infotype, every wage type, and every accounting document is real and replicable in your sandbox. This is not just “PA30” and “PA40” – it’s the complete lifecycle of an employee inside SAP.

Time to turn the black box of HR into a crystal‑clear story of people and profit.

1. The Hire to Retire Mindset – It’s a Financial Cycle in Disguise

Hire to Retire (H2R) covers everything from workforce planning and recruitment to employee separation and pension payments. In SAP, it spans Personnel Administration (PA), Organizational Management (OM), Time Management (PT), Payroll (PY), and Benefits (BN). The ultimate output is not just a payslip – it’s a set of journal entries that post salary expenses, liabilities, and tax payments to the general ledger, and often allocate costs to cost centers, production orders, or projects. A real HCM consultant doesn’t just “run payroll”; they understand the integration with FI/CO so well that they can explain to the CFO why the GL account for salary expense changed this month.

Before you even open PA40, you must ask:

• What is the employee’s legal entity (personnel area), which drives tax and social insurance rules?
• Which cost center will bear the employee’s salary, and is it linked to a profit center?
• How are the wage types (basic pay, allowances, overtime) defined in the payroll schema, and what is their posting behavior in FI?
• What happens retroactively if a salary change is made after payroll has been run?
• When an employee leaves, what components make up the final settlement, and how are they taxed?

We will answer all of that by building a complete employee record, running real payroll, and tracing the accounting entries.

2. Organizational Structure – The Framework of HR

Before a single employee is hired, the enterprise structure must be defined. In HCM, this comprises Personnel Areas, Personnel Subareas, Employee Groups, and Employee Subgroups. These control everything from default pay scale to holiday calendar. For GlobalTech, we set up:

• Personnel Area (PA): 1000 – Bangalore Plant. This is the highest HR organizational unit and corresponds to a company code in many setups.
• Personnel Subarea (PSA): 0001 – Production Workers, 0002 – Administrative Staff. Each subarea defines the grouping for payroll accounting (e.g., monthly vs. weekly payroll), tax group, and default holiday calendar (IN – India).
• Employee Group (EG): 1 – Active, 2 – Retired.
• Employee Subgroup (ESG): A1 – Monthly Wage Earner (Management), B1 – Hourly Wage Earner (Production). ESG determines the payroll procedure (e.g., monthly salary vs. hourly calculation), the time management status, and the default wage type model.

These assignments are maintained via the IMG or transaction SM30 views. They are the invisible threads that pull together payroll rules.

2.1 Organizational Management (OM) – The Reporting Structure

Beyond the personnel structure, SAP provides Organizational Management to model the company’s departments and positions. For GlobalTech, we create:

• Organizational Unit: Production Department (Org. unit 50000100).
• Position: Assembly Operator (Position 60000100).
• Job: Production Worker (Job 70000100).
• Cost Center: 1100 – Assembly Cost Center (already used in PP).

Using transaction PPOME (or PPOCE), we build a tree structure. The position is linked to the job (which holds the task description) and to the cost center via the “Account Assignment” infotype (1018) or directly in the position’s characteristics. This linkage is what later drives automatic cost assignment when an employee is hired.

Consultant Tip: Always link positions to cost centers in OM. When you hire someone into a position, infotype 0001 (Organizational Assignment) automatically pulls the cost center. This ensures all payroll costs flow to the correct controlling object without manual errors.

3. Master Data – The Employee’s Digital Twin

Every employee is a unique master record identified by the Personnel Number (PERNR). We will hire an employee Ravi Kumar as an Assembly Operator. Let’s step through the essential infotypes that build his digital file.

3.1 Hiring via PA40 (Personnel Actions)

Transaction PA40 is the central cockpit for personnel actions. We select action type “Hire” for today’s date and enter the personnel number (if external number assignment) or let the system generate one. Assume PERNR 500001.

Then we fill in a sequence of infotypes:

Infotype 0001 – Organizational Assignment

• Company Code: 1000
• Personnel Area: 1000
• Personnel Subarea: 0001
• Employee Group: 1 (Active)
• Employee Subgroup: B1 (Hourly Wage Earner)
• Cost Center: 1100 (Assembly Cost Center)
• Position: 60000100 (Assembly Operator)
• Job: 70000100 (Production Worker)
• Organizational Unit: 50000100
• Payroll Area: 01 (Monthly payroll – India)

Infotype 0002 – Personal Data

• Name: Ravi Kumar, Date of Birth: 12‑Mar‑1990, Gender: Male, Marital Status: Married.

Infotype 0006 – Addresses

• Permanent address: #45, Staff Colony, Bangalore 560001.

Infotype 0007 – Planned Working Time

• Work schedule rule: PROD1 (Production shift 08:00‑17:00, Monday‑Friday).
• Employment percentage: 100%. Working week: 40 hours.

Infotype 0008 – Basic Pay

This is the heart of payroll. We define the wage type(s) that represent Ravi’s salary components.

• Wage Type 1000 (Basic Pay): Amount 18,000 INR per month. Indirect valuation via pay scale group can also be used, but we’ll use direct amount.
• Wage Type 1100 (House Rent Allowance): 40% of basic = 7,200 INR. (We can enter as fixed or percentage; we’ll set as percentage in customizing; for simplicity, we’ll manually maintain amount 7,200.)
• Wage Type 1200 (Conveyance Allowance): 1,600 INR.
• Wage Type 2000 (Provident Fund – Employee contribution): 12% of basic = 2,160 INR – usually a deduction. We’ll set as deduction wage type with amount 2,160.

We’ll define these wage types in customizing and assign them to the employee. For now, we enter the amounts manually. The system calculates the total gross.

Infotype 0009 – Bank Details

• Bank country: IN, Bank key: 001 (State Bank of India), Bank account number: 12345678901, Account holder: Ravi Kumar.

Infotype 0014 – Recurring Payments/Deductions

For fixed recurring deductions or additions like union fees, professional tax, etc. We add Professional Tax (WT 2100) 200 INR deduction per month.

Infotype 0015 – Additional Payments

For one‑time payments, like a joining bonus. We add a joining bonus of 5,000 INR (WT 1500).

After saving, the system performs an automatic retroactive accounting check (if payroll has been run for the period). Since it’s a fresh hire, no backpay. The personnel file is now active.

4. Time Management – Where Hours Become Money

Ravi is an hourly worker. His planned working time is 8 hours a day, 5 days a week. But the shop floor may require overtime, or he may be absent. Time management captures actual hours worked, which feed into payroll.

4.1 Recording Attendances and Absences

Transaction PA61 (Maintain Time Data) or PA70 (Fast Entry). For a given week in May 2026, Ravi works the full schedule plus 5 hours overtime on Saturday. We record:

• Attendance type 0050 (Normal Working Time) – 40 hours (Mon‑Fri).
• Attendance type 0200 (Overtime at 1.5x) – 5 hours (Sat).

The overtime attendance type has a wage type assigned in configuration (e.g., WT 2200) that will generate additional pay.

4.2 Time Evaluation (PT60 or RPTIME00)

At the end of the month, the time evaluation program processes all recorded time data, checks for clashes, calculates overtime based on rules, and generates wage types (e.g., WT 2200 with 5 hours * hourly rate). The hourly rate is derived from basic pay / planned hours (18,000 INR / 160 hours = 112.50 INR per hour). Overtime rate 1.5 = 168.75 per hour, so 5 * 168.75 = 843.75 INR. This amount is posted as a positive wage type for payroll.

We can simulate time evaluation for Ravi with report RPTIME00 and view the generated wage types. The integration with payroll is automatic: the payroll driver reads the time wage types and includes them in the gross.

5. Payroll – The Engine That Calculates Take‑Home and Postings

Now we run payroll for the month of May 2026 for Ravi. Payroll is executed by a country‑specific driver; for India, it’s PC00_M99_CALC (or HINCALC0 for India, or a generic PC00_M40_CALC). Let’s use the international payroll driver PC00_M99_CALC as a generic representation.

5.1 Payroll Control Record

Before payroll, the payroll area “01” must be in the correct status. Use PA03 to set the payroll control record to “Released for Payroll”. We set the period to May 2026.

5.2 Execute Payroll: Transaction PC00_M99_CALC

Enter payroll area 01, period 05.2026, selection of employees (by personnel number range, include 500001). Execute in simulation mode first to check the results. Once satisfied, run in live mode.

The payroll program reads all relevant infotypes (0008, 0014, 0015, time wage types) and processes them through a schema (e.g., X000 for India). It calculates:

• Gross pay = Basic (18,000) + HRA (7,200) + Conveyance (1,600) + Overtime (843.75) + Joining Bonus (5,000) = 32,643.75 INR.
• Deductions: Provident Fund (WT 2000) 2,160, Professional Tax (WT 2100) 200. Total deductions = 2,360.
• Net pay = 30,283.75 INR.

The system stores these results in the payroll results tables (cluster RD). You can display the payroll log via PC_PAYRESULT (or transaction PE01/PE02). The log shows every step of schema processing, from gross to net.

5.3 Payroll Posting to Accounting (FI)

Now the crucial step: posting payroll results to FI. Run the program RPCIPJ00 (or for India, HINCPOST) to create a post‑transfer document. This program reads the payroll results, groups wage types by symbolic accounts (e.g., WAGE -> Expense, WAGE -> Payable), and generates an FI document.

For Ravi’s May payroll, the symbolic account assignment in customizing (table T030) might map:

• Wage type “Basic Pay” (1000) and other earnings -> Debit expense account 630000 (Salary Expense), Credit payable account 160010 (Salary Payable). The cost assignment (cost center 1100) is taken from infotype 0001.
• Deductions like PF (2000) -> Debit Salary Payable, Credit PF Payable (160020).
• Net pay -> Credit Bank (110000).

So the FI document would look like (simplified):

• Dr. Salary Expense (630000) 32,643.75 INR
• Cr. Salary Payable (160010) 30,283.75 INR
• Cr. PF Payable (160020) 2,160 INR
• Cr. Professional Tax Payable (160030) 200 INR

Later, when the net pay is transferred via bank, a payment run (F110) clears the Salary Payable account.

Hands‑on Exercise: After running payroll and posting, go to FB03 and display the accounting document. Drill down to the line items and verify the cost center 1100 appears. This proves HCM‑FI‑CO integration.

6. Full Scenario 1: Scen‑HCM‑01 – Hiring a Production Worker and Full Payroll

Let’s compress the entire flow for Ravi into a single run‑book:

1. Master data: Personnel area 1000, subarea 0001, ESG B1.
2. Hire via PA40: infotype 0001 cost center 1100, infotype 0008 basic pay 18,000, HRA 7,200, conveyance 1,600. Infotype 0009 bank details.
3. Time recording: PA61 – 40 hours normal, 5 hours overtime (type 0200).
4. Time evaluation: PT60 generates WT 2200 = 843.75 INR.
5. Payroll run: PC00_M99_CALC for May 2026. Net pay 30,283.75 INR.
6. Post to accounting: RPCIPJ00 creates FI document #510000001. Verify expense and payables.
7. Third‑party remittance: PF and PT are paid to authorities via a separate payment run.
8. Result: Employee’s cost is allocated to cost center 1100, ready to be absorbed in product cost.

7. Full Scenario 2: Scen‑HCM‑02 – Mid‑Month Salary Revision

After joining, Ravi’s basic pay is increased to 20,000 INR effective 15‑May‑2026. This triggers retroactive accounting. The process:

• Use PA30 to change infotype 0008 with a new record valid from 15‑May‑2026. Basic pay = 20,000, HRA = 8,000, conveyance = 1,800.
• The system marks the previous record as delimited and sets a retroactive accounting trigger.
• Next payroll run for May will recalculate the entire month using pro‑rated values: first half at old rate, second half at new rate. The payroll driver automatically splits the period and computes wages accordingly.
• The difference from the previous run is paid as backpay in the current period.

This demonstrates the power of SAP’s retroactive accounting. Users must be aware that any change to a payroll‑relevant infotype triggers a re‑calculation across the whole retroactive period, which can cause differences that need to be explained to employees.

8. Full Scenario 3: Scen‑HCM‑03 – Organizational Restructure and Cost Center Change

GlobalTech reorganizes and moves the Assembly Department from cost center 1100 to a new cost center 1105. This involves updating the position in OM and then mass‑changing employees assigned to that position. In OM, we change the account assignment of position 60000100 to cost center 1105. Then we run a program to update infotype 0001 for all holders of that position (transaction RHINTE30). After the change, all future payroll postings will use cost center 1105. Any retroactive changes for a past period will still go to the old cost center if the validity aligns.

This scenario shows the importance of OM integration: a single change can cascade across hundreds of employees, saving hours of manual work and ensuring consistency.

9. Full Scenario 4: Scen‑HCM‑04 – Termination and Final Settlement

After three years, Ravi resigns. His last working day is 31‑May‑2026. The HR department processes a termination action via PA40 (action type “Leaving”).

• Enter infotype 0001: effective date 31‑May‑2026.
• Infotype 0041 (Date Specifications): enter leaving date 31‑May‑2026.
• Infotype 0015: enter settlement components such as Notice Pay (WT 3000) 20,000 INR, Gratuity (WT 3100) 50,000 INR (exempt up to certain limit).
• Run payroll for May. The payroll program identifies that the employee is a leaver and calculates the final salary plus settlements, applying tax rules (TDS on notice pay, etc.).
• After payroll posting, the net amount is paid, and the employee’s status is changed to “Withdrawn” after all clearances.

This scenario covers the entire exit lifecycle, including the integration with FI for settlement liabilities.

10. Integration Checkpoints – HCM to FI/CO/PP

The true beauty of SAP is how HR feeds into controlling and financial accounting. Let’s map the exact touchpoints we’ve used:

• HCM → FI: Payroll posting (RPCIPJ00) creates journal entries for expenses, payables, and tax liabilities. Third‑party remittance (PF, PT, TDS) are handled via accounts payable.
• HCM → CO: The cost center from infotype 0001 ensures salary costs are allocated to the correct controlling object. In activity confirmations (PP), the worker’s labor time is valued using activity price and compared to actual payroll cost – revealing a cost variance that management accounting analyzes.
• HCM → PP: The employee’s master data can be linked to a work center via the HR‑AS (Assignment to Work Center) infotype. This enables capacity planning and labor costing directly in production orders. When a production order confirmation records labor hours, the system can use the employee’s actual labor rate or a standard rate.
• HCM → SD (indirect): Project systems and service orders can also absorb labor costs if time is recorded against them.

Thus, Ravi’s basic pay isn’t just a number – it’s a cost driver that impacts the COGS of every ProSwitch he helps assemble.

11. Troubleshooting Common HCM Issues

1. Payroll run fails with “No entry in table T511K for wage type”: This means the wage type is not configured or not assigned to the payroll accounting area. Use SM30 to maintain the wage type configuration or check the payroll log for specifics.
2. Posting to accounting produces an error “Account not defined in T030”: The symbolic account for a wage type is missing in the account determination table. Configure it in T030 for the chart of accounts and wage type group.
3. Retroactive accounting triggers unexpected backpay: Check infotype change logs (PA51) to identify which change caused the trigger. Validate that the new record’s validity overlaps the payroll period.
4. Time evaluation doesn’t generate expected overtime: Verify the attendance type and the day type rules in the time schema (TM00). Ensure the attendance is recorded with a valid reason and that the absence counting class is correct.
5. Termination payroll calculates wrong tax: Check the termination action’s infotype 0041 and the taxability settings for settlement wage types. Tax code logic in the payroll schema may need adjustment.

12. Consultant Wisdom – Best Practices and Pitfalls

• Never go live without a comprehensive testing of the payroll control record and payroll periods. A single misconfigured payroll area can cause all employees to be omitted from payroll.
• Set up retroactive accounting periods carefully. In most countries, you must limit retroactivity to avoid recalculating years of history due to a minor change. Use feature LGMST.
• Integrate OM with FI/CO from day one. Link every position to a cost center. When a new cost center is created, update OM first, then cascade to employees – this ensures financial statements reflect the true organization.
• Use wage type models (PA30, infotype 0052) to default wage types for employee subgroups. This speeds up hiring and ensures compliance.
• Train the HR team on the importance of infotype validity dates. A wrong date on a pay change can cause massive overpayment or underpayment.
• Keep the payroll log (cluster RD) safe and archived. It is your audit evidence for every deduction and payment.

13. Interactive “Try It Now” Checklist

Log into your SAP IDES or training system and execute these steps:

1. Verify the enterprise structure (PA, PSA, ESG) or create your own.
2. Hire an employee using PA40 with cost center linkage.
3. Maintain basic pay and other recurring wage types.
4. Record time data for a period with overtime.
5. Run time evaluation and check generated wage types.
6. Run payroll for the employee in simulation, then live.
7. Execute the posting to accounting and review the FI document in FB03.
8. Change the basic pay mid‑period and re‑run payroll to observe retroactive calculation.
9. Process a termination and final settlement.
10. Explore OM: create a new position linked to a different cost center, and move the employee; verify payroll posting follows.

14. Final Words – People, Pay, and Profit Are One

Hire to Retire is the cycle that gives life to an organization. When you can take an employee from recruitment to final settlement, run payroll, post the costs to the right cost center, and explain how those costs end up in the product cost and ultimately the P&L, you’re no longer a module specialist – you’re a business analyst who speaks the language of value. This article has given you the real‑world blueprint, the exact scenarios, and the troubleshooting skills. Now it’s your turn to hire, pay, and retire with confidence.

This completes our five‑part Business Process First series. You now possess the end‑to‑end knowledge of the core logistics and financial processes that run any SAP‑powered business. Keep learning, keep questioning, and keep building. The path from fresher to trusted consultant is paved with the stories you can tell from your sandbox.

– FreeLearning365, in tech partnership with @techbook24