The Data Loader in the SAP Field Service Management Master Data module is a tool for bulk data import and manipulation. Its primary, distinct operations are creating new records and updating existing ones. The update function offers two specific modes: 'merge', which modifies only the fields provided in the import file while leaving others unchanged, and 'overwrite', which replaces all of an existing record's values with those from the file. While deletion is possible, it is not a separate operation mode but is achieved by performing an update that sets the isDeleted flag to 'true' for the specified records.

C. Delete data records.

Deletion is not a distinct, top-level operation mode. It is accomplished by performing an update operation that sets a deletion flag on the records.

E. Read data records.

The Data Loader is an import tool for writing data (creating/updating). It is not designed for reading or exporting data from the system.

1. SAP Help Portal: SAP Field Service Management - Data Loader.

Reference: In the Administrator Guide for SAP Field Service Management

the "Data Loader" section details the available operations. It explicitly mentions the ability to "create" new objects. It also describes the two methods for updating: "overwrite all of its fields or merge the changes

" which correspond directly to options D and B. The guide further explains that to delete an object

one must "set the isDeleted field to true

" confirming that deletion is a function of an update

not a standalone operation. This supports the selection of A

B

and D as the primary

distinct modes.

A trigger in an SAP Field Service Management business rule defines the specific circumstances under which the rule's actions will be executed. This mechanism is composed of three core logical components:

1. Event (E): The specific system occurrence that initiates the rule's evaluation (e.g., Activity Created, Service Call Updated).

2. Conditions (D): A set of logical criteria that are evaluated after the event occurs. The rule only proceeds if all conditions are met.

3. Variables (B): Placeholders used to capture and store data from the event's context (e.g., the status of a service call). These variables are then used within the conditions to perform the evaluation.

Together, these three components form the complete "when/if" logic of the trigger.

A. Execution count: This is metadata related to the rule's execution history or a potential setting to limit its runs, not a logical component of the trigger itself.

C. Action: The action is the "then" part of the rule, defining what the rule does after the trigger's conditions are successfully met.

1. SAP Help Portal

SAP Field Service Management

"Business Rules": The official documentation outlines the structure for creating a business rule. It details the distinct sections for configuring the Trigger (which includes the Event and Conditions) and Variables. While the UI separates them

variables are functionally integral to defining the conditions. The documentation states

"A business rule consists of the following parts: Trigger

Variables

Actions." The trigger's conditions rely on the defined variables. (Accessed under SAP Field Service Management -> Administration -> Business Rules -> Creating a Business Rule).

2. SAP Help Portal

SAP Field Service Management

"Creating a Business Rule": This guide illustrates the configuration steps. It shows that after selecting the Event on the Trigger tab

you define Variables on a separate tab

which are then used to build the Conditions on the Trigger tab. This demonstrates the tight coupling and necessity of all three components (Event

Variables

Conditions) for the trigger mechanism to function. (Accessed under SAP Field Service Management -> Administration -> Business Rules -> Creating a Business Rule).

In SAP Field Service Management, a Smartform progresses through a defined lifecycle, represented by specific statuses. The primary valid statuses are:

Editing: The initial state when a Smartform is created or a new version is being designed. In this state, it is not available for use in the field.

Released: Once the design is complete, the Smartform is released. This makes the specific version active and available for technicians to use on their mobile devices.

Deactivated: A released Smartform version can be deactivated, which removes it from active use. It can no longer be assigned to new activities, but existing completed forms are preserved.

A. New, Editing, Archived: 'Archived' is not a standard status for Smartforms. The correct status for retiring a form from active use is 'Deactivated'.

B. New, Editing, Released: While a form is "new" upon creation, its official status is 'Editing'. 'New' is not a distinct status in the Smartform management interface.

D. Editing, Translation, Closed: 'Translation' is a feature or process for localizing a Smartform, not a primary status. 'Closed' is a status typically associated with transactional documents like service calls, not templates.

1. SAP Help Portal - Field Service Management

Smartforms: The official documentation describes the process of creating

editing

releasing

and managing versions of Smartforms. The statuses 'Editing'

'Released'

and 'Deactivated' are central to this version management.

Reference: SAP Help Portal

SAP Field Service Management > Smartforms > Working with Smartforms. The section on versioning details that a form is in an 'Editing' state until it is 'Released'. Subsequently

a released version can be 'Deactivated'.

2. SAP Help Portal - Field Service Management

Smartform Designer: The guide for the Smartform Designer explicitly details the lifecycle.

Reference: SAP Help Portal

SAP Field Service Management > Smartforms > Smartform Designer. The documentation explains that a new form or version starts in 'Editing' status. The "Release" action changes the status to 'Released'

