JinJin48

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

July 16, 2026 · 11 min read

SAP IBP Time Profile

A Time Profile is the configuration object that defines the time dimension of planning in SAP IBP — the ordered, non-overlapping sequence of period buckets (day, week, month, and so on) that every Planning Area’s planning views are ultimately expressed in. It sits in the same Phase 1 Master Data Foundation tier as Master Data Type and Attribute, but runs independently of both: Time Profile has no prerequisite of its own, and unlike Attribute it does not feed Planning Level — it feeds Planning Area directly. This article maps the standard period types Time Profile supports, its internal level hierarchy, and the field-level detail of the Manage Time Profiles app used to configure it.

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

1.1 What Is the Time Profile?#

A Time Profile is not planning data itself — it is the structural definition of the timeline that planning data is later recorded against. Conceptually it plays the role a calendar/fiscal-period table plays in any planning system: it does not hold a single demand or supply number, but every number recorded downstream is stamped against one of its periods. Every Planning Area must have exactly one Time Profile assigned before it can be activated, which is why Time Profile design is typically finalized early, alongside Master Data Type and Attribute, in Phase 1 of a model build.

1.2 Standard Period Types#

SAP IBP supports six standard period types out of the box, and picking the wrong base granularity for a planning process is expensive to correct — every level in a Time Profile is built from one of these six, and levels feeding an already-active Planning Area cannot be swapped without regenerating the profile and re-pointing everything built on it.

Design principle: SAP IBP also supports fiscal periods, but unlike the six standard period types above, fiscal periods must be loaded manually rather than generated automatically — factor this into the data-load plan whenever a design calls for fiscal-calendar-aligned Quarter/Year buckets.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Client (SAP IBP tenant / Model)
   │
   ├── Master Data Type "MDT-PROD" — Simple · Product          (Zone A sibling — see IBP-A02-01)
   │
   └── Time Profile "TP-WEEKLY" — Weekly granularity
          ├── Level 0 "WEEK" — most granular level
          │      Default Display Horizon: 0 to 104 (current week + 104 weeks ahead)
          ├── Level 1 "MONTH" — aggregates WEEK
          │      Default Display Horizon: -6 to 24 (6 months history + 24 months ahead)
          └── Level 2 "QUARTER" — aggregates MONTH
                 Default Display Horizon: -4 to 8 (4 quarters history + 8 quarters ahead)

Design principle: Time Profile sits at the same tenant-level, Phase 1 tier as Master Data Type and Attribute — it exists independently of any single Planning Area and, per internal design guidance, is typically standardized and shared across every Planning Area built on that Time Profile’s cadence, rather than recreated per Planning Area (Section 2.4).

1.4 Integration with Other Master Data Objects#

A Time Profile never stands alone — it is one of the direct inputs a Planning Area assembles, alongside Key Figure and Planning Level, but it takes an entirely separate path to get there from those other two objects.

Part 2: IBP-Specific Field Details#

2.0 Scope of IBP Ownership#

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

2.1 General Time Profile Definition#

Every Time Profile — regardless of the levels it contains — starts from the same short identification screen in the Manage Time Profiles app (New → enter ID → select levels → Name/Description → Start/End Date → Save). These fields are entered once at creation and are the foundation the level configuration in Section 2.3 is layered on top of.

2.2 Time Profile Settings#

These settings govern the overall scope of the Time Profile as a whole, on top of the identification fields entered in Section 2.1.

2.3 Time Profile Level Configuration#

A Time Profile is built from a hierarchy of levels — most granular first — where a period on a lower level rolls up to exactly one parent period on the next level up, and the timeline at every level must be continuous with no gaps and no overlaps. Creating a custom Time Profile follows a fixed sequence in the Manage Time Profiles app: choose New, select the required levels, enter an ID and descriptive name, set Start/End Date, configure each level’s name and Default Display Horizon, then save and activate.

Two more advanced level-hierarchy capabilities — a “Rolling Time Profile Level” mode and technical PERIODID(n) attributes used in formula/Key Figure calculations — exist as distinct SAP Help Portal topics but sit outside the scope of a field-level master data reference. Their mechanics could not be independently verified for this article; consult the SAP Help Portal’s dedicated topics directly before configuring either one.

2.4 Governance & Sharing#

Because a Time Profile can outlive and outgrow the single Planning Area it was first built for, SAP IBP’s own design guidance and practitioner experience both push toward standardizing rather than duplicating.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction