List Fields of the Pricing Table

 

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 more 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 Start of the navigation path System Next navigation step Services Next navigation step Table maintenance Next navigation step Extended table maintenance End of the navigation path and in the Table/view field, enter the view name V_TWLF. 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 more 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:

  • Vendor with vendor sub-assortment and vendor currency

  • Purchasing organization

  • Local currencies

  • Planned markups

  • Current final price with associated validity period

The contents of certain list fields are calculated by the program. These include:

  • Basic purchase price and purchase price (net/net)

    These prices are taken from the purchase price calculation schema and may be converted to a different sales unit and sales price unit (see Pricing Table).

  • Retail prices

    The final price is calculated from the sales price (gross) by rounding to a predefined price point.

  • Margin (net/gross)

    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:

  • Actual markup

  • Sales price (net/gross)

You can define the following list fields:

  • “Reduced from” price (ROTPR)

  • Cash price (MITPR)

  • Suggested price (VORPR)

  • Variable sales price (for exampleVKPO1)

  • Variable percentage fields (for example, PROZ1)

For more information, see Using the Condition Technique in Calculating and Determining Prices.

For information purposes, you can also use a reason for price change for each pricing item. Reasons for price changes are maintained in Customizing for Materials Management under Start of the navigation path Valuation and Account Assignment Next navigation step Valuation at Retail and Value-Based Inventory Management Next navigation step Reason for Price Change End of the navigation path.

Note Note

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.

End of the note.

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.

  • Condition type with application

    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).

  • Default currency indicator

    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.

  • Condition tables

    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, please note the following differences to storing the sales list fields:

    • Different purchase price calculation schemas can be used in determining purchase prices, depending on which vendor is found or which purchasing organization is responsible. There may also be different condition types for the basic purchase price. This is taken into account by the Condition type determination type indicator, for which there are two possible settings. One setting allows you to enter a condition type from the control data for storing the data, as you can with the other list fields. The other setting allows the condition type to be determined dynamically from the relevant purchase price calculation schema.

    • As well as an amount, each price also has a currency, a unit of measure and a price unit (see Pricing Table and Currencies). Different currencies and units of measure are generally significant for the basic purchase price. The condition record determination type takes this into account. The values for the pricing table (vendor currency, current sales unit and sales price unit) can be used for the condition record, as they are for other list fields. On the other hand, the settings for price determination (order price currency, purchase order price unit and order price unit) can also be used. You can display and if necessary, change these settings in the Purchasing detail screen of the pricing table.

    Note 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.

    End of the note.

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.

Example Example

  1. The sales price should not be saved if it is actually the same as the current sales price.

  2. Due to laws in some countries no sales prices can be created that are lower than the purchase price (net), unless a suitable reason for the price change is entered.

End of the example.

Note Note

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.

End of the note.