Free ORDER-MANAGEMENT-ADMINISTRATOR Exam Dumps Preview

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]

Three steps that the administrator should take to implement this functionality are: Create an External Data Source pointing 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.

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

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

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 Management must 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 names must 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.

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

The required amount of test code coverage when deploying an Apex class is 75%. This means that at least 75% of the Apex code must be covered by unit tests, and all of those tests must complete successfully.
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_deploying_ant_deploy.htm

Once the administrator has activated the integration between B2C Commerce and Order Management, orders being placed by customers will be sent to Order Management if the order status is set to Active or New. These are the two order statuses that indicate that an order has been created or confirmed by a customer, and that it needs to be processed by Order Management.
https://help.salesforce.com/s/articleView?id=sf.order_management_order_api.htm&type=5

A service agent should go first to the Order Summary Details page to initiate changes related to an order in Order Management. The Order Summary Details page provides a global view of the entire order lifecycle, including order capture, fulfillment, shipping, payment, invoicing, and service. From this page, a service agent can access various actions and flows to process changes such as cancellations, returns, exchanges, reshipments, refunds, and discounts. The service agent can also view related records such as Order, Fulfillment Orders, Shipments, Invoices, Credit Memos, and Change Orders.
References:
Order Management Console, Order Management Lifecycle

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]

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

Two likely causes that could make the second submission of the same JSON payload fail are: The payment data must be updated. The payment data in the JSON payload contains information such as the payment method, amount, and authorization code. If the same payment data is used for the second order, it may cause a duplicate payment error or an invalid authorization error. The Order Reference Number must be updated. The Order Reference Number is a unique identifier for each order that is generated by the external system and sent in the JSON payload. If the same Order Reference Number is used for the second order, it may cause a duplicate order error or an invalid order error.

https://help.salesforce.com/s/articleView?id=sf.order_management_order_api.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.order_management_payment_api.htm&type=5

The best way for the administrator to satisfy this requirement is to edit the Lightning Record Page and change the Template to Three Regions. A Lightning Record Page is a type of page that displays details and related information about a specific record in Lightning Experience or Salesforce mobile app. A Lightning Record Page can be customized using the Lightning App Builder, which is a tool that allows administrators to drag and drop components onto a page layout. A Template is a predefined layout that determines how components are arranged on a page. A Three Regions template is a type of template that divides the page into three columns or regions. The administrator can edit the Lightning Record Page for the Order Summary object, and change the Template to Three Regions in the Lightning App Builder.
https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_customize_lex_pages.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.lightning_app_builder_templates.htm&type=

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 products are: 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 the change type, status, date, etc.
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

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