How To Fix AFWGO_MESSAGES090 - Final results proc. &1 on &2 completed with errors

SAP Error Message - Details

• Message type: E = Error

• Message class: AFWGO_MESSAGES - Messages for Development Class AFWGO

• Message number: 090

• Message text: Final results proc. &1 on &2 completed with errors

What causes this issue?

The final results procedure you selected ran on the chosen key date or
for the selected period and was completed with no technical problems,
but some key figures were not completely calculated and could not be
written to the results database.
In the displayed log, the related messages are highlighted in color.

System Response

Those key figures for which an error message was displayed are not
saved in the results database.

How to fix this error?

Process the error messages. Next delete the saved results for the
chosen key date or period and execute the final results procedure
again as a basic run.
The results saved in the results database are available for reporting
indepedent of any postprocessing that takes place.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AFWGO_MESSAGES090 - Final results proc. &1 on &2 completed with errors ?

  The SAP error message AFWGO_MESSAGES090 indicates that a final results processing job (often related to the SAP Advanced Planning and Optimization (APO) module or similar processes) has completed with errors. This message typically arises during the execution of a planning run or when processing results in a planning area.
  Causes:
  
  Data Issues: There may be inconsistencies or missing data in the master data or transaction data that the planning process relies on.
  Configuration Errors: Incorrect settings in the planning area, such as key figures, planning levels, or planning versions, can lead to errors during processing.
  Resource Constraints: Insufficient system resources (like memory or processing power) can cause the job to fail.
  Authorization Issues: The user executing the process may not have the necessary authorizations to access certain data or execute specific functions.
  Technical Errors: Bugs or issues in the SAP system or the specific version being used can also lead to this error.
  
  Solutions:
  
  Check Logs: Review the detailed logs for the job that generated the error. This can provide specific information about what went wrong. You can access logs through transaction codes like SLG1 (Application Log) or SM37 (Job Monitoring).
  Data Validation: Ensure that all required master and transaction data is complete and accurate. Check for missing or inconsistent entries in the relevant tables.
  Configuration Review: Verify the configuration settings for the planning area. Ensure that all key figures and planning levels are correctly defined and that there are no discrepancies.
  Resource Monitoring: Monitor system resources during the job execution to ensure that there are no bottlenecks. If necessary, consider increasing system resources or scheduling jobs during off-peak hours.
  Authorization Check: Ensure that the user has the necessary authorizations to execute the job. You can check this in transaction SU53 (Authorization Check).
  Consult SAP Notes: Look for relevant SAP Notes that may address known issues or bugs related to this error message. You can search for notes in the SAP Support Portal.
  Re-run the Job: After addressing the identified issues, re-run the job to see if the problem persists.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM37: Job Monitoring
  SLG1: Application Log
  SCC4: Client Administration (to check client settings)
  
  
  SAP Documentation: Refer to SAP Help documentation for detailed information on the specific planning processes and configurations.
  Community Forums: Engage with SAP community forums or user groups for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP Basis team or open a support ticket with SAP for further assistance.