Manufacturing-Cloud-Professional Manufacturing Cloud Accredited Professional (AP-213) Questions and Answers

The best way to reassure the client that the data has been accurately calculated is to launch the calculations of the Advanced Account Forecast and compare the values with the legacy system. This will ensure that the forecast metrics, such as planned revenue, actual revenue, forecast quantity, and forecast revenue, are consistent and correct. The administrator can use the Data Processing Engine templates to configure the calculations and run them manually or on a schedule1. The administrator can also view the forecast results in the Accounts Health dashboard or the Account Forecast tab2. Using Data Loader to generate a .csv file and manually compare it to import files is not a reliable method, as it may introduce errors or inconsistencies in the data format or values. Requesting the users to verify the Advanced Account Forecast values of their accounts is not a feasible method, as it may be time-consuming, impractical, or inaccurate, depending on the number and complexity of the accounts. References: Learn How Forecast Data Is Created, View and Adjust Forecasts

To access the Rebate analytics functionality in Tableau CRM for Manufacturing, you need two licenses: Manufacturing Analytics Plus and Rebates Management Add on. Manufacturing Analytics Plus is a license that enables you to use the Analytics for Manufacturing app, which provides out-of-the-box dashboards and reports for sales agreements, forecasts, targets, and rebates. Rebates Management Add on is a license that enables you to use the Rebate Management feature, which allows you to create and manage custom rebate programs, automate payouts, and review processes. Together, these licenses allow you to perform what-if analysis, monitor program performance, and collaborate with channel partners using Tableau CRM for Manufacturing. References: Rebate Management - Salesforce Help, Salesforce Manufacturing Cloud Rebates What-If | Tableau Exchange, Streamline Channel Sales with an Intelligent Rebate Strategy - Salesforce

 According to the Salesforce Manufacturing Cloud documentation, to display the current sales agreement data in tableau CRM for manufacturing, you need to add the sales agreement object to the data flow and update the data flow. The data flow is a set of instructions that defines how data is extracted, transformed, and loaded into the app. If you do not add the sales agreement object to the data flow, the app will not have access to the sales agreement data. If you do not update the data flow, the app will not reflect the latest changes in the sales agreement data1. References: 1: Set Up the CRM Analytics App for Manufacturing Cloud

Learn more

1blob:https://www.bing.com/75924f7d-ce10-4904-b3d2-4996b3dcdca7

developer.salesforce.com2blob:https://www.bing.com/c30db82f-7512-4b86-8ad0-68f8704ae728

trailhead.salesforce.com

Program Rebate Type Benefit is a Rebate Management object that supports custom fields for rebate program(s) analysis. It is used to define the benefit tiers for a rebate type, such as the percentage or amount of rebate that is paid out based on the achievement of a certain threshold. Program Rebate Type Benefit can have custom fields that specify the criteria by which the benefits vary, such as product category, region, or industry segment. These custom fields can be used in the Analytics for manufacturing app in Tableau CRM for Manufacturing to create dashboards and reports that show the performance and impact of rebate programs. References: Rebate Management Standard Objects - Salesforce Developers, Deploy and Use Rebate Analytics - Salesforce, Salesforce Manufacturing Cloud Flashcards

The renewal days for sales agreement is a setting that defines the number of days before the end date of a sales agreement to mark the beginning of the renewal period. Users can renew a sales agreement only when the renewal period starts. This helps to plan ahead and negotiate better terms for the next sales agreement1. References: 1: Define Renewal Period for Sales Agreements | Salesforce Help2

When designing a Manufacturing Cloud implementation, it is important to consider the data sources and quality of the existing third-party systems that will be integrated with Manufacturing Cloud. One of the key considerations is to determine the system of record for each data category required by the business, such as customer information, product data, order history, inventory levels, and so on. The system of record is the authoritative source of data that is trusted and maintained by the business. By identifying the system of record for each data category, you can ensure data consistency, accuracy, and integrity across the integrated systems. You can also avoid data duplication, conflicts, and errors that may arise from having multiple sources of data for the same category. References: What Is Manufacturing Cloud?, Data Integration

