Free Salesforce Manufacturing-Cloud-Professional Practice Exam with Questions & Answers

 A consultant should use an external object to access account order information from an ERP system. An external object is similar to a custom object, but the record data is stored outside the Salesforce organization. By using external objects, the consultant can access the order data in real time via web service callouts, without replicating the data in Salesforce. This way, the sales teams can view the current state of the order information related to an account, without wasting storage and resources keeping data in sync1. A standard Order object or a custom object would require copying the order data from the ERP system to the Salesforce organization, which is not the desired solution for UC. References: 1: External Objects2

Universal Containers does not want to bring actual orders data into Salesforce, but still wants to use the actual orders data to analyze the effectiveness of their sales agreements, they must select the Manually Using actual orders API option in the sales agreement setup. This option allows them to use an API to upload actual order data from an external system into Salesforce and associate it with the sales agreements. This way, they can compare the planned and actual quantities and revenues of each product or product category in the sales agreement. The other options require either creating orders in Salesforce or linking contracts to orders in Salesforce, which Universal Containers does not want to do. References: Choose How Sales Agreement Actuals Are Calculated, Create Orders to Calculate Sales Agreement Actuals

To export Account Based Forecast data, the user needs to add the fields that capture the forecasting quantity data, including any sales team adjustments. The ‘Adjusted Forecast Quantity’ field shows the forecast quantity after applying the adjustment percentage for each account product forecast. The ‘Total Adjusted Forecasted Quantity’ field shows the sum of the adjusted forecast quantity for all the account product forecasts in the same account forecast1. These fields are available in the standard report type of ‘Account Forecasts with Product Period Forecast’, so there is no need to create a custom report type. References: What Is Manufacturing Cloud?, Create Holistic Forecasts with Advanced Account Forecasting

 Data Processing Engine (DPE) Templates are used to customize the data model and calculations for account-based forecasting in Manufacturing Cloud. DPE Templates allow users to define the dimensions, metrics, and formulas for their forecasts based on their business needs. In this case, UC needs to customize the DPE Template to include the product category as a dimension, and the ordered quantity, revenue, shipped quantity, and revenue as metrics. UC also needs to specify the custom fiscal year and the weekly forecast frequency in the DPE Template. The other options are not relevant for this requirement. Sales Agreement Metrics are used to track the performance of sales agreements, not forecasts. Advanced Account Forecast Fact object is a standard object that stores the forecast data, not a customization option. References: Customize Data Processing Engine (DPE) Templates, Account-Based Forecasting in Manufacturing Cloud

https://www.salesforce.com/products/manufacturing-cloud/overview/

Actuals are the quantities of products that have been fulfilled or shipped to the customer as part of a sales agreement1. Manufacturing Cloud calculates actuals based on orders that are associated with a sales agreement2. For an order to be included in the actuals calculation process, the following three conditions need to be fulfilled23:

The order needs to have Status = Activated. Only activated orders are considered for actuals calculation. Draft orders are not included.

The date in the Order Date field should be in the past. Only orders with a start date that is on or before the current date are considered for actuals calculation. Future orders are not included.

The Sales Agreement field needs to be populated on the order. Only orders that have a reference to a sales agreement record are considered for actuals calculation. Orders that are not linked to a sales agreement are not included.

https://help.salesforce.com/s/articleView?id=sf.sa_admin_actualscalc_task.htm &language=en_us&type=5

 To set up Tableau CRM for Manufacturing, an Admin needs to have the Manufacturing Einstein Admin permission set and the Manufacturing Analytics Admin permission set. The Manufacturing Einstein Admin permission set grants access to the Manufacturing Einstein features, such as Account Forecasting and Account Manager Targets. The Manufacturing Analytics Admin permission set grants access to the Manufacturing Analytics app and its dashboards, such as Sales Agreement Performance and Account Health1. The other permission sets are not specific to Manufacturing Cloud and do not provide the necessary access to set up Tableau CRM for Manufacturing. References: 1: Set Up Users and Permissions for Manufacturing Cloud2

n: A sales agreement is a contract between a manufacturer and a customer that specifies the terms and conditions of a long-term sales relationship. A sales agreement consists of a sales agreement record and one or more sales agreement products. A sales agreement product is a line item that represents a product or a product category that the customer agrees to purchase over a period of time. A sales agreement product schedule is a subcomponent of a sales agreement product that defines the quantity and revenue expectations for each time period within the sales agreement term. To load data into sales agreements, you must follow the correct data load sequence to ensure data integrity and avoid errors. The data load sequence is as follows:

First, load the sales agreement records, which contain the basic information about the sales agreement, such as name, account, start date, end date, status, and so on.

Second, load the sales agreement products, which are related to the sales agreement records by the Sales Agreement ID field. Each sales agreement product must have a valid product or product category, name, initial planned quantity, and price book entry.

Third, load the sales agreement product schedules, which are related to the sales agreement products by the Sales Agreement Product ID field. Each sales agreement product schedule must have a valid period, quantity, and revenue. References: Sales Agreement, Sales Agreement Product, Sales Agreement Product Schedule, Data Load Sequence for Manufacturing Cloud