/ACCGO/NET_DRY_MSG079 - Scenario not supported for obligation storage locations (&1 / &2 )

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/NET_DRY_MSG -

• Message number: 079

• Message text: Scenario not supported for obligation storage locations (&1 / &2 )

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/NET_DRY_MSG079 - Scenario not supported for obligation storage locations (&1 / &2 ) ?

  The SAP error message /ACCGO/NET_DRY_MSG079 indicates that there is a scenario not supported for obligation storage locations. This error typically arises in the context of the SAP S/4HANA system, particularly when dealing with the new General Ledger (G/L) accounting and the integration of various modules like Asset Accounting (FI-AA) and Controlling (CO).
  Cause:
  The error message is triggered when the system encounters a situation where the obligation storage locations specified (indicated by the placeholders &1 and &2) are not compatible with the current configuration or business process. This can happen due to several reasons, including:
  
  Incorrect Configuration: The storage locations may not be properly configured in the system for the specific scenario you are trying to execute.
  Missing Master Data: The necessary master data for the storage locations may not be set up correctly.
  Business Process Limitations: The specific business process you are trying to execute may not support the use of the specified storage locations.
  Authorization Issues: There may be authorization issues preventing the system from accessing the required data.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Review the configuration settings for the obligation storage locations in the relevant customizing transactions (e.g., SPRO).
  Ensure that the storage locations are correctly defined and linked to the appropriate company codes and plants.
  
  
  
  Verify Master Data:
  
  Check the master data for the materials or assets involved in the transaction. Ensure that the storage locations are correctly assigned and active.
  
  
  
  Review Business Processes:
  
  Confirm that the business process you are trying to execute is supported for the specified storage locations. Consult the SAP documentation or your functional team for guidance.
  
  
  
  Check Authorizations:
  
  Ensure that the user executing the transaction has the necessary authorizations to access the storage locations and perform the required actions.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes that may address this specific error message. SAP frequently releases updates and patches that may resolve known issues.
  
  
  
  Testing:
  
  After making the necessary changes, perform testing to ensure that the error no longer occurs and that the business process can be executed successfully.
  
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP Help Portal for detailed information on configuration and troubleshooting related to obligation storage locations.
  SAP Community: Engage with the SAP Community forums to seek advice from other users who may have encountered similar issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (Customizing), SE11 (Data Dictionary), and SE37 (Function Modules) for deeper investigation.
  
  If the issue persists after following these steps, it may be beneficial to involve your SAP support team or consult with an SAP expert for further assistance.