The Statement of Work (SOW) Bid process in SAP Fieldglass is designed for competitive sourcing. Unlike a standard SOW created for a pre-selected supplier, the SOW Bid process begins without a supplier being chosen. The initial steps involve defining the work using a classification and template (C). After internal approval, this SOW Bid is distributed to multiple suppliers for bidding (E). Once a winning bid is selected, the process transitions into a more standard SOW workflow, now populated with the chosen supplier's details, to finalize the contract (B). This multi-supplier, competitive front-end is the primary differentiator from the standard single-supplier SOW approval process.

A. The SOW Bid process is a specific workflow within the SOW Module; it does not take place before the module is engaged.

D. A standard SOW also generates these details. This is a characteristic of the SOW document itself, not a differentiator of the bid approval process.

1. SAP Help Portal - SAP Fieldglass: Creating a Statement of Work Bid. This official documentation outlines the SOW Bid creation process. It specifies that a buyer initiates the process by selecting a template and classification

but the supplier is not selected at this stage. It also details the step of sending the bid to multiple suppliers. (Refer to the sections on "Initiating an SOW Bid" and "Submitting the Bid to Suppliers").

2. SAP Fieldglass Statement of Work (SOW) Configuration Guide. This guide details the workflow configurations. It distinguishes the SOW Bid workflow (SOW Bid Approval) from the standard SOW workflow (SOW Approval)

clarifying that the former is designed for sourcing and precedes the selection of a single supplier

while the latter manages an SOW with an already-identified supplier. (Refer to the chapter on "Statement of Work Module Workflow Configuration").

3. SAP Fieldglass Services and External Workforce Program Administration (FG-100) Courseware. This official training material explains the end-to-end SOW lifecycle. It explicitly contrasts the standard SOW creation with the SOW Bidding process

highlighting that bidding is used to competitively source a supplier

and upon award

the winning bid is converted into a regular SOW for execution. (Refer to Unit 5: Statement of Work (SOW) Management

Lesson on "SOW Bidding").

The maximum number of concurrently scheduled reports is a system-level setting within SAP Fieldglass. This limit is in place to manage system resources and ensure performance stability for all users. Such backend configurations are not exposed to customer administrators through self-service tools like the Configuration Manager or other administrative menus. The standard and required procedure to request a change to this default limit is to create a service request with the SAP Fieldglass Support team, who will then assess the request and make the necessary adjustments.

B. Using a Configuration Upload connector: Connectors are designed for mass data uploads and integration (e.g., users, suppliers, invoices), not for modifying core application configuration parameters or system limits.

C. Accessing the Configuration Manager Dashboard: The Configuration Manager allows administrators to manage many self-service settings, but it does not include system-wide performance and resource limits like the maximum number of scheduled reports.

D. Making changes to the Company Details section in the Administrator Menu: The Company Details section is used for managing high-level organizational information such as company name, address, and default currency, not technical application limits.

1. SAP Help Portal

SAP Fieldglass Reporting User Guide: In the section titled "Scheduling a Report to Run

" the documentation explicitly states

"By default

you can schedule up to 25 reports at one time. If you need to schedule more than 25 reports

please contact your SAP Fieldglass representative." This directly validates that contacting SAP support is the correct procedure. (Document available on help.sap.com for SAP Fieldglass).

2. SAP Help Portal

SAP Fieldglass Configuration Manager Guide: A review of the available self-service options and configuration workbooks detailed in this guide shows the absence of any setting related to report scheduling limits. This omission confirms that this parameter is not a customer-configurable item and must be handled by SAP Support. (Document available on help.sap.com for SAP Fieldglass).

In SAP SuccessFactors Recruiting Management, the Question Library is a central repository where administrators can create, store, and manage questions. These questions (e.g., for prescreening) can then be grouped together and associated with job requisition templates. This grouping functions as a "Job Question Checklist" that can be consistently and easily shared across multiple job postings derived from those templates, ensuring a standardized screening process. This feature allows for efficient reuse of common questions.

A. Qualification: A qualification represents a skill, competency, or certification required for a role, not a mechanism for grouping and sharing questions.

