You are using Condition Contract Management (CCM) functionality. You have a condition contract for which you are creating a new condition record. This condition record is being created for a condition table, in which Condition Contract Number (COCO_NUM) was not defined as an access field.
Based on the above, you are experiencing one of the below symptoms in transaction WCOCO:
- a condition is deleted from a condition contract, and then the user creates a new condition contract, with the same condition record data, which had been deleted previously. Error W_CB296 is issued, indicating that the condition was already maintained in another condition contract.
- a condition contract (which contain condition records) is logically deleted, and then the user creates a new condition contract with the same condition data as in the previous contract, error W_CB296 is issued.
- Condition Contract Management in SAP S/4HANA
- Condition Contract Management in SAP ERP
W_CB296, W_CB 296, Condition was already maintained within Condition Contract &1, WCOCO, LOEVM_KO, KONP-LOEVM_KO, WCOCOF-LOGICAL_DELETED, COCO_NUM, deleted condition record, physical deletion , KBA , LO-GT-CHB , Charge Back , LO-GT-CCS , Condition Contract Settlement , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.