Salesforce Certified Manufacturing Cloud Accredited Professional Practice Test - Questions Answers

To populate a custom metric so that it shows on the forecast grid, you can use either of the following options:

Implement a record trigger flow on Account Product Forecast (APF): A record trigger flow is a type of Salesforce Flow that runs when a record is created, updated, or deleted. You can use a record trigger flow to update the custom metric field on the APF object based on some logic or formula. The APF object stores the forecast data for each account and product combination. The custom metric field must be added to the APF object as a custom field.For example, you can create a record trigger flow that calculates the profit margin as a custom metric by dividing the revenue by the cost for each APF record1.

Implement a record trigger on Account Product Period Forecast (APPF): A record trigger is a type of Apex trigger that runs when a record is inserted, updated, deleted, or undeleted. You can use a record trigger to update the custom metric field on the APPF object based on some logic or formula. The APPF object stores the forecast data for each account, product, and period combination. The custom metric field must be added to the APPF object as a custom field.For example, you can create a record trigger that calculates the average revenue per unit as a custom metric by dividing the revenue by the quantity for each APPF record2.

The other options are not valid methods to populate a custom metric for the forecast grid.

Implementing an apex trigger on APF or APPF will not work because apex triggers cannot update the same object that triggered them.This will cause a recursive loop and throw an error3.

Using the recalculate all forecast button on the account forecast settings page will not work because this button only recalculates the existing metrics based on the account forecast calculation settings.It does not populate any custom metrics that are not part of the calculation settings4.Reference:1:Create a Record-Triggered Flow | Salesforce Help2:Triggers | Apex Developer Guide | Salesforce Developers3:Apex Trigger Best Practices and the Trigger Framework - Salesforce Developers Blog4:Recalculate All Forecasts | Salesforce Help

Changing the forecast frequency from quarterly to monthly in the account settings will affect the existing account forecasts in two ways:

A full regeneration of all the eligible account forecasts will be carried out. This means that the existing account forecasts will be deleted and new ones will be created based on the new frequency.The regeneration process may take some time depending on the number of accounts and products involved1.

All the previously active account forecasts will expire. This means that the account managers will not be able to view or edit the old account forecasts that were based on the quarterly frequency.They will only see the new account forecasts that are based on the monthly frequency2.

To give the account managers 'Read' access to the new custom field on the APF table, there are two possible actions that can be taken:

Clone the standard permission set Manufacturing Account Forecast to a new permission set with license type Manufacturing Forecast Psl. Grant Read access to the field on the new permission set. Assign the cloned permission set to the account managers. This option will create a copy of the existing permission set and allow the administrator to modify the field access for the new custom field.The cloned permission set will require the same license type as the original one, which is Manufacturing Forecast Psl3.

Give 'Read' access to the field on the standard Manufacturing Account Forecast permission set. This option will directly edit the field access on the existing permission set and apply the changes to all the users who have been assigned this permission set.The administrator can use the field accessibility tool to check and change the field access for the standard permission set4.

In Tableau CRM for Manufacturing, the user types that can be selected to receive credit for an order in the Tableau CRM configuration wizard when calculating actuals against account manager targets are:

Opportunity Owner: The user who owns the opportunity that is associated with the order.This option is useful when you want to track the performance of the sales reps who closed the deals that resulted in the orders2.

Custom Lookup Field for a user on Account: The user who is referenced by a custom lookup field on the account that is associated with the order.This option is useful when you want to track the performance of a specific role or function that is related to the account, such as a regional manager or a service agent2.

Order Owner: The user who owns the order.This option is useful when you want to track the performance of the users who are responsible for fulfilling the orders2.Reference:Configure Tableau CRM for Manufacturing

The Forecast Analysis dashboard in Tableau CRM for Manufacturing allows users to monitor the accuracy of their forecast based on the forecasted, adjusted, and actual revenue and quantity. With this dashboard, users can analyze how forecasts vary across time and plan measures to improve forecast accuracy. Two of the key performance indicators that can be calculated on this dashboard are:

Mean absolute percentage error (MAPE): This is a measure of how close the forecasted values are to the actual values. It is calculated as the average of the absolute percentage errors for each period. A lower MAPE indicates a more accurate forecast.

Actual vs Forecasted Revenue: This is a comparison of the actual revenue and the forecasted revenue for each period. It shows how much the revenue deviated from the forecast and whether the forecast was overestimated or underestimated.

Before creating the Analytics for Manufacturing App, users need to ensure that their Salesforce org has the required data for the app to work properly. One of the data requirements is that at least one record must exist in each of the Manufacturing Cloud objects to be analyzed, such as Account Manager Targets, Sales Agreements, and Advanced Account Forecast Sets. If the org does not have any records in these objects, the app creation will fail and users will get an error message instructing them to add the required data and try again.

To ensure that only invoices with status paid are included in the rebate calculation, the admin should validate the invoice status in the ERP system before bringing the data into Salesforce. This way, the admin can avoid importing unnecessary or inaccurate data that might affect the rebate performance and payout. The other options are not feasible or efficient because:

Option B is incorrect because transactions with any status are included in the journal by default.The admin needs to set up eligibility conditions in the rebate types to filter out transactions based on status or other criteria1.

Option C is incorrect because creating a custom field in the transaction journal and copying the invoice status data into it is redundant and time-consuming.The invoice status is already available as a standard field in the transaction journal object2.

Option D is incorrect because updating the data processing engine job to filter out transactions based on invoice status is not possible.The data processing engine job is used to process the data from the transaction journal into the rebate journal, and it does not have any filtering options3.

The calculation method that can calculate a benefit structure on a total quantity of 150 units, where the first 100 units earn $0 per unit and the next 50 units earn $10 per unit, isStepped.According to the Manufacturing Cloud Developer Guide1, the stepped calculation method defines a benefit structure based on the quantity ranges and the corresponding benefit values. For example, if the quantity range is 0-100, the benefit value is $0; if the quantity range is 101-150, the benefit value is $10; and so on. The benefit value for each quantity range is applied to the entire range, not just the incremental quantity. Therefore, the total benefit for 150 units is $500 (50 x $10).

The minimum and maximum range values of a rebate type benefit define the threshold of the attainment metric for the benefit to apply. The values must be in ascending order and cannot overlap with other ranges. Therefore, the sequence of 0 to 100, 101 to 200, 201 to 300, and 301 to 400 would be valid, as each range is distinct and sequential.Reference:Rebate Management Basics>Create and Manage Rebate Programs>Create a Rebate Type Benefit