Order-Management-Administrator Salesforce Order Management Administrator Accredited Professional (AP-219) Questions and Answers

The type of relationship that exists between FulfillmentOrder and Order Delivery Method is Lookup (OrderDelivery Method). A Lookup field is a type of custom field that creates a relationship between two objects, but does not support rollup summary fields. In this case, a FulfillmentOrder has a Lookup field named Order Delivery Method that references an Order Delivery Method record. An Order Delivery Method is a record that represents a delivery option for fulfilling orders, such as standard shipping, express shipping, in-store pickup, etc. An Order Delivery Method can have many FulfillmentOrders associated with it, but a FulfillmentOrder can only have one Order Delivery Method. Verified References: https://help.salesforce.com/s/articleView?id=sf.custom_field_types.htm &type=5https://help.salesforce.com/s/articleView?id=sf.order_management_order_delivery_method.htm &type=5

The objects that will be created in Order Management when a customer orders a product through B2C Commerce but changes the quantity ordered after the Order Summary record is created in Order Management, and then returns one of the productsare:

A Return Order object. 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.

A Change Order object. A Change Order is a record that represents a change request for an order or part of an order. A Change Order has a lookup relationship to the Order Summary object, and it contains information such as thechange type, status, date, etc.

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

The object that the user should navigate to to review credit card payment data for a specific Order is Order Payment Summary. An Order Payment Summary is a record that represents a payment made for an order or part of an order. An Order Payment Summary has a lookup relationship to both Order Summary and Invoice objects, and it contains information such as the payment amount, method, status, etc. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.htm &type=5

The best way for an administrator to synchronize licenses from the production org when preparing a sandbox for development is to run the Match Production Licenses to Sandbox without a Refresh tool in Setup. This tool allows administrators to match theirsandbox licenses with their production licenses without refreshing their sandbox. This way, the administrator can ensure that the sandbox has the same number and type of licenses as the production org, and avoid any license-related issues when developingor testing in the sandbox. Verified References:https://help.salesforce.com/s/articleView?id=sf.data_sandbox_licenses.htm &type=5

The object that the administrator shouldlook 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 References:https://help.salesforce.com/s/articleView?id=sf.order_management_credit_memo.htm &type=5

Based on some changes in Universal Containers’ Commerce engine, new Orders are expected to have two additional attributes at the header level. In Order Management, besides Order, the other object that also needsto be extended is Order Summary. An Order Summary is a record that stores information about an order, such as the total amount, the number of items, and the fulfillment status. An Order Summary is created by a process called Create Order Summary Process, which runs whenever an order is created or updated. The process calls a flow called Create OrderSummary Flow, which calculates the order summary fields and creates or updates the order summary record. To extend an object in Order Management, an administrator can create custom attributes on that object that match the API name and data type of the corresponding attributes in B2C Commerce. References: Order Management Objects

Two likely causes that could make the second submission of the same JSON payload fail are:

The payment data must be updated. The payment data in the JSONpayload contains information such as the payment method, amount, and authorization code. If the same payment data is used for the second order, it may cause a duplicate payment error or an invalid authorization error.

The Order Reference Number must be updated. The Order Reference Number is a unique identifier for each order that is generated by the external system and sent in the JSON payload. If the same Order Reference Number is used for the second order, it may cause a duplicate order error or an invalid order error.

Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_order_api.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_payment_api.htm &type=5

Two objects that are found within Order Management are:

Fulfillment Order. A Fulfillment Order is a record thatrepresents a group of products in an order that are fulfilled together from the same location. A Fulfillment Order has alookup relationship to the Order Summary object, and it contains information such as the fulfillment location, delivery method, status,etc.

Payment Summary. A Payment Summary is a record that represents a payment made for an order or part of an order. A Payment Summary has a lookup relationship to both Order Summary and Invoice objects, and it contains information such as the payment amount, method, status, etc.

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

Whenan order contains products that will need to be shipped to multiple addresses, multiple fulfillment orders will be created. A fulfillment order is a record that represents a part of an order that is fulfilled by a specific location and shipped to a specific address. A fulfillment order can have one or more fulfillment order lines, which are the products that are included in the fulfillment order. An order can have one or more fulfillment orders, depending on how many locations and addresses are involved inthe order fulfillment. References: Order Management Objects, Order Fulfillment Flows

One invoice will be created when using the Create Invoice Apex action in a flow. The Create Invoice Apex action is a custom action that creates an invoice for an order summary. An invoice is a document that requests payment from a customer for an order. An invoice can include one or more fulfillment orders and one or more credit memos. A fulfillment order is a record that represents a part of an order that is fulfilled by a specific location. A credit memo is a record that represents a partial or full refund for an order or a fulfillment order. An order summary can have multiple fulfillment orders and credit memos associated with it, but only one invoice will be created for the entire order summary. References: Order Management Objects, [Create Invoice Apex Action]

The type of relationship that exists between FulfillmentOrder and Location is Many-to-One Lookup (Location) FulfilledFrom Location Id. A Lookupfield is a type of custom field that creates a relationship between two objects, but does not support rollup summary fields. A Many-to-One relationship means that many child records can be related to one parent record, but not vice versa. In this case, a FulfillmentOrder has a Lookup field named FulfilledFrom Location Id that references a Location record. A Location is a record that represents a physical location from which order product items are fulfilled, such as warehouses and retail stores. A Locationcan have many FulfillmentOrders associated with it, but a FulfillmentOrder can only have one Location. Verified References: https://help.salesforce.com/s/articleView?id=sf.custom_field_types.htm &type=5https://help.salesforce.com/s/articleView?id=sf.order_management_location.htm &type=5

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 References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_order_routing_rank_by_closest_distance.htm &type=5

The Order Summary object is used to create an invoice. An invoice is a document that requests payment from a customer for an order. An invoice can include one or more fulfillment orders and one or more credit memos. A fulfillment order is a record that represents a part of an order that is fulfilled by a specific location. A credit memo is a record that represents a partial or full refund for an order or a fulfillment order. To create an invoice, an administrator can use the Create Invoice Apex action in a flow. The Create Invoice Apex action requires the Order Summary ID as an input parameter and creates an Invoice record associated with the Order Summary record. References: Order Management Objects, [Create Invoice Apex Action]

When building a flow for multiple locations, an administrator should consider the following challenges:

Multiple locations will introduce nested loops which can make the canvas substantially larger. For example, a flow that handles multiple fulfillment orders per order and multiple fulfillment order lines per fulfillment order will need to loop through both levels of records. This can make the flow more complex and harder to maintain.

Multiple locations can lead to limit exceptions. For example, a flow that queries or updates a large number of records across multiple locations may hit the SOQL query limit or the DML statement limit. To avoid this, an administrator should use bulkified actions and optimize the flow performance. References: Order Fulfillment Flows, [Flow Performance Best Practices]

The correct time and way for creating an Invoice is at any point after the Fulfillment Order is created, by customizing flow “Create Invoice”. This flow is a core action that creates an Invoice record from a Fulfillment Order record, and updates the status of both records accordingly. The administrator can customize this flow to suit their business needs,such as adding conditions, actions, or subflows. Verified References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_create_invoice.htm &type=5

When a customer applies a discount when placing an order, an order adjustment group summary is created. An order adjustment group summary is a record that represents a modification to the order amount,such as a discount, a surcharge, or a tax. An order adjustment group summary can have one or more order adjustments, which are the individual modifications that are applied to the order or the order items. An order can have one or more order adjustment group summaries, depending on how many types of modifications are applied to the order. References: Order Management Objects, [Order Adjustments]

Two ways that an administrator can query Order Summaries using APIs in Workbench are:

Platform API. The Platform API is a set of REST and SOAP APIs that allow developers to access data and functionality in Salesforce from external systems. The Platform API includes various resources and operations for querying, creating, updating, or deleting records in Salesforce, such as Order Summaries. The administrator can use the Platform API in Workbench byselecting the REST Explorer or SOAP Explorer tabs, and entering the appropriate request URL and parameters.

Composite API. The Composite API is a type of REST API that allows developers to execute multiple subrequests in a single HTTP request. The Composite API includes various resources and operations for batching, tree, sObject collections, or transactions in Salesforce, such as Order Summaries. The administrator can use the Composite API in Workbench by selecting the REST Explorer tab, and entering theappropriate request URL and JSON body.

Verified References: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite.htm

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 References:https://help.salesforce.com/s/articleView?id=sf.order_management_return_order.htm &type=5

The Analyze function in the Lightning Record Page editor helps an administrator analyze the performance of a Lightning RecordPage. It provides recommendations on how to improve the page load time, such as removing unused components, reducing the number of fields, or using conditional visibility rules.

Use Data Loader. Data Loader is a client application that allows administrators to bulkimport or export data from Salesforce using CSV files. The administrator can use Data Loader to import data into Order Management objects, such as Order Summary, Order Item Summary, Fulfillment Order, etc., or export data from these objects for backup or analysis purposes.

Verified References: https://appexchange.salesforce.com/ https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5