Payroll, Integration, and Reporting
Payroll
Employee Central Payroll Essentials
EC Payroll is SAP HCM-based and integrated with Employee Central. EC holds master and payroll-relevant data; payroll calculation runs in the payroll system. Key concepts include Pay Group (a foundation object grouping employees for payroll), Payroll System Configuration (maps legal entity to payroll system), pay components and pay component groups, frequency and frequency conversion, recurring versus one-time payments, and payroll periods and cycles. Payroll Control Center monitors runs, errors, and post-payroll activities; off-cycle runs handle corrections.
Traps: assuming EC calculates net pay for EC Payroll (it does not); confusing pay group with payroll area; forgetting frequency conversion when pay component frequency differs from pay group frequency; and mixing pay component with pay component group. Replication of master and time data from EC to payroll is a prerequisite for a clean run.
Worked example: An employee has a salary pay component with frequency Annual and a pay group of Monthly. A frequency conversion from Annual to Monthly must exist for the amount to be handled correctly.
Rule of thumb: if pay is calculated, it is payroll; if it is stored and replicated, it is EC.
Integration and Reporting
Integration Patterns and Report Types
Integration options include Integration Center (scheduled or event-based inbound and outbound mappings), OData API (entity-level REST access), Compound Employee API (a full employee snapshot including employment, job, compensation, and personal data), and SOAP/SFAPI for older objects. Middleware such as CPI or Boomi often orchestrates flows. Replication of EC data to EC Payroll or to analytics is a distinct integration pattern.
Reporting: Report Center hosts table reports (simple flat lists), canvas reports (multi-block, complex output), and story reports in People Analytics (visual analytics). Ad hoc and query-based reports support quick extracts.
Traps: using OData when a full employee extract is needed (use Compound Employee); assuming Integration Center can perform any transformation without middleware; confusing report types; and forgetting that reports respect RBP and target populations.
Worked example: To send a nightly file of new hires to a vendor, use Integration Center with a scheduled outbound integration filtered on hire date.
Rule of thumb: real-time single record uses OData; full employee snapshot uses Compound Employee; scheduled file exchange uses Integration Center.