Pricing Table (SAP Library - Strategic Sales)

Pricing Table

Use

The results of sales price calculations are displayed in the pricing table.

The pricing table is a list, the structure of which (list header, columns, and so on) is defined by the list group and the list variants. The rows in the pricing table are also known as pricing items. Further information is available under List Group and List Variants.

You can change the values in the fields of the pricing table that are ready for input, thus modifying the suggested value for the sales price.

Features

In the SAP system, prices are always made up of an amount and the parameters relating to it (currency, price unit and unit of measure (9.99 USD for 5 pieces, for example)). Within a calculation, the price unit and the unit of measure are the same for all the prices (sales price unit and sales unit). The prices can, however, have different currencies (see Currencies).

The pricing table contains two different types of field - those that are designed to be ready for input and those that are not. The fields that are not ready for input include, for example, master data fields such as the purchase order currency of the vendor and the planned markup. The fields that are ready for input are checked before the pricing table is displayed to see whether there are reasons why any of these fields should not be ready for input:

The sales-side list fields (Actual markup and Final price, for example) are not ready for input for articles with fixed prices and for those articles for which a different pricing reference article is maintained in the master data (variants of a generic article, for example). For further information, see Price Fixing and Pricing for Generic Articles and Variants).

The Basic purchase price field is only ready for input when the pricing parameters for the pricing item (vendor order currency, sales price unit and price unit) match the pricing parameters of the relevant condition record (order price currency, order price unit and purchase order price unit)

The Sales unit field is not ready for input for pricing levels below the distribution chain, as sales units are maintained at distribution chain level. This also applies to the Sales price unit field.

Setting the indicator SPU not variable in the sales view of the article master prevents different sales price units from being used. In this case, the Sales unit field in the pricing table is also not ready for input.

The Vendor and Purchasing organization fields are not ready for input in promotion follow-up processing, as this data is determined in promotions processing.

You can change those calculations that have been made on the basis of the system settings (calculation schema, planned markup, and so on) by overwriting the values in the fields that are ready for input. You can also change more than one field of an item at the same time. Inconsistent entries, for example, simultaneously changing the planned markup and the final price, are not allowed by the system.

Note

In addition to changing the values in the fields that are ready for entry in the pricing table, you can also make changes in the detail screens for Purchasing and Sales.

Once the data has been released, a new calculation is performed for each changed item. This calculation is dependent on the field that was changed. Items for which a calculation could not be performed or which have warning messages attached to them are listed in a log with a message to this effect.

You can display additional details, such as item details, vendor and article data, and so on, for every pricing item:

Changing values in fields that are ready for input

When changing values in fields that are ready for input, it is important to realize that other pricing items may also be affected by the changes.

Changes in the Basic purchase price field:

If you change the basic purchase price of an article in a pricing item, other pricing items containing this article may also change. Checks are necessary to prevent inconsistencies arising when the basic purchase price is saved. The rule here is that purchase prices in the pricing table must be the same if an identical condition record is generated when you save.

Note

The settings in Customizing for Pricing under Control data for pricing table and data backup form the basis of the check.

If the consistency check reveals that, for two or more pricing items, the condition table and the identification key of the condition record to be generated are identical, the unchanged items are adjusted to bring them into line with the changed items. Differing sales units are taken into account in the comparison.

If the purchase price is changed, either the actual markup or the sales price will be adjusted in the new calculation or the planned markup will be applied, depending on the settings you make under Pricing type in Customizing for Pricing.

Changes in the Vendor field:

If you change the vendor, a new basic purchase price is determined for the article and for the changed vendor, and the item is completely recalculated. The new calculation is given priority in the final comparison with the other pricing items. You should be aware that previous changes may be lost here.

Note

You can display the vendors determined in source of supply determination using the input help. Place the cursor on the vendor field and choose F4.

The basic purchase prices - and any changes to them - are buffered internally. If a calculation has already been performed for the vendor selected, the system finds the basic purchase price in the buffer and performs the new calculation using this price. A comparison with other items is then carried out using the basic purchase price from the buffer.

Note

The same procedure is followed when the purchasing organization is changed, or when the vendor and purchasing organization are changed simultaneously.

Changes in the Sales unit or Sales price unit field.

If the sales unit or sales price unit is changed, new calculations are performed for each of the affected items (distribution chain and related sites or price lists). This means that new purchase prices for articles or other vendors or purchasing organizations with different purchase prices can be determined. The new calculations are given priority in the final comparison with the other pricing items. This means that previous changes in the basic purchase price in the pricing items involved in the comparison may be lost.

Note

Changes in the Sales unit or Sales price unit field do not take simultaneous changes in other list fields into account.

Changes in the Actual markup field:

The purchase price remains unchanged when the actual markup is changed. The sales price is calculated on the basis of the purchase price with the new markup.

Changes in the Gross sales price field:

If you change the calculated sales price in the Gross SP field, the system will calculate your entry again, rounding it up or down to a price point defined in the price point group.

Changes in the Final price field:

If you change the entry in the Final price field, the system will not round to price points. This allows you to define sales prices that are not rounded to price points.

Note

You can use Edit ® Copy price field to adopt the price in the field on which your cursor is placed as the final price. The calculation is adjusted accordingly.

Changing the price determination date

A recalculation is always required after the price determination data has been changed, as the calculation-relevant parameters (purchasing conditions, planned markups, and so on) may have different values for the new date. You have the option of adopting values from particular list fields, despite the change in date.

Two-step price calculation

In two-step price calculations for distribution centers and the stores they supply, there is a row in the pricing table for the distribution center along with rows for its associated stores. Changes to data in a distribution center row will affect calculations for its related stores.