Ansicht
Dokumentation
RWVKPIC4 - Subsequent Layout of Pricing Documents Directly from Conditions
BAL_S_LOG - Application Log: Log header data PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Purpose
This report is for retrospectively generating pricing documents for conditions for sales prices if no such document is available. This may, for example, be because the condition was created using the usual condition maintenance (transaction VK11). The starting point for the analysis used is formed by the condition table entries for the condition types for sales prices. Direct structuring of pricing documents from conditionsis therefore also discussed in describing this report, as opposed to retrospective structuring from the worklist (see reports RWVKPIC1 and RWVKPIC2). You specify the condition type and the condition table for the analysis in the selection screen.
The report assumes that the majority, or at least a large number of conditions do not have a pricing document. In the event that only a small number of condition records do not have a pricing document, use report RWVKPIC3.
Integration
Prerequisites
Features
To avoid an overflow in the main memory, you need to restrict the number of condition records to be processed in the report. You can set this restriction in the "Restrictions" group box for organizational levels and material numbers. A maximum limit of 30,000 condition table entries is also set for condition record selection. This limit is not exceeded if you make insufficient restrictions. The number of conditions selected is recorded in the report log. If this number is 30,000, it is assumed that the restrictions set were insufficient. The report must then be repeated if necessary with a new, suitable restriction. The last selected condition record, which was also recorded in the log, can be included for the new restriction, as condition record selection takes place sorted by primary key.
The condition records selected are processed in blocks. You define the block size using the parameter "
number of conditions in the processing block" in the selection screen.
The first stage of processing is the check as to whether a pricing document item exists for a condition.
If this is not the case, one or more pricing items are structured for the condition concerned in accordance
with the other control parameters (see following description of indicators). A distinction is made here
between pricing items for which only a pricing document needs to be created (group 1), and those for
which a new condition needs to be created as well as a pricing document (group 2). Processing of the block finishes with the temporary storage of the price calculations generated in one or two pricing documents.
It is often not necessary to create pricing documents for all conditions. This means that you can restrict the selection using the minimum validity period.
If the indicator "Carry out new calculation for 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 currency conversion" is set, the system analyzes the conversion entries for price calculations from organizational levels/material groups entered in the Euro Workbench (see transaction WEWU).
Selection
Standard Variants
Output
The system creates a log for the report run. This contains details on runtime.
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 currency conversion (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 than the number of pricing items created, as errors can occur when carrying out price calculations for the pricing items strucured. These errors are then stored in the error log for this report.
Activities
Example
CPI1466 during Backup BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 5360 Date: 20240520 Time: 134155 sap01-206 ( 107 ms )