and the "Deactivate" action is available for released versions.

The Screen Configuration feature in SAP Field Service Management is a powerful tool for tailoring the user interface. Its primary capabilities include controlling the layout of fields on a screen, such as displaying, hiding, reordering (sorting), and organizing them into groups. Furthermore, it allows for the implementation of business logic through UI rules, which can use expressions for field validation (e.g., making a field mandatory based on another field's value). The feature also supports multilingual environments by displaying the appropriate custom translations for field labels, ensuring a localized user experience across different regions.

C. Can only be defined for mobile screens: This is incorrect. Screen configurations can be applied to both the mobile application and web-based applications like the Planning & Dispatching board.

D. Can define color coding: This is incorrect. While the UI can be customized, defining specific color codes for fields or text is not a standard function within the Screen Configuration tool itself.

1. SAP Help Portal

SAP Field Service Management

Administration Guide

"Screen Configuration" section: This document details the core functions of screen configurations. It explicitly states that administrators can "define which fields are displayed on a screen

in which order

and how they are grouped." This directly supports option A.

2. SAP Help Portal

SAP Field Service Management

Administration Guide

"UI Rules" subsection: This section explains that UI rules

which are part of a screen configuration

can be used to define expressions to control field properties like IsRequired and IsReadOnly. This functionality is used for field validation

supporting option B.

3. SAP Help Portal

SAP Field Service Management

Administration Guide

"Translations" section: This guide explains how custom labels and their translations are managed. The Screen Configuration tool is where these labels are applied to fields

and it is responsible for rendering the correct translated text based on the user's language settings

which supports option E. The documentation also shows screen configurations being applied to web modules

invalidating option C.

SAP Field Service Management provides a RESTful (Representational State Transfer) API, known as the Data API, for accessing and manipulating its data. To update an existing record, a developer would send an HTTP PATCH request to the specific object's endpoint. This request includes the object's unique identifier and a JSON payload containing the fields to be modified. This approach aligns with the standard principles of REST architecture for performing partial updates on resources.

B. Using an OData service: While OData is built on REST principles, the SAP FSM Data API is documented as a general RESTful API and does not adhere to the specific OData protocol conventions.

C. Using an RFC-enabled service: RFC (Remote Function Call) is a proprietary SAP protocol used for communication between ABAP-based systems (e.g., SAP S/4HANA) and is not the technology used for the FSM cloud API.

D. Using a SOAP-based service: The SAP FSM API is built on the modern REST architectural style, which uses standard HTTP methods, not the older, more rigid SOAP (Simple Object Access Protocol) protocol.

1. SAP Help Portal

SAP Field Service Management Developer Guide

Data API - Introduction: "The Data API is a RESTful API that allows you to access and manipulate data in SAP Field Service Management." This statement confirms the fundamental architecture of the API.

2. SAP Help Portal

SAP Field Service Management Developer Guide

Data API - Core Concepts

HTTP Verbs: This section explicitly lists the standard HTTP methods used. It specifies: "PATCH: Updates an existing object. You can use this method to update one or more properties of an object." This directly confirms the method for updating a record.

Creating a "Moment Set," now known as a Checklist Template in SAP Field Service Management, is a multi-step design process. The process begins with creating the template container itself (B. Create Moment set). This empty template is then populated with individual elements, or "Moments," which are the questions, instructions, or input fields for the technician (D. Create Moment). To add dynamic behavior, such as conditional visibility or validation, business rules must be configured for these moments (A. Setup Business rule). These three steps constitute the core activities for designing and building a functional checklist template.

C. Create Item and assign it: Items, such as equipment or materials, are not assigned during the creation of a generic checklist template. The template is assigned later to a specific activity or service call which may relate to an item.

E. Create and assign QR code: A QR code is a mechanism used to trigger or launch an already published checklist template. Its creation is a deployment step that occurs after the template has been fully designed and created.

1. SAP Help Portal

SAP Field Service Management

"Creating Checklist Templates": This document outlines the fundamental steps. It states

"1. In the main menu

select Smartforms & Checklists. 2. Select New Checklist Template... 4. From the toolbox

drag and drop the required elements [Moments] to the canvas." This directly supports options B and D.

2. SAP Help Portal

SAP Field Service Management

"Checklist Business Rules": This source details the configuration of logic within a template. It explains

"Business rules allow you to define the behavior of a checklist. For example

you can define a rule that a certain element is only displayed if a certain value has been entered in a previous element." This supports option A as an integral part of the creation and design process.

3. SAP Help Portal

SAP Field Service Management

"Checklist QR Codes": This document clarifies the purpose of QR codes

stating

"You can generate a QR code for a checklist template. When a technician scans this QR code with their mobile device

the corresponding checklist is opened." This confirms that QR code generation is a post-creation step for triggering a completed template

making option E incorrect as a creation step.

In SAP Field Service Management Smartforms, a visibility condition is a powerful feature used to create dynamic and context-sensitive forms. It is an expression that evaluates to either true or false. When applied to a UI component, the component will only be displayed if the condition evaluates to true. This logic can be applied at a granular level to individual elements (like text fields, checkboxes, or labels) or at a broader level to entire chapters, effectively hiding or showing sections of the form based on user input or pre-existing data.

B. It is used to change Smartform mode from development to active.

This is incorrect. Changing a Smartform's status is a lifecycle management action performed in the administration panel, typically referred to as "publishing," and is not controlled by a dynamic condition within the form itself.

D. It is used to hide a Smartform from the mobile device.

This is incorrect. The assignment and availability of an entire Smartform (checklist) to a user or device is managed through business rules and user group permissions, not by a visibility condition within the form's design.

1. SAP Help Portal

SAP Field Service Management

Smartforms and Feedback

Smartform Designer:

Reference for Answer A (Elements): In the section describing various UI elements (e.g.

Input

Checkbox

Label)

the "Visibility Condition" property is detailed. The documentation states

"You can enter an expression to define when the element is visible. If the expression evaluates to true

the element is displayed. Otherwise

it is hidden." This directly supports that visibility conditions are used to hide specific elements.

Reference for Answer C (Chapters): In the section describing the "Chapter" element

the documentation explicitly mentions

"You can also set a visibility condition for a chapter. If the condition is not met

the chapter and all its elements are hidden." This confirms that visibility conditions apply to chapters.

The SAP Field Service Management Query API is a RESTful API designed for retrieving data from the system. According to the official SAP developer documentation, all responses from the Query API are returned in JSON (JavaScript Object Notation) format. JSON is a lightweight, human-readable, and machine-parsable data-interchange format, making it the standard for modern web APIs. The API does not support other data formats like XML or HTML for its response payload.

A. Text: This is too generic. While JSON is a text-based format, the response is specifically structured as a JSON object, not as unstructured plain text.

B. XML: The SAP FSM Query API exclusively uses JSON for its responses. It does not provide an option to receive data in XML format.

C. HTML: HTML is a markup language used to display content in a web browser. It is not a data interchange format and is not used for API responses.

1. SAP Help Portal

SAP Field Service Management Developer Guide: In the "Query API" section

all examples of API responses are explicitly shown in JSON format. The guide states

"The Query API is a RESTful API that allows you to retrieve data from SAP Field Service Management." The structure of RESTful responses in this context is consistently JSON. (See section: Query API > Querying Objects).

2. SAP Help Portal

SAP Field Service Management Developer Guide: The "API Basics" section implicitly confirms the use of JSON by detailing the structure of requests and responses

which aligns with standard JSON-based REST API conventions. The Content-Type header for such APIs is typically application/json. (See section: API Basics > Authentication and Authorization).

A field service technician updates the status of a service assignment by interacting with the predefined workflow steps presented in the mobile application. These steps, such as 'Start Travel', 'Check In', 'Complete', directly correspond to a change in the assignment's status. Selecting a workflow step is the designated action for a technician to report their progress, which in turn updates the status in the back-end system, ensuring real-time visibility for dispatchers and planners.

A. By adding a checklist: Adding or completing a checklist is a task performed during the service execution phase; it does not inherently change the overall status of the assignment itself.

B. By navigating to the address on the service assignments: While initiating navigation might be associated with the 'En Route' status, the status change is explicitly triggered by selecting the 'Start Travel' workflow step, not by the navigation action alone.

C. By opening the service assignments: Opening an assignment in the mobile application is a preparatory step to view details. This action is for information retrieval and does not alter the assignment's status.

1. SAP Help Portal

SAP Field Service Management Mobile for iOS and Android: In the section "Working with Activities"

the documentation states

"When you are ready to begin working on an activity

you can update its status by selecting a workflow step." This confirms that workflow steps are the primary mechanism for status updates. (SAP Help Portal

SAP Field Service Management

"Working with Activities" section).

2. SAP Learning Hub

Course FSM100 - SAP Field Service Management: Unit 5

"Mobile Application

" details the technician's user experience. It explicitly covers how technicians progress through a service call by selecting sequential workflow steps on their mobile device

which updates the activity status accordingly. (SAP Learning Hub

FSM100

Unit 5

Lesson: Mobile Application Workflow).