How To Fix CFD_REGISTRY_CHECK099 - Dummy field name must be same in Persistence and Change Indicator Include

SAP Error Message - Details

• Message type: E = Error

• Message class: CFD_REGISTRY_CHECK - Custom Fields: Messages for Registry Check

• Message number: 099

• Message text: Dummy field name must be same in Persistence and Change Indicator Include

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message CFD_REGISTRY_CHECK099 - Dummy field name must be same in Persistence and Change Indicator Include ?

  The SAP error message CFD_REGISTRY_CHECK099 indicates that there is a mismatch in the naming of a dummy field between the Persistence and Change Indicator includes in your Custom Field and Logic (CFL) implementation. This error typically arises when you are working with custom fields in SAP S/4HANA or SAP Business Technology Platform (BTP) and involves the configuration of fields that are intended to be used for change tracking or persistence.
  Cause:
  The error occurs when:
  
  A dummy field (often used for technical purposes) is defined in the Persistence include but has a different name in the Change Indicator include.
  The system expects these dummy fields to have the same name in both includes to ensure consistency and proper functionality.
  
  Solution:
  To resolve this error, you need to ensure that the dummy field names are identical in both the Persistence and Change Indicator includes. Here are the steps to do this:
  
  
  Access the Custom Fields and Logic App:
  
  Go to the Custom Fields and Logic app in your SAP system.
  
  
  
  Identify the Custom Field:
  
  Locate the custom field that is causing the error.
  
  
  
  Check the Persistence Include:
  
  Open the Persistence include for the custom field and note the name of the dummy field.
  
  
  
  Check the Change Indicator Include:
  
  Open the Change Indicator include for the same custom field and verify the name of the dummy field.
  
  
  
  Align the Field Names:
  
  If the names are different, modify one of them to match the other. Ensure that the naming is consistent across both includes.
  
  
  
  Save and Activate:
  
  After making the necessary changes, save your work and activate the custom field.
  
  
  
  Test the Changes:
  
  Test the functionality to ensure that the error is resolved and that the custom field behaves as expected.
  
  
  
  Related Information:
  
  Dummy Fields: These are often used in SAP to manage technical aspects of custom fields, such as change tracking or data persistence.
  Custom Fields and Logic: This is a feature in SAP S/4HANA that allows users to create custom fields and logic without extensive coding.
  Error Handling: Always check the SAP Notes and documentation for any specific guidelines or updates related to custom fields and error messages.
  
  If the issue persists after following these steps, consider consulting SAP support or checking the SAP Community for additional insights and solutions.