Order-Management-Administrator Sample Questions Answers

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 number of Fulfillment Orders created depends on three factors: Fulfillment Location, Delivery Method and Recipient Address. These factors determine how the Order Items are grouped and allocated to Fulfillment Orders based on routing rules and inventory availability. For example, if an order has two items that can be fulfilled from different locations, or have different delivery methods or recipient addresses, then two Fulfillment Orders are created for that order. Verified References: https://help.salesforce.com/s/articleView?id=sf.om_order_fulfillment.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 Payment Gateway 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 the payment 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=5 https://help.salesforce.com/s/articleView?id=sf.order_management_order_payment_summary.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 best way for the administrator to meet this requirement is to create an External Data Source in Setup that references the external platform where the Pricebook is held. 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. This way, the administrator can access the Product Price Book data from the external platform without importing it into Salesforce. Verified References: https://help.salesforce.com/s/articleView?id=sf.external_object_overview.htm &type=5

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 enables businesses 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 type of relationship that exists between FulfillmentOrder and Location is Many-to-One Lookup (Location) FulfilledFrom Location Id. A Lookup field 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 Location can 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=5 https://help.salesforce.com/s/articleView?id=sf.order_management_location.htm &type=5

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 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 components that can be used to modify the user experience in the Order Summary detail page 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 or functionality 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 of records 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 and context.

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

The main types of building blocks when working in Flow Builder are:

• Elements: These are the components that define the 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. Resources can 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]

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=5 https://help.salesforce.com/s/articleView?id=sf.code_viewing_debug_logs.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 cannot exist 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 is created. 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

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 that allows 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 are used 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 through the 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

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 their sandbox 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 developing or testing in the sandbox. Verified References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_licenses.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 needs to 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

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 the same 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 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.
• Change Order. 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 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 design element 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=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_loop.htm &type=5

The number of Fulfillment Orders that would be created for this order is one per destination, totaling 3. A Fulfillment Order is a record that represents a group of products in an order that are fulfilled together from the same 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. The number of Fulfillment Orders created depends on three factors: Fulfillment Location, Delivery Method and Recipient Address. These factors determine how the Order Items are grouped and allocated to Fulfillment Orders based on routing rules and inventory availability. In this case, since the products must be shipped to three different locations, three Fulfillment Orders are created for each destination. Verified References: https://help.salesforce.com/s/articleView?id=sf.order_management_fulfillment_order.htm &type=5

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 has a 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

The Order Delivery Method and Delivery Method objects are used to configure delivery methods for orders. A delivery method is a way of delivering an order to a customer, such as standard shipping, express shipping, or in-store pickup. A Delivery Method record defines the name, description, type, and cost of a delivery method. An Order Delivery Method record associates an order with a delivery method and stores additional information such as the delivery address, tracking number, and status. References: Order Management Objects, [Delivery Methods]

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