SAP SD Pricing Procedure Configuration Step by Step

In SAP SD, what is a pricing procedure?

In SAP SD, a pricing procedure is a systematic set of rules that instructs the system on how to determine the ultimate cost of a good or service in a sales document. It enumerates and arranges in a predetermined order every pricing component that may be relevant to a transaction, including base price, discounts, surcharges, freight, taxes, and cost. SAP scans the pricing method line by line, applies each condition type sequentially, and determines the net value, tax amount, and profit margin when a user writes a sales order, quotation, contract, or billing document.

For regular domestic price, SAP standard pricing method, RVAA01, is utilized. The majority of businesses don't start from scratch when creating a pricing procedure in SAP. They duplicate RVAA01, give it a unique name that begins with Z, and alter it to conform to their business regulations. One of the most crucial abilities for any SAP SD consultant is knowing how a pricing procedure operates, and practically all SAP SD interview questions ask about it.

Pricing Procedure's Significance in SAP Sales and Distribution

One of the most delicate aspects of the sales process is pricing, which is automated, accurate, and consistent thanks to the pricing technique. Without it, users would have to manually compute prices, discounts, and taxes, which would result in mistakes, hold-ups, and consumer complaints.

A well-thought-out pricing strategy benefits the company in a number of ways. It guaranties that each client receives the right price in accordance with the terms that were agreed upon. Different prices are supported for various client groups, geographical areas, materials, order amounts, and validity periods. It lessens revenue leakage brought on by incorrect discounting or overlooked fees. Because the system instantly calculates prices as soon as the material and quantity are entered, it also expedites order processing.

Additionally, the pricing process regulates the flow of values into other modules. The figures determined here are posted to Financial Accounting for revenue, discounts, freight, and tax using account keys. Values are transferred to reporting tools for margin analysis and to Controlling for profitability analysis through statistical and subtotal settings. Because pricing serves as a conduit between the finance team and Sales and Distribution, errors in the process can have an impact on both financial statements and customer invoicing.

SAP SD Pricing Procedure Components

Each of the many interconnected parts that make up a pricing procedure has a distinct function. Condition tables, access sequences, condition types, condition records, and the pricing process itself are the primary constituents.

Condition tables specify the combination of fields, such as customer and material or price list and currency, for which a price or discount is recorded. The order in which the system searches those condition tables is specified by access sequences. Individual pricing components, such as a base price, a discount, a freight charge, or a tax, are represented by condition types. The actual values, such as a price of $1,000 per unit valid from a specific date, are stored in condition records. Lastly, the pricing process governs the behavior of each condition type and puts them in a logical computation sequence.

This is one way to think about it. The number is stored in the condition record; the condition table indicates where the number is kept; the access sequence indicates where the system should search first; the condition type indicates the type of number; and the pricing method instructs the system on when and how to utilize it.

SAP SD Pricing Condition Technique

SAP finds and applies pricing information automatically using the condition technique. SAP looks for the most pertinent condition record depending on the information in the document, including customer, material, plant, sales organization, price group, and date, rather than keeping a single set price against a material. Because various customers, nations, or time periods may pay different rates for the same resource, pricing is highly flexible.

Pricing is not the only application of the condition technique. Additionally, SAP uses it to determine output, accounts, partners, content, materials, and free items. Understanding the pricing condition technique can help you understand how many other SAP components obtain their data, which is why it is regarded as a fundamental idea in SAP SD .

Essential Components of the Condition Method

The four primary components of the condition technique function in a chain.

The condition table is the first component. It specifies the essential fields, such as Customer and Material or Material only, under which entries are recorded. One level of detail is represented by each table.

The access sequence is the second component. This search method presents condition tables in priority order, starting with the most particular and working down to the most broad. For instance, the system looks for a price for a client and material first, then a price for a price list and material, and lastly a general price for the material by itself. Unless the exclusive indicator is not set, it ceases searching as soon as it discovers a valid entry.

The condition type is the third component. It is connected to an access sequence and represents a pricing factor, such as a price, discount, or tax. Important settings like condition class, calculation type, plus or minus sign, and whether it can be manually altered at the header or item level are also carried by it.

