JinJin48

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

July 8, 2026 · 10 min read

SAP Fieldglass Contingent Type

Contingent Type, Qualification, and Job Posting Template are the first Job Posting Configuration masters built in Phase 3, immediately after the Rate Structure objects covered in FG-A04-01 and FG-A04-02. Contingent Type classifies a requisition by engagement category and drives its approval workflow; Qualification defines a skill or certification requirement independently of any one Template; Job Posting Template is the reusable assembly point that pulls both together with a Rate Category to become the shell every hiring manager launches a new job posting from. This article first covers the concepts shared by all three objects across every Fieldglass process area that touches job posting, then moves into the field-level detail Fieldglass Administrators configure for each.

Part 1: Contingent Type — Core Concepts (All Modules)#

1.1 What Is the Contingent Type?#

Contingent Type is a classification master that groups job requisitions by engagement category — contractor, temp staff, intern, or any other segmentation the tenant needs — and fixes the approval workflow every requisition of that type must pass through. It does not itself carry rate or skill data; those live on Rate Category (FG-A04-01) and Qualification respectively. Getting the Contingent Type design right up front (how many types, split by what dimension) determines how much approval friction hiring managers experience for the life of the tenant.

1.2 Contingent Type, Qualification, and Job Posting Template Compared#

These three objects answer three different questions in job posting setup — what kind of engagement is this, what skill does it require, and what reusable shell combines the answers — and confusing their roles is a common cause of over-built Template libraries.

Design principle: A Job Posting Template is not itself a master record with independent behavior — it is an assembly of references (Contingent Type, Qualification, Rate Category) fixed at creation. Changing which Contingent Type or Rate Category a Template points to after live requisitions 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): Contingent Type owns Job Posting Template as a true 1:N parent, while Job Posting Template separately references Qualification as a requirement — a reference, not a child, since the same Qualification is reused across many Templates.

Data hierarchy with a concrete example

Contingent Type "CT-CONTRACTOR" — job posting basis
   │
   └── Job Posting Template "JPT-IT-01" — IT contractor template
          │
          ├── ── requires ──> Qualification "QUAL-PMP" — PMP certification (one or more Qualifications)
          │
          └── ── references ──> Rate Schedule "RS-SHIFT-01" (Zone C) — inherits Rate Structure from Rate Category "RC-STD" at creation

Note: Qualification is maintained as its own independent master, not nested under Contingent Type — the same Qualification (e.g. “QUAL-PMP”) is commonly attached to Job Posting Templates built on different Contingent Types.

1.4 Integration with Other Master Data Objects#

None of these three objects stand alone — Contingent Type reaches into User Management for its workflow, Job Posting Template reaches into Rate Structure for its pricing, and both eventually reach into Company Structure to determine who receives the posting.

Part 2: FG-Specific Field Details#

2.0 Scope of FG Ownership#

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

2.1 Contingent Type — Classification & Workflow#

Contingent Type carries the fields that give a requisition its engagement category and its approval path — the two decisions that shape every downstream Job Posting Template built on it.

2.2 Qualification — Requirement Configuration#

Qualification carries the fields that define a single skill or certification requirement — maintained once and reused across as many Job Posting Templates as apply.

2.3 Job Posting Template — Template Assembly#

Job Posting 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