🔄 Mapping Pricing Conditions from SAP CPS to SAP ...

Yogananda

This blog explores how to map pricing conditions from CPS to CPQ, and how to pass them back to S/4HANA Sales Order, Solution Quotation, or Solution Order—ensuring consistency, accuracy, and automation.

Note : Ensure you have Document Pricing is enabled in your SAP CPQ tenant

Understand the difference between Stalesless Pricing vs Document Pricing from the ground level.

In the evolving SAP ecosystem, integrating pricing logic across systems like SAP CPS (Configuration & Pricing Services), SAP CPQ (Configure Price Quote), and S/4HANA is critical for delivering a seamless quote-to-cash process.

How to set Pricing Procedures to populate the Prices coming from CPS to CPQ and CPQ to backend S/4 HANA

How to map CPS Pricing Condition Types to the SAP CPQ Quote Line Items Fields

🧩 Why Map Pricing Conditions to SAP CPQ Line Items?

SAP CPQ acts as the central quoting engine in many enterprise sales processes. However, pricing logic often resides in Variant Pricing (VP) and Pricing Procedures defined in S/4HANA or CPS. Mapping these conditions to CPQ line items is essential because:

Consistency: Ensures pricing in CPQ matches backend systems.
Automation: Reduces manual intervention and errors.
Transparency: Sales reps see the same pricing logic as backend users.
Integration: Enables seamless handover of quotes to S/4HANA for order processing.

🔧Key Components Involved

CPS (Configuration & Pricing Services),– Hosts the pricing logic and variant configuration model (LO-VC and AVC)
SAP CPQ – Front-end for sales reps to configure, receives pricing from backend and quote, negotiate with customer.
S/4HANA – Backend system for order processing and fulfillment.
Pricing Procedure – Defines how pricing is calculated using condition types.
Condition Types – Represent discounts, surcharges, taxes, etc.
Variant Configuration (VC) – Drives product configuration and stateless pricing logic.
Standard Integrations - SAP provides standard integration packages to connect backend for Master data, and placing a order to S/4 HANA Public, Private Cloud and Onprem

🛠️ Steps to Map Pricing Conditions from CPS to CPQ

1. Define Pricing Conditions in S/4HANA

Create or reuse condition types (e.g., PR00, K004, RA01, RB00, EK01).
Assign them to a pricing procedure.
Ensure access sequences are defined for condition records.

2. Expose Pricing Logic via CPS

CPS acts as a middleware to expose S/4HANA pricing logic.
Use APIs or integration flows to expose condition types and pricing results.

3. Configure SAP CPQ to Consume CPS Pricing

Enable SAP Variant Configuration & Pricing (CPS) integration in CPQ.
Ensure you have Document Pricing enabled in your CPQ for interaction (interactive Sales Pricing)
Map CPS pricing outputs to CPQ line item fields via Setup - Pricing - Pricing Procedures.
For custom business requirement, Use scripting or custom logic to parse CPS response and populate CPQ QICF.

4. Map Condition Types to CPQ Line Items

Use Standard Quote Item fields or Create Quote Item custom fields in CPQ to hold condition values (e.g., base price, discounts, customer price, Rebates, Surcharges, Free Item.... etc).
Use mapping logic to assign CPS condition types to these fields.
Ensure the mapping supports multiple condition types per line item.

5. Pass Pricing Back to S/4HANA via Standard Integration Packages

When quote is accepted by customer, CPQ sends the configuration and pricing data back via Integration Iflow.
Iflow is mapped with all Pricing conditions set in CPQ ( Pricing Procedure Mapping)
Iflow will use standard APIs to create:
- Sales Orders
- Solution Quotation
- Solution Order
Ensure pricing conditions are passed as part of the payload or re-determined in S/4HANA using the same pricing procedure.

Below is the Integration mapped from SAP CPQ Quote Item fields to SAP S/4 HANA Public Cloud - Solution Order

Below is the Integration mapped from SAP CPQ Quote Item fields to SAP S/4 HANA Private Cloud - Solution Quotation

🔄Round-Trip Pricing Flow

✅Best Practices

Use consistent condition types across systems.
Test pricing logic in CPS thoroughly before exposing to CPQ.
Use version control for pricing procedures and VC models.
Log and monitor CPS calls for performance and accuracy.
Train sales teams on how pricing is derived in CPQ.

📌Conclusion

Mapping pricing conditions from CPS to CPQ and back to S/4HANA is a foundational step in achieving a unified and automated sales process. By aligning pricing logic across systems, businesses can ensure accuracy, reduce errors, and accelerate the quote-to-cash cycle.