ORDER-MANAGEMENT-ADMINISTRATOR Practice Questions

The object that the administrator should look at to find payment information about a returned item

on an Order Summary is Credit Memo. A Credit Memo is a record that represents a refund or credit

issued to a customer for a returned item. A Credit Memo has a lookup relationship to both Order

Summary and Return Order objects, and it contains information such as the credit amount, status,

payment method, etc. Verified Reference:

https://help.salesforce.com/s/articleView?id=sf.order_management_credit_memo.htm&type=5

Three possible causes of this issue are:

The administrator has duplicate Product SKUs in the JSON query. A Product SKU is a unique identifier

for a product that is used to track inventory and sales. A Product SKU must be unique within an org,

and it cannot be duplicated in a composite API call. If the administrator has duplicate Product SKUs in

the JSON query, it will cause an error when loading test orders via the Workbench.

The number of subrequests in the JSON query exceeds the 20 subrequest limit. A subrequest is a

single HTTP request that is part of a composite API call. A composite API call can contain up to 20

subrequests in a single JSON body. If the administrator has more than 20 subrequests in the JSON

query, it will cause an error when loading test orders via the Workbench.

Record IDs used within the request are incorrect. A record ID is a unique identifier for a record that is

used to reference and manipulate data in Salesforce. A record ID must be valid and exist in the org,

and it must match the data type and format of the corresponding field. If the administrator has

incorrect record IDs in the JSON query, such as using 15-character IDs instead of 18-character IDs, or

using IDs from a different org, it will cause an error when loading test orders via the Workbench.

Verified Reference: https://developer.salesforce.com/docs/atlas.enus.api_rest.meta/api_rest/resources_composite_composite.htm

https://developer.salesforce.com/docs/atlas.enus.api_rest.meta/api_rest/dome_composite_sobject_tree_flat.htm

The number of Fulfillment Orders that would be created for this order is one per destination, totaling

3. A Fulfillment Order is a record that represents a group of products in an order that are fulfilled

together from the same location. A Fulfillment Order has a lookup relationship to the Order

Summary object, and it contains information such as the fulfillment location, delivery method,

status, etc. The number of Fulfillment Orders created depends on three factors: Fulfillment Location,

Delivery Method and Recipient Address. These factors determine how the Order Items are grouped

and allocated to Fulfillment Orders based on routing rules and inventory availability. In this case,

since the products must be shipped to three different locations, three Fulfillment Orders are created

for each destination. Verified Reference:

https://help.salesforce.com/s/articleView?id=sf.order_management_fulfillment_order.htm&type=5

The Platform API and the Composite API are two ways that an administrator can use APIs in

Workbench to query Order Summaries. The Platform API allows querying, creating, updating,

deleting, and searching records in Salesforce. The Composite API allows combining multiple requests

into a single call, which can improve performance and reduce complexity12

The administrator can use two tools to debug an issue with an Apex trigger: Log Inspector in the

Developer Console and Debug Logs in Setup. The Log Inspector is a tool that displays a graphical

representation of a debug log, which is a record of database operations, system processes, and errors

that occur when executing a transaction or running unit tests. The Log Inspector helps you analyze

and troubleshoot your code by highlighting errors, checkpoints, and execution times. The Debug Logs

page in Setup lets you monitor and retain debug logs for users, Apex classes, Apex triggers, and

Lightning components. You can view, download, or delete debug logs from this page.

At minimum, a custom attribute must be created on the Order Item and Order Item Summary objects

for the values to automap in Order Management from B2C Commerce Cloud at the order item level.

A custom attribute is a field that stores additional information about an object that is not captured by

the standard fields. A custom attribute can be created on any object in Order Management, but it

must have the same API name and data type as the corresponding attribute in B2C Commerce Cloud.

For example, if an order item has a custom attribute called Color in B2C Commerce Cloud, then an

Order Item and an Order Item Summary must also have a custom attribute called Color in Order

Management for the value to automap. Reference: Order Management Objects, [Custom Attributes]

Dynamic Actions allow an administrator to add visibility rules for the buttons in the Highlights Panel

on the Lightning Record Page. Dynamic Actions let you configure when and where actions appear on

a record page based on criteria such as record field values, user permissions, or device type.

The object record that is created when customer returns a product after fulfillment is Return Order. A

Return Order is a record that represents a return request for an order or part of an order. A Return

Order has a lookup relationship to both Order Summary and Change Order objects, and it contains

information such as the return reason, status, date, etc. Verified Reference:

https://help.salesforce.com/s/articleView?id=sf.order_management_return_order.htm&type=5

The recommended approach for deploying certain pages in Order Management to approved mobile

devices is to install the Salesforce mobile app from Apple Store or Google Play and save the pages

with the options of both Desktop and Phone applied. The Salesforce mobile app is designed for easy

data access on the go. You can view Order Management record pages on the mobile app, but you

can’t access its console features, like screen flows. To make a page available on the mobile app, you

need to save it with the options of both Desktop and Phone applied in the Lightning App Builder.

Reference: Salesforce Order Management, Mobile App Theme FAQ

The best way for the administrator to accomplish this task is to add the “Order Routing Rank By

Closest Distance” action to the fulfillment flow. This action is a flow core action that ranks the

fulfillment locations by their distance from the delivery location, and returns a list of ranked

locations. The administrator can use this action to find the optimal fulfillment location for each order

based on proximity. Verified Reference:

https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_order_routing_rank

_by_closest_distance.htm&type=5