C. Asset Type: This is a configuration related to Asset Management or Accounting for classifying physical or intangible assets, which is irrelevant to recruiting questions.

D. Activity Checklist: This feature is typically used in modules like SAP SuccessFactors Onboarding to track completion of tasks, not to group screening questions for job applicants.

1. SAP Help Portal: Recruiting Management - Question Libraries in Recruiting Management.

Reference: This guide details the creation and management of questions in a central library. It states

"You can create libraries of questions that can be added to job requisitions... This feature allows you to reuse questions across multiple job requisitions." This directly supports the concept of grouping (in a library) and sharing (across templates/requisitions). The term "Job Question Checklist" functionally describes a set of these questions applied to a job.

2. SAP Help Portal: Recruiting Management - Job Requisition Templates.

Reference: The section on configuring Job Requisition Templates explains how to pre-populate fields and associate elements like question libraries. It notes that questions can be added to the template

ensuring that any requisition created from it will automatically include that "checklist" of questions

fulfilling the "easily shared" requirement of the question.

The Clause Library in SAP Fieldglass is the designated repository for administrators to create, store, and manage standardized contractual language. These pre-approved clauses are then available for insertion into various documents, including Statements of Work (SOWs). This functionality ensures legal consistency, compliance with company policies, and accelerates the SOW creation process by providing a centralized source for approved legal text. The library allows for version control and categorization of clauses, making it the correct tool for managing contractual agreements.

A. Schedule Library: This library is used to create and manage templates for payment schedules, billing plans, or project milestones, not for storing legal or contractual text.

B. Event Library: This is used to define and manage business rules and workflow events, such as notifications or approvals, within the SOW lifecycle, not for contractual content.

C. Question Library: This library stores standardized questions used for supplier qualification, interviews, or performance reviews, and is not intended for holding contractual clauses.

1. SAP Fieldglass

"Administrator Fundamentals Guide": In the section on "Admin Objects

" the guide details the purpose of various libraries. It specifies that the Clause Library is used to "create and store clauses that can be added to Statements of Work (SOWs)." (Refer to the chapter on Library Management).

2. SAP Fieldglass

"Working with Statements of Work (SOWs) User Guide": This guide explains the SOW creation process

referencing how users can "add clauses from the company's Clause Library" to the SOW document to define terms and conditions. (Refer to the section on "Creating a Statement of Work").

3. SAP Help Portal

"SAP Fieldglass - Statement of Work (SOW)": The official documentation describes the components of an SOW

explicitly mentioning that "Clauses" containing legal language are managed in and inserted from the Clause Library by administrators. (Document ID: SAP Fieldglass SOW Management).

In SAP Fieldglass, associating a proxy role to a user role is a fundamental administrative task for managing delegation. This action defines a rule-based eligibility pool. It specifies which roles (the proxy roles) contain users who are permitted to act as a proxy for users assigned to the original role. This allows for scalable and secure management of proxies, ensuring that delegation of responsibilities, such as approvals, is restricted to users with appropriate functions and permissions as defined by their assigned roles, rather than managing permissions on an individual-by-individual basis.

A. This is incorrect because the association is between roles to create a pool of potential proxies, not selecting specific proxy users for one user.

B. This is incorrect as the association is made to a specific user role, not for multiple user roles simultaneously in a single action.

C. This is incorrect because the process involves selecting roles whose members can act as proxies, not selecting a single individual user.

1. SAP Fieldglass Help Portal

"Proxy Management": The documentation explicitly states

"Proxy roles are associated with user roles to determine which roles can serve as a proxy for another role. For example

the Administrative Assistant role can be associated with the Hiring Manager role. This means that any user with the Administrative Assistant role can be a proxy for any user with the Hiring Manager role." This directly supports the concept of selecting roles that can serve as proxies for another role.

2. SAP Learning Hub

Course TFG60 - SAP Fieldglass Services and External Workforce

Unit: User and Company Structure: This course material details the configuration of user roles and their associated permissions and settings. In the section on advanced user management

it describes how proxy roles are linked to primary user roles to establish a framework for delegation

reinforcing that the association is a role-to-role definition.

The SAP Fieldglass supplier Admin menu is the central hub for administrators to manage their company's profile, users, and configuration settings. Supplier administrators can directly edit their company's profile information, which includes the company name. They also have the necessary access to view critical financial information, such as the rates associated with job postings and statements of work. Furthermore, a key administrative task is managing communication, which includes the ability to view and configure distribution lists for system notifications. These functions are fundamental for the supplier's self-service administration within the SAP Fieldglass platform.

B. Reject time or expense sheet: This is a transactional task for approvers within a specific workflow. It is not a general administrative function found in the Admin menu.

C. Manage sites serviced: The buyer typically controls the scope of a supplier's service area. Therefore, a supplier may only be able to view assigned sites rather than actively "manage" them.

1. SAP Fieldglass - Help Portal: Supplier Basic Navigation Guide: This guide outlines the main menu options for suppliers. The 'Admin' menu is shown to contain links for managing the 'Company Profile' (which includes the company name)

'Distribution Lists'

and other administrative settings. Access to view rates is implicit in the management of rate-bearing objects like SOWs and Job Postings

which admins can access. (Reference: SAP Fieldglass Help Portal

"Supplier Basic Navigation" section).

2. SAP Fieldglass - Help Portal: Working with Your Profile as a Supplier: Official documentation details that the 'Company Profile'

accessible via the Admin menu

is where suppliers maintain their company details

including the legal name. This confirms option A. The documentation also describes how distribution lists are managed under a specific Admin menu item

confirming option E. (Reference: SAP Fieldglass Help Portal

"Company Profile" subsection for Suppliers).

3. SAP Fieldglass - Configuration Guide (for Buyers): This documentation explains the buyer's ability to configure and control supplier access and scope. It details that buyers can restrict which of their sites a supplier is eligible to service

supporting the reasoning that a supplier may not have full "manage" capabilities over this data

making option C incorrect. (Reference: SAP Fieldglass Configuration documentation related to Supplier Management and Site restrictions).

The 'View all Work Items' functionality is a powerful administrative tool within SAP Fieldglass. It is designed to provide administrators with a comprehensive overview of all active, pending tasks across the entire organization. This visibility is crucial for monitoring workflow progress and identifying bottlenecks. Furthermore, a key capability of this feature is to allow the administrator to intervene when necessary. They can select a specific work item and perform the required action (e.g., approve, reject) on behalf of the originally assigned user, which is essential for situations where a user is unavailable.

A. Send new work items to users within the company.

This function is for managing and acting on existing work items, not for initiating or creating new ones.

D. See all notifications that have been sent to a specific user.

This tool displays actionable work items (tasks requiring a decision), not a historical log of informational notifications.

1. SAP Fieldglass Administrator Guide: In the section describing administrative functions

the guide details the 'Work Items' feature. It specifies that users with the "View All Work Items" permission can "view all active work items in the company" and "take action on behalf of the user to whom the work item is assigned." (Reference: SAP Help Portal

SAP Fieldglass Administrator Guide

Chapter on "Admin Menu"

Section on "Work Items").

2. SAP Fieldglass Configuration Guide: The guide for configuring user roles and permissions explicitly lists "View All Work Items" as a permission that grants the ability to see and act upon the work items of other users system-wide. This confirms the dual capability of viewing and acting. (Reference: SAP Help Portal

SAP Fieldglass Configuration Guide

Chapter on "User Roles and Permissions").

The Cost Center Allocation Segmented Object Detail (SOD) is specifically designed for scenarios where financial costs need to be distributed across multiple cost objects. When a user selects a value in a Cost Center Allocation SOD, the system uses predefined allocation rules associated with that value to automatically derive and populate the corresponding cost centers and their allocation percentages. This directly fulfills the requirement of deriving cost objects from the SOD value.

A. Grid SOD: This SOD type is used for capturing multiple line items of data in a tabular format, such as itemized expenses or detailed time entries, not for deriving cost objects.

