Use
The columns in the pricing table are also known as list fields. The list group and list variant define which list fields are displayed.
You can modify the price calculation by changing the values in the fields that are ready for input.
For further information, see
Pricing Table.Features
Particular characteristics are defined for every list field. These characteristics are: output length, principle ready for input status, list field type and indicator for resetting the ready for input status for pricing articles or fixed price articles. To display the characteristics for the list fields, choose System ® Services ® Table maintenance ® Extended table maintenance and enter the view name V_TWLF in the Table/view field. Price fields, percentage fields and list fields without amounts are differentiated using the list field type. Price fields are also differentiated according to the currency in which they are displayed. For further information, see
Currencies.You can maintain descriptions for the list fields under Texts for List Fields in Customizing for Pricing. These are then displayed as column headings in the pricing table.
Determining field contents
The majority of the list fields have predefined set meanings. There are, however, also list fields for which the meaning is defined by Customizing settings.
The master data fields and certain conditions are among those fields that have a fixed meaning. These are determined by the program using the appropriate master records and condition records. These include, for example:
The contents of certain list fields are calculated by the program. These include:
These prices are taken from the purchase price calculation schema and may be converted to a different sales unit and sales price unit (see
The final price is calculated from the sales price (gross) by rounding to a predefined price point.
The margin is calculated from the sales price (net/gross) and the purchase price (net/net). The retail margin is calculated in the same way.
You can define the data transfer between the sales price calculation schema and the list fields for the user-definable list fields under Control Data for the Pricing Table and Data Backup in Customizing for Pricing. Some list fields also have a predefined meaning here. These include:
You can define the following list fields as you wish:
For more information, see
Using the Condition Technique in Calculating and Determining PricesFor information purposes you can also use a reason for price change for each pricing item. Reasons for price changes are maintained in Customizing under Materials Management ® Valuation and Account Assignment ® Valuation at Retail and Value-Based Inventory Management ® Reason for Price Change.
Due to the legally binding rules, in some countries you have to give a reason when the sales price is to be lower than the purchase price.
Storing field contents
You can store the values of the price and percentage fields in the system.
You can define the storage of values for each list field in the master conditions. You do this under Control Data for the Pricing Table and Data Backup in Customizing for Pricing.
You can define the condition type to which the value of a list field is to be stored. You can store values to main condition types or to supplementary conditions. In the case of supplementary condition types, the related main condition type is also stored at the same time. Permitted applications are M (Purchasing) and V (Sales).
You can use the default currency indicator to determine the currency that is to be used for the price fields when the condition record is stored.
For main condition types, you enter the condition table to which the prices for the different pricing levels (site, distribution chain, price list or site price list) are to be stored.
When defining the storing of the Basic purchase price list field, there are two differences to storing the sales list fields that you should note:
You maintain the settings for price activation in Pricing under Control Data for the Pricing Table and Data Backup in the same way as you make the settings for the promotion condition types. Control data for the basic purchase price is mandatory.
In sales price calculations, condition record storage is determined via the indicator for storing purchasing and sales condition records. If the indicator is set for purchasing, condition records are created for all the main condition types maintained for application M, and their related supplementary conditions. The same applies for the sales indicator and the main condition types for application V.
With the Business Add-In (BAdI) SPC_POSTING_CONTROL you can change the saved field contents for a pricing item, that have just been described and that are determined with Customizing, according to your particular requirements. By doing so, when you save a pricing position in the sales price calculation, you can actively influence the conditions to be created.
The BAdI can be compared with a filter. You can use the BAdI to prevent individual or all condition records from being updated.
To control the BAdI filter conditions you can have a simulated update displayed in the detail screen for a pricing item, which highlights which condition records are to be created. In this detail screen you can also control the effects of the BAdI manually. For example, you can create pricing records that are normally excluded under BAdI rules.