Learn, Practice, and Improve with SAP C_TFG61_2405 Practice Test Questions

Explanation:

In SAP Fieldglass, the foundational master data elements (also called organizational structures) define how work is organized, tracked, and reported across the system. These elements are essential for assigning, categorizing, and reporting on contingent labor and services spend.

The three key master data elements are:

Business Unit (A)
Represents the highest organizational level for reporting and managing work assignments.
Used to group projects, cost centers, and users for financial and operational tracking.

Site (B)
Defines a physical or logical work location where contingent workers perform tasks.
Essential for tracking assignments, compliance, and local labor regulations.

Cost Center (E)
Used for financial tracking and reporting.
Provides a link between Fieldglass assignments and the organization’s accounting system (e.g., GL reporting).

Why the Other Options Are Incorrect

C. Locations ❌
In Fieldglass, Locations are often subcomponents or attributes of Sites, not considered a foundational master data element.

D. User ❌
Users are system participants (employees, approvers, managers) but are not master data. They are linked to master data for access and assignment purposes.

Reference
SAP Help Portal – SAP Fieldglass Configuration Guide → Organizational Setup
SAP Learning Hub – SAP Fieldglass Master Data Concepts

Explanation:

In SAP Fieldglass, invoiced Time and Expense Sheets generate invoices that are used within the services procurement process as follows:

A is correct:
SAP Fieldglass is primarily a procurement and invoicing approval platform, not a payment execution system. Buyers typically run reports or download approved invoices to process payments in an external financial system (e.g., SAP ERP, S/4HANA, or other accounting software). This is the standard practice for payment flows.

C is correct:
A key feature of SAP Fieldglass is the ability to consolidate multiple Time/Expense Sheets into a single, summarized invoice per supplier (often per billing period). This reduces administrative overhead and simplifies the invoicing process.

B is incorrect:
Buyers do not submit payments directly within SAP Fieldglass. The system handles invoice generation, approval, and integration with external payment systems, but actual payment execution occurs outside of Fieldglass.

D is incorrect:
While tax calculations can be configured in SAP Fieldglass, invoices themselves are not used to calculate tax adjustments. Tax rules are typically defined in master data or system configuration and applied during invoice generation, not recalculated from existing invoices.

Reference:

SAP Fieldglass documentation on Invoice Processing and Payment Integration emphasizes that approved invoices are exported to external financial systems for payment.

Explanation:

Alerts and Escalations in SAP Fieldglass are tied to Thresholds configuration. Thresholds are rules that define limits or conditions (such as budget, time, or compliance parameters). When these limits are approached or exceeded, the system can trigger Alerts (notifications) or Escalations (automatic actions like sending issues to higher-level approvers).
This ensures proactive monitoring and governance of services procurement activities.

Why not the other options?

A. Activity Item:
Activity Items are tasks or deliverables within a Statement of Work (SOW). They don’t control alerts or escalations.

B. Decision Form Template:
These are used for structured decision-making processes (e.g., supplier selection forms). Not related to alerts/escalations.

D. Wizard:
Wizards guide users through step-by-step processes (like creating an SOW). They don’t manage thresholds or alerts.

E. None:
Incorrect, because Alerts and Escalations are explicitly part of Thresholds configuration.

Reference
SAP Fieldglass Services Procurement Configuration Guide: Thresholds are used to define conditions that trigger alerts and escalations for proactive compliance and monitoring.

Explanation:

The Contact Us Details section in the Admin menu is specifically designed to centralize the Program Management Office (PMO) or internal helpdesk information. When an administrator configures this section, the details (such as email addresses, phone numbers, or hours of operation) are visible to users when they click the "Contact Us" link within the application's help menu.

More importantly for your question, SAP Fieldglass uses these specific details to populate the system-generated footers of automated email notifications. This ensures that every time a supplier or worker receives a message from the system—such as a notification about a new SOW or an expiring work order—they have a direct line to the correct internal contact rather than the generic SAP Fieldglass support desk.

Why Other Options Are Incorrect

B is incorrect:
While an Email Message Template allows you to edit the body and structure of specific notifications, it is not the central repository for the global footer contact details. Using this for contact info would require manual updates across hundreds of individual templates.

C is incorrect:
The Message Center is a user-facing inbox within the application where users read and manage their notifications; it is not a configuration tool for administrative settings.

D is incorrect:
Messages usually refers to the actual sent items or the audit log of communications, not the configuration area for global contact footers.

References
SAP Fieldglass Services Procurement Administration: "Managing Messaging and Contact Us Information."

Explanation:

In SAP Fieldglass Services Procurement, a General Ledger Account (GLA) is a configuration element used primarily for financial tracking, reporting, and integration with external accounting/ERP systems (e.g., SAP S/4HANA). It serves as a structured data item that acts as a central repository for classifying and organizing accounting-related information. Specifically:

GLAs are created in the Financial Data section.
They are associated with Task Codes (for time/labor allocation) and Expense Codes (for reimbursable costs).
This association enables detailed cost allocation, accurate financial classification of contingent labor spend, and proper mapping during invoicing and reporting.
GLAs support integration exports (e.g., to downstream ERP systems) and advanced reporting on spend by GL account.

This makes the GLA function as a centralized placeholder/repository for accounting classification data within Fieldglass, bridging operational data (time/expenses) to financial ledgers.

Why the other options are incorrect:

A. Managing pay rates and bill rates
→ Incorrect. Pay rates and bill rates are managed via Rate Schedules, Rate Categories, Worker Profiles, and SOW/Job Posting configurations—not GL Accounts.

C. Record keeping a company's financial data
→ Incorrect (and nearly identical to D). While GLAs support financial tracking, the actual "record keeping" of transactional financial data (debits/credits, balances) occurs in the company's core ERP General Ledger (e.g., SAP FI). Fieldglass GLAs are classification/mapping tools, not the primary record-keeping system.

D. Record keeping a company's financial data
→ Same as C—incorrect for the same reason.

References:
SAP Help Portal – General Ledger Account: "SAP Fieldglass allows you to create and use general ledger accounts for reporting and integration purposes. When a general ledger account has been created, task and expense codes can be associated with it." (help.sap.com > SAP Fieldglass > Financial Data section).

Explanation:

In SAP Fieldglass, Pick Lists are used to create predefined lists of values that can be selected from a dropdown menu when entering or updating data. This allows for standardization of data entry, reduces errors, and ensures consistency across the system.

Key points about Pick Lists:
They are admin-configurable, meaning administrators can add, modify, or deactivate list values.
Commonly used for fields such as job types, expense categories, or service types.
Help streamline reporting and analytics because data is standardized.

Why the Other Options Are Incorrect

A. Job Posting Templates ❌
Templates define pre-set fields for creating job postings, but they do not manage the list of selectable values themselves.

B. List View ❌
List Views are reporting or display configurations used to filter and present data, not to create dropdown lists.

C. Master Data ❌
Master Data refers to core organizational or worker-related data (like Business Units, Sites, or Cost Centers), not selectable lists for dropdown menus.

Reference
SAP Help Portal – SAP Fieldglass Admin Guide → Pick Lists
SAP Learning Hub – SAP Fieldglass Administration → Pick Lists

Explanation:

System Broadcasts in SAP Fieldglass are administrative messages used to communicate important information to users. The platform provides flexible configuration options for these broadcasts:

B is correct:
Administrators can schedule broadcasts to start and end at specific dates and times, allowing precise control over when messages appear.

C is correct:
Broadcasts can be targeted to specific user groups (e.g., hiring managers, suppliers, workers) based on roles, organizations, or other criteria, ensuring relevant audiences receive the message.

E is correct:
When configuring a broadcast, administrators can choose to display it on users’ home pages and/or send it via email, depending on notification settings.

A is incorrect:
While broadcasts can be edited or deleted before they become active, once a broadcast is published and sent (especially via email), it cannot be fully retracted. Deleting an active broadcast removes it from the home page, but any emailed version cannot be recalled, so “retracted” is not an accurate description of this functionality.

D is incorrect:
System Broadcasts are not dependent on an overnight agent run. They are triggered according to their schedule or immediately upon publication, independent of batch processing jobs.

Reference:
SAP Fieldglass Administrator Guide – System Broadcasts section outlines the capabilities to schedule, target, and deliver broadcasts via multiple channels, while noting that sent broadcasts cannot be fully retracted.