JinJin48

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

July 19, 2026 · 17 min read

SAP SF Performance Form Template

Performance Form Template is the master data object that defines a reusable, versioned review-form structure — its sections (Goal, Competency, Overall/Summary), each section’s weighting and Rating Scale binding, and the Route Map that governs its approval workflow — used throughout SAP SuccessFactors Performance & Goals to generate every employee’s actual, live Performance Form for a given review cycle. It sits at the end of the Goal & Performance Configuration sub-block of Phase 2 (Permission & System Configuration), consuming both Rating Scale and Goal Plan Template as direct prerequisites: per the module’s Setup Flow, a Performance Form Template cannot be built until its Goal Plan Template (and, transitively, that template’s Rating Scale) already exist. This article covers what a Performance Form Template is, its common form-type variants, how it sits as the final node 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: Performance Form Template — Core Concepts (All Modules)#

1.1 What Is the Performance Form Template?#

Performance Form Template is a client-level (tenant-level) foundation object that carries no employee data of its own — an individual employee’s actual completed review lives in a separate, instantiated Performance Form record, not in the template. The template’s sole purpose is to define the reusable shape (sections, section weighting, scale bindings, and approval workflow) that every employee’s live review for a given cycle is generated from, so that the review experience and its scoring mechanics are structurally consistent across an entire population rather than freeform per manager.

1.2 Performance Form Template Variants (Form-Type Patterns)#

A Performance Form Template’s form type is not a cosmetic choice — it directly determines which sections exist, whether a final overall rating is captured at all, and how heavily the resulting form feeds downstream compensation decisions. Getting the form type wrong either produces an incomplete review record management can’t act on, or an overbuilt form that burdens raters with sections the cycle doesn’t need.

Design principle: like Rating Scale and Goal Plan Template before it, a Performance Form Template’s section structure, weighting, and scale bindings should be locked at blueprint — once forms are launched for a live population, changing the template does not retroactively alter already-generated live forms, but it still requires careful re-sequencing against the Rating Scale and Goal Plan Template the next launch depends on.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Performance Form Template sits in the tenant-level “Talent & Compensation” zone of the SuccessFactors Master Data Landscape, at the final position of one of two independent client-level chains bundled into that zone (the Talent chain this article concludes, 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
   │             │
   │             └── Performance Form Template "PFT_Annual2024" — Annual Review, 4-section, of GPT_2024  ← this article
   │
   └── 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 Performance Form Template as a direct child of Rating Scale (a parallel sibling to Goal Plan Template), and separately nests Route Map as a further child of Performance Form Template (Level 9: Rating Scale → Goal Plan Template / Performance Form Template → Route Map). 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 both points differently. (1) Chain shape: the landscape draws a single serial solid chain RS_5pt → GPT_2024 → PFT_Annual2024 — confirmed in the SVG as two vertical line segments at the same horizontal center (x=1060), y=945→1000 (Rating Scale → Goal Plan Template) and y=1095→1150 (Goal Plan Template → Performance Form Template), using identical stroke color and weight for both segments. This is consistent with the Setup Flow’s explicit dual-prerequisite line “Performance Form Template ← (Rating Scale, Goal Plan Template)”: Performance Form Template’s own direct upstream prerequisite in the chain is Goal Plan Template, not Rating Scale directly — Rating Scale reaches the Goal section indirectly through the Goal Plan Template it consumes, while the Overall/Summary and Competency sections can additionally bind Rating Scale directly (see Section 1.4). Cardinality note: as with the Rating Scale → Goal Plan Template segment (see SF-A03-08), the landscape’s SVG renders no 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 the relationship as “consumes (direct prerequisite)” in Section 1.4 rather than asserting an unverified 1:N/N:1 count. (2) Route Map: contrary to the ER Diagram’s nesting of Route Map as a child of Performance Form Template, the landscape places Route Map (“RM_Std”) as a standalone Zone D node — no solid connector to or from PFT_Annual2024 exists in the SVG (confirmed: no line segment spans the vertical gap between the Performance Form Template node at top:1145px and the Route Map node at top:1295px) — with only a dashed reference chip to Permission Role (RM_Std ↗ PR_ESS). This matches the Setup Flow’s own prerequisite line “Route Map ← (Permission Role)” rather than the ER Diagram’s nesting under Performance Form Template. Route Map is therefore explicitly NOT part of this article’s hierarchy chain or Section 1.4 integration table — it is a standalone object configured independently against Permission Role; see SF-A03-10.

Design principle: because Performance Form Template — like Rating Scale and Goal Plan Template before it — carries no employee data of its own, its own hierarchy position is intentionally shallow (client level, single node) at the end of the chain. The structural complexity that matters to a consultant lives one level up (how it binds to Goal Plan Template and Rating Scale, Sections 2.2–2.3) and one level down (how it becomes each employee’s actual live review, Section 2.5), not in extra sub-levels of the template object itself.

1.4 Integration with Other Master Data Objects#

Performance Form Template sits at the end of a short, linear integration chain — it consumes exactly two upstream inputs (Goal Plan Template directly, and Rating Scale both indirectly through the linked Goal Plan Template and directly for its non-Goal sections) and has no direct downstream master-data consumer of its own; instead it is instantiated into individual employee Performance Form records at runtime (Section 2.5). 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 Performance Form Template at all: per the Section 1.3 verification, Route Map is configured independently against Permission Role with no connector to Performance Form Template in the landscape, and the Compensation-chain objects consume a completed rating outcome only as a downstream business rule at runtime, never a stored reference to Performance Form 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 Performance Form Template needs to exist — it is what every launched Performance Form and every reference from a review-cycle configuration resolves back to.

2.2 Form Section Configuration#

Form Section Configuration is the repeatable child record — one row per section — that shapes what an employee’s actual review form looks like and how each part of it contributes to the overall outcome once instantiated from this template.

2.3 Rating Scale Binding (Section-Level)#

Because Performance Form Template can reach a Rating Scale two different ways — directly for non-Goal sections, and indirectly through its bound Goal Plan Template for the Goal section — this data section exists specifically to track and validate those bindings against each other.

2.4 Route Map & Workflow Binding#

Route Map & Workflow Binding is how a Performance Form Template picks up its approval workflow at launch time — the workflow steps themselves are defined and owned entirely on the Route Map object, not duplicated here.

2.5 Usage in Review Cycle Instantiation#

A Performance Form Template itself contains no employee data and produces no score — it only becomes meaningful once a review cycle is launched and an individual, editable Performance Form record is generated per employee from it. This section covers how that instantiation works and where the most common design mistakes occur.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction