Pass the Salesforce Salesforce Order Management Order-Management-Administrator Questions and answers with CertsForce

The PricebookEntry, Contact, and Account objects are required when creating orders using the composite API. The composite API is a REST API that allows creating multiple records in one request. To create an order using the composite API, an administrator needs to provide the following information:

The Account ID of the customer who placed the order

The Contact ID of the customer who placed the order

The Pricebook Entry IDs of the products that are ordered

The quantity and unit price of each product

The order status andcurrency References: [Create Orders Using Composite API], [Composite Resources]

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

The best practice to create this functionality is to use a Process Builder. A Process Builder is a declarative toolthat allows administrators to automate business processes based on certain criteria and actions. The administrator can create a Process Builder that triggers when a Fulfillment Order is created, and then executes an Outbound Message action that sends the information to the external accounting system. Verified References: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.process_action_outbound_message.htm&type=5

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 OrderDeliveryMethod and Locations objects have their tabs set to Tab Hidden by default. These objects are used to store information about how an order is delivered and where it is fulfilled from, respectively. They are not meant to be accessed directly by users, but rather through related lists or lookup fields on other objects. References: Order Management Objects

 Two reasons that could cause the issue of not being able to deploy a Change Set from a development org to a test org are:

The development org has not been approved to upload Change Sets from within the test org. To deploy ChangeSets between two sandbox orgs, the administrator needs to establish a deployment connection between them. A deployment connection allows one org to send outbound Change Sets and another org to receive inbound Change Sets. The administrator can create a deployment connection request from the development org and approve it from the test org.

The development org and test org are not associated with the same production org. To deploy Change Sets between two sandbox orgs, they must be linked to the same production org. A production org is an org that contains live data and business processes. A sandbox org is a copy of a production org that is used for development, testing, or training purposes. Sandbox orgs inherit the deployment connections of their source production orgs. References: Deploy Using Change Sets, Deploy a Change Set

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 fromB2C 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 havethe 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. References: Order Management Objects, [Custom Attributes]

The Ensure Funds process works on only the items passed into the Ensure Funds method. This method is a flow core action that verifies that there are enough funds available for each Order Item passed into it, and updates their payment status accordingly. The administrator can pass any Order Items into this method, regardless of their status or delivery group. Verified References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_ensure_funds_async.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]

The best way for the administrator to meet these requirements is to create a copy of the Order Summary lightning record page for the service team and remove the Process Exceptions component. Activate the lightning record page by profile for all Service team profiles. A Process Exception is a record that represents an error or exception that occurred during the order lifecycle, such as payment authorization failure, inventory allocation failure, fulfillment location assignment failure, etc. A Process Exception hasa lookup relationship to the Order object, and it contains information such as the exception type, status, message, etc. The Process Exceptions component is a standard component that displays process exceptions related to an order on its record page. The administrator can use the Lightning App Builder to create a copy of the Order Summary lightning record page for the service team and remove the Process Exceptions component from the page layout. The administrator can then activate the lightning record page by profile for all Service team profiles, so that they do not see Process Exceptions on any Order Summaries. Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_process_exception.htm &type=5 https://help .salesforce.com/s/articleView?id=sf.om_process_exceptions_component.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_assign_lex_pages.htm &type=5