Purpose
This report is for retrospectively generatingpricing documents forconditions for sales prices
if no such document is available. This may, for example, be becausethe condition was created using the usual condition maintenance(transaction VK11). The starting point for the analysis used is formedby the condition table entries for the condition types for salesprices. Direct structuring of pricing documents from conditions
is therefore also discussed in describing this report, as opposed toretrospective structuring from the worklist (see reportsRWVKPIC1 and RWVKPIC2). Youspecify the condition type and the condition table for the analysis inthe selection screen.
The report assumes that the majority, or at least a large number ofconditions do not have a pricing document. In the event that only asmall number of condition records do not have a pricing document, usereport RWVKPIC3.

Features
To avoid an overflow in the main memory, you need to restrict thenumber of condition records to be processed in the report. You can setthis restriction in the "Restrictions" group box for organizationallevels and material numbers. A maximum limit of 30,000 condition tableentries is also set for condition record selection. This limit is notexceeded if you make insufficient restrictions. The number ofconditions selected is recorded in the report log. If this number is30,000, it is assumed that the restrictions set were insufficient. Thereport must then be repeated if necessary with a new, suitablerestriction. The last selected condition record, which was alsorecorded in the log, can be included for the new restriction, ascondition record selection takes place sorted by primary key.
The condition records selected are processed in blocks. You define theblock size using the parameter "number ofconditions in the processing block" in the selection screen.
The first stage of processing is the check as to whether a pricingdocument item exists for a condition. If this is not the case, one ormore pricing items are structured for the condition concerned inaccordance with the other control parameters (see following descriptionof indicators). A distinction is made here between pricing items forwhich only a pricing document needs to be created (group 1), and thosefor which a new condition needs to be created as well as a pricingdocument (group 2). Processing of the block finishes with the temporarystorage of the price calculations generated in one or two pricingdocuments.
It is often not necessary to create pricing documents for allconditions. This means that you can restrict the selection using theminimum validity period.
If the indicator "Carry out new calculationfor old conditions" is set, you can set the indicator "
No pricing document for old conditions
" at the same time so that a pricing document is not generated for"old" conditions either.
If the indicator "Include currencyconversion" is set, the system analyzes the conversion entries forprice calculations from organizational levels/material groups enteredin the Euro Workbench (see transaction WEWU).

Output
The system creates a log for the report run. This contains details onruntime.
The log also contains details on processing the conditions. These are:

• Number of conditions selected


• Number of conditions without pricing document


• Number of pricing items structured, for which only a pricing document
is to be created (group 1)

• Number of pricing items, for which a new condition record is to be
created, either by a new price calculation or by including currencyconversion (group 2)

• Number of pricing documents generated


• Number of pricing document items actually created for group 1


• Number of pricing document items actually created for group 2

The number of pricing document items actually created can be lower thanthe number of pricing items created, as errors can occur when carryingout price calculations for the pricing items strucured. These errorsare then stored in the error log for this report.