Oracle CPQ ABO — Implementation SKU Incorrectly Added to Existing Assets During Amendment

Summary:

Background & Architecture

Our implementation uses a SKU-based pricing model (as opposed to attribute-based pricing). Each component of a software offering is a separate, discrete SKU under a single CPQ model.

For example, Product A is broken into three SKUs:

• PROD-A-MON → Monthly Fee (Recurring)
• PROD-A-LIC → License Fee (One-Time)
• PROD-A-IMP → Implementation Fee (One-Time)

Original Purchase (6 Months Ago)

Customer X purchased Product A at a time when the business was not yet charging an Implementation Fee.

Their quote included only:

• ✅ PROD-A-MON — Monthly Fee → Included
• ✅ PROD-A-LIC — License Fee → Included
• ❌ PROD-A-IMP — Implementation Fee → NOT included (not charged at the time)

After order fulfillment, the CPQ Asset Store for Customer X holds