SAP Fieldglass Contingent Workforce Management — Lesson 1: Fieldglass Architecture, Company Configuration, User Roles, Suppliers, Sites, and Master Data

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing Fieldglass company and supplier configuration.
• Perform and validate user roles, sites, and master data using reviewable system evidence.
• Evaluate the condition where a worker cannot start or invoice because job-seeker data, work-order terms, onboarding tasks, and rate rules disagree and select proportionate corrective action.

Detailed Topics

• Fieldglass Architecture applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Company Configuration applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• User Roles applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Suppliers applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Sites applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Master Data applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a services procurement team controlling external labor cost, compliance, supplier performance, and worker access across multiple business units. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the Fieldglass contingent workforce lifecycle and compliance register. It also tests the exception where a worker cannot start or invoice because job-seeker data, work-order terms, onboarding tasks, and rate rules disagree.

Hands-On Exercise

Complete a controlled SAP exercise covering Fieldglass Architecture, Company Configuration, User Roles, Suppliers, Sites, and Master Data and preserve the verified result in the Fieldglass contingent workforce lifecycle and compliance register.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences Fieldglass company and supplier configuration.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the Fieldglass contingent workforce lifecycle and compliance register should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “a worker cannot start or invoice because job-seeker data, work-order terms, onboarding tasks, and rate rules disagree” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The Fieldglass contingent workforce lifecycle and compliance register connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Fieldglass Architecture, Company Configuration, User Roles, Suppliers, Sites, and Master Data, explain the resulting SAP behavior, and defend the outcome through the Fieldglass contingent workforce lifecycle and compliance register.