Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

CPQ BOM Mapping Overview

203 views

Published on

Walpole Partnership present their "CPQ Bill Of Material (BOM) Mapping And System Configuration Overview" slides.

Please get in contact if you would like to talk to one of our CPQ experts about starting your BOM Mapping journey.

Published in: Technology
  • Be the first to comment

CPQ BOM Mapping Overview

  1. 1. CPQ Bill Of Material (BOM) Mapping And System Configuration
  2. 2. © Walpole Partnership Ltd. 2014 Contents • BOM Definition • Configuration and Commerce in the CPQ Process • BOM Mapping Overview • BOM Mapping Typical Use Case • BOM Tree Example • Oracle CPQ Cloud BOM Technical Scope • BOM Mapping Benefits Overview
  3. 3. © Walpole Partnership Ltd. 2014 BOM Definition  A BOM is a list of raw materials, sub-assemblies, intermediate assemblies, sub- components, parts and the quantities of each needed to manufacture an end product  Hierarchical and Multi-level  Sales BOM vs Production BOM  Typically ERP = Master
  4. 4. Configuration and Commerce in the CPQ Process Salesperson, distributor, or customer (user) 3. Prepare and Propose (Document Designer) 1. Select and Configure (Configuration) 2. Price and Quote (Commerce) Configuration Commerce
  5. 5. © Walpole Partnership Ltd. 2014 BOM Mapping Overview
  6. 6. © Walpole Partnership Ltd. 2014 BOM Mapping Typical Use Case  CPQ Administrators have different options to activate and map the relevant BOM Mapping tables applied to a typical use case:
  7. 7. © Walpole Partnership Ltd. 2014 BOM Tree Example
  8. 8. © Walpole Partnership Ltd. 2014
  9. 9. © Walpole Partnership Ltd. 2014 Oracle CPQ Cloud BOM Technical Scope  CPQ can hold up to five BOM Mapping platform tables:
  10. 10. © Walpole Partnership Ltd. 2014 BOM Mapping Benefits Overview  Simplifies the UI with less user interaction  Protects the system performance by triggering controlled rules  Makes it easy for changes in ERP to be reflected in CPQ  Reduces dual maintenance  Ensure data integrity and consistency  Minimizes implementation time  Supports stand alone data driven Sales BOM

×