Introducing Pricing Fundamentals in S/4HANA Cloud

Objective

After completing this lesson, you will be able to describe the core concepts and architecture of the pricing condition technique within SAP S/4HANA Cloud sales processes.

Introductory Video

Understanding Core Pricing Concepts and Architecture in SAP S/4HANA Cloud

Why Understanding Pricing is Crucial

A robust understanding of pricing fundamentals is paramount for SAP sales application consultants. Effective pricing configuration directly impacts a company's sales efficiency, customer satisfaction, and ultimately, its profitability. Misconfigured pricing can lead to revenue leakage, customer disputes, and compliance issues. For instance, an incorrectly applied discount due to a misunderstanding of condition types could result in significant undercharging over time. This lesson lays the groundwork for you to confidently explain these core mechanisms as they operate in SAP S/4HANA Cloud.

The Condition Technique and Its Components

At the heart of pricing in SAP (including S/4HANA Cloud) is the Condition Technique. This powerful and flexible mechanism determines how prices, discounts, surcharges, taxes, and freight are calculated in sales documents. It involves several key components working together:

  • Condition Types: These represent different kinds of prices, discounts, or surcharges used in your daily business transactions. For example, PPR0 often represents a base price (Default Gross Price), DM01 a material discount, YK07 a customer-specific discount (custom), and YBHD a freight charge (custom). Each condition type has specific control parameters defining its characteristics (e.g., whether it's a percentage or fixed amount, positive or negative).

  • Condition Tables: These are combinations of fields (keys) that define the criteria for a condition record. For example, a condition table for a customer-specific material price might include the fields 'Sales Organization', 'Distribution Channel', 'Customer', and 'Material'. SAP provides many standard tables, and you can create custom ones.

  • Access Sequences: An access sequence is a search strategy that the system uses to find valid condition records for a condition type. It specifies the sequence of condition tables the system should read until a valid record is found. For example, for a material price, an access sequence might first look for a customer-specific material price, then a price list category price for the material, and finally a general material price.

  • Pricing Procedures: The pricing procedure defines the sequence in which condition types are processed and calculated within a sales document (e.g., sales order). It specifies which condition types are included, their order, whether they are mandatory or statistical, and how they interact (e.g., sub-totals, calculation bases for percentages).

  • Condition Records: These are the actual data records that store the specific values for your condition types, based on the keys defined in the condition tables. For example, a condition record could state that for customer 'CUST01' and material 'MAT01', the price (condition type PPR0) is $95.00.

Diagram illustrating the relationship between Condition Types, Condition Tables, Access Sequences, and Pricing Procedures. A Pricing Procedure box contains multiple Condition Type steps. An arrow points from a Condition Type (e.g., PPR0) to an Access Sequence box. The Access Sequence box has numbered arrows pointing sequentially to different Condition Table boxes (e.g., Table 1: Cust/Mat, Table 2: Material). Each Condition Table box indicates it holds Condition Records.

During sales order processing, when you enter items, the system automatically triggers the pricing determination process. It uses the assigned pricing procedure for the sales document type and other criteria (like sales area, customer) to find relevant condition types. It then searches for valid condition records via access sequences and condition tables, and finally calculates the net price for each item and the total value of the order.

Key Architectural Aspects in S/4HANA Cloud

While the Condition Technique is a long-standing SAP concept, its implementation in SAP S/4HANA Cloud is characterized by certain architectural aspects:

  • Streamlined Data Models: SAP S/4HANA aims for simplified data models compared to older ERP systems. This can optimize performance and data handling for pricing processes, though the fundamental logic of the condition technique remains.

  • Fiori-First Approach: User interaction, including configuration for many areas and master data maintenance, primarily occurs through modern, role-based SAP Fiori applications, offering an improved user experience.

  • Defined Extensibility Points: S/4HANA Cloud offers structured ways to extend standard functionalities to meet specific business needs for pricing, ensuring upgrades are smoother.

  • Cloud-Specific Configuration Paths: Tools like SAP Central Business Configuration (CBC) (especially for public cloud initial setup) and the "Manage Your Solution" Fiori app (for ongoing adjustments and configuration activities/SSCUIs) are central to setting up and adapting the system.

The main types of extensibility available to tailor pricing include:

  • Key User Extensibility: This allows business experts or key users to make adaptations, such as adding custom fields to condition tables or reports, or modifying Fiori UIs with minimal to no coding.

  • Developer Extensibility (Embedded Steampunk): This enables developers to write custom ABAP code within a cloud-compliant framework for more complex logic or enhancements directly within the S/4HANA Cloud system.

  • Side-by-Side Extensibility: This involves building separate applications on the SAP Business Technology Platform (BTP) that integrate with S/4HANA Cloud pricing processes, often used for more significant custom applications or innovations.

Real-World Scenario: Illustrating Core Concepts

Consider a scenario: Your company, "GlobalTech Inc.", sells advanced routers. For a standard domestic customer purchasing the 'RouterX1' model, the base list price is $250. Currently, there's a special promotion offering a 10% discount for any order of 5 or more 'RouterX1' units. Additionally, a fixed shipping and handling fee of $15 applies to each order. How would these elements be represented by core pricing concepts?

  • The base list price of $250 would likely be stored in a Condition Record for a Condition Type like PPR0 (Price / Default Gross Price).

  • The 10% promotional discount (e.g., a quantity-based material discount using DM01) would be handled by another Condition Type with a corresponding Condition Record (potentially using quantity scales) specifying 10% for 'RouterX1' when the quantity is >= 5.

  • The $15 shipping and handling fee would be a separate Condition Type (e.g., YBHD - Freight (custom)) with a fixed value, also stored in a Condition Record.

All these condition types would be arranged in a specific sequence within a Pricing Procedure. When a sales order is created, the system uses this procedure and relevant Access Sequences (linked to the condition types) to find the applicable Condition Records and calculate the final price.

Summarizing Pricing Fundamentals

Duration: 5 minutes

Key Takeaways

  • The Condition Technique is the fundamental framework for pricing in SAP S/4HANA Cloud, determining how prices, discounts, surcharges, taxes, and freight are calculated.

  • Core components of this technique are Condition Types, Condition Tables, Access Sequences, Pricing Procedures, and Condition Records.

  • Condition Types represent various pricing elements (e.g., PPR0, DM01).

  • Condition Records store the actual values for these condition types.

  • SAP S/4HANA Cloud architecture features streamlined data models, a Fiori-first approach, and specific extensibility options (Key User, Developer, Side-by-Side).

  • Understanding these concepts is vital for effective pricing configuration and problem-solving.

Do This, Avoid This

Do This:

  • Clearly identify and understand the business requirements for pricing before attempting configuration.

  • Familiarize yourself with standard SAP-delivered condition types and pricing elements.

  • Think about how different pricing components interact within a pricing procedure.

  • Always consider the data that will be needed in condition records to support the defined condition types.

Avoid This:

  • Assuming all pricing elements are just simple price lookups; the Condition Technique is more complex.

  • Confusing Condition Types (the definition of a price/discount) with Condition Records (the actual value).

  • Overlooking the importance of Access Sequences in determining which condition record is found.

Quick Reference Idea

As a practical takeaway, consider creating a simple table or mind map for yourself that lists each core component of the Condition Technique (Condition Type, Condition Table, Access Sequence, Pricing Procedure, Condition Record) and write a one-sentence definition and its primary purpose. This can be a valuable aid for reinforcing your understanding.

Analyzing a Sales Deal for Pricing Components (Conceptual Exercise)

Exercise Objective

This exercise will help you apply your understanding of core pricing components by analyzing a sales scenario and identifying how different pricing elements would be represented using the Condition Technique, with detailed solution guidance provided.

Your company, "TechSolutions Ltd.", offers the following deal to a preferred customer, "Alpha Corp", for the product "TS-LaptopPro":

  • Standard list price for TS-LaptopPro: $1200 per unit.

  • Special discount for Alpha Corp on all laptop models: 5% off the list price.

  • Promotional discount on TS-LaptopPro this month: An additional $50 off per unit if purchasing more than 3 units of TS-LaptopPro in a single order.

  • Standard domestic shipping charge: $25 flat fee per order.

Prerequisites

Completion of the preceding concepts in lesson "Introducing Pricing Fundamentals in S/4HANA Cloud".

Familiarity with the definitions of Condition Types, Condition Records, Condition Tables, Access Sequences, and Pricing Procedures.

Steps

  1. From the scenario in the Context section, identify the four distinct pricing elements that need to be represented in the SAP system.

    Think about each value or adjustment that contributes to the final price: the starting price, any reductions, and any additions.

    1. The first pricing element is the 'Standard list price for TS-LaptopPro: $1200 per unit'. This is the base price for the product.

    2. The second pricing element is the 'Special discount for Alpha Corp on all laptop models: 5% off the list price'. This is a customer-specific percentage discount.

    3. The third pricing element is the 'Promotional discount on TS-LaptopPro this month: An additional $50 off per unit if purchasing more than 3 units of TS-LaptopPro in a single order'. This is a material-specific, customer-specific, quantity-based fixed amount discount.

    4. The fourth pricing element is the 'Standard domestic shipping charge: $25 flat fee per order'. This is a fixed freight or shipping surcharge.

  2. For each of the four pricing elements identified, suggest a suitable Condition Type that could be used in SAP, referencing the types discussed in the lesson (e.g., PPR0, DM01, YK07, YBHD) or describing its nature.

    Match the nature of the pricing element (price, specific discount type, charge) to the purpose of the condition types.

    1. For the 'Standard list price ($1200 per unit)', a condition type like PPR0 (Price / Default Gross Price) would be appropriate to represent the base price of the material.

    2. For the 'Special discount for Alpha Corp (5%)', a customer-specific discount condition type, similar to a custom type like YK07 (Customer Discount), would be used.

    3. For the 'Promotional discount on TS-LaptopPro ($50 off for >3 units for Alpha Corp)', a condition type like DM01 (Material Discount) could be configured with scales for quantity and specific to material, or a more specific custom promotional condition type could be created.

    4. For the 'Standard domestic shipping charge ($25 per order)', a freight condition type, similar to a custom type like YBHD (Freight), would be suitable.

  3. Describe the key information that Condition Records would need to hold for each suggested condition type to implement the scenario. Also, mention plausible key fields for the underlying Condition Tables.

    Condition records store the actual values and validity. Condition tables define the keys to find these records.

    1. For PPR0 (TS-LaptopPro price): The Condition Record would store the amount $1200 and the unit (e.g., USD). The Condition Table keys could be Sales Organization / Material Number (TS-LaptopPro).

    2. For YK07 (Alpha Corp discount): The Condition Record would store the percentage 5%. The Condition Table keys could be Sales Organization / Customer Number (Alpha Corp).

    3. For DM01 (Promotional discount): The Condition Record would store the amount $50 and specify a quantity scale (e.g., 'from 4 units' since it's 'more than 3'). The Condition Table keys could be Sales Organization / Material Number (TS-LaptopPro) / perhaps a Promotion ID.

    4. For YBHD (Shipping charge): The Condition Record would store the amount $25. The Condition Table keys could be based on Sales Organization / Shipping Conditions, or it might be a general order-level charge.

  4. Explain how an Access Sequence would be critical for the 'Promotional discount on TS-LaptopPro' to ensure it applies correctly, especially if Alpha Corp also receives their standard 5% customer discount on the same product.

    Think about how the system decides which discount to apply if multiple discounts could be relevant for the same item and customer.

    1. An Access Sequence assigned to the condition type for the promotional discount (e.g., DM01 or a custom type) dictates the order in which the system searches for valid condition records.

    2. To ensure the $50 promotional discount is considered appropriately alongside the 5% customer discount (YK07), their respective condition types would be placed in the Pricing Procedure. The order in the procedure and exclusion rules (if any) determine if both apply or if one overrides another.

    3. For finding the promotional discount itself, its Access Sequence might first search for a very specific record (e.g., Customer 'Alpha Corp' + Material 'TS-LaptopPro' + Promotion ID). If not found, it might search for a broader promotional record (e.g., Material 'TS-LaptopPro' + Promotion ID).

    4. The key is that access sequences find *a* valid record for a given condition type. How multiple *different* condition types (like a customer discount and a promotional discount) interact is primarily controlled by the Pricing Procedure (e.g., are they additive, or does one make the other inactive via exclusion logic?).

  5. Identify the single SAP pricing component that organizes all these different condition types in a defined sequence and controls their calculation to arrive at the final net price for Alpha Corp.

    Which component acts as the overall "calculation schema" or roadmap for pricing?

    1. The overarching component that organizes all relevant condition types (like PPR0, YK07, DM01, YBHD) in a specific calculation sequence is the Pricing Procedure.

    2. The Pricing Procedure determines the order of calculation, which conditions are mandatory or statistical, how percentage discounts are based, and where subtotals appear, ultimately leading to the final price for the customer.

Result

Upon completing this analysis by following the detailed substep solutions, you have applied your understanding of how different business requirements for pricing directly translate into the setup and interaction of fundamental SAP Condition Technique components: Condition Types, Condition Records, Condition Tables, Access Sequences, and Pricing Procedures.

(Note: The specific condition type codes (PPR0, DM01, etc.) are examples. In real projects, companies often create custom condition types (e.g., starting with Z) by copying and adapting standard ones to precisely meet their unique business needs. The logic of structuring these elements within the Condition Technique, however, remains consistent.)

Learning

SAP FacebookSAP YoutubeSAP LinkedIn