Products in CPQ – BRIM S/4 Solution Quotation Integration

[Urmil_Apte]

CPQ public cloud and S/4 Solution Quotation private cloud is very popular integration amongst SAP customers as it offers best of these both worlds enabling the customer’s sales team to create efficient quotes at a faster pace, negotiate the price and seal the deal.

The Master Data – Products and Business Partners in this integration plays a key role and it is imperative to understand the same for efficient process management. Let us look at the Products in this post.

1. Leading system for Product creation in this integration is S/4 HANA, where integration is enabled with SAP Cloud Integration.
2. Type of Products supported in this integration are:
   1. Sales
   2. Subscription
   3. Service Contract
3. Product details that arrive to SAP CPQ from S/4:
   1. Name
   2. System ID
   3. Product Type
   4. Part Number
   5. Unit of Measure
   6. Category
   7. OrderItemType (property with value Sales or Subscription or Service Contract) which can’t be changed via the API or in the application.
4. SAP Variant Configuration and Pricing is used as a default mechanism for configuring and pricing
   products in SAP CPQ.
5. ImportMaterialsFromERP SOAP API is used to import the products in CPQ
6. Set-Up Required in CPQ
   1. Product Types
   2. Product Categories
   3. Billing Cycle
   4. Service Profile
   5. Response Profile
   6. Billing Date
   7. Settlement Period
7. Change Process scenarios are only supported for Subscription
8. Products supported
   1. Simple Products             
   2. Configurable
   3. Multi-level/Parent-Child – Bundle, Non-Bundle, CPQ Bundle. BOM Explosion is required.

Products	General Item Category Group Code	Transactional Document Created on S/4 side	Children	Additional Info
Bundle Multi-level Product	Bundle (like a dummy product)	Bundle Parent will not have any follow-on document, as they are like dummy products. The children will have follow-on documents as per their type.	Sales(simple and configurable) Service Contract simple and configurable), Subscription( multi-level),	Mixed Product Type of parent child combination is allowed.e.g. Sales product can have sales, service contract and subscription product as child products
Non- Bundle Multi-level Product	Multi AVC		Sales, Subscription, Service Contract	Same type of products should be used as parent -child. e.g. Sales parent can have only sales as child products.

 

Transition Journey for Different Products

Type of Product	Additional Attributes Added during replication to CPQ	Transactional Document Created on S/4 side
Sales	None	Solution Quotation -> Sales Order
Subscription	·       Contract Duration ·       Billing Cycle Contract Extension Period	Solution Quotation -> Subscription Contract
Service Contract	·       Service Profile ·       Response Profile ·       Billing date ·       Service Contract Duration Settlement period	Solution Quotation -> Service Contracts

Value Mapping for SAP CPQ Integration with SAP Billing and Revenue Innovation Management

This key mapping for product is Bi-Directional(BD).

Agency	Identifier	Mapping	Agency	Identifier
CPQ	UnitofMeasure	BD	S/4	QuantityUnit
CPQ	OrderItemType	BD	S/4	QuotationItemOrderItemType
CPQ	ConditionCurrency	BD	S/4	ConditionCurrency
CPQ	BundleItemCategory	BD	S/4	Bundle
S/4	IndustrialSectorCode	BD	CPQ	PrimaryIndustry
S/4	ProductHierarchyInternalID	BD	CPQ	ProductCategoryUSEnglish
S/4	ProductTypeCode	BD	CPQ	OrderItemType
S/4	TimeZoneCode	BD	CPQ	TimeZone
S/4	CountryCode	BD	CPQ	Country
S/4	FormOfAddressCode	BD	CPQ	FormOfAddress
S/4	ProductTypeCode_ItemCategoryGroupCode	BD	CPQ	OrderItemType
S/4	RegionCode	BD	CPQ	State

Once Set-up is done in all systems – CPQ, CPI and  S/4 HANA, the master data creation can start and products can be replicated from S/4HANA to CPQ. Examples in SAP Help portal can be referred to for further reference on Master Data Creation.