Worker or Work Item Closure Requirements:

Closure refers to finalizing or ending a worker's engagement or completing a work item in SAP Fieldglass.

Mandatory Details for Closure:

Defined Reason:The system requires a predefined reason code for tracking and auditing purposes.

Closure Date:A specific end date must be provided to indicate when the worker or work item engagement terminates.

Non-Mandatory Details:

Supervisory Approval:While approvals may be part of workflow setups, they are not a mandatory step for closure.

Specific Comments:Comments are optional and depend on organizational policy.

References:SAP Fieldglass Workflow Management – Worker Closure Requirements

Work Order Overview:

In SAP Fieldglass, aWork Orderis a structured dataset that contains all relevant information for a specific assignment, contract, or engagement.

It includes key details such as job description, rates, duration, worker information, and approval workflows.

Purpose:

It acts as the central document for managing the terms of an engagement between the buyer organization and the worker (via the supplier).

Ensures transparency and compliance with organizational and legal requirements.

References:SAP Fieldglass – Work Order Overview

Approval Group Requirements

A. Approval Groups for each currency: This ensures compliance with financial policies specific to regional or currency differences.

D. Approval Groups for different modules: Each SAP Fieldglass module (e.g., Contingent Workforce or Services Procurement) requires dedicated Approval Groups due to unique workflows.

Excluded Options

B. The same Approval Group for multiple modules: This is not recommended as modules have distinct transaction types and workflows.

C. Specific Users must be assigned: While users are crucial, this is not a mandatory configuration requirement for creating Approval Groups.

Reference

SAP Fieldglass documentation: "Approval Groups – Configuration and Best Practices."

Use of Invoiced Time/Expense Sheets

A. Buyers run Reports or download the Invoices to process payments externally: Most buyers use external financial systems to process payments based on reports or downloaded invoices.

B. Buyers consolidate the Invoices to create bulk Supplier invoices: Consolidation allows efficient management of multiple expenses into a single invoice for payment.

Excluded Options

C. Invoices are used to calculate tax adjustments within SAP Fieldglass: SAP Fieldglass does not typically handle detailed tax adjustments directly.

D. Buyers submit payments in SAP Fieldglass to Suppliers for the generated Invoices: Payments are processed externally, not directly through SAP Fieldglass.

Reference from SAP Fieldglass Documentation

Refer to "Invoice Management and Reporting" for detailed use cases.

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."

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

Setting Program Office Contact Details

TheEmail Message Templateallows administrators to include Program Office contact details in the footer of all automated emails sent by SAP Fieldglass.

This ensures consistent communication and provides recipients with a direct point of contact.

Excluded Options

B. Program Office User's Account: User account settings do not control footer content in messages.

C. Home Page Announcement: This is for displaying messages on the platform's homepage, not in emails.

D. Message Center: Used for in-platform messaging, not email communication.

Reference

SAP Fieldglass documentation: "Customizing Email Message Templates."