Configuration Work Group Conference – CWG 2014 – Day2 – Oct7 2014

I would like to start the day with a big Shout out to Lawrence Matusek on his 50th Birthday. Happy Birthday LM

As usual this year CWG is all about CPQ, SSC, Hybris apart from other sessions where customers presented their VC journey or best practices in VC. Below are some important points from the sessions I attended


CPQ – Configuring the Accelerator UI for product configuration in Hybris 5.3 WCMS

Product could be imported from ERP. Model has to be IPC compliant

  • Hybris pricing functionality based on sap master data (like PR00)
  • Orders can be configured. Page is generated dynamically
  • SSC Pricing engine is used for pricing
  • Product Cockpit – used to maintain product and catalog data
  • Consists of ID,Description etc for product – this is not replicated from ERP. This is to show stuff from a UI perspective
  • Identifier links VC
  • Any changes has to be sync to reflect change

Configuring the page – Hybris web content management cockpit

  • Page is divided into different sections. Each section is filled with content
  • Ex: Navigation bar has catalog stuff
  • Add to cart from config page, information is passed to ERP
  • ERP manages cart in Hybris
  • ATP, date confirmation and complete price calculation is done in ERP and returned from ERP including tax
  • Can also be used for non configurable parts. It performs ATP for non configurable parts and promises dates based on schedule lines in sap
  • It also does sap credit checks
  • SAP error messages are not shown. Own error and information messages can be defines as needed

Pricing Options

  • Asynchronous – Use Hybris Pricing based on sap master data in cart and hybris.
  • Synchronous – Using ERP pricing using specialized API which does just pricing. Its not using any API. Its developed as part of EHP7. downside is ERP going down
  • Changes to orders created in HYBRIS in SAP will be reflected back in Hybris
  • Order history shows all orders. Once changed in SAP…cannot be changed in Hybris
  • Classification data can be replicated from ERP to Hybris Data Models
  • Desc is not restricted to 30 chars in Hybris

Solution Sales Configuration

  • Bottom up config with n dynamic relationships
  • Where a solution has lot of relations
  • Example is configuring a data center
  • SSC – Runtime component and Modeling Tool
  • Runtime – supports sales process
  • Modeling – Design rules to support runtime
  • Syntax Extensions
  •  Prioritized defaults – A if possible else B else C else D
  • Import content from CSV files
  • External – Runtime access to sap database tables
  • SSC_ is reserved. Cannot be used by customers
  • Multiple KB export
  • Optional validate on export
  • Trace functionality

SAP Solution Sales and Billing

  • BRIM – Billing and Revenue Innovation Management – SSB is offered under BRIM
  • Subscriptions, metered usage. Ex: Usage based billing services
  • Usage Metering and Usage rating. Transfering usage to SD
  • SAP flexible solution billing – available independently. Its useful to do all billing relevant items in one invoice
  • This can provide flexibility of getting billing info from external systems
  • Standard integration of SAP CC (convergent charging) for rating and charging into ERP convergent invoicing
  • Master Data: Invoice Groups – define rule work flow Y/N, reference values – value is sorting criteria…sales order and service order needs it to bring them together
  • Invoice package – done via batch jobs – package parks all billing relevant items until the invoice date is reached
  • Solution Sales: CRM System
  • Master Agreement for customer which has all products. Can have partner functions who can enter the bundle
  • Create a solution quotation. Solution quotations can be created from scratch. No need for master contracts. This has one time services, recurring services etc.
  • External reference has to be entered in solution quotation. Also possibility to assign WBS elements as accounting objects
  • Usage Based Business – need a unique identifier has to be assigned to contract
  • Then system generates sale orders, contracts and service orders based on products in bundle
  • Once service is done, Debit Memo request Is sent to ERP and items are in staging area
  • Preview of Invoice is possible, modify the way it is presented
  • Systems: SAP CRM (solution design and quotation management), SAP Convergant Charging (Usage measuring and rating), ERP Billing and Settlement with EHP7

IPC -Set of engines to provide configuration, pricing and Tax determination

  • IPC just requires Business Suite
  • Supports multi-level, variant tables, class nodes
  • IPC engines are written in Java but reside on the ABAP application server
  • IPC executes dependencies several times faster than VC
  • Offers a flexible web based UI. Better user guidance
  • Dependency Profiling – Convenient tool to record dependency execution times. Can be turned on/off any time during configuration session
  • Difference between ERP VC and IPC is Knowledge Base
  • KB is a collection of master data relevant for configuration. Need to be generated prior to runtime usage. KB can be easily distributed to other systems
  • PMEVC can be used to generate runtime version
  • XCM – Extended Configuration Management
  • Activate VMC (to have IPC in sap)
  • Check VMC running