Order-Management-Administrator Questions and Answers

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

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

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 administrator can use two tools to debug an issue with an Apex trigger: Log Inspector in the Developer Console and Debug Logs in Setup. The Log Inspector is a tool that displays agraphical representation of a debug log, which is a record of database operations, system processes, and errors that occur when executing a transaction or running unit tests. The Log Inspector helps you analyze and troubleshoot your code by highlighting errors, checkpoints, and execution times. The Debug Logs page in Setup lets you monitor and retain debug logs for users, Apex classes, Apex triggers, and Lightning components. You can view, download, or delete debug logs from this page.

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

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

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

Two ways that Order Management licenses can be assigned are:

By Permission Set. A Permission Set is a collection of settings andpermissions that give users access to various tools and functions in Salesforce. A Permission Set can be assigned to individual users or groups of users, regardless of their profile or role. An administrator can create a Permission Set that includes the Order Management User permission, which enables users to access Order Management features and data. The administrator can then assign this Permission Set to the users who need Order Management licenses.

By User. A User is a record that represents a person who can log in and access Salesforce. A User has various fields and settings that determine their access and permissions in Salesforce, such as profile, role, license type, etc. An administrator can assign an Order Management license to a user by editing theuser record and selecting Order Management User from the License Type picklist. The administrator can also enable the Order Management User permission on the user record.

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

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 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. Verified References:https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_deploying_ant_deploy.htm

The OrderDeliveryMethod and Locations objects have their tabs set to Tab Hidden by default. These objects are used to store information about how an order is delivered and where it is fulfilled from, respectively. They are not meant to be accessed directly by users, but rather through related lists or lookup fields on other objects. References: Order Management Objects

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

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

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

Two ways that an administrator can query Order Summaries using APIs in Workbench are:

Platform API. The Platform API is a set of REST and SOAP APIs that allow developers to access data and functionality in Salesforce from external systems. The Platform API includes various resources and operations for querying, creating, updating, or deleting records in Salesforce, such as Order Summaries. The administrator can use the Platform API in Workbench byselecting the REST Explorer or SOAP Explorer tabs, and entering the appropriate request URL and parameters.

Composite API. The Composite API is a type of REST API that allows developers to execute multiple subrequests in a single HTTP request. The Composite API includes various resources and operations for batching, tree, sObject collections, or transactions in Salesforce, such as Order Summaries. The administrator can use the Composite API in Workbench by selecting the REST Explorer tab, and entering theappropriate request URL and JSON body.

Verified References: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite.htm

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

Two reasons an admin should choose an Event over a Trigger when it comes to building out a solution are:

Events are asynchronous. This means that events are processed in the background, without blocking the main execution thread. This can improve the performance and user experience of the solution, as well as avoid governor limits and timeouts.

Events do not participate in a transaction scope. This means that events are independent of the transaction that publishes them, and they do not affect the rollback or commit behavior of the transaction. This can avoid unwanted side effects and errors in the solution, as well as decouple the logic from the data.

Verified References: https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro.htm https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_considerations.htm

The Status field on an Order Summary object is a picklist data type. A picklist is a field that allows users to select one value from a predefined list of values. The Status field on an Order Summary object indicates the current state of the order, such as Draft, Activated, Completed, or Cancelled. The values for the Status field are defined in the OrderStatus picklist field on the Order object. References: Order Management Objects, [Picklist Fields]

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

Two ways that this off-platform job can be established without additional third-party tools are:

Install a minimal set of dev tools on a machine such as the Command Line Interface (CLI) and create appropriate scripts to import files containing the data. The CLI is a tool that allows developers to interact with Salesforce from the command line. The developer can use the CLI to create scripts that use commands such as force:data:bulk:upsert or force:data:tree:import to import data from CSV or JSON files into Salesforce.

Authorize a machine against the Salesforce org’s APIs with appropriate security measures and create a script to call the APIs. The APIs are interfaces that allow developers to access data and functionality in Salesforce from external systems. The developer can use the APIs, such as REST API or Bulk API, to create a script that authenticates with Salesforce using OAuth 2.0 or JWT, and then performs operations such asinsert, update, or delete on Order data.

Verified References: https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_data.htm https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_intro.htm