How To Fix KO358 - No scrap/WIP/variance calculation in version-specific confirmation

SAP Error Message - Details

• Message type: E = Error

• Message class: KO - Master data for CO orders

• Message number: 358

• Message text: No scrap/WIP/variance calculation in version-specific confirmation

What causes this issue?

At present, the system can only determine variances, scrap, and WIP
using the results of the <DS:GLOS.standard_cost_estimate>standard cost
estimate</> for the material produced.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If you want to determine variances, scrap, or WIP, confirmation can
only take place based on the standard cost estimate for the material
produced. Set the appropriate switch in the repetitive manufacturing
profile in customizing.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KO358 - No scrap/WIP/variance calculation in version-specific confirmation ?

  The SAP error message KO358, which states "No scrap/WIP/variance calculation in version-specific confirmation," typically occurs in the context of production order confirmations in SAP. This error indicates that the system is unable to perform the necessary calculations for scrap, work in progress (WIP), or variances due to the specific version of the confirmation being processed.
  Causes:
  
  
  Version-Specific Confirmation: The error often arises when a confirmation is being processed in a version that does not allow for scrap, WIP, or variance calculations. This can happen if the production order is set up in a way that does not support these calculations.
  
  
  Configuration Issues: There may be configuration settings in the controlling (CO) module or production planning (PP) module that are not set up correctly, preventing the calculations from being executed.
  
  
  Missing Master Data: Required master data, such as cost centers, activity types, or production versions, may be missing or incorrectly configured.
  
  
  Incorrect Order Status: The status of the production order may not allow for the calculations to be performed, such as if the order is already completed or closed.
  
  
  Solutions:
  
  
  Check Configuration: Review the configuration settings in the controlling and production planning modules to ensure that they are set up to allow for scrap, WIP, and variance calculations. This includes checking the settings for the production order type and confirmation parameters.
  
  
  Review Production Order: Ensure that the production order is in the correct status for confirmation. If the order is completed or closed, you may need to reopen it or create a new order for further confirmations.
  
  
  Verify Master Data: Check that all necessary master data is correctly maintained. This includes ensuring that cost centers, activity types, and production versions are properly defined and linked to the production order.
  
  
  Use Correct Confirmation Version: If you are using version-specific confirmations, ensure that you are using the correct version that supports the required calculations.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific details on the configuration and settings related to production order confirmations.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, as they may provide insights specific to your system configuration.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CO11N (for confirmation) and CO02 (for production order change) to troubleshoot and manage production orders.
  SAP Notes: Check for any SAP Notes related to error KO358, as there may be specific patches or updates that address this issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing additional insights or solutions.
  
  By following these steps, you should be able to identify the cause of the KO358 error and implement a solution to resolve it.