Pricing Worklist: Link when Transferring Conditions from Legacy (SAP Library

Pricing Worklist: Link when Transferring Conditions from Legacy Systems

Purpose

When transferring conditions for sales prices from legacy systems, it is necessary to create a link to the pricing worklist function to ensure that the system can adjust the sales prices accordingly when changes are made to pricing-relevant purchasing conditions. For further information on how the pricing worklist function works, see Pricing Worklist.

The link to the pricing worklist function is created by subsequently generating pricing documents with document indexes for the conditions for the sales prices that were transferred using IDocs. This takes place in two steps using a special worklist (table WIND, document type 11).

Prerequisites

The following settings must be maintained in Customizing for Pricing:

Under Subsequent Index Compilation for Sales Prices, you define which condition types with associated condition tables are to have worklist entries generated for them (Customizing table T6/1).
Under Control Data for Pricing Table and Data Backup, you need to maintain the Customizing settings for saving sales prices in the sales price calculation function so that they correspond to the transferred sales price conditions.
The settings necessary for the pricing worklist function must be maintained under Pricing Worklist.

All master data settings required for creating sales price calculations must be maintained.

Process Flow

Linking the pricing worklist function takes place in two steps:

Pricing worklist entries are automatically updated to document type 11 in the WIND table for the condition types entered in Customizing table T6/1 during IDoc inbound processing.
Pricing documents and document indexes (table S111, document type 10) are generated from this pricing worklist using report RWVKPIC2 (Subsequent Compilation of Document Indexes: Create Pricing Documents and Document Indexes).

This step does not generate any new conditions for sales prices. Instead, the condition record number of the original condition is transferred to the pricing item of the subsequently-generated pricing document. This creates the link between condition and pricing document. As with standard sales price calculation, the document indexes are created when the pricing document is generated.

Note

Report RWVKPIC2 automatically deletes those entries for which a pricing item could be generated in a pricing document from the pricing worklist. If an error is found during processing, however, the entry is not deleted. The following problems may cause errors:

Customizing settings for saving sales prices in the sales price calculation function do not correspond to the transferred sales price conditions.
No sales price calculation could be performed for the combination of articles and organizational level on which the calculation is based.
An error occurred when the calculation was being saved.

RWVKPIC2 creates a log showing any errors that occurred.

To process the worklist entries that contain errors, proceed as follows:

Use the log to help you correct the errors in the required sales price conditions.

You do not need to process errors in those sales price conditions that are not required, such as those that relate to articles or stores that are no longer used.

Start the report again.
Use report RWVKP03D to delete the remaining worklist containing the sales price conditions that are no longer required.

Results

Pricing documents with associated document indexes exist for the sales price conditions that were transferred from the legacy system, just as in a standard sales price calculation.

Note

You can use report RVKPIC1 (Subsequent Compilation of Document Indexes: Create Pricing Worklist) to generate a pricing worklist for the subsequent generation of pricing documents from the change pointers for condition changes (table BDCP). This could be necessary, for example, in cases where conditions are created for sales prices with standard condition maintenance (table VK11), or where sales price calculations were performed using sales types that erroneously did not provide for document generation.

Here, too, pricing worklist entries are updated only for those condition types that are entered in Customizing table T6/1. Further processing is carried out using report RWVKPIC2, as it is when transferring data from legacy systems.