Several different functions in Pricing are based on the condition technique. Sales prices, for example, are stored as condition records in the system, and calculations are performed using sales price calculation schemas.

According to how they are used, the following types of calculation schemas can be differentiated between in Pricing:

• Purchase price calculation schemas
• Sales price calculation schemas
• Calculation schemas for price determination

Purchase price calculation schemas are defined in Customizing for Purchasing; sales price calculation schemas and calculation schemas for determining prices are defined in Customizing for Sales and Distribution.

When you are setting up calculation schemas for Pricing, you should take the following special features into account.

The purchase price calculation schema is used to calculate the purchase price for merchandise procured from an external supplier.

• The purchase price calculation schema assigned to a pricing item is determined using the schema group of the vendor and the schema group of the purchasing organization.

• In the purchasing calculation schema only condition records with the indicator relevant to pricing are taken into account.

• The scale that applies to the purchase price (net/net) in the purchasing calculation schema must be flagged with the subtotal S. The condition value in this level is converted to the sales price unit and sales price unit of measure and entered in list field EKPNN. The pricing currency of the pricing position and the currency of the price determination correspond with one another.

• The first main condition type found that represents a price (condition class B) is used for the basic purchase price displayed in the pricing table.

Sales price determination is performed in the sales price calculation function using a sales price calculation schema. The schema is a set of rules for calculating the sales price from the purchase price. The price determination information, such as planned markup (planned margin) or competitor prices, required for this calculation is read from the database using the main conditions in the schema.

You should bear the following points in mind when calculating sales prices:

• The sales price calculation schema must be structured according to a markup calculation.
• Data is transported from the sales price calculation schema to the pricing table. You can control this transport separately. As certain list fields in the pricing table have a fixed meaning, for example, Net sales price field (VKPNE), you should make sure that when data is transported to these fields the relevant parameters in the sales price calculation schema are taken into account.
• When the sales price is changed, for example in the list field Sales price (gross) (VKPBR), the actual markup is adjusted in stages, in line with the changed sales price. A reverse calculation is never performed.

The procedures involved in sales price calculations are regulated by the following Customizing steps:

• Data transfer between the sales price calculation schema and the pricing table is defined in Customizing for Pricing under Control Data for Pricing Table and Data Backup. A condition type or a subtotal for the sales price calculation schema must be entered in the list fields of the pricing table.

• The sales price calculation schema assigned to a pricing item is defined by the associated pricing type. Pricing types are maintained in Customizing for Pricing and are assigned to a distribution chain or a price list (with currency) in a second step.

The supplied calculation schemas WWS001 to WWS004, together with the control parameters, can be used as examples for constructing sales price calculation schemas and for data transport.

• The starting point is the purchase price (net/net) that was determined with the purchase price determination function and that has now been transported to the schema using condition type EKNN, (see graphic, arrow 1).
• The actual markup in the pricing table is linked to condition types AUFS and AUFX using subtotal 2. These markups relate to the purchase price in the calculation schema.
• The sales price (net) and the sales price (gross) are linked to subtotals 5 and 6 respectively. The gross price is calculated by adding taxes (condition type MWST) to the net price. The prices are transported from the schema to list field VKPNE or VKPBR (see graphic, arrows 2 and 3).

With settings for rounding to price points, the sales price from the specified schema is rounded (see graphic, arrow 4) and the price calculation is adjusted in line with the rounded final price. When you save this the value of list field ENDPR is written to the database as a condition (see graphic, arrow 5).

Many applications in the Retail area use a calculation schema for price determination to read saved sales prices or further sales conditions from the database. The pricing overview in Pricing and the POS interface - outbound are just two of these.

In two-step price calculation, a schema of this type is used in the same way as a purchase price calculation schema to determine the transfer price for a distribution center. This means that determining the basic purchase price and the purchase price is performed in the same way it would be using the purchase price calculation schema. The purchase price (net/net) is to be flagged in the same way using subtotal S. The results of this price determination are displayed in the Purchasing detail screen.

You define calculation schemas for price determination in Customizing for Sales and Distribution.

• The calculation schema for price determination is defined using the sales area, the document schema and the customer schema.

• On the basis of the sales order, the system first accesses the master data of the anonymous customer (as site customer) determined from the POS inbound profile for aggregated sales. The POS inbound profile is entered in the site master of the site or of the reference site.
• If an inbound profile is not maintained, or does not contain an anonymous customer, the system uses the customer data of the site or reference site itself in the second step.
• If the sales area data of the customer determined in this way is maintained, the system uses the customer schema entered there. If no sales area data is maintained for this customer, the initial value for the customer schema is used to determine the schema.
• If no entry has been made in Customizing for the key determined in this way, the system uses sample calculation schemas supplied with the standard system: VKP001 for store distribution chains, VKP002 for distribution center distribution chains and VKP003 for wholesale distribution chains.

• In the calculation schema for price determination, the sales price (or promotion price) must have the same condition type (or promotion condition type) as the sales prices calculated using sales price calculations (or the promotion prices activated in promotion processing).