How To Fix /ACCGO/UIS_API070 - LDC &1 Event ID &2: Cannot find event change indicator data

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_API -

• Message number: 070

• Message text: LDC &1 Event ID &2: Cannot find event change indicator data

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 /ACCGO/UIS_API070 - LDC &1 Event ID &2: Cannot find event change indicator data ?

  The SAP error message /ACCGO/UIS_API070 LDC &1 Event ID &2: Cannot find event change indicator data typically occurs in the context of the SAP General Ledger (G/L) accounting or during the processing of event-driven data in the system. This error indicates that the system is unable to locate the change indicator data for a specific event, which is necessary for processing.
  Causes:
  
  Missing Data: The event change indicator data for the specified event ID may not exist in the database. This could happen if the data was not created or was deleted.
  Configuration Issues: There may be configuration issues in the system that prevent the proper linking of event IDs to their change indicators.
  Data Consistency Issues: There could be inconsistencies in the data due to incomplete transactions or errors during data migration.
  Authorization Issues: The user may not have the necessary authorizations to access the required data.
  
  Solutions:
  
  Check Data Existence: Verify if the event change indicator data exists for the specified event ID. You can do this by querying the relevant database tables or using transaction codes that allow you to view event data.
  Review Configuration: Check the configuration settings related to event management and change indicators. Ensure that all necessary settings are correctly configured.
  Data Consistency Check: Run data consistency checks or reports to identify any inconsistencies in the data. This may involve using transaction codes like SE16 to view relevant tables or using specific reports designed for data validation.
  Recreate Missing Data: If the data is missing, you may need to recreate it based on business processes or historical data.
  Check Authorizations: Ensure that the user encountering the error has the necessary authorizations to access the event change indicator data.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SE16 (Data Browser), SE11 (Data Dictionary), and SM37 (Job Monitoring) to help diagnose the issue.
  SAP Documentation: Review SAP documentation related to event management and change indicators for a deeper understanding of how these components interact.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the issue persists after trying the above solutions, it may be beneficial to involve your SAP Basis or technical team for further investigation, or to reach out to SAP support for assistance.