CPQ object
How do CPQ bundles and product options map to Revenue Cloud?
SBQQ__ProductOption__c and SBQQ__ConfigurationAttribute__c define bundle structure in CPQ. Revenue Cloud's Product Configurator uses a different object model, and options and attributes do not map one to one.
How it fails
Bundles rebuilt by hand look right in a demo and differ in the edge cases — optional-of-optional, quantity rollup, attribute inheritance — which is where quoting errors come from.
What to do instead
Rebuild bundles in Product Configurator and re-point automation at the new objects.
In detail
Bundle configuration moves to Product Configurator with a different object model. Option and attribute references do not map one-to-one. Uses the CPQ product configurator API
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.