How To Fix OQ_E350 - Fees had to be re-calculated. Performance issues ? -> see long text.

OQ_E350 - Overview

• Message type: E = Error

• Message class: OQ_E - IS-Oil SSR : Message pool Payment Card Processing

• Message number: 350

• Message text: Fees had to be re-calculated. Performance issues ? -> see long text.

What causes this issue?

The information structure contains fields for clearing house fees.
These fees are not calculated immediately in the data inbound process
for the payment card information.
Instead they can be dynamically calculated during the reporting
run-time or by a subsequent report storing the updated fee values back
to the information structure.
Using this 'off-line' calculation with the report has advantages on the
reporting. In this case the report will only calculate the fees where
it is not done yet and skip it for those where it is already done.
Therefore you should consider to plan in report ROIRE_S414_SAVE_FEES as
a periodic job to update the reporting structure in times where you
have a low system utilization.
If you feel that this report already took too long until the first data
was displayed you might also start the report for the desired timeframe
straight away via transaction SE38.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

OQ_E350 - Details

• The SAP error message OQ_E350, which indicates that "Fees had to be re-calculated," typically arises in the context of pricing and billing processes within SAP, particularly in modules like SAP SD (Sales and Distribution) or SAP FI (Financial Accounting). This error can be associated with performance issues, especially when the system is trying to recalculate fees for a large number of transactions or complex pricing conditions.
  
  Cause:
  
  Data Changes: Changes in master data (like customer or material master) or transaction data (like sales orders or invoices) can trigger a recalculation of fees.
  Complex Pricing Conditions: If the pricing procedure involves many conditions or complex calculations, it may lead to performance issues during recalculation.
  Large Volume of Data: Processing a large volume of transactions at once can strain system resources, leading to delays and potential errors.
  
  Configuration Issues: Incorrect configuration in pricing procedures or condition records can lead to unexpected recalculations.
  
  
  Solution:
  
  Analyze the Long Text: The long