JinJin48

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

July 19, 2026 · 15 min read

SAP SF Goal Plan Template

Goal Plan Template is the master data object that defines a reusable, versioned goal-plan structure — goal categories (e.g. Performance / Behavior / Growth), per-category weighting, cascading rules, and the Rating Scale used to score goal achievement — used throughout SAP SuccessFactors Performance & Goals to shape what an employee’s actual live goal plan for a given cycle looks like. It sits directly downstream of Rating Scale and directly upstream of Performance Form Template in the Goal & Performance Configuration sub-block of Phase 2 (Permission & System Configuration): a Goal Plan Template cannot be built until its Rating Scale exists, and any Performance Form Template that includes a Goal section lists Goal Plan Template as one of its two direct prerequisites. This article covers what a Goal Plan Template is, its common cadence and cascading variants, how it sits in the Rating Scale → Goal Plan Template → Performance Form Template chain in the Talent & Compensation zone of the landscape, and every field an Admin Center consultant configures for it.

Part 1: Goal Plan Template — Core Concepts (All Modules)#

1.1 What Is the Goal Plan Template?#

Goal Plan Template is a client-level (tenant-level) foundation object that carries no employee data of its own — an individual employee’s actual goals live in a separate, instantiated Goal Plan record, not in the template. The template’s sole purpose is to define the reusable shape (categories, weighting rules, cascading behavior, field layout, and scoring reference) that every employee’s goal plan for a given cycle is generated from, so that goal-setting is structurally consistent across an entire population rather than freeform per manager.

1.2 Goal Plan Template Variants (Cadence and Cascading Patterns)#

A Goal Plan Template’s cadence and cascading design are not cosmetic choices — they directly shape how tightly individual goals stay aligned to organizational strategy and how much administrative overhead the template design creates across a review cycle. Getting cascading permissions or cadence wrong either produces goal plans disconnected from business priorities or an unmanageable re-issuance burden.

Design principle: choose cascade behavior and goal-category structure deliberately at blueprint — like Rating Scale, changing a Goal Plan Template’s category count, weighting, or cascade setting after goals are already live for a cycle risks orphaning already-set goals or breaking weighting totals mid-cycle.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Goal Plan Template sits in the tenant-level “Talent & Compensation” zone of the SuccessFactors Master Data Landscape, in the middle position of one of two independent client-level chains bundled into that zone (the Talent chain this article covers, and a parallel, unrelated Compensation chain owned by a sibling article):

Client (SuccessFactors Instance)
   │
   ├── Rating Scale "RS_5pt" — 5-level, 1 = Below Expectations – 5 = Outstanding
   │      │
   │      └── Goal Plan Template "GPT_2024" — FY2024, Performance/Behavior/Growth categories, of RS_5pt  ← this article
   │             │
   │             └── Performance Form Template "PFT_Annual2024" — Annual Review, 4-section, of GPT_2024
   │
   └── Compensation Plan "CP_Merit2024" — Merit 2024, 3% budget  (Compensation chain, see SF-A03-11)
          │
          └── Compensation Template "CT_Merit" — Merit, 0-6% range, of CP_Merit2024
                 │
                 └── Eligibility Rule "ER_FT1Y" — Full-time, 1+ year, of CT_Merit

MANDATORY landscape verification note: the module Master.md’s ER Diagram nests Goal Plan Template and Performance Form Template as parallel 1:N siblings, both branching directly off Rating Scale, with no connector drawn between Goal Plan Template and Performance Form Template at all. The published SuccessFactors Master Data Landscape (sf-a01/images/04-sf-a01-master-landscape.html, Zone D, verified directly against the HTML/SVG source this session) resolves this differently: it draws a single serial solid chain RS_5pt → GPT_2024 → PFT_Annual2024, using the same connector style and stroke weight for both the Rating Scale → Goal Plan Template and the Goal Plan Template → Performance Form Template segments. This is consistent with the Setup Flow’s explicit dual-prerequisite line “Performance Form Template ← (Rating Scale, Goal Plan Template)” — Goal Plan Template is a direct upstream input to Performance Form Template, not merely a Rating-Scale sibling that happens to sit next to it. Cardinality note: the landscape’s SVG does not render an explicit cardinality digit or verb-pill on the Goal Plan Template → Performance Form Template connector itself (unlike the Compensation zone’s labelled “based on” bypass connector nearby); this article therefore describes that relationship as “feeds into (direct prerequisite)” in Section 1.4 rather than asserting an unverified 1:N/N:1 count. Route Map is a standalone Zone D node with only a dashed reference chip to Permission Role (RM_Std ↗ PR_ESS) — it has no connector to Goal Plan Template and is out of scope for this article; see SF-A03-10.

Design principle: Goal Plan Template’s own hierarchy position is intentionally shallow (client level, single node) — the structural complexity that matters to a consultant lives one level up (how it binds to Rating Scale, Section 2.1) and one level down (how Performance Form Template consumes it, Section 2.5), not in extra sub-levels of the template object itself.

1.4 Integration with Other Master Data Objects#

Goal Plan Template sits in the middle of a short, linear integration chain — it consumes exactly one upstream object (Rating Scale) and feeds exactly one direct downstream consumer (Performance Form Template). Route Map and the Compensation-chain objects (Compensation Plan, Compensation Template, Eligibility Rule) sit in the same landscape zone but have no data-model link to Goal Plan Template at all: Route Map is configured independently against Permission Role for approval routing, and the Compensation-chain objects consume a completed rating outcome only as a downstream business rule at runtime, never a stored reference to Goal Plan Template itself.

Part 2: SF-Specific Field Details#

2.0 Scope of SF Ownership#

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

2.1 Template Definition (Core Identification)#

Template Definition is the minimum record a Goal Plan Template needs to exist — it is what every Performance Form Template’s Goal-section picker and every instantiated employee goal plan resolves back to.

2.2 Goal Category Configuration#

Goal Category Configuration is the repeatable child record — one row per category — that shapes how an employee’s goal plan is structured and scored once it is instantiated from this template.

2.3 Cascading & Alignment Settings#

Cascading & Alignment is what turns a Goal Plan Template from a flat, per-employee structure into a mechanism for propagating strategic goals down through the organization — and it is also the configuration area most likely to be over- or under-scoped at blueprint.

2.4 Goal Field Configuration#

Goal Field Configuration defines exactly what an employee sees and fills in on the goal-entry screen when adding a goal under this template — independent of which category it belongs to.

2.5 Usage in Consuming Templates#

A Goal Plan Template itself scores nothing directly — it only becomes meaningful once an employee’s live Goal Plan is instantiated from it and, separately, once a Performance Form Template’s Goal section is bound to it for scoring. This section covers how that downstream binding works and where the most common design mistakes occur.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction