Ansicht
Dokumentation
RWVKPIC3 - Subsequent Layout of Pricing Documents Directly from Conditions
ROGBILLS - Synchronize billing plans TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Purpose
This report is for retrospectively generating pricing documents for conditions for sales prices if there is no such document available. This may 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 only a few condition records without a pricing document are available in the condition table. For the unlikely event that the majority, or at least a large number, of the condition records do not have a pricing document, report RWVKPIC4 was created.
Integration
Prerequisites
Features
As condition tables can have a large number of entries, block processing had to be set up for analyzing the conditions and creating the pricing documents.
Conditions analysis takes place in blocks of 10,000 records. For this purpose, a cursor is set in the database and a corresponding block is selected.
For each condition, the system checks whether a pricing document item is available. 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). The checks and structuring of price calculations take place for the whole block. If the
number of condition records without a
pricing document entered in the selection screen is exceeded after processing a block, the system
generates (temporarily stores) one or two pricing documents depending on whether one or both groups
(1/2) contain entries. Due to block processing, the pricing documents can contain considerably more than the number of items entered.
When temporary storage takes place, the cursor for selection is closed. The analysis then continues at the point where it left off. If the report is interrupted in the meantime, you can also enter a starting point in the selection screen in the group box "Lower limit for program continuation". This can be taken from the log, which contains the first and last record of a block.
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, for example.
If the indicator "Carry out new price calculation for 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 one pricing document is to be created (group 1)
- Number of pricing items structured, 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 structured. These errors are then stored in the error log for this report.
Activities
Example
TXBHW - Original Tax Base Amount in Local Currency ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 5459 Date: 20240520 Time: 115427 sap01-206 ( 104 ms )
