JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

July 18, 2026 · 10 min read

SAP SF Business Unit

Business Unit is the second-level organizational master data object in SuccessFactors Employee Central, sitting directly below Legal Entity and directly above Division in the standard organizational chain. It groups the Divisions, Departments, and Cost Centers of a Legal Entity into a major business line or region — for example, a Sales headquarters, a Manufacturing arm, or a regional operating unit. Every Division that a consultant configures (when the Business Unit level is enabled) is ultimately assigned to exactly one Business Unit. This article covers what Business Unit is, how it sits in the broader hierarchy, and every field an Employee Central consultant configures.

Part 1: Business Unit — Core Concepts (All Modules)#

1.1 What Is the Business Unit?#

Business Unit is a foundation object one level below Legal Entity — it does not represent the legal/statutory employer boundary itself, but the first major internal grouping underneath it. Where Legal Entity answers “who is the legal employer,” Business Unit answers “which major line of business, or region, does this part of the organization belong to.” Division, Department, and Cost Center are then nested beneath it to further subdivide that grouping.

1.2 Business Unit Configuration Patterns#

Business Unit is not selected from a fixed SAP type code — but every implementation still has to decide two independent dimensions before go-live: the design axis the level is organized around, and whether the level is used at all.

Design principle: Decide the design axis (functional vs. regional) and whether the level is enabled once, at blueprint. Every Division created afterward inherits that axis — retrofitting either decision later means re-parenting every Division under new Business Unit codes.

1.3 Organizational Levels and Data 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 Organizational Management (Org Unit / Business Area)

Design principle: Business Unit → Division → Department → Cost Center is a strict single-parent chain below Legal Entity. When the Business Unit level is bypassed (see 1.2), Division attaches directly to Legal Entity instead — but the chain below whichever level is used remains single-parent throughout.

1.4 Integration with Other Master Data Objects#

Business Unit does not stand alone — it is the mandatory upward link to Legal Entity and the mandatory downward grouping for everything organized beneath it.

Part 2: SF-Specific Field Details#

2.0 Scope of SF Ownership#

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

2.1 Core Identification#

Core Identification is the minimum record a Business Unit needs to exist — it is what every Division that belongs to it references when it points “up” to a Business Unit.

2.2 Legal Entity Assignment#

This section ties the Business Unit record to its parent Legal Entity and to the display/ownership attributes consultants set for org chart purposes.

2.3 Status & Lifecycle#

Status governs whether a Business Unit is available for new assignments — this section is where consultants handle reorganizations, mergers, and business-line closures.

2.4 S/4HANA Integration#

For clients running S/4HANA HR/OM alongside SuccessFactors Employee Central, Business Unit reconciliation is less standardized than Legal Entity’s, since S/4HANA has no single dedicated “Business Unit” object.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction