C_TFG51_2405 Questions and Answers

Purpose of Transaction ID

TheTransaction IDis a unique identifier assigned to each integration transaction in SAP Fieldglass.

It ensures seamless tracking and differentiation between multiple integrations, especially in cases where several processes are triggered simultaneously.

Excluded Options

A. Client Message: Refers to specific integration messages, not unique identifiers.

B. Server Status: Indicates the operational status, not a distinguishing factor for transactions.

D. Initiator: Refers to the user or system triggering the process, not a unique identifier.

Reference

SAP Fieldglass documentation: "Integration Management – Understanding Transaction IDs."

Default Scheduling Limits:

SAP Fieldglass allows a maximum of 25 scheduled reports per company by default.

Increasing the Limit:

To increase this limit, a request must be made to theSAP Fieldglass Support Teamvia a support ticket.

This ensures the system's performance is not impacted and the requested change aligns with SAP's best practices.

Non-Applicable Options:

Configuration changes (via the Dashboard, Upload Connector, or Admin Menu) do not provide the functionality to adjust report scheduling limits.

References:SAP Fieldglass Support Documentation – Report Configuration

Role-Based Permission Assignment:

In SAP Fieldglass, user roles are mapped to workflows and determine the permissions assigned to users.

Roles (e.g., Buyer, Approver, Supplier Contact) are configured during system setup based on organizational needs.

How Permissions Are Assigned:

When a user is assigned to a specific role, their permissions are automatically aligned to the role’s predefined attributes.

Permissions define what the user can view, edit, or approve within the system.

Role Setup Process:

Administrators configure workflows and assign roles during the implementation or user onboarding process.

Changes to roles or permissions can be made via theAdmin > User Accountssection.

References:SAP Fieldglass Configuration Guide – User Role Management

Purpose of Advisor Reports

Advisor Reports are designed to provide users with actionable insights based on the data within SAP Fieldglass.

They help users identify trends, flag potential issues, and offer recommendations for improving contingent workforce processes.

These reports empower users to make informed decisions and take appropriate actions, such as adjusting budgets or reallocating resources.

Excluded Options

A. To educate Users on the Reporting module and functionality: This describes training or documentation, not the purpose of Advisor Reports.

C. To assist in the process of creating new Reports: Advisor Reports are predefined, not tools for report creation.

D. To support Users through the hiring process: While indirectly useful, this is not the primary intent of Advisor Reports.

Reference

SAP Fieldglass documentation: "Advisor Reports Overview and Usage."

Worker Pay Type Configuration

Worker Pay Type defines rates based on the type of worker selected for a position.

This ensures that pay structures align with worker classifications, such as hourly, salaried, or project-based rates.

Excluded Options

B. Unit Type: Relates to units of work (e.g., hours, days), not worker-specific rates.

C. Labor Type: Categorizes labor but does not directly control rates.

D. Contingent Type: Governs workflow and templates, not rate structures.

Reference

SAP Fieldglass documentation: "Configuring Worker Pay Types and Rates."

Definition of Approval Group

Approval Groups consist of users assigned to review and approve specific Work Items (e.g., job postings, time sheets).

Notifications are sent to these users whenever their action is required.

Excluded Options

B. Document defining approval levels: This describes approval policies, not the group itself.

C. Supplier approval of Time Sheets: Suppliers are not part of buyer-side Approval Groups.

D. Approving multiple objects simultaneously: Approval Groups handle individual transactions as per their workflows.

Reference

SAP Fieldglass documentation: "Understanding Approval Groups and Workflow Assignments."

Role of Job Posting Templates

Job Posting Templates provide buyer companies with granular control over the configuration and rules for specific labor positions.

These templates standardize requirements such as qualifications, rates, and approval workflows, ensuring compliance and efficiency.

Excluded Options

A. Decision Form: Guides procurement type selection but does not provide detailed control over labor position settings.

B. Contingent Type: Governs workflow and organizational rules but lacks position-specific customization.

C. Approval Groups: Manage approval workflows but do not dictate position-specific configurations.

Reference

SAP Fieldglass documentation: "Job Posting Templates – Configuration and Use."

Task Codes Overview:

Task Codesare used to define specific tasks or activities for which a worker can record time.

These are critical for timesheet submissions as they provide context for the hours worked.

Importance:

Without at least one Task Code, a worker cannot associate their time entries to a specific task, which prevents them from submitting time for approval.

Task Codes also ensure accurate billing and payment processes.

Configuration:

Administrators assign Task Codes during the worker's onboarding process in theWorker Profile > Task Assignmentssection.

References:SAP Fieldglass Timesheet Management – Task Code Configuration

Purpose of a Corporate Calendar

A Corporate Calendar in SAP Fieldglass defines regional or organizational schedules, including holidays and work patterns.

It supports compliance with local regulations and facilitates accurate time tracking for contingent workers.

Included Details

Recurring non-working days: Allows for pre-scheduled non-working days (e.g., weekends, public holidays) that apply regularly.

Specific non-working days: Designates individual dates (e.g., one-time public holidays) when no work is expected.

Excluded Options

B. Default date format: Relates to system settings, not corporate calendar configuration.

D. Core working hours: Defines work schedules but is not part of the corporate calendar itself.

Reference

See SAP Fieldglass user guides under "Corporate Calendar Configuration" for detailed setup.

Minimum Shifts for Rate Schedule:

ARate Schedulein SAP Fieldglass is used to define hourly rates for workers based on shifts or specific working hours.

At leastone shiftis required to create a valid rate schedule.

Reason for the Requirement:

Without defining at least one shift, the schedule cannot serve its purpose of associating rates with specific working hours.

References:SAP Fieldglass Rate Management – Rate Schedule Creation

Push Time Sheets Functionality

ThePush Time Sheetspage enables administrators to manually resend a Time Sheet to a worker’s account if it has not been received or is missing.

This helps resolve instances where system or communication issues have prevented Time Sheet delivery.

Excluded Options

B. Advance a Time Sheet through the approval process: Approvals are managed via workflows, not the Push Time Sheets page.

C. Send notifications for overdue Time Sheets: Notifications are configured separately in system settings.

D. Submit a Time Sheet on the Worker’s behalf: Time Sheets must be submitted by workers or proxies, not through this feature.

Reference

SAP Fieldglass documentation: "Using the Push Time Sheets Feature."

Potential Candidates Functionality:

This feature is used to identify and match candidates from a pool based on their skills, experience, and other criteria outlined in the Job Posting.

Process:

When a Job Posting is created, suppliers or internal databases may propose candidates.

ThePotential Candidatesfunctionality allows for automated or manual filtering of these candidates to find the most suitable options.

References:SAP Fieldglass Job Posting – Finding Potential Candidates

SAP Fieldglass allows organizations to manage their contingent workforce effectively. When it comes to creating buyer users, there are specific methods supported by the system:

Access the User List:Navigate toAdmin > User Accounts > User Listin the SAP Fieldglass buyer module. This is where all current user accounts are displayed.

Create a New User:

Click on the "Create" button to start a new user creation process.

Enter the required user details such asUsername, Email Address, Roles, and Permissions.

Assign specific buyer groups, ensuring the user has access to the correct modules and functions.

Save the User Account:Once all required fields are filled, click "Save" to create the new user. The system may send an email notification to the user with their login details.

References:SAP Fieldglass Help Portal (User Management) - Help Documentation on Buyer Users