JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 10 min read

SAP SF Legal Entity

Legal Entity is the top-level organizational master data object in SuccessFactors Employee Central — it represents the legal, tax-registered entity (typically a company or subsidiary) that employs staff and anchors every level of the organizational hierarchy below it. Every Business Unit, Division, Department, and Cost Center that a consultant configures is ultimately assigned to exactly one Legal Entity, and every Employment record references a Legal Entity as the employee’s legal employer. This article covers what Legal Entity is, how it sits in the broader hierarchy, and every field an Employee Central consultant configures.


Hub-and-spoke diagram showing Legal Entity at center, connected to Business Unit, Employment, and S/4HANA Company Code

Legal Entity is a foundation object — the highest level of the SuccessFactors organizational structure. It does not represent a reporting line or a team; it represents the actual legal/statutory registration under which employees are hired, paid, and reported to authorities. Everything below it (Business Unit, Division, Department, Cost Center) exists to organize people and cost within the boundary that Legal Entity defines.

AspectDetails
RoleRoot of the organizational hierarchy; the legal/statutory employer boundary that every Employment record references
Modules using itEmployee Central (owner — foundation object framework), Employee Central Payroll (groups payroll runs by legal employer for statutory reporting), Recruiting/Onboarding (job requisitions and new hires typically inherit the Legal Entity of the hiring organization)
TransactionsAdmin Center → “Manage Organization, Pay and Job Structures” (create/edit foundation object records); “Import and Export Data” (mass load via CSV); Business Rules can auto-derive Legal Entity from other Employment fields
Key TablesOData API entity FOLegalEntity (Foundation Object) — SuccessFactors has no classic ABAP table; each record is effective-dated rather than table-row based
S/4HANA noteLegal Entity is commonly mapped 1:1 to an S/4HANA FI Company Code. It can be created natively in SuccessFactors or synced inbound from S/4HANA — the sync direction is a blueprint decision (see 1.2)

2x2 matrix comparing S/4HANA-synced vs SF-native, and Operating vs Holding Legal Entity patterns

Legal Entity is not selected from a fixed SAP type code the way a purchasing document type is — but every implementation still has to decide two independent dimensions before go-live: where the record is mastered, and whether the entity actually employs people.

PatternMarkerUse CaseKey Behavior
S/4HANA-Synced Legal EntityExternal SyncClient already runs FI Company Code in S/4HANA/ECCLegal Entity is created and maintained via inbound integration from S/4HANA; manual edits in SuccessFactors are typically restricted or get overwritten on the next sync run
SuccessFactors-Native Legal EntityNativePure-cloud HR deployment, or an entity that exists only for HR purposes (e.g. an HR shared-service company with no FI counterpart)Legal Entity is created and maintained directly in Employee Central Admin Center; no downstream FI dependency
Operating Legal EntityOperatingEntity directly employs staffHas active Employment records against it; drives payroll country/legal grouping and statutory reporting
Non-Operating / Holding Legal EntityHoldingEntity exists for corporate/legal structure completeness only (e.g. a holding company with no direct headcount)Configured in the picklist but rarely or never referenced by an Employment record; used only so the org chart reflects the real legal structure

Design principle: Decide the sync direction (S/4HANA-synced vs. SF-native) once, at blueprint. Flipping an existing Legal Entity from native to synced later requires a data reconciliation project, since the External Code / Company Code mapping becomes the system-of-record key going forward.


1.3 Organizational Levels and Data Hierarchy

Zone crop from the SuccessFactors Master Data Landscape showing Zone A — Legal Entity at the top of the Organization Foundation hierarchy

Data hierarchy with a concrete example

Client (SuccessFactors Instance)
   │
   └── Legal Entity "LE_JP01" — Japan Legal Entity, Company Code JP01
          │
          ├── Business Unit "BU_Sales" — Sales HQ, of LE_JP01
          │      │
          │      └── Division "DIV_East" — East Japan, of BU_Sales
          │             │
          │             └── Department "DEPT_S01" — Sales Team 1, of DIV_East
          │                    │
          │                    └── Cost Center "CC_1000" — Sales cost center, of DEPT_S01
          │
          └── (external sync) ──> S/4HANA FI Company Code "JP01"

Location "LOC_TKY01" — Tokyo HQ, Asia/Tokyo TZ
   (independent tenant-level master — not nested under Legal Entity)