The pricing procedure, which arranges condition types sequentially and regulates their processing, is the fourth component. When a sales document is prepared, the system scans the pricing method, searches the condition tables using its access sequence for each type of condition, and selects the value from the first condition record that matches.

SAP SD Pricing Procedure Determination

SAP determines which pricing procedure to apply in a particular document using pricing procedure determination. The sales organization, distribution channel, division, document pricing method, and client pricing procedure are the four values that the system combines.

Both the billing type and the sales document type, such as standard order OR, are allocated to the document pricing procedure. The customer pricing process is kept up to date under the sales area data in the customer master's billing tab. These two values, when combined with the sales area, indicate a single price process.

The system is unable to locate a procedure if the customer pricing procedure is absent from the customer master or if the combination has not been kept up to date in the determination table. The sales order has a pricing error as a result, and unless it is fixed, the item may not be processed further. Checking these assignments should be the first step in any SAP pricing troubleshooting because this is one of the most frequent problems seen in actual projects.

Requirements Prior to Setting Up a Pricing Process

A few things need to be ready before you begin the pricing procedure configuration. It is necessary to construct and allocate the organizational structure, which includes the company code, sales organization, distribution channel, division, and sales area. A customer price procedure should be completed on the sales area billing tab when creating customer master records. Price-related fields such as material pricing group and price reference material should be set when necessary, and material master records should be kept with the sales organization's views.

Additionally, you demand a certain pricing requirement from the company. This should specify which prices, discounts, surcharges, freight costs, and taxes are required, as well as the sequence in which they should be computed and whether or not each is done automatically. To transfer modifications to quality and production systems, you must submit a transport request and obtain authority for configuration in SPRO. Since the standard method RVAA01 already includes tested logic, it is highly advised to copy and alter it rather than starting from scratch.

Define Condition Tables in SAP SD

Step 1: Making condition tables is the first stage in the configuration process. Which fields are merged to determine a price is determined by a condition table. A table containing client and Material, for instance, allows a price to be saved for a particular client purchasing a particular material, whereas a database with just Material indicates that a single price is applicable to that material for all customers.

Transaction code V/03 or the SPRO menu path under Sales and Distribution, Basic Functions, Pricing, Pricing Control, Define Condition Tables are two ways to establish condition tables. Numbers in custom condition tables must range from 501 to 999. Create the table after choosing the fields from the field catalog. The database table beneath the generated table is created by the system. Because too many custom tables can slow down pricing, you should only develop tables when the conventional ones don't satisfy your needs.

Define Access Sequences in SAP SD

Step 2: Define Access Sequences. Determining the access sequence is the second stage. The system is instructed by an access sequence which condition tables to look through and in what order. It can be kept up to date using the SPRO pricing menu's Define Access Sequences option or transaction code V/07. Z should be the first letter in custom access sequences.

After creating the access sequence, add the condition tables with access numbers, such 10, 20, and 30, to the Accesses section. Put the most general table last and the most specialized table first. Examine the Exclusive indicator for each access. If it is set, once a record is located in that table, the system stops looking. Additionally, keep any necessary field mapping and examine the Fields section, where you can see how each field in the table derives its value from the document. PR00 is the base price's standard access sequence.

Define Condition Types in SAP SD

Step 3: Define Condition Types. Determining condition kinds is the third stage. One pricing component, such as a base price, customer discount, freight, or tax, is referred to as a condition type. Use the SPRO path Define Condition Types under Pricing Control or transaction code V/06. It is advisable to copy an existing condition type, such as K007 for a discount or PR00 for a price, and start the new one with Z.

The condition class, such as A for discount or surcharge, B for prices, and D for taxes, is a crucial setting on the condition type. The method of calculation, whether percentage, fixed amount, quantity dependent, or weight, determines how the value is determined. Conditions like freight and tax are categorized under the condition category. Whether the value is a discount, a surcharge, or both is determined by the plus or minus indicator. The condition type and the search method from step 2 are connected by the access sequence field. The ability to manually modify the condition at the header or item level, whether it is a group condition, and whether scales, like lower prices for higher quantities, are permitted are further crucial features.

Specify the Pricing Procedure in SAP SD

Step 4: Specify the Pricing Process. Determining the price process itself is the fourth step. Use the SPRO menu Maintain Pricing Procedures under Pricing Control or transaction code V/08. First, transfer the standard procedure RVAA01 to a different name, such ZVAA01. Next, open the new procedure's control data and add your condition types as new lines.

Step number, counter, condition type, and control fields like From, To, Manual, Mandatory, Statistical, Print, Subtotal, Requirement, Alternative Calculation Type, Alternative Condition Base Value, and Account Key are entered for each line. Later in this blog, these control fields are described in more detail. Put the lines in the proper sequence for the computation. For instance, base price comes first, followed by discounts, a net value subtotal, freight, taxes, and finally the total value. Because each line may depend on the numbers above it, the sequence is important.

Define Pricing Procedure Determination in SAP SD

Step 5: Define Pricing Procedure Determination. Determining the pricing procedure is the fifth stage, which helps the system choose when to apply your new technique. Use the SPRO path Pricing Procedure Determination under Pricing Control or the transaction code OVKK.

First, confirm the existence of the document pricing procedure and the customer price method. These are straightforward one-digit codes, such as A for ordinary sales orders, 1 for domestic customers, and 2 for export customers. Next, enter the new pricing procedure, such as ZVAA01, against the combination of the sales organization, distribution channel, division, document pricing procedure, and client pricing procedure in the determination table. For header-level pricing checks, the condition type field can also be used to suggest a default condition type, such PR00.

Assign the Sales Document Type to the Pricing Procedure

Step 6: Assign the Sales Document Type to the Pricing Procedure. As this is part of the determination key, the sixth step is to ensure that the appropriate document pricing procedure is tied to your sales document type and billing type. Open the sales document type in transaction VOV8, such as OR, and make sure the right code, such A, is entered in the Document Pricing Procedure box. Use transaction VOFA on the billing type, like F2, for billing documents.

On the customer's end, launch the customer master in XD02 or VD02, select the Sales Area Data, Billing Documents tab, and input the Pricing Procedure code, for example 1 for domestic, in the Customer Pricing Procedure field. The price procedure determination will be unsuccessful without this value. Data migration teams should ensure that every submitted client has this information filled out.

Create Condition Records in SAP SD

Step 7: Make Condition Records. The exact pricing values are kept in condition records. Without them, the pricing process is merely a framework, and the system will indicate that no price could be obtained. Create condition records using transaction VK11, modify them using transaction VK12, and show them using transaction VK13. In certain situations, you can also use the pricing menu for condition records by condition type and VK31 for mass maintenance.

In VK11, select the key combination that lists the condition tables from the access sequence after entering the condition type, such as PR00. The amount, currency, unit of measurement, and validity dates should be entered after the important values, such as customer and material. Select the scales option and enter quantity breaks and their pricing if scales are required. Preserve the document. One of the most common causes of a missing price is an expired record, therefore always make sure that the validity dates include the date of the sales document.

Test the Pricing Procedure in a Sales Order

Step 8: Evaluate a Sales Order's Pricing Process. Testing is the last phase. Using VA01, create a sales order with a material that has a valid condition record and a test customer that follows the proper customer price method. To view how each condition type was determined, open the item conditions screen after entering the sales area, order type, material, and quantity.

Verify that the base price is appropriately selected, that discounts and surcharges are applied in the proper sequence, that subtotals display the anticipated amounts, and that tax is computed using the appropriate base. Use the conditions screen's analysis feature to see which access was checked step-by-step and why a condition record was or was not identified. Before transferring the configuration to the production system, test various situations, including different clients, quantities with scales, manual condition adjustments, canceled documents, and billing documents.

Crucial T-Codes for Setting Up Pricing Procedures in SAP SD

It saves a lot of time to know the primary transaction codes for support and setup tasks. Condition tables are created with V/03, access sequences are defined with V/07, condition types are defined with V/06, and pricing procedures are maintained using V/08. VOV8 is utilized for sales document kinds, VOFA for billing types, and OVKK for pricing procedure determination. Condition records are created, modified, and displayed using VK11, VK12, and VK13. Sales orders are created, modified, and displayed using VA01, VA02, and VA03, where the pricing outcome can be examined. SPRO with the SD Pricing Control menu provides access to all of the implementation guide's features, whereas VOK0 opens the pricing configuration menu with many of these features in one location.

