How To Fix KJ120 - No WIP at actual cost allowed in Product Cost by Period

SAP Error Message - Details

• Message type: E = Error

• Message class: KJ - Cost Object Controlling for Make-to-Order Production

• Message number: 120

• Message text: No WIP at actual cost allowed in Product Cost by Period

What causes this issue?

In Product Cost by Period,
<DS:GLOS.3526B774AFAB52B9E10000009B38F974>work in process</> can only
be calculated at target cost. This is because the
<DS:GLOS.3526B637AFAB52B9E10000009B38F974>variance calculation</>
process only calculates variances by period, so WIP at actual costs
would not be included. This would result in actual costs being settled
more than once.
You are using Product Cost by Period if there is a periodic
distribution rule in the
<DS:GLOS.3526B633AFAB52B9E10000009B38F974>settlement rule</> that
settles to material with a percentage of greater than 0.

How to fix this error?

Use <DS:GLOS.3526B609AFAB52B9E10000009B38F974>full settlement</> or
calculate the work in process at target costs.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KJ120 - No WIP at actual cost allowed in Product Cost by Period ?

  The SAP error message KJ120 "No WIP at actual cost allowed in Product Cost by Period" typically occurs in the context of product costing and work in progress (WIP) accounting. This error indicates that the system is not allowing the calculation of WIP at actual costs for a particular period, which can be due to several reasons.
  Causes:
  
  
  Costing Variant Settings: The costing variant used may not be configured to allow WIP at actual costs. This can happen if the settings for the costing variant do not permit WIP calculations or if the relevant parameters are not set correctly.
  
  
  Period Closing: If the period has been closed in the system, it may prevent any further WIP calculations or adjustments from being made.
  
  
  Costing Type: The costing type used may not support WIP at actual costs. For example, if the costing type is set to only allow standard costing, it will not permit actual cost calculations.
  
  
  Material Master Settings: The material master data may not be set up correctly for WIP calculations. This includes settings related to valuation classes and cost elements.
  
  
  Missing Configuration: There may be missing configuration in the controlling area or the company code that affects how WIP is handled.
  
  
  Solutions:
  
  
  Check Costing Variant: Review the costing variant settings in the configuration (Transaction code OKKN) to ensure that WIP at actual costs is allowed. Make sure the relevant parameters are set correctly.
  
  
  Open Period: If the period is closed, you may need to reopen it to allow for WIP calculations. This can be done through the period closing transaction (Transaction code OB52).
  
  
  Review Costing Type: Ensure that the costing type being used allows for WIP at actual costs. You may need to adjust the costing type settings in the configuration.
  
  
  Material Master Review: Check the material master data for the relevant materials to ensure that they are set up correctly for WIP calculations. This includes verifying valuation classes and cost elements.
  
  
  Configuration Check: Review the configuration settings in the controlling area and company code to ensure that all necessary settings for WIP calculations are in place.
  
  
  Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific guidance related to your system configuration and version.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OKKN (Costing Variants), OB52 (Open/Close Posting Periods), and CK11N (Create Material Cost Estimate) for troubleshooting.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that address the issue.
  User Forums: Consider visiting SAP community forums or user groups where similar issues may have been discussed, providing additional context or solutions.
  
  By following these steps, you should be able to identify the cause of the KJ120 error and implement the necessary solutions to resolve it.