Employment "EMP_000001" (Employee Central) ── assigned to ──> Legal Entity "LE_JP01"
   (every hire's Employment record references exactly one Legal Entity as legal employer)

Design principle: Legal Entity → Business Unit → Division → Department → Cost Center is a strict single-parent chain — every object below Legal Entity must resolve to exactly one Legal Entity at the top, with no cross-entity sharing.


1.4 Integration with Other Master Data Objects

Hub-and-spoke showing Legal Entity at center connected to Business Unit, Employment, S/4HANA Company Code, Location, and Cost Center

Legal Entity does not stand alone — it is the anchor that every other organizational and employee-data object ultimately references, directly or indirectly.

ObjectRelationshipPractical Notes
Business UnitDirect child (1:N) — every Business Unit must belong to exactly one Legal EntityThe first and only mandatory step below Legal Entity when Business Unit is enabled; if Business Unit is not used, Division/Department attach one level higher
EmploymentEmployment record references Legal Entity as the legal employerDetermines the statutory reporting group and, in Employee Central Payroll deployments, the payroll country grouping for the employee
S/4HANA FI Company CodeExternal sync source/target — Legal Entity commonly mirrors an S/4HANA Company Code 1:1Keeps the HR legal-entity structure aligned with the FI company code, which matters for headcount cost allocation and consolidated statutory reporting
LocationIndependent tenant-level master, frequently co-referenced on the same employeeEmployees are typically assigned both a Legal Entity (via Employment) and a Location (via Job Information) — the two dimensions are maintained separately and answer different questions (“who employs this person” vs. “where do they physically work”)
Cost CenterIndirect, via the Business Unit → Division → Department → Cost Center chainLegal Entity does not directly own Cost Center, but every Cost Center ultimately rolls up to one Legal Entity through the org hierarchy — relevant when building headcount cost reports segmented by legal entity

Part 2: SF-Specific Field Details

2.0 Scope of SF Ownership

Checklist showing Employee Central ownership across Legal Entity data sections: Identification, Company/Country, Currency, Status, S/4HANA Integration

Data SectionSF InvolvementNotes
Core Identification◎ OwnerExternal Code, Name, Effective Start Date
Company & Country Assignment◎ OwnerCompany Code, Country/Region
Currency & Reporting Defaults◎ OwnerDefault Currency used for compensation and budget defaults
Status & Lifecycle◎ OwnerActive/Inactive status, effective-dated change history
S/4HANA Company Code Integration○ Shared with FI/BasisExternal Code mapping, sync direction, sync frequency

Legend: ◎ = Owner / Critical, ○ = Direct involvement


2.1 Core Identification

Checklist of key Legal Entity core identification fields: External Code, Name, Effective Start Date, Effective-Dated record chain

Core Identification is the minimum record a Legal Entity needs to exist — it is what every other foundation object references when it points “up” to a Legal Entity.

FieldDescriptionPractical Usage
External CodeUnique identifier for the Legal EntityThe key value every downstream reference (Business Unit, Employment, integration payloads) points to. Should be decided once with the integration team — changing it after go-live breaks any middleware mapping keyed on the old value.
NameDisplay name of the Legal EntityLocalizable per language pack in a global instance. Keep the naming convention consistent with the FI Company Code short text when synced, so HR and Finance teams recognize the same entity across systems.
Effective Start DateDate this version of the record becomes activeEvery field change is captured as a new effective-dated row, not an overwrite. This is what allows an org-chart-as-of-date query to reconstruct historical structure — critical for audit and year-end reporting.
Effective-Dated HistoryChain of prior versions of this Legal Entity recordUsed to answer “what was this entity’s status/name/currency on date X.” Consultants should avoid deleting history rows; correct forward with a new effective-dated entry instead.

2.2 Company & Country Assignment

Checklist of Legal Entity company and country fields: Company Code, Country/Region

This section ties the Legal Entity record to the statutory/regulatory context it operates under, and is the field pair most frequently reconciled against S/4HANA.

FieldDescriptionPractical Usage
Company CodeThe company/legal-entity code, typically mirroring the S/4HANA FI Company CodeThe single most important reconciliation field for S/4HANA-synced deployments. During blueprint, confirm whether this field is inbound-only (from S/4HANA) or maintained natively — mixing both leads to conflicting updates.
Country/RegionStatutory country of registrationDrives which country-specific Employee Central business rules, picklists, and (in Employee Central Payroll deployments) payroll country grouping apply to employees assigned to this Legal Entity.

2.3 Currency & Reporting Defaults

Checklist of Legal Entity currency fields: Default Currency and downstream compensation/budget defaults

Currency set at the Legal Entity level becomes the fallback default for compensation, budget, and reporting objects assigned underneath it, unless overridden lower in the hierarchy.

FieldDescriptionPractical Usage
Default CurrencyBase currency for the Legal EntityUsed as the default currency proposal on Compensation Information and Budget records for employees/departments under this Legal Entity. In multi-country instances, confirm with the Compensation team whether local-currency override is required at Department or Employment level.

2.4 Status & Lifecycle

Checklist of Legal Entity status and lifecycle fields: Status, effective-dated deactivation, downstream impact

Status governs whether a Legal Entity is available for new assignments — this section is where consultants handle entity closures, mergers, and reorganizations.

FieldDescriptionPractical Usage
StatusActive / Inactive flagSetting a Legal Entity Inactive does not terminate existing Employment records — it only blocks the entity from being selected on new records going forward. Deactivation should always be effective-dated to match the actual legal closure/merger date, not the date the admin makes the change in the system.
Deactivation ImpactDownstream effect of an Inactive Legal EntityBefore deactivating, check for any Business Unit, Department, or open Employment record still pointing to the entity — those need to be re-pointed to the surviving Legal Entity first in an M&A or restructuring scenario.

2.5 S/4HANA Company Code Integration

Stack layered diagram showing the S/4HANA Company Code to SuccessFactors Legal Entity sync flow: mapping, direction, frequency

For clients running S/4HANA FI alongside SuccessFactors Employee Central, Legal Entity is typically the first foundation object reconciled between the two systems, since Company Code is a hard prerequisite for FI postings.

FieldDescriptionPractical Usage
External Code MappingCross-reference between SuccessFactors External Code and the S/4HANA Company Code valueConfirm during blueprint whether the two codes are identical strings or require an explicit mapping table — identical values dramatically simplify every downstream integration (payroll, cost allocation, reporting).
Sync DirectionWhether S/4HANA is the system of record (inbound to SF) or SuccessFactors is (outbound to S/4HANA)Most implementations treat S/4HANA FI as the system of record for Company Code/Legal Entity, since statutory entity creation is a Finance-led, not HR-led, event. Confirm ownership explicitly to avoid both teams maintaining the same entity independently.
Sync FrequencyBatch (scheduled) vs. near-real-time replicationTypically delivered via SAP-provided integration content (e.g. Employee Central to S/4HANA master data replication) or custom middleware. Batch-only sync means a newly created S/4HANA Company Code is not immediately usable in Employee Central — plan hire dates around the sync schedule during go-live cutover.

L1) Big Picture

