JinJin48

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

July 19, 2026 · 17 min read

SAP SF Time Profile

Time Profile is the master data object that bundles exactly one Work Schedule with one or more Time Account Types into a single reusable unit, then gets assigned to an employee population to determine both their scheduled working-hours baseline and which leave categories they can request. It is the object where the two parallel chains of Phase 2’s Time Configuration group — Holiday Calendar → Work Schedule (SF-A03-03/04) and Time Type → Time Account Type (SF-A03-05) — actually converge into something usable at the employee level. This article covers what a Time Profile is, its bundling variants (by country/region, by leave-category coverage, by population), how it sits as the convergence point of the Time Configuration group in the same landscape zone as the parallel Permission Management chain, and every field an Admin Center consultant configures for it.

Part 1: Time Profile — Core Concepts (All Modules)#

1.1 What Is the Time Profile?#

Time Profile is a client-level configuration object that carries no scheduling or accrual logic of its own — it exists purely to bundle two already-built inputs, exactly one Work Schedule and one or more Time Account Types, into a single reusable object that can be assigned to an employee population. Neither half is meaningful to an employee in isolation: a Work Schedule without a bundled Time Account Type tells the system when someone is expected to work but nothing about their leave entitlements, and a Time Account Type without a bundled Work Schedule defines a leave balance with no working-hours baseline to measure it against. Time Profile is the point where the two parallel Time Configuration chains — Holiday Calendar → Work Schedule and Time Type → Time Account Type — converge into the one object Time Sheet and Time Off actually read for a given employee.

1.2 Time Profile Bundling Variants#

A Time Profile is a selection exercise more than a build exercise — the real design decisions are which country’s Work Schedule to bundle, and which subset of already-built Time Account Types applies to a given employee population. Treating one profile as a catch-all for every country or population is a routine cause of incorrect scheduled-hours or missing-leave-category issues that surface as employee-facing errors rather than build-time warnings.

Design principle: build a Time Profile as the country/population-specific combination point, not as a duplicate of its Work Schedule or Time Account Type variants — reuse the same building-block objects across profiles wherever the schedule and leave rules genuinely match, and only create a new Time Profile where the actual bundle differs.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Time Profile sits in the same tenant-level “Permission & Time” zone of the SuccessFactors Master Data Landscape as Permission Group / Permission Role (SF-A03-01/02), Holiday Calendar / Work Schedule (SF-A03-03/04), and Time Type / Time Account Type (SF-A03-05) — it is the fourth object group in that zone, and the only one that does not start its own configuration chain. Instead, it sits below both Time Configuration chains and draws one required input from each. The other three chains exist in the same landscape zone but belong to sibling articles:

Client (SuccessFactors Instance)
   │
   ├── Permission Group "PG_Manager" — Managers, Direct Reports  (see SF-A03-01)
   │      │
   │      └── Permission Role "PR_ESS" — Employee Self-Service, of PG_Manager  (see SF-A03-02)
   │
   ├── Holiday Calendar "HC_JP2024" — Japan 2024, 16 holidays  (see SF-A03-03)
   │      │
   │      └── Work Schedule "WS_JP_Std" — JP Standard, 40H/week, of HC_JP2024  (see SF-A03-04)
   │
   └── Time Type "TT_Annual" — Annual Leave, category  (see SF-A03-05)
          │
          └── Time Account Type "TAT_Annual" — 20 days, 5-day carryover, of TT_Annual  (see SF-A03-05)

Time Profile "TP_JP_Std" — JP Standard, Work Schedule + Time Account Type bundle
   ├── assigned to ──> Work Schedule "WS_JP_Std"
   └── assigned to ──> Time Account Type "TAT_Annual"

MANDATORY landscape verification note: the module Master.md’s ER Diagram shows Time Profile as the convergence point of both upstream chains (Work Schedule → Time Profile ←── Time Account Type), and the Master Process table’s own field list for Time Profile shows a single Work Schedule reference alongside a “Time Account Types” field that explicitly allows more than one bound record — meaning a Time Profile requires exactly one Work Schedule and one or more Time Account Type records as its bundled inputs. The published SuccessFactors Master Data Landscape (sf-a01/images/04-sf-a01-master-landscape.html, Zone C) draws this as two purple dashed “uses” arrows converging on TP_JP_Std — a LEFT bypass from WS_JP_Std and a RIGHT bypass from TAT_Annual — each representing one instance of the underlying N:1 relationship from the Time Profile side (many Time Profiles commonly reuse the same Work Schedule or the same Time Account Type, as already flagged from those objects’ own side in SF-A03-04 Section 1.3 and SF-A03-05 Section 1.3). Neither the Setup Flow nor the Hierarchy Structure in the source models any further master-data object as depending on Time Profile — its documented downstream role is profile creation, employee assignment, and leave-rule configuration, and its accompanying note describes it as configured per country/region to integrate a Work Schedule and Time Account Type(s) and assign the result to an employee. That downstream role is therefore a runtime, employee-level assignment rather than another master-data object’s build-time prerequisite; see Section 1.4 for how that assignment surfaces in practice.

Design principle: Time Profile itself has no organizational sub-levels — it is the single row where the two upstream Time Configuration chains converge into one bundle. All of its own structural complexity lives in which Work Schedule and which Time Account Type(s) it points to (Part 2), not in additional hierarchy nesting.

1.4 Integration with Other Master Data Objects#

Time Profile doesn’t stand alone — it exists solely to combine already-built Work Schedule and Time Account Type objects into the one bundle that an employee assignment, and every downstream time/leave calculation, actually resolves to.

Part 2: SF-Specific Field Details#

2.0 Scope of SF Ownership#

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

2.1 Profile Definition (Core Identification)#

Profile Definition is the minimum record a Time Profile needs to exist — it is what every employee assignment (Section 2.5), and every reference to the profile elsewhere in the system, resolves back to.

2.2 Work Schedule Binding#

Work Schedule Binding is the field group that supplies a Time Profile’s scheduled-hours half of the bundle — without a valid binding here, the Time Account Type bundle in Section 2.3 has no working-hours baseline to attach leave against.

2.3 Time Account Type Bundle#

The Time Account Type Bundle is where the actual leave taxonomy for a population gets decided — this is the section that differentiates otherwise-similar Time Profiles more than any other field group in the object.

2.4 Country / Region Scope#

Country / Region Scope documents which jurisdiction a Time Profile is built for — a thin field group by count, but the one most consultants get burned by skipping, since it is a documentation convention rather than a system-enforced constraint.

2.5 Usage in Employee Assignment#

A Time Profile performs no employee-level calculation on its own — it only becomes meaningful once assigned to an individual employee. This section covers how that assignment works and where the most common maintenance gaps occur.

Prerequisite: because a Time Profile edit affects every employee already assigned to it, and a reassignment can strand an in-flight leave request against a Time Account Type no longer in the new bundle, always review current employee assignments and any open Time Sheet / Time Off transactions before editing a live Time Profile’s Work Schedule or Time Account Type bundle, or moving an employee to a different one.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction