CPQ object
What happens to SBQQ__Subscription__c records in Revenue Cloud?
CPQ's subscription, amendment and renewal mechanics are structurally different from Revenue Cloud's asset-based lifecycle. Logic that assumes CPQ subscription records — amendment opportunities, renewal opportunities, co-termination maths — does not translate directly.
How it fails
Renewals and amendments are the processes nobody exercises on day one, so this tends to surface weeks after go-live, against real contracts.
What to do instead
Re-derive against Asset Lifecycle Management; treat existing amendment code as requirements, not implementation.
In detail
Amendment and renewal mechanics differ structurally in Revenue Cloud's asset-based lifecycle. Logic assuming CPQ subscription records will not translate directly. Touches CPQ amendment/renewal objects
Find every occurrence in your own org
A scan reads your Apex, triggers and Flows and lists exactly where this appears — class by class, with the line it was found on.
Read-only, two OAuth scopes, no package to install, and no sales call.