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
Process Flow
Linking the pricing worklist function takes place in two steps:
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.
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:
RWVKPIC2 creates a log showing any errors that occurred.
To process the worklist entries that contain errors, proceed as follows:
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.
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.
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.