Order-Management-Administrator Questions 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

The object that is created and linked to the Order Summary when a customer cancels an order prior to fulfillment is Cancel Order. A Cancel Order is a record that represents a cancellation request for an order or part of an order. A Cancel Order has a lookup relationship to both Order Summary and Change Order objects, and it contains information such as the cancellation reason, status, date, etc. Verified References:https://help.salesforce.com/s/articleView?id=sf.order_management_cancel_order.htm &type=5

Two objects that are found within Order Management 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.
• 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

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

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 want to 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

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 anexternal 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

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

The correct statement about Person Accounts and Contacts is that Person Accounts are appropriate for B2C transactions while Account-Contact model is appropriate for B2B transactions. A Person Account is a type of account that represents an individual consumer, rather than a business or organization. A Person Account combines the features and fields of both the Account and Contact objects, and it does not require a Contact record to be associated with it. A Person Account is suitable for B2C transactions, where the customers are individual consumers who purchase products or services for personal use. An Account-Contact model is a type of data model that represents a business or organization as an account, and its employees or affiliates as contacts. An account can have many contacts associated with it, but a contact can only belong to one account. An Account-Contact model is suitable for B2B transactions, where the customers are businesses or organizations that purchase products or services for professional use. Verified References: https://help.salesforce.com/s/articleView?id=sf.accounts_person.htm &type=5https://help.salesforce.com/s/articleView?id=sf.accounts_contacts.htm &type=5

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 passany 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

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

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

The correct time and way for creating an Invoice is at any point after the Fulfillment Order is created, by customizing flow “Create Invoice”. This flow is a core action that creates an Invoicerecord from a Fulfillment Order record, and updates the status of both records accordingly. The administrator can customize this flow to suit their business needs, such as adding conditions, actions, or subflows. Verified References:https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_om_actions_create_invoice.htm &type=5