An Invoice Scheduler is set up with Target Date = January 15 and Bill Usage ChargesFalse.
Which setting will generate invoice lines?
Invoice Scheduler Settings:
Target Date = Jan 15
Bill Usage Charges = FALSE
This means:
The scheduler will generate invoice lines for Order Products only, not usage summaries.Thus the correct rule is:
A --- Order Products with Next Billing Date equal to or earlier than January 15
Why the other options are wrong:Option
Why Incorrect
B --- Usage Summaries
Ignored because Bill Usage Charges = False.
C --- Next Billing Date equal to or after
Billing only generates lines for dates <= Target Date.
D --- Next Charge Date
Not used by Invoice Scheduler.
Thus A is correct.
What are three key characteristics of an implementation partner leading arevenue cloud scoping session?
A Revenue Cloud consultant leading scoping must have:
A -- Excellent communication: Key for translating technical and business requirements.
B -- Planning/monitoring/review skills: Required to drive structured discovery workshops.
E -- Awareness of design pitfalls & mitigation: Ensures a scalable CPQ/Billing architecture.
Options C and D are irrelevant: competitor knowledge or sales quota experience are not key skills for scoping a CPQ/Billing project.
What is the most Scalable way to set the legal Entity on the Order Product and Order Product Consumption Schedule?
Requirement:
Set Legal Entity on Order Product and OP Consumption Schedule in a scalable way.
Runs before insert, so no second update transaction is needed.
Scalable (bulk-safe, low CPU, no recursion).
Modern Salesforce best practice for field population.
Works consistently across:
Order Products
Usage/Consumption Schedules
Why D. Before-Save Flow is correctWhy not the others?Option
Why Incorrect
A . Workflow Rule
Deprecated, not scalable, cannot run before-save.
B . Custom Setting
Storage mechanism, not automation logic.
C . QCP
Only affects Quote stage, not Order Products or Consumption Schedules AFTER order creation.
Thus **D is the correct, scalable, and recommended pattern.
A revenue cloud user story for a subscription-based company looking to replace their legacy system states ''as a pricing manager ,bulk discounts will include previously purchased quantities for pricing calculations on the quote in order to reward loyal customers.
what should be included in the design of this solution?
How does Hold Billing work?
Salesforce Billing's Hold Billing field on Order Product works exactly as follows:
When Hold Billing = Yes, Salesforce Billing does not generate invoice lines for that Order Product.
Once the user sets Hold Billing back to No, Billing:
Calculates the missed invoice periods
Creates catch-up invoice lines so billing is not lost
Correct Behavior (per Documentation)This means:
Invoicing is suspended
Catch-up invoice lines are created for the entire period Hold Billing was active
Thus, C is the correct and documented behavior.
Why the other answers are incorrectOption
Description
Why Incorrect
A
Prevents invoice document generation and emails
Misleading: the function specifically stops invoice line creation for the order product; it does not manage email notifications.
B
Hold Billing auto-resets on activation
False. Hold Billing is a manual field and does not auto-clear.
D
Only invoices after Hold Billing is set to No are created
Incorrect---Billing creates catch-up invoices for missed time.
Thus, C is completely aligned with Salesforce Billing behavior.
Currently there are no comments in this discussion, be the first to comment!
Hobert
20 days agoMable
27 days agoPeggie
1 month agoHaydee
1 month agoStephaine
2 months agoGeorgene
2 months agoYesenia
2 months agoHelaine
3 months agoCarey
3 months agoVal
3 months agoNorah
3 months agoJuan
4 months agoGlenn
4 months agoKristine
4 months agoPaola
4 months agoShaniqua
5 months agoMarquetta
5 months ago