Variance Calculation for Product Cost Collectors with Quantity-based Valuation This function in Product Cost Controlling for Discrete Industries enables you to determine variances for product cost collectors with quantity-based valuation. This application is only available for product cost collectors manufactured on the basis of an iPPE quantity structure.
Variance calculation does the following:
Shows the variance between target costs and control costs
Calculates the difference between actual costs and work in process in the Industry Business Solution Discrete Industries allocated to an object on the one hand, and the credit from goods receipt postings (total variance) on the other
Determines the scrap variances by valuating the unplanned scrap quantities at target cost
Determines production variances
Explains how the variances originated and assigns the variances to different variance categories depending on the cause
The system updates the variances for each object by cost element or cost element and origin. You can apply the knowledge acquired through the variance calculation function to control your costs.

You can also analyze your data for specific days, weeks, or months in the
Business Information Warehouse
using the
Daily Production Costs
function.
You can use the
Schedule Manager
to facilitate the period-end closing process.
If you use the
Schedule Manager
with the flow definition, you can correct the errors in the objects using the multilevel worklist.
User-defined error management enables you to indirectly influence the program flow of variance calculation.
Make sure you have done the following:
Make sure you have taken account of the special requirements for product cost collectors with quantity-based valuation and the general prerequisites for product cost controlling with sales-order-related and make-to-stock production with reporting points .
If you want to include activities in costing and confirmation , you must link iPPE to Overhead Cost Controlling.
In make-to-stock environments, preliminary costing for the product cost collector on the basis of iPPE is required.
The product cost collector for which you want determine variances must have a valid variance key.Note that the
Scrap
indicator in the variance key is ignored. That is, scrap variances are always reported as long as scrap is activated in the valuation variant. In addition, the setting for
Write line items
is ignored – line items are never saved.
In Customizing, you can specify the variance key as a default value for each plant. The system then transfers the variance key into the master records of the plant materials that you create. If you then create a production order or product cost collector for a material, the system transfers the variance key into the master record of the product cost collector.
For cost-critical materials, the
Material
origin
indicator in the costing view of the material master record must be set, or origin groups must be used. The system can then determine which materials and which primary cost element caused the variances. If you have already created material master records in which
Material origin
is
not selected, you can select this indicator for the affected materials automatically using program RKHKMAT0. To do this, choose
Tools
→
ABAP Workbench
→
Development
→
ABAP Editor.
The product cost collector for which you want to determine variances must have a variance key.
Before you can start variance calculation, you must carry out the following steps in Customizing for
Product Cost Controlling
in
Cost Object Controlling
under
Product Cost by Period
→
Period-End Closing ® Variance Calculation:
Define Variance Keys The
Scrap
indicator for unplanned scrap in variance calculation is ignored.
Define Default Variance Keys for Plants
Define Variance Variants:
If you want the scrap variances to be shown in the target cost version to which the variance variant is assigned and the scrap variances to be deducted from the actual costs, select
Scrap variance
.
Valuation variant for WIP and scrap:

In the standard system, you specify in the
valuation variant for WIP and scrap
whether you want to determine the target costs for valuation of scrap variances on the basis of the following:
Preliminary cost estimate for the product cost collector or production order
Alternative material cost estimate
Current valid standard cost estimate
These settings are ignored for product cost collectors with quantity-based valuationThat is,
the
valuation variant for WIP and scrap
in the s
ettings for the target cost versions is not interpreted by the system.
When actual costs are posted, the target quantities for the component withdrawals and activities are specified in accordance with the posted assembly quantities. When the target costs are calculated, these component and activity quantities are valuated directly using the valuation variant specified in the
costing variant planned
of the product cost collector. No existing cost estimate is used in the valuation.Consequently, the valuation variant for WIP and scrap plays no role in quantity-based valuation.
Define target cost version: Note that in this scenario, the assignment of the target cost version affects variance calculation in a different way than the settings of the target cost version in the SAP standard system. Furthermore, the scope of functions in target cost calculation varies depending on whether you are in a make-to-order or make-to-stock production environment. You can find more information on target cost calculation for product cost collectors with quantity-based valuation under
Types of Variance Calculation
below.
The indicators
mixed-price variances
and
minor differences
are ignored in this scenario.
Take organizational steps to ensure that WIP is always calculated before the variances.
Product cost collectors are only included in variance calculation when the status of the order is not one of the following:
DLFL (deletion flag). You should assign status DLFL to product cost collectors that are no longer needed.
DLT (deleted)
You can withdraw the deletion flag after it has been set, for example if follow-up costs are incurred for the order. The deletion indicator, however, cannot be withdrawn.
The variance calculation function for the Industry Business Solution
Discrete Industries
determines the planned quantities from an APO planned order or from the Rapid Planning Matrix. You can specify the corresponding actual quantities in APO when you enter the confirmation. The planned and actual quantities are then transferred into the DI system. Separate recording of variances in the DI system enables variances to be assigned directly to a product cost collector without reference to a production order. This provides detailed variance information in Controlling, where the variances are valuated and analyzed with the variance calculation function.
The variance calculation function always compares the control costs with the target costs. The system calculates target costs and control costs in accordance with the type of variance calculation and the production approach (mass production based on sales orders or make-to-stock production). In this scenario, you always perform periodic variance calculation in which the target costs of the period are compared with the control costs of the period.
In the Industry Business Solution
Discrete Industries
you can calculate variances in different ways depending on the production approach. With all variance types with the reference figure "actuals" (that is, in the standard system with target cost versions 0, 1, or 3) the control costs are the actual costs from which the work in process and scrap variances have been deducted. For the scrap variances to be deducted from the actual costs, the
scrap variances
indicator in the valuation variant must be selected.
The
input quantity variances and
resource-usage variances are based on the variances against the target quantities of components and activities that were recorded during the confirmations. Like the WIP quantities, these variance quantities are valuated using the valuation variant specified in the
costing variant planned
of the affected product cost collector and are reported as input quantity variances.
The
scrap variances are based on the confirmed actual scrap quantities. Scrap is valuated on the basis of the target quantities for components and activities that correspond to the confirmed assembly scrap quantities. Like the WIP quantities, these target quantities are valuated using the valuation variant specified in the
costing variant planned
of the product cost collector. The scrap variances are calculated as the difference between the actual scrap value and the planned scrap value. The planned scrap is entered in the iPPE access of the production version at assembly level. The target quantities for components and activities corresponding to the planned scrap are updated in the system at the time of the goods receipt and are used to calculate the planned scrap. The system also reports input price variances, remaining input variances, output price variances, lot size variances, and remaining variances.
For more information, refer to Assembly Scrap in iPPE .

Variances are only reported if a variance key has been entered in the product cost collector. The Customizing settings for the variance key are irrelevant. No line items are updated. Only the Customizing settings of the variance version are interpreted. Variances are valuated on the basis of the valuation variant specified in the product cost collector under
costing variant planned
.
The Daily Production Costs function enables you to determine the production costs for product cost collectors used in the APO confirmation independently of the normal period-end closing process.For example, you can analyze data for specific days, weeks, or months.
In make-to-order production, variances can only be calculated in target cost version 0 because there is only one possible comparison object:
Comparison object against which the variances are calculated: |
Comparison object to be chosen in the settings for the target cost version: |
|---|---|
Target quantities in accordance with the
|
Current standard cost estimate |
In mass production on the basis of sales orders with quantity-based valuation, the target cost versions supplied by SAP have the following settings and effects:
Target cost version |
Reference object |
Object of comparison in the target cost version |
Object of comparison against which the variances are calculated |
|---|---|---|---|
0 |
Actual costs |
Current standard cost estimate |
Target quantities in accordance with RPM in APO |
1 |
Actual costs |
Plan costs/preliminary cost estimate |
Not available |
3 |
Actual costs |
Alternative material cost estimate |
Not available |

In each variance calculation run, no more than one target cost version of those selected can contain an alternative material cost estimate.
The following objects of comparison are relevant for variance calculation with quantity-based valuation:
Comparison object against which the variances are calculated: |
Comparison object to be chosen in the settings for the target cost version: |
|---|---|
Current standard cost estimate |
Current standard cost estimate |
Target quantities in accordance with APO planned order |
Plan costs/preliminary cost estimate |
Preliminary cost estimate of product cost collector |
Alternative material cost estimate |
The target cost versions supplied by SAP have the following settings and effects in make-to-stock production with quantity-based valuation:
Target cost version |
Reference object |
Object of comparison in the target cost version |
Object of comparison against which the variances are calculated |
|---|---|---|---|
0 |
Actual costs |
Current standard cost estimate |
Current standard cost estimate |
1 |
Actual costs |
Planned costs calculated in the preliminary cost estimate of the product cost collector |
Target quantities in accordance with APO planned order |
3 |
Actual costs |
Alternative material cost estimate |
Preliminary cost estimate of product cost collector |

Variances cannot be calculated in target cost version 2.
In each variance calculation run, no more than one target cost version of those selected can contain an alternative material cost estimate. In order-related production, if you want variances to be calculated in the corresponding target cost version you must create a preliminary cost estimate for the product cost collector on the basis of iPPE data.
The system compares the control costs with the calculated target costs and assigns the variances to variance categories in the following sequence:
Scrap Variances
Input price variances: Note that in this scenario, the setting
Define Primary Data for Input Price Variances
is not interpreted by the system.
Resource-usage variances
Input quantity variances
Remaining input variances
Output price variances
Lot size variances
Remaining variances
You can display the messages that were issued during the variance calculation process with
Extras
→
Messages.
You can also:
Assign particular messages to areas of responsibility. This enables you to structure the log by area of responsibility.
Change the message type of particular messages (such as information, warning, error). This enables you to control whether the message appears in the log and whether the order number appears in the worklist when the message is issued.
You can use parallel processing to reduce the runtime of the
variance calculation
process.
If you run the
variance calculation
process outside the
Schedule Manager
, enter a server group for background processing.
If you run the
variance calculation
process using the
Schedule Manager
, set the
Parallel processing
indicator in the selection screen of the program when you create the job variant. An entry field then appears in which you enter the server group.
You can view and edit the objects with errors that were processed with the individual functions. You use the multilevel worklist for this purpose. The multilevel worklist enables you to edit the faulty objects of an individual processing step (that is, a single function) or of an entire processing step sequence.
A prerequisite for using the multilevel worklist is that you are using the
Schedule Manager
in conjunction with a flow definition.