To meet the requirements of UC, a Manufacturing Cloud consultant should recommend the following features: Partner Visit Management, Action Plans, and Generic Visit Key Performance Indicators. Partner Visit Management helps sales managers schedule visits to dealer and distributor locations, monitor performance, follow up on sales agreements, and capture key metrics1. Action Plans allow sales managers to create lists of tasks and associated assessment indicators that are commonly repeated across multiple visits2. Generic Visit Key Performance Indicators enable sales managers to compare the expected metrics versus the actual metrics for the key performance indicators they defined and then take necessary actions3. These features help UC to standardize the tasks to be performed during visits, understand how effective these visits are in getting partners to renew, and report on this data in Salesforce. The other features are not relevant for the given scenario. Advanced Account Forecasting is used to create holistic forecasts based on sales agreements, orders, opportunities, and account metrics4. CRM Analytics for Manufacturing is used to gain insights into sales performance, pipeline health, and customer satisfaction. Experience Cloud is used to create branded digital experiences for customers, partners, and employees. Service Console for Manufacturing is used to provide customer service and support across multiple channels. References: Partner Visit Management Workflow, Build Distributor Relationships with Partner Visit Management, Strengthen Relationships with Partners, Create Holistic Forecasts with Advanced Account Forecasting, [CRM Analytics for Manufacturing], [Experience Cloud], [Service Console for Manufacturing]

 The first step for Manufacturing Cloud implementation is to enable Manufacturing Cloud features in Setup. This step allows you to access the Manufacturing Cloud objects, fields, tabs, and components in your org. You can enable Manufacturing Cloud features for Sales, Service, or both, depending on your business needs. To enable Manufacturing Cloud features, you need to have the Customize Application permission and the Manufacturing Cloud license assigned to you1. References: Enable Manufacturing Cloud Features

n: Sales Agreements are the standard feature in Manufacturing Cloud that allow users to track and manage their run-rate or long-term negotiated business. Sales Agreements unify the data from ERP and order management systems with the contract terms, including planned volumes and revenues, so that both operations and account teams can have a 360-degree view of the customer. Sales Agreements also enable users to forecast their run-rate business more accurately and efficiently by using account-based forecasting. Opportunities are used to track new business or one-off business, not run-rate business. Opportunity or Sales Agreements is not a valid option, as they are two different features. References: What Is Manufacturing Cloud?, Forecast Your Run-Rate and New Business with Account-Based Forecasting, Salesforce Launches Manufacturing Cloud—Aligning Sales and Operations to Deliver More Transparent and Predictable Business Outcomes, Salesforce Blog: Manufacturing Cloud

You can use apex triggers to populate a custom metric on the forecast grid. A custom metric is a field that you can add to the Account Product Forecast (APF) or Account Product Period Forecast (APPF) objects to display additional information on the forecast grid. For example, you can create a custom metric to show the profit margin or the cost of goods sold for each product. To populate a custom metric, you need to write an apex trigger on the APF or APPF object that calculates the value of the custom metric based on the data in the record. You can use the standard or custom fields in the APF or APPF object as inputs for the calculation. For example, you can use the Planned Quantity, Planned Revenue, and Product Cost fields to calculate the profit margin. You can also use the fields from the related objects, such as the Account, Product, or Sales Agreement, by using the relationship queries. For example, you can use the Account Name or the Sales Agreement Status fields to filter the records for the calculation. After writing the apex trigger, you need to deploy it to your org and activate it. Then, you can add the custom metric field to the forecast grid layout and see the values populated on the grid. References: Create Custom Metrics for Account Forecasts, Apex Developer Guide, Relationship Queries

To ensure that the 100 new products appear in sales agreements, they must be marked as active and added to the standard price book. This is necessary for managing products and categories within a sales agreement and allows for the addition of new product lines or categories to activated sales agreements .

 You can recalculate payouts for closed periods in two situations: when the member benefits change due to changed requirements, or when the member submits transactions after the payout period is closed, or there is an error in the payout calculation. In both cases, you need to modify the payout records and run the rebate flow again to recalculate the payouts. The first method is to recalculate payouts due to changed benefits, which means that the benefit structure and terms have changed after the payout was calculated for a period. The second method is to recalculate payouts with no charge in benefits, which means that the benefit structure and terms have not changed, but the transactions or the payout calculation have changed. References: Recalculate Payouts for Closed Periods, Rebate Management

To create a custom metric for display on Agreement Terms, you need to create custom fields on the Sales Agreement Product and Sales Agreement Product Schedule objects, and map them using the Data.com Administration tool. The custom fields must have the same data type as the default fields, and only number, currency, and formula field types are available for mapping. Therefore, the correct answer is C. Only number, currency, and formula field types are available for mapping. References: Customize Salesforce Field Mappings, Create Custom Fields for Sales Agreement Products and Schedules

