Every SAP SuccessFactors module, explained.

The modules, and what each one does.

SAP sells SuccessFactors as a suite, which it now calls the HXM Suite, but customers buy it in pieces. A company can run Employee Central alone. Another can run Learning alone with no Employee Central anywhere in the building. That is why there is no single correct answer to how many modules there are, and why the useful question is which ones a customer has switched on. The table below is the working list you will be expected to know, with the HR function that owns each one, because in a real project the module owner is the person who signs off your configuration.

Time Off, Time Sheet and Position Management are not separate modules, whatever a job advert says. They are capabilities inside Employee Central, licensed with it and configured with the same tools. Getting that right in an interview is a cheap win.

Employee Central: the module everything else reads from.

Employee Central is the core HR module and the system of record. It holds the organisational structure, every employee file, the full job and pay history, and the events that change them. Every other module in the suite pulls foundation data out of it: Recruiting reads job classifications and locations, Compensation reads pay components and pay ranges, Succession reads positions, Payroll receives the whole employee master. If Employee Central is configured badly, every module downstream inherits the problem.

SAP documents all of this in the Implementing Employee Central Core guide and the Employee Central Time Off guide on the SAP Help Portal, and those two guides are the honest answer to where a consultant checks behaviour rather than guessing. Read the release notes as well: SuccessFactors ships on a fixed release cycle and behaviour genuinely changes between releases.

Recruiting: RCM and RMK are not the same thing.

Recruiting is where candidates get confused, because SAP ships two products under one heading and job adverts use the acronyms interchangeably. They are different products, with different users and different skills.

Recruiting Management, RCM, is the applicant tracking system. Recruiters live in it. The configuration is template driven: the job requisition template, the candidate profile template and the application template are XML objects with field definitions and field level permissions per status. Around them sit applicant status configuration, which controls the pipeline the recruiter moves candidates through and who can see which field at each step, requisition approval routing, offer approval and offer letter templates, interview scheduling and interview central, agency access, and the email notification templates that fire on status change.

Recruiting Marketing, RMK, is the candidate facing half, delivered today through Career Site Builder. It is the public career site, the branded landing pages, the search engine friendly job pages, job alerts, the talent community that captures people who are not ready to apply yet, and the campaign emails that bring them back. Jobs posted in RCM appear on that site through a sync, so a very common support ticket, and a very common interview question, is that a requisition is approved and posted but does not show on the career site, which sends you to the posting settings and the sync rather than to the requisition itself.

Put simply: RCM manages people who have already applied, RMK exists to make them apply. SAP keeps them in separate documentation sets, Recruiting Management and Career Site Builder, and in most projects they are separate workstreams with separate business owners.

Onboarding, and why the version matters.

Onboarding takes a person from accepted offer to first day and beyond. It handles the new hire data review, country specific compliance forms and signatures, the tasks that make a first day work such as buddy assignment, meeting scheduling and equipment provisioning, and it also covers the two processes people forget: offboarding when someone leaves, and crossboarding when someone moves internally.

The version question is worth understanding because it still appears in job descriptions. The original Onboarding was a separately acquired platform with its own tooling. The current Onboarding is built on the Employee Central platform, so it uses MDF objects, business rules, workflows and role based permissions, the same tools as Employee Central. SAP has retired the old product, and its own Implementing Onboarding documentation describes only the current one. The practical consequence is that Onboarding is normally implemented after Employee Central and Recruiting, because it consumes data from both, and that an Employee Central consultant can pick it up far more quickly than someone starting from nothing.

A fair interview question here is to trace the data: what comes across from the requisition and the candidate record into Onboarding, what the new hire fills in themselves, and at what point the record becomes a real employee in Employee Central. If you can draw that flow you are ahead of most freshers.

The talent modules: performance, pay and succession.

Performance and Goals, usually written PMGM, is two things joined together. Goal Management gives you the goal plan template, the goal library, and cascading and alignment between manager and team goals. Performance Management gives you the appraisal form template, the rating scales, the competency library, and the route map, which is the workflow of the form: the steps it moves through, who owns each step, and the step types such as the modify stages, the one to one meeting and the signature stage. Around them sit 360 multi rater reviews, calibration sessions where managers agree ratings against a distribution, and continuous performance management for activities, achievements and ongoing feedback.

