Salesforce Manufacturing-Cloud-Professional Manufacturing Cloud Accredited Professional Exam (WI25) Exam Practice Test

Upon the installation of the Analytics app, the default dashboards on the Account page include "Accounts agreement performance" and "Forecast analytics for the selected account." These dashboards provide a comprehensive overview of an account's performance in terms of sales agreements and forecast accuracy, allowing for in-depth analysis and strategic planning based on historical and current data.

A System Integration Testing (SIT) environment is used as an environment to perform system-to-system testing. This means that the SIT environment is used to test the integration of different systems or components that are part of the Salesforce Manufacturing Cloud solution. The SIT environment allows the verification of the functionality, performance, and reliability of the integrated systems, as well as the identification and resolution of any defects or issues that may arise during the integration process. The SIT environment is typically a replica of the production environment, but with a smaller data set and lower security requirements. The SIT environment is also used to validate the data migration and synchronization between the source and target systems, as well as the compatibility and interoperability of the APIs and web services that are used for the integration. References:

Manufacturing Cloud - Salesforce

How to Perform Automated Integration Testing in Salesforce

Automate and Test During Integration

The detailed technical design document is a document that describes the technical specifications and architecture of a solution. It is based on the functional and nonfunctional requirements that are captured in the business requirement document1. Therefore, the detailed technical design document should be completed after the business requirement document has been generated, and before the development and testing phases of the project. This ensures that the technical design aligns with the business needs and expectations, and provides a clear roadmap for the implementation team2. References: 1: Get Started with the Technical Project Documentation3, 2: Documentation and Implementation Diagrams1

To create sales agreements from historical data for a Manufacturing Cloud solution, a consultant must consider the following data items: Accounts, Orders, Order Lines, and Products. These are the core objects that are used to create and manage sales agreements in Manufacturing Cloud. Accounts represent the customers or partners that have sales agreements with the organization. Orders and Order Lines represent the actual sales transactions that are associated with the sales agreements. Products represent the items or services that are sold or purchased through the sales agreements. Invoices and Opportunities are not required for creating sales agreements from historical data, as they are not part of the sales agreement object model. Invoices are used to track the billing and payment status of the orders, while Opportunities are used to track the potential sales deals that may or may not result in orders. References: Sales Agreement Object Model, Create a Sales Agreement, Sales Agreement Fields

Account Based Forecasting and Sales Agreements are two Manufacturing Cloud functions that should be configured to have a complete picture of both run-rate and net-new business. Account Based Forecasting allows you to forecast your sales revenue based on the account level, rather than the opportunity level. This gives you more visibility into the demand from your existing customers, as well as the potential from new customers. Sales Agreements allow you to manage the sales lifecycle of your long-term contracts with customers, including pricing, volumes, and order realization. This helps you to track and fulfill your run-rate business, as well as to identify and capture new business opportunities within your agreements. References: Forecast Your Run-Rate and New Business with Account-Based Forecasting - Salesforce Help, [Create and Work with Sales Agreements - Salesforce Help]

Account manager targets are records that represent the revenue goals for account managers. They can be filtered by different criteria using list views. By default, Salesforce Manufacturing Cloud provides two list views to filter account manager targets by the assigned user: Assigned by Me and Assigned to Me. Assigned by Me shows the targets that the current user has created and assigned to other users. Assigned to Me shows the targets that the current user owns and is responsible for achieving. References: Learn About Manufacturing Cloud and Explore, Filter Account Manager Targets with List Views

Before you create the analytics for manufacturing App, you need to ensure that your data meets some specific requirements. One of these requirements is that at least one record must exist in each of the Manufacturing cloud objects to be analyzed, such as sales agreements, account forecasts, account manager targets, and rebates. Otherwise, the data fails the CRM Analytics check and you see an error message. Having records in these objects ensures that the app can import and display relevant data for your business1. References: Data Required to Create the Analytics for Manufacturing App

 The Forecast Analysis dashboard in Tableau CRM for Manufacturing is a tool that helps business analysts evaluate the accuracy and quality of the account forecasts generated by the Manufacturing Cloud. It allows them to compare the actual revenue with the forecasted revenue, as well as the planned revenue, for each account, product, and product category. It also shows the mean absolute percentage error (MAPE) in the forecast, which is a measure of how close the forecast is to the actual revenue. The lower the MAPE, the better the forecast. The dashboard also provides other metrics, such as forecast bias, forecast coverage, and forecast attainment, to help analysts identify areas of improvement and optimize the forecasting process1. References: Protect and Grow Your Business Unit, Forecast Analysis Dashboard, How Forecasting Works in Tableau

 When using the mass update multiple values of a single metric of a sales agreement terms tab, the three actions that are available are: replace with, decrease by, and increase by. These actions allow the user to update the values of a metric across multiple periods and products in a sales agreement. For example, the user can replace the forecasted quantity of a product with a new value, or increase the discount percentage of a product by a certain amount. The other options, update with and multiply by, are not valid actions for mass update. References: Mass Update Account Forecast Action, Update Multiple Values in Advanced Account Forecasts

 Account Manager Targets is a feature of Manufacturing Cloud that allows you to set up and manage sales goals and track performance for your account managers and their teams. To use this feature, you need to enable it in Setup and define some settings that affect how targets are created, assigned, and distributed. The three options that can be defined by an admin in the Setup area in Account Manager Targets are:

Target Measure Type: This is the unit of measurement for the targets, such as revenue, volume, or any custom measure. You can define up to three target measure types for your org and assign them to different target types. For example, you can have a target type for revenue and another one for volume, and use different target measure types for each one.

Team Member Hierarchy: This is the hierarchy that determines how targets are rolled up from individual account managers to their managers and so on. You can use the standard User Role hierarchy or a custom hierarchy based on a custom object. The hierarchy affects how targets are distributed, aggregated, and reported.

Distribution Frequency: This is the frequency at which targets are distributed from parent targets to child targets. You can choose from monthly, quarterly, or yearly distribution. The distribution frequency affects how targets are calculated and displayed for different time periods.

References: Account Manager Targets in Manufacturing Cloud | Salesforce Trailhead Module, Enable Account Manager Targets - Salesforce, Define Account Forecast Settings Unit | Salesforce Trailhead Module

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.

o add products to an order that is on an active sales agreement, the order must be in Draft status. Once an order is in Draft status, you can add products from the sales agreement or from the product catalog. You can also edit the order details, such as quantity, price, and discount. After you add the products, you can submit the order for approval. The order status changes to Pending, and the order is locked for editing. The order must be approved before it can be activated. Once the order is activated, the order status changes to Active, and the order is synced with the sales agreement. The order actuals are reflected in the sales agreement actuals. References: Approve and Activate a Sales Agreement, Get Started with Salesforce Order Management

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

For a manufacturer managing orders and contracts in an external system like SAP, the administrator should select the option to manually use API upload. This allows for the bulk upload of updated quantities at regular intervals through integration, which the Salesforce org picks up during a daily scheduled job to update sales agreements .

 The Mass Update function allows you to update multiple values of a single metric of a sales agreement in the Sales Agreement Terms tab. You can use this function to quickly adjust the planned quantity, revenue, or margin of multiple products and periods with a single action. The available actions are Decrease By, Increase By, and Replace With. These actions let you specify a percentage or an absolute value to decrease, increase, or replace the existing values. For example, you can use the Decrease By action to reduce the planned quantity of all products by 10% for the next quarter. You can also add a note to explain the reason for the mass update. References: Mass Update Sales Agreement Action, Update Multiple Values of Sales Agreements

 = 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

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

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

 The recommended method for an administrator to enable the full functionality of the Service Console for Manufacturing app is to grant the Service Agents the Service Console for Manufacturing and Industry Service Excellence permission sets. These permission sets provide access to the Service Console for Manufacturing app and the components within it, such as the Customer 360 Timeline, the Asset Performance Monitor, and the Warranty Claims Manager1. Adding the Service Console for Manufacturing component to the Service Console Lightning Page Layout or creating a custom permission set are not necessary steps to enable the app functionality2. References: Set Up Users and Permissions for Manufacturing Cloud, Learn About Service Console for Manufacturing

A consultant should prepare a template with the requirements and their associated priority, and work with the client to evaluate each item. This is the best way to advance to the next step of the project, because it helps the consultant and the client to align on the scope, objectives, and expectations of the project. It also allows the consultant to understand the client’s business needs, challenges, and opportunities, and to prioritize the requirements based on their value and feasibility. By working collaboratively with the client, the consultant can also build trust and rapport, and ensure that the client is engaged and satisfied with the project outcome. References:

Manufacturing Cloud - Salesforce

Considerations for Working with Manufacturing - Salesforce

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

When facing a deployment error indicating that the Sales Agreement object does not exist in the target environment, the first step the administrator should take is to ensure that Sales Agreements are enabled in the production organization. This is a crucial prerequisite for deploying Sales Agreements-related changes and functionalities from a development sandbox to a production environment, as the absence of enabled Sales Agreements in the target environment can lead to deployment failures .

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

The administrator would configure Field-Level Security for the Advanced Account Forecast Partner and Advanced Account Forecast Fact objects to provide users with separate levels of visibility to forecast data. The Advanced Account Forecast Partner object stores the partner information for each account forecast record, such as the partner name, partner type, and partner role. The Advanced Account Forecast Fact object stores the forecast values for each account forecast record, such as the forecast amount, forecast quantity, and forecast margin. By setting the Field-Level Security for these objects, the administrator can control which users can view, edit, or delete the partner and fact data for each account forecast record. This way, the administrator can ensure that the users only see the relevant forecast data for their role and business unit12. References: 1: Set Field-Level Security for Fact and Partner Object in Advanced Account Forecasting3, 2: Forecast Fact Object Included with Advanced Account Forecasting4

 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

The Time Period filter on a sales agreement record page allows you to view the sales agreement terms and schedules for different time periods. You can choose from three options: Range, Set Periods, and Current Period. Range lets you specify a start and end date for the filter. Set Periods lets you select up to eight periods from a list of predefined periods, such as quarters, months, or weeks. Current Period shows the current period based on the sales agreement’s period type and start date. Custom and Fiscal Year are not available options for the Time Period filter. References: = Filter Sales Agreement Schedules by Time Period, Filter Sales Agreement Terms by Products or Categories

 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

On the Forecast settings page within Salesforce Manufacturing Cloud, actions such as updating the forecast start period, forecast adjustment period, and forecast formula will trigger the regeneration of all the eligible accounts that meet the forecast generation criteria. These updates necessitate a re-evaluation of forecast data to ensure that the forecasts remain accurate and reflective of the latest business conditions and settings. This regeneration process is integral to maintaining the integrity and relevance of forecast data, facilitating effective planning and decision-making based on the most current information .

 These three user types can be selected to receive credit for an order in the Tableau CRM configuration wizard when calculating actuals against account manager targets. The configuration wizard guides users through the creation of an app from the Analytics for Manufacturing template and allows them to customize the data and settings for the app. One of the settings is to choose who gets credit for the orders, which determines how the actual revenue is attributed to the account managers. The user can select one of the following options:

Account Owner: This option credits all orders to the account owner’s actual revenue, regardless of who owns the order. This is useful when the account owner is responsible for the overall relationship and revenue of the account.

Order Owner: This option credits all orders to the order owner’s actual revenue, regardless of who owns the account. This is useful when the order owner is responsible for the individual order and revenue of the order.

Other User: This option credits all orders to a custom user’s actual revenue, based on a custom lookup field for a user on the account. This is useful when there is a different user, such as a sales engineer or a partner, who is responsible for the order and revenue of the order.

References: = Create and Share an App from the Analytics for Manufacturing Template, Salesforce Authentication - Tableau, The Configuration Wizard - Salesforce Developers

Salesforce Manufacturing Cloud can be integrated with Oracle ERP orders data using two options:

Use an AppExchange ISV solution: This option allows you to leverage existing solutions from independent software vendors (ISVs) that are available on the Salesforce AppExchange platform. These solutions are designed to simplify and automate the integration process between Salesforce and Oracle ERP systems. Some examples of AppExchange ISV solutions are rSTAR, DBSync, and Jitterbit.

Use API integration with custom logic: This option allows you to use the Salesforce APIs and the Oracle ERP APIs to create custom logic for integrating the orders data between the two systems. You can use any programming language or tool that supports REST or SOAP web services to build the integration logic. You can also use the MuleSoft Accelerator for Manufacturing, which is a prebuilt integration solution that connects Salesforce Manufacturing Cloud with Oracle ERP Cloud1.

References:

ERP and Salesforce: Everything Manufacturers Need To Know

Integrate Salesforce.com with Oracle Integration Cloud

Oracle Cloud Using the Salesforce Adapter with Oracle Integration Cloud

All About Integrating Oracle ERP and Salesforce CRM-rSTAR Technologies

What Is Manufacturing Cloud? - Salesforce

Account Forecasting is a prerequisite feature for using the Advanced Account Forecasting Analytics for Manufacturing app. This app allows users to create holistic forecasts across multiple dimensions and horizons, and analyze their forecast data using dashboards. To enable Account Forecasting, users need to have the Manufacturing Cloud permission set license and the Manufacturing Cloud permission set assigned to them. The other options are not relevant for this requirement. Sales Agreements and Orders are not required for creating and sharing the app, although they can be used as data sources for the forecasts. References: Create Holistic Forecasts with Advanced Account Forecasting, Set Up Users and Permissions for Manufacturing Cloud, Use Advanced Account Forecasting Analytics for Manufacturing

 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

The Advanced Account Forecast object is used to track the expected and actual order values for each account and product family. It allows field reps to compare the forecasted and actual order values for each account and product family, and update them as needed. The Advanced Account Forecast object also enables field reps to collaborate with their distributors and align on the sales agreements, orders, and brand-promotion campaigns12. References: Meet Manufacturing Cloud, Strengthen Relationships with Partners

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

One of the methods to calculate Actuals for sales agreements is to automatically derive them from direct orders. A direct order is an order that is created from the related list of a sales agreement record. A daily automated process calculates the product quantity fulfilled in each activated order, and then updates that quantity in the sales agreement. This method allows you to track the actual performance of your sales agreements based on the orders placed by your customers or partners. You can also use other methods to calculate Actuals, such as importing quantities from external sources, or using orders associated with contracts. References: Create Orders to Calculate Sales Agreement Actuals, How Are Sales Agreement Actuals Calculated?

Manufacturing Cloud provides three permission sets related to Sales Agreements, Account Forecasting, and Account Manager Targets. These permission sets give users access to the features and data models that are specific to the manufacturing industry. The permission sets are:

Manufacturing Account Forecast: This permission set lets users track account forecasts for quantity and revenue metrics of products. Users can view and edit the Account Product Forecast and Account Product Period Forecast objects, as well as the related objects such as Account, Product, and Sales Agreement.

Manufacturing Sales Agreements: This permission set gives users access to sales agreements that work with orders, contracts, and more. Users can view and edit the Sales Agreement and Sales Agreement Line Item objects, as well as the related objects such as Account, Product, and Order.

Manufacturing Account Manager Target: This permission set gives users access to Account Manager Target features that include creating, assigning, and distributing targets. Users can view and edit the Account Manager Target and Account Manager Target Line Item objects, as well as the related objects such as Account, Product, and Sales Agreement.

References: Assign the Manufacturing Permission Sets to Users, Set Up Users and Permissions for Manufacturing Cloud

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

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 Account Manager Target object represents a target created by an account manager for a fiscal year, measure, and target value1. To measure the account managers on a CSAT target, the admin should add a picklist value on the Measure field with Label = CSAT and add Measure Type = Other, on the Account Manager Target object. This way, the account managers can create and assign targets for the CSAT measure to their direct reports2. The other options are incorrect because they either use the wrong object, field, or value for the CSAT target. References: Create and Assign Targets, Set Up and Configure Account Manager Targets, Discuss Salesforce Manufacturing-Cloud-Professional Exam Topic 1 Question 19, Manufacturing Cloud Developer Guide

To conduct proper testing of Manufacturing Cloud, the end users need the following items:

Sandbox access: A sandbox is a copy of the production environment that allows users to test changes and features without affecting the live data. Manufacturing Cloud offers different types of sandboxes for different testing purposes, such as learning, pre-release, and base12.

Test data: Test data is a set of realistic and representative data that is used to simulate the actual business scenarios and workflows in Manufacturing Cloud. Test data can be created manually, imported from external sources, or copied from the production environment34.

Process scripts: Process scripts are step-by-step instructions that guide the users through the testing scenarios and expected outcomes. Process scripts help to ensure that the testing is consistent, comprehensive, and aligned with the business requirements . References: Create a Manufacturing Cloud Trial Org, Try Manufacturing Cloud for Free, Create Test Data for Your Full Sandbox, Import Data into Your Org, [Create a Test Plan for Your Salesforce Implementation], [Test Your Salesforce Implementation].

For integrating order data from an ERP system into Sales Agreements in Salesforce, the best practice is to create specific permission sets and possibly permission set groups that grant the necessary permissions, including write access to custom objects. These permission sets should then be assigned to the integration user account. This approach ensures that the integration user has precisely the access needed without the broad permissions that would come with using a Salesforce administrator account. It also allows for more granular control and security by limiting permissions to only those necessary for the integration's functionality.

Salesforce Manufacturing Cloud allows users to define the renewal period for sales agreements in their org. The renewal period is the number of days before the end date of a sales agreement from when users can renew the agreement. Users can renew a sales agreement only when the renewal period starts. The other options are not related to the renewal of sales agreements. References: Define Renewal Period for Sales Agreements

 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