C_TFG61_2601

In SAP Fieldglass, a Statement of Work defines how a supplier delivers contracted services, while a contingent worker job posting supports a different engagement model. C_TFG61_2601 evaluates the administrative decisions behind that distinction and the configuration needed to govern services from supplier selection through payment. The SAP Certified – Administrator – SAP Fieldglass Services Procurement credential focuses on applying company structures, reusable services settings, and transaction controls within the vendor management system.

Company Structure and Master Data Associations

Services procurement relies on organizational data that determines where work occurs, who can act, and how spending is assigned. Business units, sites, legal entities, and cost centers serve different purposes. Administrators must recognize how these objects relate to user permissions, reporting, and financial allocation rather than treating them as interchangeable labels.

Master data associations restrict combinations of organizational values to those that belong together. Supplier records, user roles, and approval groups also influence which parties participate in a services transaction. Reviewing these relationships helps identify why an SOW may offer an unexpected selection or reach the wrong reviewer.

SOW Templates, Classifications, and Supplier Bids

An SOW template establishes repeatable rules for a particular category of contracted work. Configuration can connect templates with SOW types, classifications, suppliers, clause libraries, and approval requirements. The template provides the administrative framework; the individual SOW records the specific commercial engagement.

For C_TFG61_2601, pay attention to these boundaries:

• SOW classifications versus the templates available for a service category.
• Clause libraries versus contract-specific terms entered on an SOW.
• Question libraries for SOW bids versus supplier responses to a particular bid.
• Approval group configuration versus an approval action on an individual transaction.

SOW bidding introduces supplier comparison before a services agreement is finalized. Administrators should understand the reusable objects that support consistent bid information, alongside the workflow used to review and select responses.

Milestone Events, SOW Workers, and Invoice Controls

Services agreements may contain event-based payments, recurring schedules, fees, and worker roles. Event and fee libraries help standardize commercial characteristics, while SOW worker roles define how people assigned to contracted services are represented. This is distinct from sourcing individual contingent workers through job postings.

Approval and financial processing continue after an SOW is created. Administrators need to understand supplier acceptance, changes to active agreements, worker onboarding activities, time and expense handling where applicable, and the relationship between approved services and invoices. SOW closure is another separate lifecycle action, not simply the final payment.

A web-based practice test runs in the browser with nothing to install, while downloadable PDF questions and answers can be printed and annotated for offline revision. For C_TFG61_2601, connect each administrative setting to its effect on SOW creation, supplier collaboration, milestone approval, and invoice review.