How To Fix FKK_CC104 - Master data object not changed in FI-CA

FKK_CC104 - Overview

• Message type: E = Error

• Message class: FKK_CC -

• Message number: 104

• Message text: Master data object not changed in FI-CA

What causes this issue?

Master data object &V1& &V2& was created or changed. The change was
successfully distributed to SAP Convergent Charging. However, the master
data object was not changed in Contract Accounts Receivable and Payable,
possibly because the posting of the change is still being executed or
because the update process was unsuccessful.

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?

Check the update process in Contract Accounts Receivable and Payable
that is supposed to change master data object &V1& &V2&.
If it is not possible to restart the update process, you can reverse the
change in SAP Convergent Charging. To do so, select the corresponding
error entry in the monitor and send it to SAP Convergent Charging. As a
result, the unchanged data of the master data object is distributed to
SAP Convergent Charging, and the change in SAP Convergent Charging is
thereby reversed.

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 FKK_CC104 - Master data object not changed in FI-CA ?

  The SAP error message FKK_CC104 ("Master data object not changed in FI-CA") typically occurs in the context of the Financial Accounting - Contract Accounts Receivable and Payable (FI-CA) module. This error indicates that an attempt was made to change a master data object (such as a business partner, contract account, or other related entities) but the system determined that no actual changes were made to the data.
  Causes:
  
  No Changes Made: The most common cause is that the user attempted to save changes to a master data object, but the data submitted was identical to the existing data.
  Data Validation Issues: There may be validation rules in place that prevent certain changes from being saved if they do not meet specific criteria.
  Authorization Issues: The user may not have the necessary authorizations to make changes to the master data object.
  Technical Issues: There could be underlying technical issues, such as database locks or inconsistencies in