How To Fix CK_MCSO012 - No costing variant in requirements class. See long text

CK_MCSO012 - Overview

• Message type: E = Error

• Message class: CK_MCSO - Messages for Mass Costing of Sales Documents

• Message number: 012

• Message text: No costing variant in requirements class. See long text

What causes this issue?

No costing variant is assigned to requirements class &V1&.

System Response

Processing continues with the next item.

How to fix this error?

Check the customizing settings for <ZK>Product Cost by Sales Order</>
under <ZK>Control of Sales-Order-Related Production/Product Cost by
Sales Order -> Check Requirements Classes.</>
Note
You can remove this message from the log with the customizing
transaction <DS:TRAN.OPR4_CKMC>User-Defined Error Management for Mass
Costing of Sales Documents</>. The item will still not be costed,
however.

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CK_MCSO012 - Details

• The SAP error message CK_MCSO012 "No costing variant in requirements class" typically occurs during the costing process in SAP, particularly when dealing with material costing or product costing. This error indicates that the system cannot find a costing variant associated with the requirements class for the material or product being processed.
  
  Cause:
  
  Missing Costing Variant: The primary cause of this error is that there is no costing variant defined for the requirements class that is being used for the material.
  Incorrect Configuration: The configuration settings for the costing variant or requirements class may not be set up correctly.
  Material Master Data: The material master data may not be properly maintained, leading to the absence of a costing variant.
  Costing Type: The costing type may not be assigned correctly in the configuration.
  
  
  Solution:
  To resolve the CK_MCSO012 error, you can follow these steps:
  
  
  Check Requirements Class:
  
  Go to the transaction code OKTZ (Define Requirements Classes) and check if the requirements