This business process shows you how to create and process a worklist comprising all those price calculations affected by changes to parameters relevant to pricing.

Parameters such as the basic purchase price or vendor discounts, which form the basis for the calculation of sales prices (that is retail prices or warehouse transfer prices), can change during the validity period of a sales price. To be able to update sales prices to reflect these changes, you must be able to find all the relevant price calculations.

This function enables you to compile a pricing worklist, which is a list of all price calculations that have been stored in the form of pricing documents and that are affected by the parameter changes, taking the validity period of each price calculation into account.

You can only use the pricing worklist function if a pricing document with a document index is created when you save a sales price.

2. Generate the pricing worklist from the worklist of price calculations you wish to update.

When a change is made to the master data concerned in the pricing worklist function (regular vendor indicator and vendor subrange in the info record, source of supply indicator in the article master), you no longer have to perform IMG activities 1 and 2. This is because when the master data change is saved, the pricing that is affected by this is determined at the same time and the appropriate entries are created in the pricing worklist.

3. Process the pricing worklist for specific articles and organizational units.
4. The new prices that are calculated are stored, as before, in pricing documents. You can change the results by setting certain parameters, such as the article markup rate, the margin, the sales price or the final price.
5. Save new sales prices that you are happy with and delete any price calculations that you do not want.

A pricing item in the pricing worklist is created in much the same way as a pricing item in the sales price calculation. The following 2 activities are all you need to do:

1. Perform pricing for purchasing based on the conditions that have been changed to determine the purchase price (net/net).
2. Calculate the markup based in the purchase price you determined in the first step.

Once you have completed the first step, the system checks whether a purchase price change has been made at all and whether it is necessary to make an entry in the pricing worklist. Such a situation normally arises when you create a purchase condition with a validity period in the future that overlaps with existing conditions. In the period up to the validity start date of the new conditions, there are no changes. The original condition is taken into consideration in the creation of worklist entries, however, due to the validity end date having been brought forward.

You can use the Business Add-In (BAdI) PWL_SP_DETERMINATION when a pricing worklist item is being created to control how the pricing worklist is structured so that it fits the needs of your company.

Method PROCESSCHECK_AND_SP_DETSEQ_SET, which is called after the first activity is completed, has 2 functions. Based on the purchase price determination for the new purchase conditions, you can also check - in addition to the standard check described – whether an entry needs to be made in the pricing workist at all. This way you can determine a lower (percentage) threshold value for a purchase price change of which no entry should fall short.

You can also determine with which sales price determination sequence the pricing in sales should be performed in the second activity. You can use sales price determination sequence 02 as a default if you do not want to change the sales price, for example, for articles with a lot of competition.

The second method, CALCULATION_ITEM_MODIFY, which is called after the second activity is complete, fulfills 2 functions. A check can also be run here to see whether an entry has to be made in the pricing worklist. The same price point may have been found in a markdown pricing despite purchase price conditions having changed, and this would make an entry unnecessary. You can also make changes to the pricing item in this method. This would therefore be useful in a scenario where, for example, only part of the increase in the purchase price for certain articles should be transferred to the customer via a sales price increase.