B. Cost Center Attribute SOD: This SOD type is used to capture additional descriptive information (attributes) related to a selected cost center, rather than deriving the cost object itself.

C. Custom Field SOD: This is a generic SOD used for capturing unique data not covered by standard types. It lacks the specific, built-in logic for cost distribution and derivation.

1. Official Vendor Documentation: SAP Fieldglass Help Portal

"Segmented Object Detail Types". This guide details the purpose of each SOD type. The section on "Cost Center Allocation SOD" explicitly states its function is to enable the distribution of costs to multiple cost centers based on a single SOD value selection.

2. Official Vendor Documentation: SAP Fieldglass

"Configuration Guide for Core Functionality". In the chapter on Financial Data Configuration

section "Configuring Segmented Object Details

" the guide explains that the Cost Center Allocation type is the designated tool for creating rules that derive cost object assignments. (Reference: Chapter 5

Section: "Financial Data Management").

In the SAP Fieldglass Discount method, the Managed Service Provider (MSP) fee is calculated as a percentage of the Supplier Bill Rate. The buyer is billed the full Supplier Bill Rate. The MSP fee is then deducted from this amount before the payment is remitted to the supplier. Therefore, the fee is effectively subtracted from the Supplier Bill Rate to determine the supplier's net proceeds, while the buyer's cost remains the Supplier Bill Rate.

A. The Fee is added to the Buyer Bill Rate: This is incorrect. The Buyer Bill Rate is the final rate; a fee is not added on top of the final amount. This describes an illogical financial process.

B. The Fee is subtracted from the Buyer Bill Rate: This is misleading. In the Discount model, the Buyer Bill Rate and the Supplier Bill Rate are the same. The fee is an internal deduction from the supplier's payment.

C. The Fee is subtracted from the Pay Rate: This is incorrect. The MSP fee is a commercial arrangement between the buyer/MSP and the supplier, not a deduction from the contingent worker's direct pay rate.

1. SAP Fieldglass TFG61 Courseware: TFG61ENCol19 - SAP Fieldglass: Services and External Workforce Management

Unit 5: Financial Data

Lesson: Rate Structures and Fees. This section details the three primary fee models: Markup

Discount

and Fixed. It explicitly states that the Discount model calculates the fee based on the Supplier Bill Rate and deducts it from the supplier's payment.

2. SAP Help Portal - SAP Fieldglass: Configuration Guide for Rate Structures. In the section "Fee Structures

" the Discount method is defined as: "A fee calculated as a percentage of the supplier rate. The fee is deducted from the amount paid to the supplier." This confirms the fee is subtracted from the supplier's billed rate.

Invoice Adjustments in SAP Fieldglass are line items used by a buying organization to modify an invoice total after it has been submitted by a supplier. These adjustments can represent either a positive amount (a debit, increasing the amount due) or a negative amount (a credit, decreasing the amount due). This functionality is a buyer-side action, meaning that users from the buying organization add these adjustments to an invoice. Suppliers can view the adjustments made to their invoices but cannot create or add new adjustments themselves.

B. Invoice Adjustments can be either a credit or a debit item to be added to an invoice

This statement is factually correct but is a verbatim duplicate of option A, indicating a flaw in the question's construction.

C. An invoice Adjustment must always be a taxable item

This is incorrect. The taxability of an invoice adjustment is a configurable attribute. Administrators define 'Adjustment Types' and can specify whether each type is taxable or non-taxable.

1. SAP Fieldglass: Configuration Manager Guide - In the section for creating and managing 'Adjustment Types'

the configuration options include a "Taxable" checkbox. This allows administrators to define an adjustment as either taxable or non-taxable

demonstrating that they are not always taxable. (Refer to module: Financial Configuration > Adjustment Types).

2. SAP Fieldglass: Invoicing and Consolidated Invoicing User Guide - The guide details the process for buyers to add adjustments to supplier invoices. The workflow explicitly shows this as a buyer-side function. It also describes entering either a positive or negative value for the adjustment

confirming it can be a debit or credit. (Refer to chapter: Working with Invoices > Adjusting Invoices).