How To Fix /ACCGO/FEE123 - No fees were determined for event &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/FEE -

• Message number: 123

• Message text: No fees were determined for event &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/FEE123 - No fees were determined for event &1 ?

  The SAP error message /ACCGO/FEE123 No fees were determined for event &1 typically occurs in the context of the SAP Convergent Charging (SAP CC) or SAP Convergent Invoicing (SAP CI) modules. This error indicates that the system was unable to determine any fees for a specific event, which can be due to several reasons.
  Causes:
  
  
  Missing Fee Configuration: The fee configuration for the specific event type may not be set up correctly in the system. This could mean that there are no fee rules defined for the event in question.
  
  
  Event Type Not Mapped: The event type being processed may not be mapped to any fee structure in the system.
  
  
  Inactive Fee Rules: The fee rules that should apply to the event may be inactive or not valid for the current date.
  
  
  Data Issues: There may be issues with the data being passed to the fee determination process, such as missing or incorrect parameters.
  
  
  Business Rules: The business rules defined for fee determination may not be met, leading to no fees being applicable.
  
  
  Solutions:
  
  
  Check Fee Configuration: Review the fee configuration for the specific event type in the SAP system. Ensure that the necessary fee rules are defined and active.
  
  
  Verify Event Mapping: Ensure that the event type is correctly mapped to the appropriate fee structure. This may involve checking the configuration settings in the relevant customizing transactions.
  
  
  Activate Fee Rules: If the fee rules are inactive, activate them and ensure they are valid for the current date and applicable to the event type.
  
  
  Review Input Data: Check the data being sent to the fee determination process. Ensure that all required fields are populated correctly and that there are no discrepancies.
  
  
  Consult Business Rules: Review the business rules that govern fee determination to ensure that the conditions for applying fees are met.
  
  
  Debugging: If the issue persists, consider debugging the fee determination process to identify where the logic is failing.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration, or SE80 for debugging and checking the relevant programs.
  Documentation: Refer to SAP documentation or help guides specific to SAP Convergent Charging or Invoicing for detailed configuration steps.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to fee determination.
  
  If the problem continues after checking these areas, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.