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

Two APIs that an admin can suggest so that customers can initiate order cancellations and returns from the B2C Commerce storefront and have theiraction carry out the cancel and return operations in Order Management are:

Connect APIs. These are RESTful APIs that expose resources in Order Management, such as orders, payments, shipments, etc. They allow customers to perform CRUD (create, read, update,delete) operations on these resources from external systems, such as B2C Commerce.

REST APIs. These are HTTP-based APIs that enable developers to access data in Order Management using standard HTTP methods, such as GET, POST, PUT, PATCH, and DELETE. Theyallow customers to interact with Order Management resources using JSON or XML formats.

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

The best thing for the customer service representative to do in this situation is to wait until the Order Summary is created. An Order Summary is a record that represents the financial summary of an order that is received from an external system, such as B2C Commerce or B2B Commerce. An Order Summary is created after an order is ingested into Order Management, and it triggers various flows and processes for order fulfillment and payment processing. A Pending Order Summary is a temporary record that indicates that an order has been received but not yet processed by Order Management. A customer service representative cannot service an order until it has an Order Summary record. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_order_summary.htm &type=5

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

Two statements about the Order Summary object that are accurate are:

It does not exist without the original Order object.An Order Summary is a record that represents the financial summary of an order that is received from an external system, such as B2C Commerce or B2B Commerce. An Order Summary has a master-detail relationship to the Order object, which means that it cannotexist without its parent Order record.

It is read-only for financial order data. An Order Summary contains financial order data, such as total amount, tax amount, discount amount, etc., that are populated from the external system when the order iscreated. These fields are read-only and cannot be edited in Order Management.

Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_order_summary.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

The Order Summary object is a customobject that stores information about an order, such as the total amount, the number of items, and the fulfillment status. The Order Summary object 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. The process and the flow are part of the Order Management package and must be installed and activated for the order summary object to be created. References: Order Management Lifecycle, Order Management Objects, Configure Order Management Flows

The best way for an administrator to quickly examine the relationships between several objects is to go to Schema Builder and check the boxes next to the object names. Schema Builder is a tool that allows administrators to view and modify the data model of their org in a graphical interface. Schema Builder shows the objects and fields in the org, as well as the relationships between them. The administrator can use Schema Builder to select the objects that they want to examine, and see how they are connected to each other. Verified References:https://help.salesforce.com/s/articleView?id=sf.schema_builder.htm &type=5

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 agraphical 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.

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

Three steps that the administrator should do to implement this functionality are:

Create an email template. An email template is a reusable message that contains merge fields that are populated with data from records when the email is sent. The administrator can create an email template for the Payment Summary object that includes information such as the payment amount, date, status, etc.

Create an email alert action. An email alert action is a type of action that sends an emailto one or more recipients when a flow executes. The administrator can create an email alert action that uses the email template created in the previous step and sends it to the owner of the associated account when a new Payment Summary is created.

Create an approval process on the Payment Summary object. An approval process is a way to automate the approval of records based on certain criteria and actions. The administrator can create an approval process on the Payment Summary object that requires an approval after review from a designated approver.

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

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’taccess 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. References: Salesforce Order Management, Mobile App Theme FAQ

The Product Eligibility Flag is a custom field on the Product object that indicates whether a product is eligible for a specificselling channel. An administrator can use this field to control what inventory is exposed on different channels, such as web, mobile, or store. For example, if a product has the Product Eligibility Flag set to Web Only, it will not be available for otherchannels. References: Order Management Objects, [Product Eligibility Flag]

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]

Three statements that are true about change sets are:

Sending a change set between two orgs requires a deployment connection. A deployment connection is a link between two orgs thatallows one org to send change sets to another org.

Change sets can only be sent between orgs that are affiliated with a production org. A production org is an org that is used for live operations and data, and it can have one or more sandbox orgs that areused for development and testing. Change sets can only be sent from a sandbox org to its associated production org, or from one sandbox org to another sandbox org that shares the same production org.

Change sets can contain only modifications made throughthe Setup menu. A change set is a collection of metadata components that can be deployed from one org to another. Metadata components are customizations that are made through the Setup menu, such as custom objects, fields, workflows, etc.

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

The Status field on an Order Summary object is a picklist data type. A picklist is a field that allows users to select one value from a predefined list of values. The Status field on an Order Summary object indicates the current state of the order, such as Draft, Activated, Completed, or Cancelled. The values for the Status field are defined in the OrderStatus picklist field on the Order object. References: Order Management Objects, [Picklist Fields]

Two practices that are needed for a custom attribute to map into Order Management assuming the attribute has been created on the necessary objects are:

The types must match within reason. The data type of the custom attribute in Order Managementmust match or be compatible with the data type of the corresponding attribute in the external system, such as B2C Commerce or B2B Commerce. For example, if the attribute is a string in B2C Commerce, it must also be a string in Order Management.

The namesmust be an exact match. The name of the custom attribute in Order Management must be exactly the same as the name of the corresponding attribute in the external system, including capitalization and punctuation. For example, if the attribute is named “kitItem” in B2C Commerce, it must also be named “kitItem” in Order Management.

Verified References: https://documentation.b2c.commercecloud.salesforce.com/DOC2/topic/com.demandware.dochelp/OrderManagement/Administration/AdminAttrMgrCustomAttributes.html