How To Fix /ACCGO/FEE179 - Data is saved but settlement group fee is not copied to settlement unit

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/FEE -

• Message number: 179

• Message text: Data is saved but settlement group fee is not copied to settlement unit

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/FEE179 - Data is saved but settlement group fee is not copied to settlement unit ?

  The SAP error message /ACCGO/FEE179 indicates that while data has been saved, the settlement group fee was not copied to the settlement unit. This can occur in the context of financial transactions, particularly when dealing with settlement processes in SAP.
  Cause:
  
  Configuration Issues: The settlement group fee may not be properly configured in the system. This could be due to missing or incorrect settings in the fee configuration or settlement group settings.
  Missing Data: Required data for the settlement group fee might be missing or incomplete, preventing it from being copied to the settlement unit.
  Authorization Issues: The user may not have the necessary authorizations to perform the operation, leading to incomplete processing.
  System Bugs: There could be a bug or issue in the specific version of SAP being used that affects the copying of fees to the settlement unit.
  
  Solution:
  
  
  Check Configuration:
  
  Review the configuration settings for the settlement group fees in the relevant customizing transactions (e.g., SPRO).
  Ensure that the settlement group is correctly defined and that the fees are properly assigned to it.
  
  
  
  Verify Data Completeness:
  
  Check if all required fields and data for the settlement group fee are filled out correctly.
  Ensure that the relevant master data (e.g., customer/vendor, contract) is complete and accurate.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to perform the settlement process. This can be checked in the user roles and profiles.
  
  
  
  Check for System Notes:
  
  Look for any SAP Notes or patches that might address this specific error. You can search the SAP Support Portal for relevant notes.
  
  
  
  Debugging:
  
  If you have access to technical resources, consider debugging the process to identify where the copying of the fee fails.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation related to the settlement process and fees for any additional insights or requirements.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO for configuration, SE11 for data dictionary, and SE80 for object navigator.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the context in which it occurs.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.