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

The best way for the administrator to meet this requirement is to modify the compact layout on the Credit Memo object. A Credit Memo is a record that represents a refund or credit issued to a customer for an order or part of an order. A Credit Memo has various fields and related lists that display information such as the credit amount, status, reason, etc. A compact layout is a type of layout that determines which fields appear in the highlights panel at the top of a record page in Lightning Experience or Salesforce mobile app. The administrator can use the Object Manager to modify the compact layout on the Credit Memo object and add the Total Amount field to the compact layout. This way, the sales team can see the Total Amount field in the highlights panel at the top of the Credit Memo record page. Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_credit_memo.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.compact_layouts_overview.htm &type=5

To set up a mock payment gateway in a new org, an administrator shouldtake the following steps:

Create a Payment Provider: This is a custom metadata type that defines the configuration and behavior of a payment gateway. A payment provider specifies the name, type, class, and endpoint of the payment gateway.

Create a Named Credential: This is a Salesforce feature that securely stores authentication information for connecting to external services. A named credential specifies the URL, identity type, authentication protocol, and certificate of the payment gateway.

Create a Payment Gateway: This is a custom object that represents an instance of a payment provider. A payment gateway references a payment provider and a named credential, and defines additional settings such as currency, mode, and timeout. References: Salesforce Payments and Order Management, [Named Credentials]

Three objects that are likely to get created in Order Management as an order progresses through its lifecycle are:

Fulfillment Order. A Fulfillment Order is a record that represents a group of products in an order that are fulfilled together from thesame 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.

Return Order. A Return Order is a record that represents a return requestfor 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.

Change Order. A Change Order is a record that represents achange 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 the change type, status, date, 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_return_order.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_management_change_order.htm &type=5

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

Create an External Data Sourcepointing to the external system’s database. An External Data Source is a type of metadata that defines the connection and authentication information for an external system that stores data outside of Salesforce. The administrator can create an External Data Source using the Lightning Connect OData 2.0 or 4.0 adapters, which support read-only access to data in relational databases.

Create an External Object for each table of accounting data in the external system. An External Object is a type of custom object that maps to a table in an external system. The administrator can create an External Object for each table of accounting data that they want to access from Salesforce, and define its fields and relationships accordingly.

Create an Indirect Lookup field to connect to the Account. An Indirect Lookup field is a type of custom field that links a child External Object record to a parent standard or custom object record. The administrator can create an Indirect Lookup field on the External Object that references the Account object, and specify the external column name and value that match the Account ID.

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

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

The best way for the administrator to recommend tracking the kits so that they remain grouped together during returns in Order Management is to use custom attributes. Custom attributes are fields that can be added to objects to store additional information that is not available in standard fields. The administrator can create custom attributes for the Order Item Summary object to indicate whether an item is part of a kit, and what are the other items in the kit. This way, the kits can be easily identified and handled during returns. Verified References:https://documentation.b2c.commercecloud.salesforce.com/DOC2/topic/com.demandware.dochelp/OrderManagement/Administration/AdminAttrMgrCustomAttributes.html

The best way for an administrator to research the issue when a user is encountering an error when attempting to save an Account record is to use a user trace flag and debug log on the affected user. A user trace flag enables debug logging for a specific user, and a debug log captures database operations, system processes, and errors that occur when executing a transaction or running unit tests. The administrator can use these tools to identify the root cause of the error and fix it accordingly. Verified References: https://help.salesforce.com/s/articleView?id=sf.code_add_users_debug_log.htm &type=5https://help.salesforce.com/s/articleView?id=sf.code_viewing_debug_logs.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

An administrator would enable Person Accounts during Order Management setup for the use case of connecting Order Management to B2C Commerce. B2C Commerce is a cloud-based platform that enablesbusinesses to create and manage online storefronts for consumers. B2C Commerce uses Person Accounts to represent individual shoppers who place orders on the storefronts. Person Accounts are a type of account that combines account and contact information into a single record. To connect Order Management to B2C Commerce, an administrator needs to enable Person Accounts in Order Management and install the B2C Commerce Integration package from AppExchange. References: B2C Commerce Integration, [Person Accounts]

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]

The Ensure Funds Async action requires the invoice ID as an input parameter. The action checks if there are enough funds available for the invoice and updates the invoice status accordingly. The invoice ID should be assigned somewhere in the flow before calling the action, otherwise the action will fail. References: Salesforce Payments and Order Management

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

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 object record that the administrator should create in the fault path to notify users of an error is Process Exception. A Process Exception is a record thatrepresents 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 has a lookup relationship to the Order object,and it contains information such as the exception type, status, message, etc. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_process_exception.htm &type=5

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

Three advantages of using Flow Builder vs writing Apex code to manage the main flow of Order data are:

The admin can attach a debugger to live customersessions. This allows the admin to monitor and troubleshoot the flow execution in real time, without affecting the customer experience or data integrity.

The admin can easily debug specific business cases visually. This allows the admin to test the flow with different input values and see how the flow behaves in a graphical interface, without writing any code.

Because it is visual it is also self-documenting as changes are made. This allows the admin to easily understand and maintain the flow logic, as wellas track the changes and versions of the flow.

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

Order Allocation should work onOrder Items in Awaiting Allocation status. This status indicates that the Order Item has been confirmed by the customer and is ready to be allocated to a Fulfillment Order based on routing rules and inventory availability. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_order_item_status.htm &type=5

The best way for a user to view the information exchanged between the payment platform and the external payment gateways is to navigate to Payment Gateway Logs related list on the corresponding Order Payment Summary. A Payment Gateway Log is a record that captures the request and response messages between the payment platform and the external payment gateways, such as Stripe, PayPal, etc. A PaymentGateway Log has a lookup relationship to the Order Payment Summary object, which represents a payment made for an order or part of an order. A user can use the Payment Gateway Logs related list on the Order Payment Summary page to view the details of thepayment transactions, such as the request and response payloads, status codes, timestamps, etc. Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_payment_gateway_log.htm &type=5https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.htm &type=5

The object that the Ensure Funds Apex Flow action looks for when resolving Invoice balances associated with an Order Summary is Order Payment Summaries. Thisobject represents the payments made for an order, and it has a lookup relationship to both Invoice and Order Summary objects. The Ensure Funds Apex Flow action uses this object to calculate the balance due for each Invoice and update its status accordingly. Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.htm &type=5https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_ensure_funds_async.htm &type=5