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

KO358 - Overview

• 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