How To Fix /ACCGO/DGR122 - Forward obligation has been cancelled for HLR event ID &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/DGR -

• Message number: 122

• Message text: Forward obligation has been cancelled for HLR event ID &1

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/DGR122 - Forward obligation has been cancelled for HLR event ID &1 ?

  The SAP error message /ACCGO/DGR122 Forward obligation has been cancelled for HLR event ID &1 typically relates to issues in the handling of obligations in the context of the SAP Advanced Compliance Management (ACM) or similar modules that deal with financial obligations and events.
  Cause:
  
  
  Cancellation of Obligation: The error indicates that a forward obligation associated with a specific HLR (High-Level Requirement) event has been cancelled. This could happen due to various reasons, such as:
  
  Manual cancellation by a user.
  System-triggered cancellation due to changes in the underlying data or business processes.
  Issues with data integrity or configuration that led to the obligation being marked as cancelled.
  
  
  
  Data Consistency Issues: There may be inconsistencies in the data related to the HLR event or the obligations that are linked to it.
  
  
  Configuration Errors: Incorrect configuration in the system settings related to obligations or HLR events could lead to this error.
  
  
  Solution:
  
  
  Check the HLR Event: Review the HLR event ID mentioned in the error message. Ensure that the event is still valid and that the associated obligations are correctly configured.
  
  
  Review Cancellation Reasons: Investigate why the obligation was cancelled. Check logs or transaction history to see if there were any manual interventions or system processes that led to the cancellation.
  
  
  Data Integrity Check: Perform a data integrity check to ensure that all related data is consistent and correctly linked. This may involve checking related tables and records in the database.
  
  
  Recreate the Obligation: If the obligation was cancelled in error, you may need to recreate it. This can often be done through the relevant transaction in SAP.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific module you are using (e.g., Advanced Compliance Management) for any known issues or additional troubleshooting steps.
  
  
  Contact SAP Support: If the issue persists and you cannot determine the cause or solution, consider reaching out to SAP support for assistance. Provide them with the error message, HLR event ID, and any relevant context.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as those for viewing obligations, HLR events, or logs.
  SAP Notes: Search for SAP Notes related to the error message or the specific module you are using. SAP Notes often contain fixes or workarounds for known issues.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed. Other users may have encountered the same error and can provide insights or solutions.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.