C. Keep the legacy CPQ system and build to the gaps in Revenue Cloud so the customer can use both systems to satisfy requirements

Answer DescriptionExplanation:

When implementing Salesforce Revenue Cloud for a business unit that already uses a legacy CPQ system, the following considerations should be taken:

AMap legacy CPQ system capabilities to ensure there is no loss of logic from the older system: It’s important to understand the capabilities of the legacy CPQ system and map these to the new system to ensure that there is no loss of functionality or business logic12.

B. Transform the customer’s business processes, capture new requirements for the new Revenue Cloud technology: Implementing a new system like Revenue Cloud often requires a transformation of existing business processes. It’s crucial to capture new requirements that align with the capabilities of Revenue Cloud13.

D. Customize Revenue Cloud’s user interface so the customer experiences no major interruption to the new system: To ensure a smooth transition, it can be beneficial to customize the user interface of Revenue Cloud to match the look and feel of the legacy system. This can help minimize disruption for end users14.

References

Salesforce Introduces Revenue Cloud to Help Businesses Accelerate Revenue Growth Across

Any Channel - Salesforce Sales

Salesforce Revenue Cloud: A Guide | BillingPlatform

CRM Implementation Considerations- Salesforce

The Ultimate Guide to Salesforce CRM and CPQ Integration

Oracle CPQ Cloud and Salesforce.com Integration

A. Cancel and rebill, correct the order, create and post a new invoice.

Answer DescriptionExplanation:
Upon noticing an error on a posted invoice, the recommended corrective action is to use the "Cancel and Rebill" feature. This process allows an admin to roll back the invoice to its state before the most recent billing cycle, enabling the correction of errors on the invoice record. This functionality is applicable to both draft and posted invoices, providing a way to address issues such as missing invoice lines or incorrect billing details. After canceling and rebilling, the admin can correct the order as needed and proceed to create and post a new invoice, ensuring the accuracy of billing records.

C. Required fields are missing or incorrectly populated on the legacy contract and subscription data

Answer DescriptionExplanation:
The error ‘attempt to de-reference a null object’ typically occurs when there is an attempt to access a field or method on an object that has not been initialized or has been assigned a null value. In the context of Salesforce Revenue Cloud, when amending legacy contracts and subscriptions, this error can occur if required fields are missing or incorrectly populated on the legacy contract and subscription data. This could be due to incorrect data migration or manual data entry errors. It’s important to ensure that all required fields are correctly populated when migrating legacy data to Salesforce CPQ.

References

Error:Can’t renew the contract automatically because it … - Salesforce
Guidelines for Amending Contracts - Salesforce
Legacy Data Upload for Salesforce CPQ

C. They can easily exceed limits if not carefully designed and tested
D. Formulas field data is not always available during CPQ quote calculation
E. They are computationally expensive

Answer DescriptionExplanation:

Cross-object formula fields are useful for accessing data from related objects, but they also have some drawbacks and risks, especially when used excessively in a revenue cloud project. Some of the risks are:

They can easily exceed limits if not carefully designed and tested. Cross-object formula fields count against the total number of fields allowed per object, and they also consume more resources than regular fields. If the formula is too complex or references too many objects, it can cause performance issues, errors, or failures. For example, a formula can only reference up to 10 unique relationships, and a record can only trigger up to 16 levels of cross-object formula updates. 12

Formula field data is not always available during CPQ quote calculation. CPQ quote calculation is a process that evaluates the pricing, discounts, taxes, and other factors of a quote. During this process, some cross-object formula fields may not have the latest data or may not be accessible at all, depending on the order of execution and the timing of the updates. This can lead to inaccurate or inconsistent results, or even prevent the quote from being calculated. 3

They are computationally expensive. Cross-object formula fields require more processing power and time than regular fields, as they need to query and calculate data from multiple objects and relationships. This can affect the overall performance and responsiveness of the revenue cloud project, especially when there are many cross-object formula fields involved. Additionally, cross-object formula fields can trigger cascading updates and validations, which can further increase the computational load and complexity. 4

References:

1: What Is a Cross-Object Formula? - Salesforce
2: Formula Operators and Functions - Salesforce
4: Create Cross-Object Formulas Unit | Salesforce Trailhead

C. Accounting and Finance
D. Sales Operations
E. Information Technology

Answer DescriptionScoping a Revenue Cloud project involves understanding the business needs, defining the project goals, and planning the implementation strategy12. The teams that should be involved in this process are those that have a direct stake in the project’s outcome and can provide valuable input into the project’s requirements12. These teams typically include:

Accounting and Finance: This team can provide insights into the financial processes that the Revenue Cloud project will support, such as billing, revenue recognition, and financial reporting12.

Sales Operations: This team can provide insights into the sales processes that the Revenue Cloud project will support, such as quote-to-cash, contract management, and sales forecasting12.

Information Technology: This team can provide technical expertise and support for the implementation of the Revenue Cloud project, including system integration, data migration, and IT infrastructure12. References: 12

A. Create ARR c on the opportunity Line item object, and create a price rule to copy the value from ARR c on SBQQ QuoteLine___c on opportunity Product.

Answer DescriptionExplanation:

The Salesforce CPQ (Configure, Price, Quote) system allows for the creation of custom fields on the Opportunity Line Item object, such as ARR c, to capture recurring revenue. This can be used in conjunction with a price rule to copy the value from the corresponding field (ARR c) on the SBQQ QuoteLine__c object. This solution is efficient as it leverages the existing structure and functionality of Salesforce CPQ, allowing for the seamless integration of recurring revenue data into existing pipeline reports.

References:

Salesforce Revenue Cloud documents and learning resources
Salesforce Introduces Revenue Cloud to Help Businesses Accelerate Revenue Growth Across Any Channel
Get Started with Revenue Intelligence
Introduction to Revenue Intelligence for Sales Cloud
Getting Started: Revenue Cloud: Salesforce Billing
CPQ Object Relationships - Salesforce
Object Reference for the Salesforce Platform
Salesforce CPQ Clone with Related Button to clone Quotes to a new …
Troubleshoot Salesforce CPQ Opportunity and Quote sync issues
Bundle configuration errors ‘does not belong to SObject Type’ or …
Salesforce Revenue-Cloud-Consultant-Accredited-Professional Quiz 1

C. Subscriptions

Answer DescriptionExplanation:
Customer Asset Lifecycle Management (CALM) is a feature of Salesforce Revenue Cloud that enables businesses to manage the entire lifecycle of their customer assets, from creation to renewal to termination. Customer assets are the goods and services that customers have purchased or subscribed to, and they can be tracked and updated on a single platform. CALM provides an aggregated view of the current customer assets on a contract, as well as their history, status, and future changes. CALM also allows businesses to automate the creation and activation of orders, amendments, and renewals based on the customer asset data. With CALM, businesses can gain visibility and control over their revenue streams, optimize their customer relationships, and reduce manual errors and inefficiencies.

References:

https://www.salesforce.com/au/products/revenue-lifecycle-management/
https://www.g2.com/products/salesforce-salesforce-revenue-cloud/features

A. Know which business process the requirement supports to categorize the user story
B. Identity the actor or personas in this user story
E. Identify the acceptance criteria or result for satisfying the user story.

Answer DescriptionExplanation:
User stories are short, simple descriptions of a feature or functionality from the perspective of the end user or customer. User stories are used to capture the requirements and value proposition of a product or service in an agile framework. User stories should follow some best practices to ensure clarity, consistency, and alignment with the business goals and user needs. 12

Some of the key steps when documenting user stories are:
Know which business process the requirement supports to categorize the user story. This helps to prioritize and organize the user stories based on the business value and impact they deliver. It also helps to avoid duplication and inconsistency among user stories. 3

Identify the actor or personas in this user story. This helps to define the user role, needs, goals, and motivations that drive the user story. It also helps to create empathy and understanding for the user and their context. 4

Identify the acceptance criteria or result for satisfying the user story. This helps to specify the expected outcome, behavior, or functionality that the user story should deliver. It also helps to define the scope, quality, and testability of the user story. 5

Designing the solution while the business process is being defined is not a key step when documenting user stories. This can lead to premature or biased decisions that may not address the real user problem or value proposition. User stories should focus on the what and why, not the how. The solution design should be done after the user stories are validated and prioritized, and in collaboration with the development team and other stakeholders. 6

Documenting user acceptance test scripts for the user story is not a key step when documenting user stories. This can be done later, after the user stories are refined and detailed, and before the development and testing phases. User acceptance test scripts are used to verify that the user story meets the acceptance criteria and the user expectations. [7]

References:

1: User Stories | Examples and Template | Atlassian
2: How to Write Perfect User Stories (With Templates): A Step-By-Step Guide | airfocus
3: 10 Tips for Writing Good User Stories - Roman Pichler
4: The Anatomy of a User Story | Scrum Alliance | Includes Template
5: Best Practices to Succeed with User Stories - DZone
6: UX documentation: Guide, best practices, template