/ACCGO/CAS_MSG379 - Information about reference document not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_MSG -

• Message number: 379

• Message text: Information about reference document not found

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.

AnswerBot

• What is the cause and solution for SAP error message /ACCGO/CAS_MSG379 - Information about reference document not found ?

  The SAP error message /ACCGO/CAS_MSG379 indicating "Information about reference document not found" typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with cost accounting or internal orders. This error suggests that the system is unable to find the reference document that is required for the operation you are trying to perform.
  Causes:
  
  Missing Reference Document: The reference document (such as a purchase order, invoice, or internal order) may not exist in the system or may have been deleted.
  Incorrect Document Number: The document number you are trying to reference may be incorrect or mistyped.
  Authorization Issues: The user may not have the necessary authorizations to view or access the reference document.
  Data Consistency Issues: There may be inconsistencies in the database or issues with data synchronization that prevent the system from locating the reference document.
  Configuration Issues: There may be configuration settings in the system that are not set up correctly, leading to the inability to find the reference document.
  
  Solutions:
  
  Verify Document Existence: Check if the reference document exists in the system. You can do this by searching for the document number in the relevant transaction (e.g., ME23N for purchase orders).
  Check Document Number: Ensure that the document number you are using is correct and formatted properly.
  Review Authorizations: Ensure that you have the necessary authorizations to access the reference document. You may need to contact your SAP security team for assistance.
  Data Consistency Check: Run consistency checks or reports to identify any data issues. You may need to consult with your SAP Basis or technical team to resolve any underlying data issues.
  Consult Configuration Settings: Review the configuration settings related to the module you are working in. Ensure that all necessary settings are correctly configured.
  SAP Notes and Support: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display Purchase Order), KO03 (Display Internal Order), or others depending on the context of the error.
  SAP Documentation: Refer to SAP Help documentation for detailed information on the specific module you are working with.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If the issue persists after trying the above solutions, it may be necessary to engage with your SAP support team or a consultant for further investigation and resolution.