JinJin48

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

July 8, 2026 · 9 min read

SAP Fieldglass Distribution List

The Distribution List is the fourth object listed within Fieldglass’s Phase 2 User & Permission Settings menu grouping — it sits in the Admin area alongside User Role, User, and Approval Group — but the module’s own Setup Flow marks its actual prerequisite differently: “Distribution List ← (Supplier),” not User or Approval Group. A Distribution List is a curated, reusable pool of Suppliers that a Job Posting or SOW references at publish time to control which external staffing agencies or SOW vendors are notified and invited to respond. This article maps the Distribution List’s core concepts across all Fieldglass capability areas (Part 1) — including, in Section 1.3, a full resolution of its real Supplier dependency versus its administrative landscape position — then details every field an administrator configures when creating and maintaining Distribution List records (Part 2).

Part 1: Distribution List — Core Concepts (All Modules)#

1.1 What Is the Distribution List?#

The Distribution List is a named, reusable pool of Suppliers that a Job Posting or SOW references at publish time to determine which external staffing agencies or SOW vendors are notified and invited to respond. Rather than manually selecting Suppliers on every individual posting, an administrator curates a small library of Distribution Lists once — scoped by Business Unit, Site, or labor category — and each posting or SOW simply points to the relevant list(s) instead of being built from scratch.

1.2 Distribution List Categories by Scope#

Distribution List does not carry a formal “Type” code field — instead, every list is built around one of a few common scope patterns, and getting that scope wrong is a direct, visible business problem: too broad, and Suppliers see postings irrelevant to their qualifications; too narrow or fragmented, and a program ends up managing dozens of near-duplicate lists that drift out of sync with each other.

Design principle: Scope Distribution Lists as narrowly as the program’s actual Supplier segmentation allows. A single catch-all list technically works, but it erodes exactly the value — targeted, qualified competition — that a curated Supplier pool exists to provide.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example

Zone B position (administrative grouping only — see note below)
User Role "ROLE-ADMIN" — Administrator
│
└── User "u.admin" — System Admin
       └╌╌ proximity only, not a data dependency ╌╌> Distribution List "DL-ENG-ALL" — Notification group  ◄── this article

True master-data prerequisite (Setup Flow: "Distribution List ← (Supplier)"; ER Diagram: "Distribution List ←── Supplier (N:M)")
Supplier "SUP-001" — ABC Staffing Services
│
└── assigned to ──> Distribution List "DL-ENG-ALL" — Notification group  ◄── this article

Supplier "SUP-002" — XYZ IT Resourcing
│
└── assigned to ──> Distribution List "DL-ENG-ALL" — Notification group  ◄── this article

The Fieldglass Master Data Landscape draws Distribution List in Zone B, directly beneath User “u.admin,” because it is maintained from the same Admin menu area as Users and Approval Groups — that is a menu/administrative convenience only. There is no organizational or data dependency from User Role, User, or Approval Group into Distribution List; a Distribution List does not require any of those three objects to exist and is not populated from them in any way.

The module’s own Setup Flow entry — “11. Distribution List ← (Supplier)” — and its ER Diagram entry — “Distribution List ←── Supplier (N:M)” — both confirm the actual master-data prerequisite is Supplier, a Company Structure object from Phase 1 (Zone A, FG-A02-05), not a User & Permission Settings object. A Distribution List cannot be meaningfully populated until at least one Supplier record exists to add as a member, and a single Supplier can belong to any number of Distribution Lists (N:M), exactly as the two example Suppliers above both feed the same list.

Open item for the module landscape: Zone A of the current Fieldglass Master Data Landscape models Tenant, Business Unit, Cost Center, Site, and Location only — it does not yet include a Supplier node anywhere in the diagram. Until FG-A02-05 (Supplier) is drafted and Zone A is extended to include it, this true Supplier dependency cannot be rendered as a cross-zone chip or dashed connector 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#

The Distribution List record does not stand alone — its entire purpose is to route documents to the Suppliers it contains.

Part 2: FG-Specific Field Details#

2.0 Scope of FG Ownership#

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

2.1 Basic Identification & Status#

These fields identify a list and control whether it can still be attached to new Job Postings or SOWs going forward.

2.2 Membership & Distribution Configuration#

These fields determine which Suppliers actually receive documents routed through the list, and how automatically that routing happens.

Prerequisite: At least one active Supplier record must exist before it can be added as a member of a Distribution List (Setup Flow: “Distribution List ← (Supplier)”).

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction