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

Explanation:

In SAP Fieldglass, relabeling standard system terms (for example, changing “Job Posting” to “Job Requisition”) is done using Custom Text.

Custom Text allows administrators to:

Modify labels and terminology displayed in the user interface
Adapt Fieldglass language to match a customer’s internal business terminology
Change text without altering system logic or data structures
Since the requirement is only to rename a label, Custom Text is the correct and SAP-recommended approach.

Why the Other Options Are Incorrect

A. Custom Lookup ❌
Custom Lookups are used to manage value lists (dropdown options), not UI labels or terminology.

B. Custom Field ❌
Custom Fields are used to add new data fields, not to rename existing standard objects or labels.

C. Classification ❌
Classifications control categorization and structure (such as worker types or service categories), not text displayed in the UI.

Reference
SAP Help Portal – SAP Fieldglass Configuration Guide
Custom Text allows customers to relabel standard Fieldglass terms to align with company-specific language.

Explanation:

The Messaging section in the SAP Fieldglass Admin menu is part of the system's notification and reminder framework. It is used to configure automated communications and reminders, not for real-time chat or direct user-to-user messaging.

A is correct:
Administrators can create and schedule reminders for different user groups (e.g., suppliers, hiring managers, workers) based on time or event triggers. Examples include reminders for timecard submission, onboarding tasks, or approval deadlines. This is a key administrative function within Messaging.

B is correct:
This section allows administrators to manage notifications — including setting up, modifying, and controlling how system-generated alerts (e.g., assignment approvals, document submissions, status changes) are sent, to whom, and in what format (email, in-app alerts).

C is incorrect:
The Messaging section is not a real-time chat platform. SAP Fieldglass does not include an internal chat system between buyers and suppliers for transaction discussions. Communication typically occurs via notifications, emails, or external collaboration tools.

D is incorrect:
While notifications are sent to users, this is not a "direct messaging" system like an internal inbox or instant messaging. Administrators do not use this menu to send ad hoc personal messages; rather, they configure automated system notifications.

Reference:

SAP Fieldglass Administrator Guide – Messaging and Notifications section.
Official SAP training materials highlight that the Admin Messaging area is used for configuring reminders and notifications, not for real-time communication.

Explanation:

1. Streamlining SOW Creation (Answer A)
Purpose: SOW Types reduce complexity by limiting selectable attributes during creation.
Benefit: This ensures consistency and efficiency, allowing users to quickly generate SOWs without being overwhelmed by unnecessary options.
Example: If a company frequently procures IT consulting services, an SOW Type can predefine relevant attributes (like rate structures or deliverable categories), so project managers don’t need to configure them each time.

2. Defining Settings, Rules, and Characteristics (Answer C)
Purpose: SOW Types act as templates that establish rules, workflows, and configurations for different purchasing categories.
Benefit: They enforce compliance and standardization across the organization.
Example: A "Facilities Maintenance" SOW Type might enforce specific approval workflows, budget thresholds, and supplier requirements distinct from an "IT Services" SOW Type.

❌ Incorrect Options

B. Define specifics of a project (costs, timelines, milestones):
These are captured within the individual SOW itself, not the SOW Type. The Type provides structure, but project details are entered per SOW.

D. Summarize legal terms and contractual conditions:
Legal clauses and regulatory policies are managed through SOW templates or clause libraries, not SOW Types.

📑 Reference
SAP Learning Hub: Introducing SOW Types in SAP Fieldglass — SOW Types define the standard structure, rules, and characteristics for SOWs, streamlining creation and ensuring compliance.

Explanation:

Classifications are the foundational administrative objects used to group your business into logical categories (e.g., IT, Marketing, or Facilities). They are essential because they dictate the "path" a user takes during SOW creation.
When a Buyer initiates a new SOW, the Classification is the mandatory first selection. Once selected, the system performs two critical filtering functions:

Template Filtering: Only SOW Templates associated with that specific Classification are displayed.
Supplier Filtering: Only Suppliers qualified/mapped to that Classification are available for selection.

This ensures that the correct legal templates and pre-qualified vendors are used for specific types of work, maintaining organizational governance.

Why Other Options Are Incorrect

A is incorrect: These specifics (costs, timelines, milestones) are defined by Characteristics, such as Events, Fees, and Schedules, which are added to the SOW Template.

B is incorrect: This describes SOW Types. SOW Types (e.g., SOW, SOW Bid) define the underlying business rules, settings, and the general "purchasing category" behavior.

C is incorrect: This describes the role of the SOW Template. While Classifications lead you to a template, the template itself is what stores the default field values and auto-populates information.

Reference
SAP Learning (C_TFG61_2405 Curriculum): "Configuring SOW Classifications" and "Selecting the SOW Classification, Supplier, and Template."

Explanation:

In SAP Fieldglass (Services Procurement module), time sheet approvers (e.g., supervisors or designated approvers via Approval Groups) primarily verify the accuracy and proper allocation of hours before approving submission for invoicing. This ensures correct billing, cost distribution, and compliance with the Statement of Work (SOW), Work Order, or contract terms.

Option A is correct:
Approvers check that hours are properly split and assigned to the right Rate Categories (e.g., standard, overtime, double-time, holiday). This directly impacts rate application, prevents billing errors, and aligns with rate schedules/rules defined in the system.

Option B is correct:
Approvers confirm time is correctly distributed across Task Codes (also called activity/cost codes), which map hours to specific projects, cost centers, WBS elements, or internal accounting objects for accurate cost allocation and financial tracking.

Why the other options are incorrect:

C. Presence of receipts, based on internal policies
→ Receipts are required and verified only in expense sheets (for reimbursable costs like travel/meals), not time sheets, which record labor hours only. Time sheets do not involve receipt attachments or validation.

D. Appropriate Expense Codes
→ Expense Codes apply exclusively to expense sheets for categorizing non-labor costs. Time sheets use Rate Categories for pay types and Task Codes for cost objects, not Expense Codes.
This distinction is core to Time & Expense workflows in SAP Fieldglass, separating time (labor) from expenses.

References:

SAP Help Portal – Time Sheets documentation:
Workers enter time against Task Codes; approvers review/approve submitted time sheets for accuracy before invoicing eligibility (help.sap.com > SAP Fieldglass > Time and Expense Management).

Explanation:

In SAP Fieldglass, the General Ledger (GL) is used primarily for tracking and reporting financial information related to contingent labor and services spend.

The Fieldglass GL:
Acts as a reporting structure, not an accounting system
Helps categorize spend for financial visibility and analysis
Supports integration with external ERP systems (such as SAP S/4HANA or SAP ECC) by providing cost allocation context
Enables customers to map Fieldglass transactions to their internal financial reporting structures
Fieldglass does not perform accounting postings itself; instead, it sends summarized and structured data to the customer’s financial system.

Why the Other Options Are Incorrect

B. To support Accounts Payable ❌
Fieldglass does not perform AP functions. Invoice posting and payment occur in the ERP system, not within Fieldglass.

C. For detailed tracking of task and expense codes ❌
Task and expense tracking is handled through rate structures, expense types, and service entry sheets, not the GL.

D. To define specific types of reimbursables ❌
Reimbursable definitions are managed using expense types and service item configurations, not the General Ledger.

Reference:
SAP Help Portal – SAP Fieldglass Financial Configuration Overview
SAP Learning Hub – SAP Fieldglass Services Procurement & Financial Integration

Explanation:

In SAP Fieldglass integrations, the Initiator field is the primary and most effective way to uniquely distinguish between different integration triggers. This is because it identifies the specific system or user action that started the integration process.

Here’s why each option is correct or incorrect:

A is correct:
The Initiator specifies the source or trigger of the integration (e.g., a user action like "Submit Timesheet," a system event like "Assignment Start Date," or an external system call). This directly tells you why the integration was fired, making it the best way to distinguish between different integration scenarios.

B is incorrect:
A Transaction ID is unique to a specific transaction or message instance, but it doesn’t inherently tell you what triggered the integration — it only identifies that particular message. Different initiators could generate different transactions with different IDs, but the ID itself doesn’t classify the trigger type.

C is incorrect:
Server Status indicates whether an integration message was processed successfully, failed, or is pending. It is useful for monitoring and troubleshooting but does not distinguish what triggered the integration.

D is incorrect:
Client Message typically refers to error or status messages returned to the client system. While it may contain descriptive text, it is not a reliable or structured way to uniquely identify the trigger type of an integration.

Reference:
In SAP Fieldglass integration logs and configuration (e.g., Integration Monitor, iX‑Ray), the Initiator is the key field used to filter, identify, and differentiate integration processes. SAP’s official integration guides stress using the Initiator to determine the context and business process behind an integration call (e.g., “WorkerCreation,” “TimecardSubmission,” “InvoiceGeneration”).