SAP SuccessFactors modules: the list you are expected to know
The SAP SuccessFactors modules that HR professionals and SAP learners in Kerala see in job adverts from Trivandrum, Kochi and the Gulf are not a single product, and this guide explains each one, who owns it and what to learn first. SAP sells SuccessFactors as a suite, now called the HXM Suite, but customers buy it in pieces. One company runs Employee Central alone. Another runs Learning with no Employee Central in the building. So there is no single correct count of modules, and the useful question is which ones a customer has switched on.
This guide is for HR, payroll and recruitment staff moving into SAP, graduates comparing modules, and anyone preparing for a SuccessFactors interview.
Thinking of starting? See the SAP SuccessFactors course page.
The ten modules and what each one does
Quick answer: In practice you will be asked about ten modules. The table lists each with the HR function that owns it, because the module owner is who signs off your configuration.
| Module | What it actually does | Which HR function owns it |
|---|
| Employee Central (EC) | System of record: org structure, employee master data, job and pay history, positions, Time Off | HR operations and the HRIS team |
| Recruiting Management (RCM) | Requisition to offer: applicant pipeline, interviews, offer approval and letters | Talent acquisition |
| Recruiting Marketing (RMK) | Career site, landing pages, job alerts, talent community and campaigns that feed RCM | Employer brand and recruitment marketing |
| Onboarding | New hire paperwork and compliance forms, first day tasks, offboarding and crossboarding | Talent acquisition with HR operations |
| Performance and Goals (PMGM) | Goal plans, appraisal forms and route maps, 360 reviews, calibration, continuous feedback | HR business partners and line managers |
| Compensation | Merit and bonus worksheets, eligibility and guideline rules, budgets, variable pay | Total rewards |
| Succession and Development | Talent pools, nominations, nine box matrix, talent review, development plans | Talent management |
| Learning (LMS) | Catalogue, curricula, assignment profiles, registrations, compliance training record | Learning and development |
| Workforce Analytics and Report Center | Headcount and attrition measures, story and table reports, workforce planning | HR analytics and HR leadership |
| Employee Central Payroll (ECP) | Gross to net payroll on the SAP payroll engine, hosted by SAP and fed from Employee Central | Payroll |
Time Off, Time Sheet and Position Management are not separate modules, whatever a job advert says. They are capabilities inside Employee Central, configured with the same tools. Getting that right in an interview is a cheap win.
Employee Central: the module everything else reads from
Quick answer: Employee Central is the core HR module and the system of record. Every other module pulls foundation data from it, so if Employee Central is configured badly, everything downstream inherits the problem.
Employee Central holds the organisational structure, every employee file, the job and pay history, and the events that change them. Recruiting reads job classifications from it, Compensation reads pay components, Succession reads positions, and Payroll receives the whole employee master. The configuration areas interviewers ask about are:
- The data models. The Corporate Data Model defines foundation objects such as Legal Entity, Department, Location, Job Classification and Pay Component. The Succession Data Model defines employee level fields. Both have country specific versions, which is where India specific fields such as PAN and PF details live.
- MDF and generic objects. The Metadata Framework lets you build objects, fields and rules without a data model change. Knowing when a requirement belongs in a foundation object and when in an MDF object is a standard question.
- Business rules and event reason derivation. Rules drive defaulting, validation and propagation. Event reason derivation decides which event reason a change writes to job information, and it is the most common source of bad reporting later.
- Workflows. Approval chains built from workflow configurations, dynamic groups and dynamic roles, triggered by rules on save.
- Role Based Permissions. Permission groups define who is covered, roles define what they can do, and the target population controls whose records they see. Most access defects live in the difference between granted and target population.
- Time Off. Work schedules, holiday calendars, time types and accrual rules.
Recruiting: RCM and RMK are not the same thing
Quick answer: Recruiting Management (RCM) manages people who have already applied. Recruiting Marketing (RMK) exists to make them apply. They are different products with different users and different skills.
Recruiting Management is the applicant tracking system recruiters live in. Its configuration is template driven: the job requisition, candidate profile and application templates are XML objects with field definitions and field level permissions per status. Around them sit applicant status configuration, which controls the pipeline, approval routing, offer letter templates, interview scheduling and email notifications.
Recruiting Marketing is the candidate facing half, delivered through Career Site Builder: the public career site, branded landing pages, job alerts, the talent community that captures people not yet ready to apply, and the campaign emails that bring them back. Jobs posted in RCM appear on that site through a sync, so a classic support ticket is a posted requisition that does not show on the career site, which sends you to the sync rather than the requisition. In most projects they are separate workstreams with separate owners.
Onboarding, and why the version matters
Onboarding takes a person from accepted offer to first day and beyond: new hire data review, country specific compliance forms and signatures, first day tasks such as buddy assignment and equipment, and the two processes people forget, offboarding and internal crossboarding.
The version question still appears in job descriptions. The original Onboarding was a separately acquired platform, now retired. The current Onboarding is built on the Employee Central platform, so it uses MDF objects, business rules, workflows and role based permissions. It is normally implemented after Employee Central and Recruiting, because it consumes data from both, and an Employee Central consultant picks it up far faster than someone starting from nothing.
A fair interview question is to trace the data: what comes across from the requisition, what the new hire fills in, and when the record becomes a real employee in Employee Central.
The talent modules: performance, compensation and succession
Quick answer: Performance and Goals runs the appraisal cycle, Compensation runs the annual pay review on top of those ratings, and Succession and Development plans who moves up. They depend on clean Employee Central data, so they come later in a roadmap.
- Performance and Goals (PMGM) is two things joined. Goal Management gives you the goal plan template, goal library and cascading. Performance Management gives you the appraisal form template, rating scales, competency library and the route map, which is the workflow of the form. Around them sit 360 reviews, calibration and continuous performance management.
- Compensation runs the annual review. The building blocks are the plan template and worksheet, eligibility rules, the guideline matrix that proposes an increase from rating and position in range, budget rules and compensation statements. Variable Pay is the sibling product for bonus plans. Compensation usually follows performance, because the guideline matrix wants a rating to work with.
- Succession and Development is the smallest in implementations but the most visible to executives. Succession covers nomination methods, talent pools, the performance and potential matrix everyone calls the nine box, talent review and the succession org chart. Development covers development goal plans, the career worksheet, career paths and mentoring.
Learning, analytics and the payroll module people misread
Quick answer: Learning kept its own architecture after an acquisition, Report Center and Workforce Analytics are two different things, and Employee Central Payroll is classic SAP payroll hosted by SAP rather than a new cloud payroll.
Learning (LMS) behaves least like the rest of the suite. It has its own administration interface, data model and connectors. The structures to learn are the item, course and curriculum, then programmes, catalogues, scheduled offerings, assignment profiles that push required learning automatically, and SCORM content. Many organisations buy Learning alone for compliance training.
Reporting and analytics get conflated. Report Center is the reporting front end inside the suite, and story reports, built on SAP Analytics Cloud technology, are where SAP is steering customers. Workforce Analytics proper is a separately licensed product with a curated measure library, benchmarks and workforce planning.
Employee Central Payroll is the module most often misdescribed. It is the SAP payroll engine from the on premise HCM world, hosted and operated by SAP, with the same wage types, payroll schemas and personnel calculation rules, plus the Payroll Control Center. Employee Central replicates master data and pay components into it. Country versions are localised, India included. The career consequence is real: configuring ECP is closer to classic SAP payroll work than to SuccessFactors configuration, and it is a separate track rather than a next step.
Which modules get implemented, and what to learn first
Quick answer: Employee Central goes first in nearly every project, so it has the most live instances, the most support and rollout work and the most job adverts in Kerala and the Gulf. Learn it until you can explain it without notes, then add one talent module properly.
Employee Central goes first because it is the system of record. Then the customer chooses by pain: Recruiting and Onboarding if hiring volume is the problem, Performance and Goals then Compensation if the annual cycle is. Learning runs on its own budget. Succession arrives once performance data is trustworthy. Workforce Analytics comes last, if at all. Payroll appears only where SAP payroll is already in the landscape.
That order is also the answer to what you should learn. A candidate who can configure Employee Central well is employable. A candidate who can name nine modules and configure none is not. Demand in Kerala follows the same pattern: IT services firms in Technopark and Infopark, HR outsourcing providers and Gulf facing consultancies hire Employee Central consultants for support, enhancement and rollout work, and a second module is what moves you up. Public job-portal ranges for associate SuccessFactors consultants in India start modestly and rise substantially with implementation experience. You can compare the SuccessFactors track with the other SAP modules at Cokonet Academy and across all courses, and the guide to SuccessFactors jobs in Kerala covers who is hiring.
Not sure which route fits you? Talk to a counsellor on the contact page or call +91 8075 400 500.
Why Cokonet Academy for SAP SuccessFactors training
Cokonet Academy teaches SAP SuccessFactors on a live instance in Trivandrum and Kochi, and live online for learners elsewhere in Kerala and the Gulf. Visit us on Google: Cokonet Academy, Trivandrum and Cokonet Academy, Kochi.
- NSDC partner
- 11,200+ successful placements
- 50+ corporate hiring partners
- Expert trainers in SAP (FICO, MM, ABAP), AWS, Python with AI, Data Analytics and Power BI
- Individual instance access, an implementation capstone, mock interviews and placement support with Kerala and Gulf facing employers
SAP SuccessFactors course details
The SAP SuccessFactors course at Cokonet Academy is an Employee Central course by design. A course that claims all ten modules in a few months is showing you demonstrations, not teaching you configuration.
- What it covers: The hire to retire process and the shape of the suite, Employee Central foundations, the succession data model, events, workflows and business rules, role based permissions, MDF extensibility, Time Off, reporting through Report Center, and the basics of integration and data migration, finishing with an implementation capstone on a live instance
- Best for: HR, payroll and recruitment professionals, MBA HR graduates, SAP HCM users moving to the cloud, and Gulf returnees from HR roles
- Duration: About 4 to 5 months
- Formats: Weekday batches, weekend batches and live online classes
- Locations: Classroom training in Trivandrum and Kochi, live online from anywhere else in Kerala or the Gulf
- Includes: Capstone project, interview preparation and placement support
See the full syllabus and next batch dates on the SAP SuccessFactors course page.
Visit our training centres
Walk in for a free career consultation and we will say honestly whether SuccessFactors fits your background. Open Monday to Saturday, 9:30am to 10:00pm.
Enrol now
Join the SAP SuccessFactors course, explore all programmes at Cokonet Academy, or call and WhatsApp +91 8075 400 500 to book a free counselling session.