Account Manager Targets is a feature in Manufacturing Cloud that allows businesses to set and track sales goals for their account managers based on product volume, revenue, or any other custom measure. Account managers can create, assign, and edit targets for their team members and monitor their performance against the targets. When a target is changed in Account Manager Targets, the change is not reflected immediately in the assignment values of the team members. To see the updated assignment values, you must perform the Refresh Assignments action on the Assignments tab of the target record. This action recalculates the assignment values based on the new target value and distributes the target among the team members according to the assignment rules. The other actions are not valid for Account Manager Targets. References: Account Manager Targets in Manufacturing Cloud, Learn About Account Manager Targets, Enable Account Manager Targets, Assign an Account Manager Target

Program Based Business is a feature of Manufacturing Cloud that allows manufacturers to track and manage the demand from their end customers (such as phone brands) and compare it with the actual orders from their channel partners (such as distributors or contract manufacturers). This feature helps manufacturers to plan for future opportunities, optimize their inventory and production, and increase their market share. Program Based Business enables manufacturers to:

Create programs that represent the end customer demand for a specific product or product family over a period of time.

Associate sales agreements and orders with programs to track the actual performance against the program demand.

Use program analytics to monitor the program health, identify gaps and risks, and take corrective actions.

Use program forecasts to generate account forecasts based on the program demand and actuals. References: Program Based Business Overview, Create a Program, Associate Sales Agreements and Orders with Programs, Use Program Analytics, Use Program Forecasts.

 = These two actions can be taken to give the Account Managers ‘Read’ access to the new custom field on the APF Table. The first action involves cloning the existing permission set that already grants access to the APF Table and its standard fields, and then modifying the cloned permission set to include the new custom field. The second action involves editing the existing permission set directly to add the new custom field. Both actions require the same license type, which is Manufacturing Forecast Psl, to access the APF Table. The other two actions are not valid because they use a different license type, which is Salesforce, that does not support the APF Table. References: = Assign the Permission Set for Advanced Account Forecast Product Category, Create Custom Fields for Account Product Forecast and Account Product Period Forecast Objects, Permission Sets and Licenses for Manufacturing Cloud

When multiple active sales agreements contain the same product for the same account and time period, you can use custom logic to determine which sales agreement to link the order to. You can use the Sales Agreement Order Linking Apex class to implement your custom logic and override the default behavior of linking the order to the sales agreement that was activated last1. References:

Sales Agreements and Forecasting in Manufacturing Cloud

Set Up and Configure Sales Agreements

n: When planning a global rollout of Manufacturing Cloud, some key considerations are:

Manufacturers may have one or many versions of core systems like an Enterprise Resource Planning (ERP) that will require integrations and design considerations that vary. Manufacturing Cloud can integrate with existing ERP systems and Order Management Systems (OMS) by using APIs, the MuleSoft Accelerator for Manufacturing, or other middleware solutions1. However, different versions of ERP systems may have different data models, business processes, and security requirements that need to be taken into account when designing and implementing the integrations2.

There are language requirements, legal variation by geography, and cultural differences. Manufacturing Cloud supports multiple languages and currencies, but it also needs to comply with the local laws and regulations of each country or region where it operates1. For example, there may be different tax rules, privacy policies, or data protection standards that affect how Manufacturing Cloud handles and stores customer data3. Additionally, there may be cultural differences in how customers and partners communicate, negotiate, and collaborate, which may require adjustments in the user interface, workflows, and analytics of Manufacturing Cloud4. References: Considerations for Working with Manufacturing, What Is Manufacturing Cloud?, Salesforce Blog: Manufacturing Cloud, Salesforce Manufacturing Cloud: enabling customer centricity for manufacturers

According to the Salesforce Manufacturing Cloud documentation, the ‘Delete sales agreement’ profile permission allows users to delete an active, approved, canceled, or expired sales agreement. However, they can only delete a sales agreement if it doesn’t have any active orders associated with it. Only users with this permission will see the ‘Delete’ option on the sales agreement record header. Account owners or other users without this permission will not see the ‘Delete’ option. The status of the sales agreement does not affect the ability to delete it, as long as there are no active orders1. References: 1: Delete a Sales Agreement - Salesforce

 The Analytics for Manufacturing App is a prebuilt app that includes dashboards to visualize and analyze data from various Manufacturing Cloud objects, such as sales agreements, account forecasts, account manager targets, and rebates. Before you can create the app, you need to ensure that your data meets some specific requirements, otherwise the app creation fails. One of the requirements is that at least one record must exist in each of the Manufacturing Cloud objects to be analyzed, such as Order, Sales Agreement, Account Forecast, and so on. This ensures that the app has some data to work with and can generate meaningful insights. The other requirements are related to record types, permissions, and field-level security1. References: Data Required to Create the Analytics for Manufacturing App, Set Up Analytics for Manufacturing, Deploy CRM Analytics for Manufacturing.

To mitigate manual errors in repetitive business processes at Universal Containers, the consultant should recommend leveraging Process Builder and Flow Builder within Manufacturing Cloud. These automation tools allow for the design and implementation of customized workflows and processes that can significantly reduce the likelihood of manual errors, thereby enhancing efficiency and accuracy in the organization's operations .

 According to the Salesforce Manufacturing Cloud documentation1, the Account Forecast Adjustments (AFA) and Account Forecast (AF) objects do not support triggers. These objects are used to store the manual adjustments and the rolling forecast records of a particular account, respectively. The other two objects, Account Product Period Forecast (APPF) and Account Product Forecast (APF), do support triggers. These objects are used to store the quantity and revenue information of a product in a particular time period and the cumulative values for a product across all periods, respectively. References: Manufacturing Cloud Standard Objects

To migrate data from a legacy system to Manufacturing Cloud, the administrator should follow the recommended order of data import. This order ensures that the data dependencies and relationships are maintained and that the data integrity is preserved. The recommended order of data import is as follows1:

Accounts: This is the first object to import, as it represents the customers and their details. Accounts are related to Sales Agreements and Orders, so they must be imported before them.

Sales Agreements: This is the second object to import, as it represents the contractual agreements between the customers and the manufacturer. Sales Agreements are related to Sales Agreement Products and Sales Agreement Schedules, so they must be imported before them.

Sales Agreement Products: This is the third object to import, as it represents the products that are included in the Sales Agreements. Sales Agreement Products are related to Sales Agreement Product Schedules, so they must be imported before them.

Sales Agreement Product Schedules: This is the fourth object to import, as it represents the forecasted quantities and prices of the Sales Agreement Products over time. Sales Agreement Product Schedules are related to Orders, so they must be imported before them.

Orders: This is the fifth and final object to import, as it represents the actual orders placed by the customers. Orders are related to Order Products, which are automatically created when the Orders are imported.

Therefore, the correct answer is B. Accounts, Sales Agreements, Sales Agreements Schedules, Orders. References: Import Data into Manufacturing Cloud

 A sales agreement is a long-term contract that defines the terms and conditions for the products and services that you sell to your customers. You can perform various actions on a sales agreement to manage its lifecycle, such as approving, activating, expiring, or deleting it. Two of the out-of-the-box actions that you can perform on a sales agreement are:

Recalculate Actuals: This action updates the actuals for the sales agreement based on the invoices and orders associated with it. You can recalculate actuals manually or schedule it to run automatically at a specified frequency. Recalculating actuals helps you track the progress and performance of the sales agreement over time.

Update Products: This action allows you to add, remove, or modify the products and categories in the sales agreement. You can update products manually or use the mass update feature to apply changes to multiple products at once. Updating products helps you adjust the sales agreement to reflect the changing needs and preferences of your customers.

 Sales Agreements and Forecasting in Manufacturing Cloud, Sales Agreement, Get Started with Manufacturing Cloud for Sales, Create and Work with Sales Agreements, Manufacturing Cloud

To delete a sales agreement, the user must have the Delete Sales Agreements permission, which is included in the Manufacturing Sales Agreement Manager permission set. This permission allows the user to delete an active, approved, canceled, or expired sales agreement, as long as it does not have any active orders associated with it. Giving the user the Delete Sales Agreements profile or the Remove Sales Agreement permission will not enable them to delete sales agreements, as these are not valid options in Salesforce Manufacturing Cloud. References: Delete a Sales Agreement, Assign the Manufacturing Permission Sets to Users.

To meet the business requirements of UC, the administrator should add a custom Material dimension to the Forecast Fact and Forecast Set objects. This will allow UC to group and filter the forecast data by the material attribute of the products. The administrator should also clone and use the standard DPE definitions to populate the new custom metrics for the Material dimension. The standard DPE definitions are templates that can be used to aggregate data from various sources, such as sales agreements, orders, opportunities, and custom objects. By cloning and using the standard DPE definitions, the administrator can save time and effort in creating the formulas and filters for the new custom metrics. The administrator does not need to configure a custom Forecast Context or create new DPE definitions from scratch, as these options are more complex and require more customization. References: Create Holistic Forecasts with Advanced Account Forecasting, Set Up Dimensions and Period Groups, Streamline Forecast Calculations with Data Processing Engine Definitions

To establish clarity between new business and run-rate business, Universal Containers should adopt a differentiated approach where new businesses use Opportunities and Collaborative Forecasting, while run-rate business utilizes Sales Agreements and Account-Based Forecasting. This strategy leverages the strengths of Salesforce Manufacturing Cloud's forecasting and agreement features to align with the distinct nature of new and run-rate business, ensuring accurate forecasting and effective management of business operations.

 The admin at badger power can set up an eligibility criteria for this rebate type with activity Date >= Jan1 and <= Jan31. This option allows the admin to specify the date range for which the rebate type applies to the transactions. The other options are either not possible or not sufficient to achieve the desired result. For example, setting up a new rebate program with a single payout period for Jan does not ensure that the rebate type is valid only for transactions completed in January. Setting the rebate type to active on Jan1 and inactive on Jan31 does not prevent the rebate type from being applied to transactions that occurred before or after January. Using the effective date on rebate type does not specify the end date for the rebate type validity. References: Eligible and Applied Rebate Types on a Transactional Object, Common Rebate Types

 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

A sales agreement is a record that captures the terms and conditions of a long-term or run-rate business relationship between a manufacturer and a customer. It can include products, product categories, prices, volumes, schedules, and other details. A sales agreement can have a maximum of 1500 products or product categories and 72 schedules. Contact Salesforce support if you want to increase the limits. Note that having a large number of product or product categories and schedules can affect system performance1. References: Considerations for Working with Manufacturing

The organization should leverage Partner Visit Management functionality to fill the gap. Partner Visit Management is a feature of Salesforce Manufacturing Cloud that enables manufacturers to collaborate with their channel partners on sales and service activities. With Partner Visit Management, manufacturers can create and assign visit plans to their partners, track their progress and performance, and provide feedback and coaching. Partners can access the visit plans through the Manufacturing partner site, which is a predefined template for Experience Cloud sites. The Manufacturing partner site also allows partners to view and update sales agreements, forecasts, and account information, as well as access resources and training materials. By using Partner Visit Management and the Manufacturing partner site, the organization can support its channel partners by providing functionality, insights, and data, as well as working closely with them to plan their work. References:

Engage with Your Partners - Salesforce

What Is Manufacturing Cloud? - Salesforce

Elevate Partner Management - Salesforce

Simplify Partner Engagement: A Guide for Manufacturers - Salesforce

Data Processing Engine (DPE) is a feature of Rebate Management that allows you to transform data that is available in your Salesforce org and write back the transformation results as new or updated records. You can use DPE to process data for standard and custom objects. Rebate Management has DPE templates that you can clone and customize to suit your business needs. The templates either help you to aggregate transactions by different criteria, or help you to manage other rebate processes. The out-of-the-box DPE jobs in Rebate Management use the templates to query, extract, filter and aggregate journal transactions based on the eligibility criteria and calculation definitions of the rebate types. The aggregated data is then stored in the Rebate Member Product Aggregate object, which is used to calculate the payouts for the program members. References: Data Processing Engine in Rebate Management | Salesforce Trailhead Module, Data Processing Engine Templates with Rebate Management - Salesforce, Data Processing Engine | Rebate Management Developer Guide | Salesforce Developers, Data Processing Engine, Batch Management, and Invocable Actions | Rebate Management Developer Guide | Salesforce Developers

The Accounts Health dashboard allows a user to analyze revenue realization, length of relationship, and customer lifetime value across accounts. Revenue realization is the actual revenue as a percentage of planned revenue. Length of relationship is the duration between today and the start date of the first sales agreement with an account. Customer lifetime value is the total of revenue generated to date and revenue anticipated from the account. These metrics help the user to assess the performance and potential of each account and identify opportunities for growth or retention. References: Calculate Key Performance Indicators Using CRM Analytics, Calculating Customer Lifetime Value (CLV) With Salesforce, How to calculate customer lifetime value

 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

Validating the functionality against business process flows is a key step in the implementation or system update of Salesforce Manufacturing Cloud. It helps to ensure that the system meets the business requirements and expectations of the stakeholders, and that it can handle the various scenarios and use cases that may arise in the manufacturing industry. By validating the functionality, you can also identify and resolve any issues or gaps that may affect the system performance, usability, or security. Additionally, validating the functionality can help you to document and communicate the system changes and benefits to the end users and other parties involved in the project. References: Implementation Guide, System Updates