How To Fix CK868 - Costing of cycle & diverges

CK868 - Overview

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 868

• Message text: Costing of cycle & diverges

What causes this issue?

The system determined that iterative costing of the materials belonging
to cycle &v1& diverges. There are probably incorrect item quantities in
one or more of the BOMs, or some of the items are weighted with large
<DS:GLOS.relevancy_to_costing>costing relevancy factors</>.
This error occurs for example when the quantity structure of material A
specifies that the manufacture of 1 kg A uses an input quantity of e.g.
10 kg A in addition to other items (with positive value).

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?

Procedure for System Administrators

Check the BOMs of the materials in cycle &v1&. You can see these
materials in the material overview of the cost estimate.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK868 - Costing of cycle & diverges ?

  The SAP error message CK868 ("Costing of cycle & diverges") typically occurs during the costing process in SAP, particularly when dealing with product costing and cost estimates. This error indicates that there is a circular dependency in the cost calculation, which means that the system cannot determine the costs because it encounters a loop in the cost structure.
  Causes:
  
  Circular Dependencies: The most common cause is a circular reference in the cost components or in the bill of materials (BOM) where one material's cost depends on another, which in turn depends on the first.
  Incorrect BOM or Routing: Errors in the BOM or routing definitions can lead to cycles in the costing process.
  Costing Variants: The configuration of costing variants may not be set up correctly, leading to issues in how costs are calculated.
  Material Master Data: Inconsistencies or errors in the material master data can also contribute to this issue.
  
  Solutions:
  
  Check BOM and Routing: Review