If conditions (such as purchase prices or discounts) change after a purchase order has been created and if the new conditions are to apply, the system can change the conditions automatically in all the documents concerned using the Automatic Document Adjustment function.

Certain conditions (such as purchase prices or DC transfer prices) are relevant to price calculations. When these conditions change, it makes sense to check if these changes affect any sales prices already on the database. With the help of the pricing worklist function, the system can find all sales price calculations affected by the condition changes. When a pricing worklist is created, the system calculates new sales prices on the basis of the changed conditions. Sales price calculations that have already been activated (documents with status C) are not changed.

Investment Buying helps you decide whether you could best cover future requirements by purchasing articles now that are due to increase in price. The function for determining investment buying requirements enables you to find all condition changes relevant to investment buying (increase in the net price for average order quantities). Using the data available, the system works out whether the return on investment is high enough for it to be worth your while procuring articles before they are actually required. If it is, it also calculates the best point in time at which to order and how much.

When the retail price for an article is changed in the SAP Retail system for particular stores, this change has to be transferred to the POS systems of the stores concerned. You can do this by using the Change Message function. This analyzes the changes made in the system, then prepares the changed data, and transfers it to the POS systems.

When conditions change, change pointers are automatically updated in table BDCP to indicate the type of change (amount, validity period and so on).

When a worklist is generated, the system prepares the change pointers for the changed conditions for the relevant application and updates them in table WIND. SAP recommends that you schedule worklist generation as a background job to be run periodically. The time between two jobs should not be too long to avoid a large number of change pointers being generated. Too many change pointers could impair the performance of the program being executed and of subsequent programs. If possible, the worklist should be generated daily.

Documents data in the application is changed on the basis of the worklist. In this step, the system either changes the condition data in existing documents (for example, purchase orders) or generates new documents with the changed data (for example, pricing documents in the pricing worklist, IDocs with changed data for POS outbound processing).