IDCategoryTitle
sf-001OverviewWhat is SAP SuccessFactors?

L2-A) Master Data

IDCategoryTitle
sf-a01OverviewSAP SuccessFactors Master Data: Overview, Hierarchy & Relationships
sf-a02-01Master DataSAP SF Legal Entity 📍
sf-a02-02Master DataSAP SF Business Unit
sf-a02-03Master DataSAP SF Division
sf-a02-04Master DataSAP SF Department
sf-a02-05Master DataSAP SF Cost Center
sf-a02-06Master DataSAP SF Location
sf-a02-07Master DataSAP SF Job Family
sf-a02-08Master DataSAP SF Job Code
sf-a02-09Master DataSAP SF Pay Grade
sf-a02-10Master DataSAP SF Position
sf-a03-01Master DataSAP SF Permission Group
sf-a03-02Master DataSAP SF Permission Role
sf-a03-03Master DataSAP SF Holiday Calendar
sf-a03-04Master DataSAP SF Work Schedule
sf-a03-05Master DataSAP SF Time Type
sf-a03-06Master DataSAP SF Time Profile
sf-a03-07Master DataSAP SF Rating Scale
sf-a03-08Master DataSAP SF Goal Plan Template
sf-a03-09Master DataSAP SF Performance Form Template
sf-a03-10Master DataSAP SF Route Map
sf-a03-11Master DataSAP SF Compensation Plan
sf-a04-01Master DataSAP SF Person
sf-a04-02Master DataSAP SF Employment
sf-a04-03Master DataSAP SF Employee Profile

L2-B) Transaction

IDCategoryTitle
sf-b01OverviewSAP SuccessFactors Transactions: Process Flow, Hierarchy & Relationships