Assigning Pricing Procedures in Sales Transactions

Objective

After completing this lesson, you will be able to apply pricing procedure determination rules to ensure the automatic assignment of the correct procedure based on sales criteria in SAP S/4HANA Cloud.

Introductory Video

Understanding Pricing Procedure Determination

The Importance of Correct Procedure Assignment

In the previous lesson, you learned how to build a Pricing Procedure—the detailed calculation recipe for your prices, discounts, and surcharges. However, a procedure is ineffective until the system knows when to use it. Pricing Procedure Determination is the crucial configuration step that creates this link. It defines the rules that allow SAP S/4HANA Cloud to automatically select the correct pricing procedure for a specific sales transaction.

Mastering this assignment logic is essential for ensuring that standard domestic sales, export sales, service transactions, or any other business scenario each get their own unique and correct pricing treatment. Incorrect determination can lead to the wrong prices being calculated, causing significant business issues.

The Key Criteria for Determination

The system determines which pricing procedure to use based on a specific combination of three key elements from the sales document:

  1. Sales Area: This is the combination of Sales Organization, Distribution Channel, and Division. It represents the specific organizational context of the sale.
  2. Document Pricing Procedure Indicator: A two-character indicator assigned to the sales document type (e.g., standard order, returns, quotation). This allows you to use different pricing procedures for different kinds of transactions (e.g., a simpler procedure for free-of-charge deliveries).
  3. Customer Pricing Procedure Indicator: A two-character indicator assigned to the customer master (Business Partner) record. This allows you to use different pricing procedures for different types of customers (e.g., a standard customer versus an intercompany partner or a retail partner).

The system combines these three elements to find a matching entry in the determination table, which then points to the specific pricing procedure to be used.

A conceptual diagram showing three icons: a building labeled Sales Area, a document icon labeled Document Pricing Procedure, and a person icon labeled Customer Pricing Procedure. Three arrows point from these icons to a central box labeled Pricing Procedure ZDOM01, illustrating that the combination of these three elements determines which procedure is selected.

Defining the Determination Indicators

The two character indicators for Document and Customer pricing procedures are defined and assigned in separate configuration and master data areas:

  • Document Pricing Procedure (Doc. PP): This indicator is assigned within the configuration of a Sales Document Type. For example, for the standard order type 'OR', you might assign the indicator 'A' for 'Standard'.

A conceptual mockup of a configuration screen for a Sales Document Type (e.g., 'OR' - Standard Order). It shows various fields, with one field labeled Doc. pricing procedure highlighted, containing the value 'A'.
  • Customer Pricing Procedure (Cust. PP): This indicator is maintained in the Customer Master / Business Partner record, specifically in the sales area data. For example, a standard domestic customer might be assigned indicator '1' for 'Standard'.

A conceptual mockup of a Business Partner (Customer) master data screen, specifically the Sales and Distribution tab. It shows various fields, with one field labeled Customer pricing procedure highlighted, containing the value '01'.

The values used for these indicators (e.g., 'A', '01') are first defined in separate configuration steps, giving them descriptions like 'Standard', 'Intercompany', etc., before being assigned.

The Determination Rule and Process

The actual assignment happens in a specific configuration activity (SSCUI) within SAP Central Business Configuration (CBC) or the "Implementation Activities" app. Here, you define the determination rule in a table that typically has five key columns that point to the pricing procedure.

The determination logic is as follows:

  1. When a sales document is created, the system identifies the Sales Area, the Document Pricing Procedure indicator from the sales document type, and the Customer Pricing Procedure indicator from the customer master.
  2. It then reads the Pricing Procedure Determination table, searching for an entry that matches this exact combination of values.
  3. Once a match is found, the system uses the pricing procedure specified in that entry for the sales document.
  4. If no match is found, the system cannot price the document and will issue an error.
A conceptual mockup of a configuration table with columns: SlsOrg, DChl, Dv, DocPP, CustPP, and Pricing Procedure. An example row is highlighted showing values '1000', '10', '00', 'A', '1' pointing to pricing procedure 'ZDOM01'.

This configuration is the final link that activates your pricing procedures in live sales transactions.

Summarizing Pricing Procedure Determination

Key Takeaways for Pricing Procedure Determination

  • Pricing procedure determination links a sales transaction to the correct pricing procedure (calculation schema).
  • The determination is based on a combination of three key criteria: Sales Area, Document Pricing Procedure Indicator, and Customer Pricing Procedure Indicator.
  • The Document Pricing Procedure indicator is set in the configuration of the Sales Document Type.
  • The Customer Pricing Procedure indicator is set in the sales area data of the Customer Master (Business Partner).
  • The assignment rule is maintained in a specific configuration activity, typically managed via SAP Central Business Configuration (CBC) for projects.
  • If the system cannot find a matching entry in the determination table for the given criteria, pricing will fail.

