A user's ability to view reports in SAP Fieldglass is governed by a multi-layered security model. The user role (B) serves as a primary container for a set of functionalities. Specific permissions (D) are assigned to these roles, granting granular access to actions like viewing, running, or creating reports. Finally, reports are organized into folders, and users must have explicit access to the report folders (E) to see the reports contained within them. These three factors—role, permissions, and folder access—work in conjunction to determine a user's report visibility.

A. Buyer company annual revenue: This is an external financial metric of the organization and has no bearing on internal application access controls for individual users.

C. Number of active users for each company instance: This is a system or license metric that does not influence the specific report access rights of any single user.

1. SAP Fieldglass Help Portal

"User Roles": The documentation specifies that user roles are collections of permissions that determine a user's access to various modules and functionalities

including Analytics and Reporting. A user's assigned role is the foundation of their access rights. (Reference: SAP Fieldglass Administrator documentation on User Role Management).

2. SAP Fieldglass Help Portal

"Reporting and Analytics Permissions": The official guides detail the specific permissions available for reporting

such as 'Report - View'

'Report - Run'

and 'Report - Edit'. These permissions must be enabled within a user's role to grant visibility and access to reporting functions. (Reference: SAP Fieldglass Reporting Administration Guide

Chapter on 'Permissions').

3. SAP Course TFG61 - SAP Fieldglass Services and External Workforce: The official certification courseware explains that report visibility is controlled not only by user role permissions but also by folder-level security. It states that administrators must grant users or user groups access to specific report folders. (Reference: TFG61 Course Materials

Unit on 'Analytics'

Section 'Report Folder Security').

The 'Contact Us Details' page is the designated administrative area within SAP Fieldglass for configuring Program Office contact information. An administrator navigates to this section to input details such as email addresses, phone numbers, and physical addresses. This information is then automatically appended to the footer of all system-generated email notifications sent from the application. This centralized setting ensures that all recipients have consistent and accurate contact information for the Program Office, eliminating the need to edit individual email templates.

B. Email Message Template: This is incorrect because templates are used to customize the body of specific types of messages, not to apply a global footer across all communications.

C. Message Center: This is incorrect as the Message Center is an interface for users to view and manage their received and sent messages within the application, not a configuration area.

D. Messages: This is incorrect because 'Messages' is a general term and not a specific administrative module for configuring system-wide settings like email footers.

1. SAP Fieldglass Help Portal

"Setting Up Company Information": The official documentation details the administrative path Admin > Company > [Select Company] > Contact Us Details. This section explicitly states that the information entered here is used to populate contact details in system communications

including email footers. (Accessed via SAP Help Portal for SAP Fieldglass Administration).

2. SAP Fieldglass "Configuration Guide": This guide outlines the steps for company-level configuration. In the chapter related to company settings

it specifies that the 'Contact Us Details' page is the source for the Program Management Office (PMO) contact information that appears in notifications. (Reference: SAP Fieldglass Configuration Guide

Section on Company Profile Management).

SAP Fieldglass allows the attachment of a Microsoft Excel template to a report to enhance the standard output with advanced Excel functionalities. This feature is used when the raw data exported from Fieldglass needs to be presented with specific corporate branding, custom formatting, or complex analysis. The template can be pre-configured with multiple worksheets containing pivot tables, charts, and formulas. When the report is run, Fieldglass populates a designated worksheet with the raw data, and the pre-built elements in other worksheets automatically update, providing a rich, formatted, and analytical final document.

B. Your company has maxed out on the number of scheduled reports.

This is incorrect. Attaching a template affects a report's format, not the system's capacity or limits for scheduling reports.

E. You do not have permission to receive the report any other way.

This is incorrect. Report permissions control access to data and the ability to run a report, not the formatting method used for the output.

---

1. SAP Fieldglass Reporting for Administrators Guide: In the section "Creating a Report with a Microsoft Excel Template

" the documentation explicitly states the purpose is to apply custom formatting and add advanced Excel features. It details how to create a template with a dedicated data sheet and other sheets for pivot tables

charts

and formulas. This directly supports using templates for better formatting (A)

including multiple worksheets with pivot tables (C)

and adding charts or formulas (D). (Accessed via SAP Help Portal

specific document version for SAP Fieldglass 2405).

2. SAP Fieldglass - Self-Paced Training Courseware (FG100): The module on "Reporting and Analytics" describes the use of Excel templates as a method for advanced report customization. It highlights that users can "add charts

pivot tables

and formulas to the template to create a more dynamic report

" which validates options A

C

and D as primary use cases. (Material available through SAP Learning Hub).

In SAP Fieldglass, currency management is a foundational configuration step. Before a currency can be utilized in any transaction (such as a job posting or a Statement of Work), it must first be enabled for the company and then explicitly associated with the specific organizational structures where it will be used. The primary organizational structures that govern transactional data are Business Units and Sites. Associating a currency with these objects makes it available for selection when users create documents linked to that specific Business Unit or Site, ensuring proper financial and geographical context.

A. Cost Center: A Cost Center is a financial accounting object to which costs are posted. While it has a currency, the availability of a currency for a transaction is governed by the higher-level organizational units (Site, Business Unit), not the individual cost center.

C. Job Posting Template: A Job Posting Template is a transactional template that uses a currency. The currency must already be configured and associated with a Site and Business Unit before it can be selected within the template.

1. SAP Fieldglass Configuration Guide: In the "Currency Management" section

the guide specifies that after a currency is enabled at the company level

it must be associated with the relevant Business Units and Sites to be made active for use in transactions within those organizational units. (Reference: SAP Fieldglass Help Portal

Configuration Guide

Chapter on Foundational Data).

2. SAP Learning Hub Course FG610 (SAP Fieldglass Foundational Objects and Configuration): Unit on "Organizational Structure" and "Financial Data" details the hierarchy and relationships. It clarifies that Business Units and Sites are the core objects for which operational settings

including active currencies

are defined. The configuration flow shows currency assignment to these specific objects.

In SAP Fieldglass, the Transaction ID is a unique identifier automatically generated for every single integration event, whether inbound or outbound. This ID serves as the primary key for tracking and troubleshooting specific data exchanges. It allows administrators and support teams to isolate and analyze a particular transaction within the Integration Monitor, distinguishing it from all other integrations, even those triggered by the same initiator or containing similar data. This uniqueness is fundamental for auditing, error resolution, and ensuring data integrity between connected systems.

A. Initiator: The initiator (a user or system) can trigger numerous integrations, so this value is not unique to a single transaction.

C. Server Status: This indicates the general operational state of the server (e.g., 'Success', 'Error') and is not a unique identifier for an individual integration event.

D. Client Message: This refers to the data payload of the integration. While the content may vary, it is not designed as a unique identifier and could be identical across different transactions.

1. SAP Help Portal - SAP Fieldglass: Integration Monitor Guide: The guide details the functionality of the Integration Monitor tool. It explicitly states

"Each transaction is assigned a unique Transaction ID that can be used to track the progress and status of the integration." (Refer to the section on 'Viewing Transaction Details').

2. SAP Help Portal - SAP Fieldglass: Web Services API Guide: In the sections describing API responses and error handling

the documentation consistently refers to the TransactionID as the unique identifier returned by the system for each API call

which is essential for support and debugging. (Refer to the chapter on 'API Responses and Status Codes').