AP-223 Exam Preparation Material | CPQ and Billing Consultant Accredited Professional

Explanation:
In Salesforce CPQ, the Order Management plugin functionality provides flexibility in customizing the default package behavior, including the ability to set the activation date for orders. This feature allows for greater control over the order management process, enabling organizations to align the activation dates of their orders with their specific business requirements. By overriding the default behavior, businesses can ensure that the activation dates are set in a manner that is consistent with their operational workflows, contractual obligations, or customer agreements. This capability is part of Salesforce CPQ's broader set of features designed to provide customizable solutions to complex quoting and order management challenges.

Explanation:
Cross object formula fields are fields that reference data from related objects using lookup or master-detail relationships. They can be useful to display information from parent or child objects without creating custom code or workflows. However, using too many cross object formula fields in a Revenue Cloud project can pose some risks, such as:
Formula field data is not always available during CPQ quote calculation. This means that the formula fields may not reflect the latest values from the related objects when the quote is being generated or updated. This can cause inaccurate pricing, discounts, or taxes. To avoid this, it is recommended to use CPQ fields or custom fields instead of cross object formula fields for quote calculation. 12
They are computationally expensive. This means that the formula fields require more processing power and time to evaluate and display the data from the related objects. This can affect the performance and responsiveness of the application, especially if there are multiple formula fields on the same object or page layout. To avoid this, it is recommended to limit the number and complexity of cross object formula fields, and use filters or conditions to reduce the number of records that need to be evaluated. 34
They can easily exceed limits if not carefully designed and tested. This means that the formula fields can cause errors or warnings if they exceed the maximum length, number, or level of relationships
allowed by Salesforce. For example, a formula field can only reference up to 10 unique relationships and span up to five levels of relationships. If these limits are exceeded, the formula field will not save or display correctly. To avoid this, it is recommended to review the formula field limits and best practices, and test the formula fields in different scenarios and environments.
Reference: 1: Lookup Price Rule query considerations with Salesforce CPQ [7]
2: Salesforce CPQ Quote Calculation Stages [8]
3: What Is a Cross-Object Formula? - Salesforce [9]
4: Tips for Reducing Formula Size and Complexity - Salesforce [10]
5: Formula Field Limits - Salesforce [11]

Explanation:
RASIC is an acronym used in project management to define the roles and responsibilities of each person who interacts with the project. Each letter represents a designated role in a task’s completion:
R (Responsible): This is the task lead C the individual who is ultimately responsible for getting the job done. There should only be one person responsible.
A (Accountable): This is the person, or people, who will approve or deny the task once it’s complete.
The person responsible can also play this role, but it can also be a technical expert or stakeholder.
S (Supporting): The individual(s) in this role actively work on the task and help the person responsible.
I (Informed): The individual(s) in this role need to be informed of the task’s progress and any decisions being made. These are the people who need to know when the task is complete.
C (Consulted): People in this role offer advice or guidance but do not actively work on the task. These are often subject matter experts who offer guidance or one-time technical reviews1.
Reference
Defining Roles and Responsibilities on a Project (RASIC) - NexightGroup

Explanation:
To implement the user story of rewarding loyal customers with bulk discounts based on previously purchased quantities, the design of the solution should include the following components:
Contracts, Subscriptions and Assets should be populated with historical data. This is necessary to track the customer’s purchase history and determine the appropriate discount tier for each product or service. Contracts, Subscriptions and Assets are the core objects of Revenue Cloud that store the information about the customer’s agreements, recurring charges, and entitlements. By migrating the historical data from the legacy system to these objects, the customer can leverage the Revenue Cloud features such as renewal management, usage-based pricing, and revenue recognition. 123
Discount schedules with Cross Orders checked. This is the feature that enables the bulk discounts based on previously purchased quantities. A discount schedule is a set of discount tiers that apply to a product or a product option based on the quantity or amount ordered. By checking the Cross Orders option, the discount schedule will consider the quantities from all the orders associated with the same account, contract, or subscription. This way, the customer can reward their loyal customers with lower prices for higher volumes. 45
Reference:
1: Revenue Management Platform & CPQ Solution - Salesforce.com US
2: Salesforce Introduces Revenue Cloud to Help Businesses Accelerate Revenue Growth Across Any Channel - Salesforce
3: Give Discounts for Long Subscriptions Unit | Salesforce Trailhead
4: Discount Schedules - Salesforce
5: Salesforce Revenue Cloud Trailmix - Trailhead