JinJin48

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

July 19, 2026 · 11 min read

SAP SF Location

Location is a physical/geographic work-location master data object in SuccessFactors Employee Central, configured within Phase 1 (Organization & Job Foundation) alongside the Legal Entity → Business Unit → Division → Department → Cost Center chain — but it deliberately sits outside that chain: it is a separate, cross-cutting foundation object that Position and Job Information reference directly, describing addresses, time zones, and holiday calendar assignment for every physical site the organization operates from. This article covers what Location is, how its cross-cutting placement differs from the organizational hierarchy chain, and every field an Employee Central consultant configures for it.

Part 1: Location — Core Concepts (All Modules)#

1.1 What Is the Location?#

Location is the master data object that anchors a physical or geographic work site — an office, plant, warehouse, or remote-work designation — with the address, time zone, and holiday calendar that everything scheduled or reported against that site depends on. Where Department answers “which team,” Location answers “which physical place,” and the two are deliberately independent: a single Department’s employees can sit across several Locations, and a single Location can host employees from many different Departments.

1.2 Location Types#

Location Type is not a structural code the way Legal Entity’s country or Cost Center’s category is — it is descriptive classification a client sets up to segment reporting and to signal which Holiday Calendar and facilities pattern a given site is expected to carry. Getting the type wrong mostly costs reporting clarity, not data-model breakage, but it is still worth deciding consistently at blueprint.

Design principle: Location Type is descriptive metadata, not a behavioral switch — it does not change how a Location record functions in the data model, but it drives which Holiday Calendar and reporting segment a Location is expected to carry, so keep the type list short and consistently applied across all Locations.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Client (SuccessFactors Instance)
   │
   ├── Legal Entity "LE_JP01" ── Business Unit ── Division ── Department ── Cost Center
   │      (organizational hierarchy chain — see SF-A02-01 through SF-A02-05)
   │
   └── Location "LOC_TKY01" — Tokyo HQ, Asia/Tokyo TZ
          (independent tenant-level master — not a level in the chain above)
          │
          ├── assigned to ──> Location Group "LG_JP" — Japan Locations (grouping/classification)
          ├── assigned to ──> Holiday Calendar "HC_JP2024" — Japan 2024 holidays
          └── referenced by <── Position "POS_SalesMgr01" — Sales Manager (default work location)

Design principle: Location does not sit inside the Legal Entity → Business Unit → Division → Department → Cost Center chain — it is a separate, cross-cutting foundation object that Position and Job Information reference directly, independent of which Department or Cost Center an employee belongs to. A single Location, such as a shared regional office, is commonly referenced by employees across many different Departments and Cost Centers at once.

1.4 Integration with Other Master Data Objects#

Because Location sits outside the organizational hierarchy chain, its relationships to other master data are all direct references rather than parent-child hierarchy links — every object below points to Location, or Location points to it, with no intermediate level in between.

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 Location needs to exist — it is what every Position, Job Information override, and Location Group reference points to.

2.2 Address & Geography#

Address & Geography fields describe the physical site itself — they feed statutory reporting, facilities/mail routing, and any geolocation-based dashboards built on top of People Analytics.

2.3 Time Zone & Holiday Calendar#

These fields make Location the site consultants configure once and every downstream time-related process — approvals, notifications, accrual calculations — reads from indirectly.

2.4 Location Group & Classification#

Location Group and Location Type are the two classification dimensions consultants set up to make large Location lists usable in reporting and picklists, without relying on the organizational hierarchy chain.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction