JinJin48

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

July 8, 2026 · 13 min read

SAP Fieldglass SOW Template

SOW Type, Worker Role, Event Library, and SOW Template are the Services Procurement counterpart to the Job Posting Configuration masters covered in FG-A04-03 — configured in the same Phase 3 stage, immediately after the Rate Structure objects in FG-A04-01 and FG-A04-02. SOW Type classifies a statement of work by pricing model and drives its approval and collaboration workflow; Worker Role defines a labor category and its rate basis independently of any one Template; Event Library maintains a reusable library of payment and milestone triggers; SOW Template is the reusable assembly point that pulls all three together to become the shell every SOW-based engagement is launched from. This article first covers the concepts shared by all four objects across Services Procurement, then moves into the field-level detail Fieldglass Administrators configure for each.

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

1.1 What Is the SOW Template?#

The SOW Template is the assembly point of Services Procurement configuration — it does not itself define a pricing model, a labor rate, or a payment trigger; it pulls a SOW Type, one or more Worker Roles, and an Event Library together into one reusable shell that a category buyer or hiring manager selects to launch a new statement of work. Getting the Template library right up front (how many Templates, split by service family) determines how much rework is needed every time a new SOW is drafted.

1.2 SOW Type, Worker Role, Event Library, and SOW Template Compared#

These four objects answer four different questions in SOW setup — what pricing model and workflow applies, what labor category and rate basis is being delivered, when does the SOW pay, and what reusable shell combines all three — and confusing their roles is a common cause of an over-built or under-governed Template library.

Design principle: A SOW Template is not itself a master record with independent behavior — it is an assembly of references (SOW Type, Worker Role, Event Library) fixed at creation. Changing which SOW Type a Template points to, or swapping its attached Worker Roles, after live SOWs exist against it is not supported; a new Template must be created instead.

1.3 Organizational Levels and Data Hierarchy#

Zone D — Job Posting · SOW · MSP (this object’s own zone): SOW Type owns SOW Template as a true 1:N parent, while SOW Template separately references Worker Role and Event Library as reusable components — references, not children, since the same Worker Role or Event Library is commonly reused across many Templates.

Zone C — Rate Structure: Worker Role carries an outbound ↗ RC-STD reference chip into this zone, since a Worker Role’s Rate Structure is inherited from the Rate Category at creation time and cannot be changed later.

Data hierarchy with a concrete example

SOW Type "SOWT-FIXED" — fixed-price SOW basis
   │
   └── SOW Template "SOWTPL-IT-01" — IT services template
          │
          ├── ── references ──> Worker Role "WR-DEV-01" — Software Developer (one or more Worker Roles)
          │
          └── ── references ──> Event Library "EL-STD" — Standard Events

Referenced by (Zone C — Rate Structure):
   Worker Role "WR-DEV-01" ── inherits Rate Structure from ──> Rate Category "RC-STD"

Note: Event Library is maintained as its own independent master, not nested under SOW Type — the same Event Library (e.g. “EL-STD”) is commonly attached to SOW Templates built on different SOW Types.

1.4 Integration with Other Master Data Objects#

None of these four objects stand alone — SOW Type reaches into User Management for its workflow, Worker Role reaches into Rate Structure for its pricing, and the parallel Contingent Labor object tree stays entirely separate despite the conceptual similarity.

Part 2: FG-Specific Field Details#

2.0 Scope of FG Ownership#

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

2.1 SOW Type — Classification & Workflow#

SOW Type carries the fields that give a statement of work its pricing model and its approval and collaboration path — the decisions that shape every downstream SOW Template built on it.

2.2 Worker Role — Role & Rate Configuration#

Worker Role carries the fields that define a labor category delivered under a SOW and the rate basis it is paid and billed against — maintained once and attached to as many SOW Templates as apply.

2.3 Event Library — Payment Event Configuration#

Event Library carries the fields that define a single payment or milestone trigger — maintained once and reused across as many SOW Templates as apply, independent of the labor roles attached to those Templates.

2.4 SOW Template — Template Assembly#

SOW Template is the assembly point — every field here either identifies the Template or points at one of the objects it pulls together, rather than defining new business logic of its own.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction