How To Fix CU355 - KNUM is assigned in CUOB but missing in CUKB (net: &)

SAP Error Message - Details

• Message type: E = Error

• Message class: CU - Variants / configuration messages

• Message number: 355

• Message text: KNUM is assigned in CUOB but missing in CUKB (net: &)

What causes this issue?

a constraint that no longer exists is assigned to a constraint net.
This error has no consequences, but you see this message so that you
can find out under what circumstances this situation can occur.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CU355 - KNUM is assigned in CUOB but missing in CUKB (net: &) ?

  The SAP error message CU355 indicates that there is a problem with the condition record for pricing in the SAP system. Specifically, it means that a condition number (KNUM) is assigned in the condition table CUOB but is missing in the condition table CUKB. This typically occurs in the context of pricing and condition records in SAP SD (Sales and Distribution) or MM (Materials Management).
  Cause:
  
  Data Inconsistency: The condition record exists in one table (CUOB) but not in the related table (CUKB). This can happen due to data inconsistencies, such as incomplete updates or errors during data migration.
  Missing Condition Records: The condition record might have been deleted or not created properly in the CUKB table.
  Custom Development: If there are custom developments or modifications in the pricing procedure, they might lead to inconsistencies in how condition records are handled.
  
  Solution:
  
  Check Condition Records: Use transaction codes like VK13 (Display Condition) to check if the condition record exists in both tables. If it exists in CUOB but not in CUKB, you may need to recreate or adjust the condition record.
  Recreate Missing Records: If the condition record is missing in CUKB, you can recreate it using the appropriate transaction (e.g., VK11 for creating condition records).
  Consistency Check: Run a consistency check for condition records. You can use transaction SDBI to check for inconsistencies in condition records.
  Transport Issues: If this issue arose after a transport, check if the transport included all necessary objects and data. You may need to re-transport or manually adjust the records.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide guidance on how to resolve it.
  
  Related Information:
  
  
  Tables Involved:
  
  CUOB: This table contains condition records for pricing.
  CUKB: This table is used for storing condition records related to the pricing procedure.
  
  
  
  Transaction Codes:
  
  VK11: Create Condition Record
  VK12: Change Condition Record
  VK13: Display Condition Record
  SDBI: Consistency Check for Condition Records
  
  
  
  SAP Documentation: Refer to the SAP Help Portal for detailed documentation on pricing procedures and condition records.
  
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or functional team for further investigation, as they may have access to more detailed logs and system settings.