Compensation runs the annual review. The building blocks are the compensation plan template and its worksheet, eligibility rules that decide who appears on whose worksheet, the guideline matrix that proposes an increase from inputs such as performance rating and position in range, budget rules, and compensation statements. Variable Pay is the sibling product for bonus plans, with business goal weighting and plan assignment. Compensation depends on clean job and pay data, so it is almost never implemented before Employee Central, and it usually follows performance because the guideline matrix wants a rating to work with.

Succession and Development is the smallest of the three in terms of implementations but the most visible to executives. Succession covers nomination methods, and the choice between position based nomination using MDF positions and incumbent based nomination changes how the whole module behaves, along with talent pools, the performance and potential matrix that everyone calls the nine box, talent review calibration, the succession org chart and talent presentations. Development covers development goal plans, the career worksheet, career paths and mentoring programmes. It reads ratings from performance and positions from Employee Central, which is why it comes late in a roadmap.

Learning, analytics and the payroll module people misread.

Learning, the LMS, behaves least like the rest of the suite because it arrived through an acquisition and kept its own architecture. It has its own administration interface, its own data model and its own connectors. The structures to learn are the item, the course and the curriculum, then programmes, catalogues, scheduled offerings and registration, assignment profiles that push required learning to a population automatically, learning plans and the learning history, approval processes, and content handling for SCORM and AICC packages. SAP documents it separately as SAP SuccessFactors Learning Administration, which tells you something about how separate it really is. Plenty of organisations buy Learning on its own for compliance training with no other SuccessFactors module in sight.

Reporting and analytics are two different things that get conflated. Report Center is the reporting front end inside the suite, and story reports, which are built on SAP Analytics Cloud technology, are where SAP has been steering customers away from the older report types. Workforce Analytics proper is a separately licensed product with a curated measure library, benchmarks and workforce planning on top. If an interviewer asks when you would build a story report rather than a table report, they are checking whether you have used Report Center or only read about it.

Employee Central Payroll is the module most often misdescribed. It is not a new cloud native payroll written for SuccessFactors. 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 that gives the payroll team a process oriented view of the run. Employee Central replicates employee master data, organisational assignment and pay component data into it through point to point replication, and cost distribution flows back towards finance. Country versions are localised, India included. SAP describes all of it in the Employee Central Payroll implementation documentation and in the guide on replicating employee master data from Employee Central to Employee Central Payroll. 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.

Implementation order in real projects is fairly predictable. Employee Central goes first because it is the system of record. Then the customer chooses based on where the pain is: Recruiting and Onboarding if hiring volume is the problem, Performance and Goals followed by Compensation if the annual cycle is the problem. Learning frequently runs on its own timeline with its own budget. Succession and Development arrives once performance data is trustworthy. Workforce Analytics comes last, if at all. Employee Central Payroll only appears where SAP payroll is already part of the landscape or the country localisation is needed.

That order is also the answer to what you should learn. Employee Central has the most live instances, therefore the most support, enhancement and rollout work, therefore the most job adverts, and every other module reads its data. Learn the data models, business rules, workflows and role based permissions until you can explain them without notes, then add one talent module properly rather than skimming five. A candidate who can configure Employee Central well is employable. A candidate who can name nine modules and configure none is not.

Associate SuccessFactors consultant roles in India are advertised in the region of Rs 4-7 L in the early years, moving up substantially with implementation experience and a second module. That is market data, not a Cokonet outcome, and your own offer will depend on employer, location and prior experience. The year by year picture is in the SAP SuccessFactors salary guide.

On our own scope, plainly: the SAP SuccessFactors course at Cokonet is an Employee Central course by design. It covers the hire to retire process and the shape of the suite, then 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. It does not attempt Recruiting, Onboarding, Compensation, Learning and payroll configuration end to end in the same programme, because a course that claims all ten modules in a few months is showing you demonstrations, not teaching you configuration. The week by week breakdown is on the SAP SuccessFactors syllabus page, and the fee structure is sent to your WhatsApp with the syllabus after a quick mobile verification rather than published here, because it depends on the batch format and which instalment or scholarship option applies.

The questions people actually ask.

The three pages this guide points to.