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

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]

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

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 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 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 reason why Fulfillment Order does not appear as an option when creating a rollup field on the Order Summary object is that the Order Summary field on the Fulfillment Order object is a Lookup. A Lookup field is a type of custom field that creates a relationship between two objects, but does not support rollup summary fields. To create a rollup summary field, the relationship between the objects must be master-detail, which means that the child record cannot exist without its parent record. Verified References: https://help.salesforce.com/s/articleView?id=sf.custom_field_types.htm & type=5https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm & type=5

The designelement in Flow that allows the admin to reset some variables at the beginning of each loop iteration is Assignment. An Assignment element lets the admin assign new values to one or more variables or sObject fields in a flow. The admin can use an Assignment element before a Loop element to initialize the variables that are used in the loop, and then use another Assignment element inside the loop to reset the variables for each iteration. Verified References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_assignment.htm & type=5https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_loop.htm & type=5

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]

Three steps that are required when deploying changes via change sets are:

Create the change set in the sandbox org. This is the first step where the administrator selects the metadata components that they wantto deploy and adds them to a change set in the source org, which is usually a sandbox org.

Upload the change set to the target org. This is the second step where the administrator sends the change set from the source org to the destination org, which is usually a production org or another sandbox org. The administrator needs to have a deployment connection with the target org and permission to upload change sets.

Deploy the change set in the target org. This is the final step where the administrator validates and deploys the change set in the destination org. The administrator needs to have permission to deploy change sets and resolve any deployment errors or warnings.

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

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

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 main types of building blocks when working in Flow Builder are:

Elements: These are the components that definethe logic and functionality of a flow. Elements include actions, assignments, decisions, loops, screens, subflows, and waits.

Resources: These are the variables, constants, formulas, collections, and record choice sets that store data in a flow. Resourcescan be used as inputs or outputs for elements.

Connectors: These are the arrows that connect elements and resources in a flow. Connectors determine the sequence and direction of the flow execution. References: [Flow Building Blocks]

A summary object represents a dynamic view ofunderlying data. A summary object is a type of object that aggregates data from related records and displays it in a single record. For example, an Order Summary object represents the financial summary of an order that is received from an external system,such as B2C Commerce or B2B Commerce. An Order Summary object aggregates data from related Order Item Summary records and displays it in fields such as total amount, tax amount, discount amount, etc. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_order_summary.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]

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 asrecord field values, user permissions, or device type.

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

Two reasons for using Flows instead of Apex code are:

Flows can be modified and created without a developer. Flows are declarative tools that allow administrators to build complex business logic using clicks instead of code. Flows do not require any programming skills or knowledge, and they can be easily modified and maintained by administrators.

Flows provide a visual debug process. Flows have a built-in debugger that allows administrators to test and troubleshoot their flows in a graphical interface. The debugger shows the flow execution path, the values of variables and sObject fields, and any errors or warnings that occur in the flow.

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

Three components that can be used to modify the user experience in the Order Summary detailpage are:

Tabs. Tabs are a type of component that allow users to switch between different views or subpages on a record page. Tabs can contain other components, such as charts, reports, or custom components, that display different information orfunctionality related to a record. The administrator can use the Lightning App Builder to add and customize tabs on the Order Summary detail page to give users more options and flexibility.

Accordion. Accordion is a type of component that allow users to expand and collapse sections of a record page. Accordion can contain other components, such as fields, related lists, or custom components, that display different information or functionality related to a record. The administrator can use the Lightning App Builder to add and customize accordion on the Order Summary detail page to give users more control and visibility.

Related List-Single. Related List-Single is a type of component that displays a single related list for a record. A related list is a list ofrecords that are linked to another record by a relationship field, such as lookup or master-detail. The administrator can use the Lightning App Builder to add and customize related list-single on the Order Summary detail page to give users more access andcontext.

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

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

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

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