Skip to end of metadata
Go to start of metadata


General Information

  • As soon as the order has status DLV or TECO variances can be calculated
  • Status DLV (delivered) can be found in table AFPO-LTRMI
  • Status TECO (technically completed) can be found in table AUFK-IDAT2


  • Order related product costing
    FUL settlement rule
    Released cost estimate has to be valid at delivery / goods receipt

  • Periodical product costing
    PER settlement rule
    Released cost estimate has to be valid the last day of the period


Target cost calculation

  • In version 0 the target costs are calculated as target costs = plan costs from standard cost estimate / lot size * actual output quantity
  • If the item is lot size independent the formula is target costs = plan costs from standard cost estimate: Plan qty. / lot size * actual output qty. = target qty


Target costs calculated dynamically (on-the-fly)

  • As long as status TECO or DLV is not set on the order, target costs are calculated dynamically (on-the-fly) and are being displayed in costs analysis in CO03 or e.g. in report KKBC_ORD.
  • As soon as the variance calculation has been executed for the first time, target costs exist on the database (with value type 5 in table COSPA and COSSA). If you are now executing KKBC_ORD the system reads the target costs from the database directly.
  • If the variance calculation is reversed then, the system does not calculate target costs dynamically again. It always reads it from database, even if they are zero.
  • If the status TECO or DLV is reversed the variance calculation sets the target costs and variances to zero.


  • SAP note 834317 - Target costs: Display of target credit in reports 
  • SAP note 2892762 - Target costs: Displaying target credit in reports (relevant as of S4CORE 105) 


KV011 "Order does not have status DLV or TECO"

  • SAP note 743766 - Variances: no error message KV011
  • KBA 1922159 - Error KV011 issues in KKS2


BS013 "System status & is active &"

  • It is the common procedure of the variance calculation and also settlement to select orders as long as they are not closed (status CLSD) or flagged for deletion (status DLFL).

  • Variance calculation selects orders from the order master data no matter of their status but the status check is done later.

  • It is recommend to set the deletion flag for all completed or fully settled production and process orders as soon as possible.

  • Orders with status CLSD or CRTD and similar will be removed and message BS013 is issued

    • BS013 can and should be turned off (suppressed) with OPR4_KKS (relevant for KKS1 and KKS2)
    • SAP note 2420801 - Status selection of period-end closing reports for production orders: With this SAP note a feature has been introduced in several period end transactions incl. the variance calculation to exclude orders with a certain status from being selected.


  • KBA 2475585 - Incorrect orders selected in variance calculation


Performance

  • KBA 1578574 - Bad performance in Variance Calculation


Variances on orders without new actual postings 

  •  SAP note 308513 "Variances on completed orders"


Parallel valuation

  • The variance calculation in a parallel valuation is not yet possible in standard (see SAP note 122902 - TP: Assignment of valuations to versions ).

  • SAP pilot-release note 2033687 - VC in parallel valuation

    Please notice that the target cost version of the parallel valuation has to be executed together with version 000 in the update run of the variance calculation. The version 000 is needed to compute the delta since the target cost version of the parallel valuation only updates delta values.

    Additionally please notice that this modification allows the calculation of variances in a parallel valuation for analytical purposes. A settlement of these variance categories is not enabled by this modification.


Error messages KV151 / KV154 / KV169

  • KV151 Only remaining var. in version 0 - no target costs for &

  • KV154 No standard cost estimate for material & in plant & on &

The settlement type in the order determines at which point the cost estimate has to be valid:

    • For the full settlement, the variances are determined across the entire term of the order. In this instance, the cost estimate must be valid on the final day of delivery (status DLV - see table AFPO-LTRMI), or if this has not yet happened, on the day of technical completion (status TECO - see table AUFK-IDAT2), or else on the day the order was created.
    • For the periodic settlement, the variances are calculated for the period. In this case, the cost estimate has to be valid on the last day of the period.
    • It is not possible to release a cost estimate for a date in the past!


  • KV169 No target costs because no price for material & CNP1 in currency &
    • The target cost calculation requires a cost estimate for which the cost component split is active in company as well as in controlling area currency.
      The cost component split in controlling area currency is not active for the costing variant (check T-code: OKKN or OKY9).
      Therefore the variance calculation issues message KV169 and cannot calculate target costs. 
    • KBA 2184974 - KV151 and KV169 occurred in Variance Calculation
    • SAP note 1229004 - Variances: Message KV 169 - no target costs calculated


Error messages KV158 / KV181 / KV192 

  • KV158 Routing/master recipe in actuals differs from qty structure for target

  • KV181 Routing/master recipe order: & - material: &
  • KV192 Cannot calculate scrap variances


  • The scrap variance calculation requires that the routing of the order and the one of the used cost estimate for the scrap variance valuation are identical.

  • SAP note 386816 - WIP and variance calculation: Errors KV158, KV181


Error message CK735 / CK736 

  • CK735 No cost estimate found for procurement alternative 
    For material/plant , no cost estimate could be found for the procurement alternative with BOM  and routing 

  • CK736 No cost estimate found for procurement alternative
    For material/plant , no cost estimate could be found for the procurement alternative with production version 

  • Always have to make sure that a released mixed standard cost estimates exists including all relevant procurement alternatives relevant to the DLV or TECO date. It is not possible to create such a cost estimate in the past.

  • The system is searching for another procurement alternative within the mixed cost estimate to calculate target costs in case the procurement alternative of the order is different if SAP note 707994 is applied.

  • The system does not search for another mixed cost estimate if none is existing relevant to the DLV or TECO date.


  • KBA 2050297 - CK735 occurs in KKS1

  • SAP modification note 707994 - Variances: Search for a procurement alternative

  • SAP pilot-release note 2028939 - Variances: Searching for a procurement alternative in case of split valuation


Error message KV161

  • KV161 WIP or scrap calculation for parallel operation sequences not possible

  • Parallel operations/sequences are not supported by the scrap variance calculation 


  • SAP note 1601599 "Scrap variance/WIP at targets: Message KV161"


Missing target costs in joint production scenario

  • Check if the order is a co-production order with an order header and order items. Then the actual costs are posted to the order header. These costs must be settled with transaction CO8A or CO8B from the order header to the order items BEFORE variance calculation is done for the order items. You may find error KV169 in the log.

  • Correct sequence is important here:

    1. Preliminary Settlement of co-products CO8A/CO8B
    2. Variance calculation
    3. Settlement to material CO88

  • If step 1 has not been done, the variances are not correct.
    To fix the data, variance calculation and settlement should be reversed. Then execute steps 1, 2 and 3 in the correct sequence. Afterwards analyze the cost reports again and check if the data is correct then.


Valuated sales order stock / valuated project stock

  • In a valuated stock scenario the first goods receipt determines the valuation. The target cost calculation follows this.
  • The target cost calculation is based on that cost estimate which is used to valuate the goods receipt of the production order. 
  • Special stock valuated materials are valuated as per the following strategy which is HARDCODED in function module CK36_STANDARD_PRICE_GET - see SAP note 520000.

    The first time a goods movement is carried out the system will go through these strategies until it can find a valid price, and then will create an entry in EBEW/QBEW. The successful strategy number is also written to field LBWST in table EBEW/QBEW.

    The system goes to the next strategy if the one before was not successful.

    From then on, the price from these tables will be used for valuating the special stock in every other goods movement.

    You can easily find which strategy was successful during the first goods receipts when looking at transaction MBBS.


  • SAP note 520000 - FAQ: Valuated special stock
  • For sales order stock one can set parameter "Without Val. Strategy" in the requirements class of the related sales order to always valuate the valuated sales order stock with the standard price of the non-allocated warehouse stock. This is not possible for project stock.


Cutoff period

  • The cutoff period for the variance calculation is set in transaction OKP1.

  • The cutoff period for variances should be adjusted periodically to avoid variance postings into old periods.


Coming soon

  • Further information coming soon

  • No labels