Automatic Update of Documents Based on Condition Changes (SAP Library

Automatic Update of Documents Based on Condition Changes

Use

Many applications create documents for which conditions are part of the document data. For example, with a purchase order the net prices for the document item in price determination are calculated from the purchase conditions. Price determination data is saved along with the document.

To update existing document data in the system based on condition changes special functions are available to you in the following application areas of SAP Retail:

Application Area	Function
Purchase order	Automatic Document Adjustment
Pricing	Pricing Worklist
POS Outbound	Change Message
Assortment list	Change Message
Order Optimizing	Investment buying determination of requirement

Purchase order:

If purchase conditions (purchase price, discount etc) change after a purchase order has been created, and if the new conditions are to apply, the system can change the conditions in all the documents concerned using automatic document adjustment.

For more information see Automatic Document Adjustment When Conditions Change.

Pricing

If certain conditions relating to pricing (for example, purchase conditions and transfer prices from distribution centers) change, it is advisable to check the effects on purchase prices already saved in the database. The system uses the pricing worklist function to determine all calculations affected by changes related to pricing conditions. When a new pricing worklist is created, new calculations are made, based on the changed conditions. There is no adjustment of already activated calculations (documents with the status C)

For more information, see Pricing Worklist.

Order optimizing/investment buying

Investment buying helps you determine future requirements resulting from purchase price increases that are to be covered by external procurement. Using the function Investment buying determination of requirement you can determine condition changes that are relevant to investment buying (price increases of net prices based on average purchase order quantities). With this data as a basis and using return on investment analysis, the system can calculate when and in what quantity it is worth procuring articles before the actual requirements date.

For more information see Investment Buying.

POS outbound and assortment lists

If purchase prices for articles and certain stores in the central SAP System have been changed, these changes must be distributed to the POS systems of the affected stores. This is achieved with the Change Message function, which analyses changes that have taken place in the system, prepares the changed data and sends it to the relevant POS systems.

For more information on POS outbound see Change Message and Procedure for POS Outbound Processing and for assortment lists see Splitting the Print Run from the IDoc Run .

Prerequisites

Change pointers for changed conditions are used as source data for document adjustment programs, however, in some applications document indexes are used as the source data for the relevant application.

For more information see Updating of Change Pointers and Document Indices.

Procedure

Updating document data based on condition changes, takes place in several steps to ensure that the related documents are adjusted effectively (performance).

There are usually three process steps for updating document data.

Updating change pointers

When conditions are changed, change pointers that indicate the type of change (amount, validity area) are automatically updated to table BDCP.

For more information see Updating of Change Pointers and Document Indices.

Note

Updating change pointers is not restricted to condition changes. This also takes place, for example, when master data and listing conditions are updated.

Creating a worklist for the corresponding application

When a worklist is created, change pointers for the changed conditions are prepared for the relevant application and updated to table WIND. It is recommended that you schedule periodic creation of worklists in the background. The period length should be kept quite short to avoid a considerable build up of change pointers. This could lead to a downturn in performance of the worklist creation program and subsequent programs. Ideally worklists should be created on a daily basis.

For more information see Worklist Generation.

As an alternative procedure you can allow direct creation of worklist entries. However, this procedure slows down the system. As an alternative procedure you can allow worklist entries to be created directly. However, this procedure slows down the system. See Direct Creation of Worklist Entries

Updating Document Data based on Worklists

The worklist provides the basis for adjusting document data in the relevant application. With this step, either condition data in existing documents is adjusted (for example, purchase order) or new documents with the changed data are created (for example, pricing documents and IDocs, with changed data in POS outbound).

For more information see Adjusting Document Data on the basis of Worklists.