Best Practices and Troubleshooting Tips

  • Use Clear Indicators: When defining your two-character indicators for documents and customers, use memorable characters and maintain clear descriptions (e.g., A = Standard, B = Intercompany, C = Web Order).

  • Document Your Logic: Keep documentation that explains why certain combinations of Sales Area, DocPP, and CustPP lead to a specific procedure.

  • Troubleshooting "Procedure Not Found": If you encounter the error "Pricing procedure could not be determined," this is the configuration to check. Verify the Sales Area of the document, the DocPP on the sales document type, and the CustPP on the customer, and ensure a valid entry exists for that combination in the determination table.

  • Test Different Combinations: When testing, create sales orders with different document types and customers to ensure they correctly pick up their intended pricing procedures.

Applying Pricing Procedure Determination Logic (Conceptual Exercise)

Your company uses three different pricing procedures in Sales Organization 1000, Distribution Channel 10, Division 00 (Sales Area 1000/10/00):

  • ZDOM01 for standard domestic sales.

  • ZEXP01 for standard export sales to international customers.

  • ZSERV1 for service-related sales orders.

The determination table in the system is configured as follows:

  • Sales Area: 1000/10/00 | Doc PP: A | Cust PP: 1 --> Procedure: ZDOM01

  • Sales Area: 1000/10/00 | Doc PP: A | Cust PP: 2 --> Procedure: ZEXP01

  • Sales Area: 1000/10/00 | Doc PP: B | Cust PP: 1 --> Procedure: ZSERV1

Prerequisites

You have completed Concept 1: "Understanding Pricing Procedure Determination" and are familiar with the three key criteria used for determination.

You understand where the Document Pricing Procedure (DocPP) and Customer Pricing Procedure (CustPP) indicators are maintained.

Steps

  1. A user creates a sales order using document type OR (Standard Order). The configuration for this sales document type has its Document Pricing Procedure indicator set to 'A'. Where in the system is this indicator maintained?

    Think about the source of the Document Pricing Procedure indicator.

    1. The Document Pricing Procedure indicator ('A' in this case) is maintained in the detailed configuration settings for the Sales Document Type (which is 'OR' in this scenario).

    2. This configuration is typically done via a specific SSCUI accessed through SAP Central Business Configuration (CBC) or the "Implementation Activities" app.

  2. The sales order is for customer CUST-123. In this customer's master data (Business Partner), their Customer Pricing Procedure indicator is set to '2' (for 'International Customer'). Where in the Business Partner master record would you typically find this setting?

    Consider which part of the customer master data is relevant for sales transactions.

    1. The Customer Pricing Procedure indicator ('2' in this case) is maintained in the Business Partner master record for customer CUST-123.

    2. Specifically, you would find it in the data related to their Sales Area (under the "Sales and Distribution" tab or equivalent BP Role), as this indicator can be different for the same customer in different sales areas.

  3. Given that the sales order is being created in Sales Area 1000/10/00, has a Document Pricing Procedure of 'A', and is for a customer with a Customer Pricing Procedure of '2', which pricing procedure will the system determine based on the configuration table in the Context?

    Look at the mock determination table provided in the context and find the line that matches all three criteria.

    1. The system will search the determination table for an entry matching: Sales Area = 1000/10/00, DocPP = 'A', CustPP = '2'.

    2. Based on the provided table, the second entry matches these criteria: "Sales Area: 1000/10/00 | Doc PP: A | Cust PP: 2 --> Procedure: ZEXP01".

    3. Therefore, the system will determine and use pricing procedure ZEXP01 for this sales order.

  4. What would happen if another sales order was created in the same Sales Area (1000/10/00) with the same document type (DocPP = 'A'), but for a new customer whose master data is missing a value for the Customer Pricing Procedure indicator?

    Consider what happens when the system cannot find a complete, matching entry in the determination table.

    1. If the Customer Pricing Procedure indicator is missing (blank) for the new customer, the system would try to find a determination rule matching: Sales Area = 1000/10/00, DocPP = 'A', CustPP = (blank).

    2. Since there is no such entry defined in the provided configuration table, the system would be unable to find a valid pricing procedure.

    3. This would result in a system error during sales order processing, typically with a message like "Pricing procedure could not be determined", and the user would be unable to fully process the document until the master data or configuration is corrected.

Result

By completing this exercise, you have applied the logic of pricing procedure determination. You have successfully identified the sources of the determination criteria (Sales Document Type and Customer Master) and used a determination table to find the correct pricing procedure for a given sales scenario. You have also analyzed what happens when determination fails.

This demonstrates your understanding of how to apply the rules that link a specific business transaction to the correct calculation schema in SAP S/4HANA Cloud.