JinJin48

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

July 8, 2026 · 9 min read

SAP Fieldglass MSP Company

MSP Company is the first of two Phase 4 objects under MSP & Certification Settings — its sibling, Certification, is documented separately in FG-A05-02. MSP Company designates a Supplier as the tenant’s Managed Service Provider (MSP) and defines the markup or discount fee that MSP earns on Bill Rate as compensation for administering the contingent workforce and/or SOW program on the client’s behalf. Configuring it is optional: per the module’s own Required vs Optional Master classification, MSP Company applies only to tenants running an MSP-operated program, not to a supplier-self-managed or direct-sourcing model. This article first covers the concepts shared across every Fieldglass process area MSP Company touches (Part 1) — including, in Section 1.3, its real Supplier dependency and a known gap in the current module landscape — then details every field a Fieldglass Administrator configures for it (Part 2).

Part 1: MSP Company — Core Concepts (All Modules)#

1.1 What Is the MSP Company?#

MSP Company is the record that formally elevates one Supplier to the role of Managed Service Provider for the tenant, and carries the fee terms the MSP earns for running the program. It does not itself define who can respond to postings, what rates apply, or how requisitions are approved — those all remain governed by the objects covered in earlier Phase 1–3 articles. MSP Company simply layers a program-administration fee on top of the transactions that already flow through the platform.

1.2 MSP Fee Structure Models Compared#

MSP Company does not carry a formal “Type” field the way Contingent Type or SOW Type do — instead, its Fee Structure field selects between two compensation models, and getting the direction wrong silently misstates every downstream invoice generated through the program.

Design principle: Confirm which Fee Structure model the client’s signed MSP contract actually uses before configuration — Markup and Discount move the invoiced amount in opposite directions, and the two are not interchangeable defaults.

1.3 Organizational Levels and Data Hierarchy#

Zone D — Job Posting · SOW · MSP (this object’s own zone): MSP Company is a standalone tenant-level node — it owns no children and carries no outbound line or chip to any other Zone D object, matching the corrected landscape’s Row 1 layout (no solid line down to Certification).

Data hierarchy with a concrete example

Zone D position (standalone tenant-level object — no children, no outbound chip, no solid line to any other Zone D node)
MSP Company "MSP-01" — Managed Svc Provider  ◄── this article

Real-world prerequisite (Setup Flow: "24. MSP Company ← (Supplier)"; ER Diagram: "MSP Company ←── Supplier (1:1)")
Supplier "SUP-001" — ABC Staffing Services
   │
   └── designated as ──> MSP Company "MSP-01" — Managed Svc Provider  ◄── this article

MSP Company sits in Zone D of the Fieldglass Master Data Landscape as a standalone Row 1 card, alongside Contingent Type and SOW Type — but unlike those two, it owns no children within Zone D. The corrected landscape removed a previously-drawn solid containment line from MSP Company down to Certification once it was confirmed the two Phase 4 objects are configured independently of one another (Certification is documented separately in FG-A05-02).

The module’s own Setup Flow entry — “24. MSP Company ← (Supplier)” — and its ER Diagram entry — “MSP Company ←── Supplier (1:1)” — both confirm MSP Company’s real master-data prerequisite is Supplier: a specific Supplier record is designated as the program’s MSP, and Fieldglass expects that Supplier to already exist before an MSP Company record can be created.

Known gap, same as flagged in FG-A03-04: Zone A of the current Fieldglass Master Data Landscape does not yet include a Supplier node — this was first flagged when FG-A03-04 (Distribution List) documented its own N:M Supplier dependency, and it remains open here. Until FG-A02-05 (Supplier) is drafted and Zone A is extended to include it, MSP Company’s Supplier dependency cannot be rendered as a cross-zone chip on the landscape image itself; it is documented here in the article text as the authoritative relationship, ahead of the landscape catching up.

1.4 Integration with Other Master Data Objects#

MSP Company does not stand alone — its entire purpose is to attach a fee to transactions that already flow through Supplier, Rate, and Template objects documented elsewhere in this module.

Part 2: FG-Specific Field Details#

2.0 Scope of FG Ownership#

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

2.1 MSP Company — Classification & Association#

MSP Company carries the fields that identify the record and tie it to the single Supplier being elevated to Managed Service Provider status.

2.2 Fee Structure — Markup/Discount Configuration#

Fee Structure carries the two fields that define how much the MSP earns and in which direction that amount moves the invoiced total — the commercial core of the MSP Company record.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction