How does Hold Billingwork?
Hold Billing is a feature of Salesforce Revenue Cloud that allows businesses to control when an order product is invoiced, based on certain criteria or events. By setting theHold Billing field toYes on an order product, the billing process is paused for that order product and all its usage summaries. This means that no invoice lines or invoice documents are generated for the order product until the hold is released. The holdcan be released by setting the Hold Billing field to No or null, either manually or automatically through a workflow or trigger. When the hold is released, Salesforce Billing will create an invoice as soon as possible, and include all the invoice lines that were accumulated during the hold period. This ensures that the customer is billed for the full amount of the order product, regardless of the hold duration. For example, if an order product has a monthly billing frequency and a hold billing period of twomonths, the first invoice after the hold will include three invoice lines: one for the current month and two for the previous months when the hold was active.Reference:
https://help.salesforce.com/s/articleView?id=sf.blng_hold_billing.htm&language=en_US&type=5
https://trailhead.salesforce.com/users/officialblaze/trailmixes/revenue-cloud-get-started-with-billing
Universal Containers has recently implemented and released CPQ to users in their production environment. After an extensive testing Cycle in a sandboxed environment.
One of the automations implemented was to set everynew quote created as "primary" at
the time of creation in order to save clicks. Users immediately began to report errors when
trying to create quotes in the production environment for the first time. What could have
caused this issue?
According to the Salesforce Revenue Cloud CPQ documentation, users need to have the Create, Read, Edit, and Delete permissions on the Quote object in order to create and manage quotes. If users do not have the proper accessto the Quote object, they will encounter errors when trying to create quotes, even if the quotes are set as primary by default. This is because the primary quote field is a lookup field that references the Quote object, and users need to have access to the referenced object in order to populate the lookup field. Therefore, the most likely cause ofthe issue is that the users did not have the proper access to the Quote object in the production environment, and this was not detected in the sandbox environment because the users had different permissions or profiles there.Reference:
https://help.salesforce.com/s/articleView?id=000316738&language=en_US&type=1
https://help.salesforce.com/s/articleView?id=000381216&language=no&type=1
In Salesforce CPQ, ensuring that users have the proper access to the Quote object is crucialfor the smooth creation and management of quotes. The issue reported by users in the production environment, where errors occurred upon trying to create quotes for the first time, likely stemmed from insufficient permissions on the Quote object. In CPQ, setting a new quote as 'primary' at the time of creation is a common practice to streamline the quoting process. However, if users lack the necessary permissions on the Quote object, they would encounter errors when attempting to create or modify quotes. It's important to note that in Salesforce CPQ, orders must be created from a primary quote, and once an order is created from a primary quote, the quote cannot be edited. This indicates that the underlying issue is related to access permissions on the Quote object, rather than post-installation scripts, access to the Opportunity Product object, or access to the Quote Line object.
Which topic of discussion comes first in a salesforce CPQ Scoping Session?
In a Salesforce CPQ Scoping Session, the first topic of discussion is typically Business Process Mapping.This involves understanding the current business processes and identifying areas where Salesforce CPQ can provide improvements. It's an essential step in the scoping process as it helps to define the project's scope and identify potential challenges earlyon. The other topics like Quote Document and e-signature, Order Management, and Products and Bundles are also important but they usually come after the business processes have been mapped and understood.
Reference
Get Started with Salesforce CPQ Unit | Salesforce Trailhead
CPQ Scoping Questionaire? : r/salesforce -Reddit
How To: Salesforce CPQ: Build a Bundle
A Subscription-based company has a Revenue Cloud user story to replace their legacy system which states "As a Sales User, I need to see my active deals (Including new and renewals opportunities) from the old system carried over to the new Salesforce CPQ system once we go-live".
What are the relevant objects that will store the extracted information from the legacy system?
What three key considerations for legacy data migration will expand the project scope of a Revenue Cloud implementation?
Legacy data migration is a critical aspect of a Revenue Cloud implementation and certain considerations can indeed expand the project scope:
A . Fragmented and incomplete information will need to be aggregated and validated, otherwise the solution will yield unexpected results: Data quality is a key factor in any data migration project.If the legacy data is fragmented or incomplete, additional effort will be required to aggregate and validate the data before it can be migrated to the new system1.
B . Extracting from multiple sources takes additional resources and time to access and process: If the legacy data resides in multiple sources, it can increase the complexity of the data extraction process.This can require additional resources and time, thus expanding the projectscope1.
E . Large volumes of data take a longer time to load: The volume of data to be migrated can significantly impact the time required for the data load process.Large volumes of data can take a longer time to load, which can extend the project timeline2.
C . The creation of external objects will bypass the need for legacy data migration: While creating external objects can help integrate external data sources with Salesforce, it doesn't necessarily bypass the need for data migration.The data still needs to be accessible and in a format that Salesforce can understand3.
D .The Amendments and Renewals process will be subject to customizations: While amendments and renewals are important aspects of the CPQ process, they are not directly related to the data migration process3.
Heather Rodriguez
8 days agoEric Lewis
10 days agoSharon Young
1 month agoGary Rivera
1 month agoMelissa Baker
2 months agoChristopher Johnson
2 months agoNancy Rogers
3 months agoMichelle Morgan
3 months agoAnthony White
4 months agoElizabeth Flores
5 months agoJoseph Johnson
4 months agoGary Campbell
4 months agoAngela Lee
4 months agoEdward Rodriguez
4 months agoBrenda Parker
4 months agoTruman
5 months agoJerlene
5 months agoMickie
6 months agoDalene
6 months agoLoreta
6 months agoMelissa
6 months agoMargarett
7 months agoTommy
7 months agoCatina
7 months agoCherri
7 months agoGenevieve
8 months agoFiliberto
8 months agoKanisha
8 months agoKathrine
8 months agoSkye
9 months agoDean
9 months agoJennie
9 months agoKendra
9 months agoOretha
10 months agoGail
10 months agoChan
10 months agoRyan
10 months agoMarsha
11 months agoGeorgene
11 months agoReta
11 months agoChristoper
11 months agoGayla
12 months agoSharee
1 year agoEdelmira
1 year agoGarry
1 year agoVanda
1 year agoChana
1 year agoCordie
1 year agoClay
2 years agoLeonor
2 years agoWava
2 years agoHayley
2 years agoPaulene
2 years agoLynelle
2 years agoNickolas
2 years agoWilletta
2 years agoJamal
2 years agoTerrilyn
2 years agoFranklyn
2 years agoJaleesa
2 years agoMarleen
2 years agoVirgie
2 years agoChristiane
2 years agoJules
2 years agoDierdre
2 years agoTyra
2 years agoLenna
2 years agoJeannetta
2 years agoElin
2 years agoBarrett
2 years agoStephen
2 years agoElly
2 years agoCarol
2 years agoRebecka
2 years agoFletcher
2 years agoJutta
2 years ago