Field-level sap successfactors to oracle fusion mapping for every entity that matters: PerPerson → HcmWorker, EmpJob → Assignment, EmpCompensation → Salary, FOLocation → Fusion Location. Pre-built crosswalks, effective-dated alignment, customer-reviewed sign-off.
It's not a one-page Excel file. Real sap successfactors to oracle fusion mapping is a sized, governed crosswalk catalog spanning standard EC entities, Foundation Objects, MDF custom objects, RBP roles, talent forms, comp plans, recruiting reqs and learning records.
SAP SuccessFactors is a cloud HXM platform with deep configurability: hundreds of standard fields across PerPerson, PerEmployment, EmpJob and EmpCompensation; Foundation Objects (FOLocation, FOCompany, FODepartment, FOPayGrade, FOCostCenter) that drive workstructure; an MDF custom-object framework that customers extend extensively; and module-specific entities for Performance, Compensation, Recruiting, Onboarding and Learning. Each of these has a place in the sap successfactors to oracle fusion mapping deliverable.
Syntra ETL ships pre-built field crosswalks for every standard EC and module entity, auto-generates discovery crosswalks for FOs and MDF objects from your tenant content, and lets HRIS / HR ops / compliance leads review and adjust before any data moves. The crosswalk catalog becomes the contract between EC and Fusion — and the evidence pack at cutover.
Whether you are doing a Big Bang full-module migration or a phased EC-first / Talent-second / Recruiting-third sequence, the mapping discipline is the same: every EC field has an explicit destination in Fusion (or an explicit retire decision), and every transformation rule is documented and replayable.
Every layer addressed in the crosswalk catalog. Nothing left as an open question at cutover.
PerPerson → HcmWorker (PersonNumber from personIdExternal), PerPersonal → Person Names + National IDs, PerEmail/PerPhone → Person Email/Phone, PerEmployment → Work Relationship with hire-date, original-hire-date, employer continuity preserved.
EmpJob → Assignment with Department, Job, Location, Manager-Chain, Position, FTE, employment status. EC Position MDF → Fusion Position when running position-managed. Effective-dated row count matched 1:1.
EmpCompensation → Salary basis + annualized comp. EmpPayCompRecurring → Element Entry with element-type and input-value crosswalk. EmpPayCompNonRecurring → non-recurring Element Entry. Currency + frequency preserved.
FOLocation → Location, FOCompany → Legal Employer + LE, FODepartment → Department, FOPayGrade → Grade, FOCostCenter → Cost Center, FOBusinessUnit → BU. Hierarchies translated parent-child in dependency order.
Performance forms → Talent Review history / archive, CompPlan → Workforce Compensation Plan, JobReq → Oracle Recruiting Requisition, Application → Job Application, Learning history → Oracle Learning Cloud or analytical archive.
Every MDF custom object inventoried, classified, and routed: DFFs for simple extensions, EFFs for multi-row, module-specific custom fields for module data, analytical archive for reporting-only. Effective-dated MDF preserved.
A five-stage flow that delivers a customer-approved mapping catalog before any production extract runs.
Discovery engine catalogs every active EC entity, every Foundation Object record, every MDF custom object definition, every RBP role, every active picklist with value count. Output: complete tenant inventory spreadsheet with row counts and last-modified timestamps.
Syntra ETL's standard EC ↔ Fusion HCM field crosswalk catalog is overlaid onto your tenant inventory. Standard fields pre-mapped; tenant-specific extensions flagged for review; FO content auto-mapped to Fusion workstructure with proposed names.
HRIS, HR ops, payroll, talent and compliance leads review the crosswalk in workshops. MDF custom objects classified for routing. RBP-to-Fusion-role translation proposed and refined. Mapping decisions logged with rationale.
Final crosswalk catalog signed off by HRIS lead and business sponsor. From this point, all transformation rules in the ETL platform reference the signed crosswalk — no silent changes.
ETL transform layer reads the signed crosswalk catalog as configuration (not code), applies it to every extracted record, produces HDL DAT files for Fusion HCM. Any field not in the crosswalk fails-fast and triggers a back-to-mapping conversation.
At cutover, the signed crosswalk + per-entity row-count reconciliation + sample-record diff + current-state-snapshot match against EC Compound Employee API become the formal evidence pack archived for SOX / audit.
The things that look like 80/20 simple mappings but consume the last 20% of the project if not addressed up front.
EC stores country-specific fields (e.g., Korean RRN, Japanese furigana, German tax class) on local-extension entities. Fusion stores them on country-specific person extensions. Mapping routes each local field to the right Fusion table.
EC effective-date semantics (begin-date inclusive) align with Fusion (EFFECTIVE_START_DATE inclusive, EFFECTIVE_END_DATE inclusive). Mapping handles the date-banding so no gap or overlap rows appear in Fusion.
Workers re-hired in EC create a new PerEmployment with continuity to prior employment. Mapping handles original-hire-date, service-date, work-relationship-id continuity correctly in Fusion.
EmpCompensation often stores comp in multiple currencies (local + corporate). Mapping preserves both, with Salary in local currency and analytical comp in corporate currency for reporting.
PerNationalId records (SSN, NI, RRN, BSN) require Fusion's encrypted person-national-id storage. Mapping handles encryption-at-rest and access-restriction policies during HDL load.
EC picklists (employment type, marital status, ethnicity) have customer-specific external codes. Mapping translates each EC picklist value to the corresponding Fusion lookup code, with stale-value handling.
The canonical sap successfactors to oracle fusion mapping for the core worker record routes SuccessFactors PerPerson → Oracle Fusion HCM Person (HZ_PARTIES / HRC_PERSON), PerPersonal → Person Names + Person National Identifiers, PerEmail / PerPhone → Person Email / Person Phone, PerEmployment → Work Relationship, EmpJob → Assignment (with Department, Job, Location, Manager, Position references), EmpCompensation → Salary, EmpPayCompRecurring → Element Entry. Each EC effective-dated version row translates into a corresponding Fusion effective-dated row keyed by EFFECTIVE_START_DATE / EFFECTIVE_END_DATE. The PerPerson personIdExternal becomes the Fusion PersonNumber, and a stable EC-to-Fusion person GUID cross-reference table is persisted in the staging warehouse for re-runs.
Foundation Objects (FOs) are SuccessFactors' workstructure backbone, and the sap successfactors to oracle fusion mapping for them is one of the most rigorous parts of the project. FOLocation maps to Fusion HCM Location (PER_LOCATIONS_V) with address, timezone and operating-unit ties. FOCompany maps to Legal Employer + Legal Entity, with statutory registration numbers preserved as legal-entity identifiers. FODepartment maps to Fusion Department, with multi-level hierarchies translated into parent-child PER_DEPARTMENTS rows. FOPayGrade maps to Grade with grade-step ladder. FOCostCenter maps to Cost Center (linked into the Fusion accounting flexfield). FOBusinessUnit maps to Fusion Business Unit. The crosswalks are auto-generated from FO content and human-reviewed before workstructure load.
SuccessFactors stores compensation across EmpCompensation (annualized comp containers) and EmpPayCompRecurring / EmpPayCompNonRecurring (individual pay components like base salary, allowances, car allowance, market premium, signing bonus). The sap successfactors to oracle fusion mapping routes EmpCompensation → Fusion Salary record, with annualized amount and currency landing on the Salary basis. Each pay component in EmpPayCompRecurring becomes a Fusion Element Entry with element type, input-value mapping, effective-date alignment and proration rules. EmpPayCompNonRecurring (one-time payments) routes to non-recurring Element Entries. Pay-component codes are crosswalked to Fusion element names through a customer-reviewed mapping file generated from EC content. Currency and frequency conversions are preserved.
SuccessFactors uses the Position MDF object as the optional position-management overlay on EmpJob assignments. The sap successfactors to oracle fusion mapping for position management depends on whether the target Fusion implementation runs position-managed (typical for public sector, regulated industries, large enterprises) or position-as-suggestion. In position-managed mode, the EC Position → Fusion Position mapping preserves position-to-position hierarchy, position-to-job classification, position FTE, position cost-allocation, position incumbent history. In suggestion mode, position attributes collapse onto the Fusion assignment. Either approach is supported, with the choice driven by the target HCM design and approved during the crosswalk-design phase in weeks 2–4 of the project.
SuccessFactors FOLocation stores address as a typed-address structure with address1, address2, city, state (country-specific picklist), zipCode, country (ISO code) and timezone. Oracle Fusion HCM Location uses HZ_LOCATIONS underneath, which is structured but country-specific. The sap successfactors to oracle fusion mapping for FOLocation normalizes the EC address into the Fusion HZ_LOCATIONS country-specific structure, validates the country code (ISO-2 → Fusion territory code), maps the state to Fusion's state validation table, and preserves the timezone. Addresses that don't pass Fusion territory-rule validation are flagged in the row-level error report so HR ops can correct upstream in EC before the next extract — typical correction rate is 0.5–2% of FOLocation records.
The sap successfactors to oracle fusion mapping for SF Recruiting Management (RCM) routes JobReq → Oracle Recruiting Cloud Requisition with reqId → External Requisition Identifier, jobReqLocale → Locale, jobTitle → Posting Title, internalJobDescription / externalJobDescription → Internal/External Description, departmentCode → Department, locationCode → Primary Location, hiringManager → Hiring Manager. Application → Job Application with application status crosswalked to Fusion phase/state. Candidate → Talent Profile with skills, education, work experience. Offer letter content migrates as historical document attachments, while live offer flows cut over to the Fusion Offers module. JobReq custom fields are inventoried and routed to Fusion DFFs on requisition with full audit-trail preservation.
Validation of the sap successfactors to oracle fusion mapping for EmpJob → Assignment runs at multiple levels. First, every EmpJob effective-dated row produces exactly one corresponding Fusion Assignment effective-dated row — row count must match. Second, the as-of-today Fusion assignment slice must match the EC current-state Compound Employee snapshot for the same employee on department, job, location, manager, position, FTE, employment status. Third, the Fusion HCM hierarchy walk (manager-chain, department-chain) must reproduce the EC org chart at a randomly sampled depth of 1,000 nodes. Fourth, statutory headcount queries (active employees by legal employer by country) must match EC headcount to the exact employee within 0.1%. The validation pack is delivered as the cutover sign-off evidence.
Yes. MDF (Metadata Framework) custom objects — SuccessFactors' extensibility layer — are inventoried in the discovery phase and classified by reporting materiality, transactional volume, and effective-dating pattern. For each MDF object the sap successfactors to oracle fusion mapping decides: route to Fusion DFF on Worker / Assignment / Person if simple attribute extension; route to Fusion EFF (Extensible Flexfield) if multi-row attribute set; route to an Oracle Recruiting / Compensation / Talent custom field if module-specific; or route to the analytical archive if reporting-only and not needed in live Fusion transactions. Effective-dated MDF objects preserve their version-row history through the same date-banded model used for EmpJob and EmpCompensation.
Book a 30-minute discovery call. We'll walk through your EC entities, Foundation Object footprint and MDF custom-object inventory — and show you the pre-built crosswalk catalog applied to your data.