T-Code	Purpose
V/03	Create condition tables
V/07	Define access sequences
V/06	Define condition types
V/08	Maintain pricing procedures
OVKK	Pricing procedure determination
VOV8	Sales document types
VOFA	Billing types
VK11 / VK12 / VK13	Create, change, and display condition records
VA01 / VA02 / VA03	Create, change, and display sales orders
VOK0	Pricing configuration menu

Typical SAP SD Pricing Conditions

Understanding the most prevalent standard condition types that SAP offers is beneficial for both configuration and interviews. The basic base price is PR00, which is typically required. K007 is a customer discount, K020 is a price group discount, K004 is a material discount, and K005 is a customer and material-specific discount. RB00 is an absolute discount, while RA00 is a percentage of gross. Both the header percentage discount (HA00) and the header absolute discount (HB00) are applied to the entire document. KF00 is a weight or quantity-based freight premium. While India employs the TAXINN technique with GST condition types JOIG for integrated GST, JOCG for central GST, and JOSG for state GST, MWST is the typical output tax condition in many other nations. The internal cost from the material master, or VPRS, is utilized to calculate margin. It has no effect on the client price and is statistical in nature.

Explanation of Pricing Procedure Control Fields

Control fields determine how each line in the SAP pricing procedure operates. Step and Counter permit many condition types at a time and specify the line's order. The pricing element is named Condition Type. Telling the system which earlier lines to use as the foundation for percentage computations is done by defining the reference range from and to. The base is the prior subtotal if From is blank.

Manual indicates that the condition must be entered by the user and is not automatically determined. The term "mandatory" refers to a requirement that must be met; if it is not, the document displays an error. Statistical indicates that, unlike cost, the value is just displayed for informational purposes and does not alter the net value. Print determines if the line appears on output forms.

Subtotal saves the line's value in a subtotal field, such A or B, so it can be utilized later on in the computation, like in a net value line or as the tax base. A regular number called a requirement determines whether the line should be processed at all, for instance, only if the customer is in a specific nation. Custom logic can be implemented by routines using Alternative Calculation Type and Alternative Condition Base Value. Accruals is utilized for provisions like rebate accruals, whereas Account Key connects the condition to a G/L account for revenue posting.

SAP SD Pricing Process Example

This is a basic illustration of the ZVAA01 bespoke pricing process for a domestic client.

Step 10 is the base price of $1,000 per unit under condition type PR00. It is required, and its gross value subtotal is set to A.

Step 20, condition type K007, offers a five percent customer discount. It offers a 50% discount per unit and bases its calculation on the value from step 10.

Step 30, condition type RB00, is a 20-unit absolute discount that can be manually entered by the sales team if necessary.

Step 40. The price, which is 930 per unit after all discounts, is displayed using subtotal B.

Step 50, condition type KF00, is quantity-based freight of 30 per unit.

Step 70, condition types JOCG and JOSG or JOIG, applies GST (for instance, 18 percent) to the net value plus freight, resulting in 172.80 per item.

Step 90, condition type VPRS, displays the material cost as a statistical line for margin analysis, while Step 80 displays the final total value of 1,132.80 per unit.

When a customer orders 100 pieces, the final invoice value is 1,13,280. This is the sum of 1,00,000 for the base price, less 5,000 for the customer discount, less 2,000 for the manual discount, plus 3,000 for freight and 18% GST on 96,000, or 17,280. This demonstrates how each line builds upon the one before it and how altering the From and To parameters or the line order might alter the outcome.

Step	Condition Type	Description	Value per Unit
10	PR00	Base price (subtotal A)	1,000
20	K007	Customer discount (5%)	-50
30	RB00	Absolute discount (manual)	-20
40	Subtotal B	Price after discounts	930
50	KF00	Freight	30
70	JOCG / JOSG / JOIG	GST (18%)	172.80
80	Total	Final total value	1,132.80
90	VPRS	Material cost (statistical)	Margin analysis only