Once the system has checked and changed the fields in the contract that are participating in the product change, in BDT event DCHCK (checks before saving (cross-view)) it checks the fields that are participating in the product change, and those that are not participating in the product change, meaning those whose attribute group is assigned to the dummy application (DUMM). Next the system makes all the checks that - irrespective of the product change - are always made when contracts are saved, to avoid inconsistencies (see also the check modules of the contract elements stored in transaction f9bacn_s7). These checks can cause problems, particularly for the fields not participating in the product change. The system outputs error messages that ultimately prevent the product change if the following prerequisites do not apply:

The following situation is problematic: An attribute is set in the source product as optional field, the corresponding field in the contract does not have a field value, and in the target product this attribute is set as required field.