How To Fix /SCMTMS/FAG_MSG799 - Historical spend report running in background

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 799

• Message text: Historical spend report running in background

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 /SCMTMS/FAG_MSG799 - Historical spend report running in background ?

  The SAP error message /SCMTMS/FAG_MSG799 typically indicates an issue related to the execution of the Historical Spend Report in the SAP Transportation Management (TM) module when it is run in the background. This error can arise due to various reasons, including data inconsistencies, configuration issues, or resource limitations.
  Cause
  
  Data Inconsistencies: There may be missing or inconsistent data in the underlying tables that the report relies on.
  Configuration Issues: Incorrect configuration settings in the Transportation Management module can lead to errors when generating reports.
  Resource Limitations: Running the report in the background may require more system resources (memory, processing power) than are available, leading to a failure.
  Authorization Issues: The user executing the report may not have the necessary authorizations to access certain data or execute the report.
  Long Processing Time: If the report takes too long to process, it may time out when running in the background.
  
  Solution
  
  Check Data Consistency: Verify the data in the relevant tables to ensure there are no inconsistencies or missing entries. You may need to run data consistency checks or reports to identify issues.
  Review Configuration: Ensure that the configuration settings for the Historical Spend Report and related components in SAP TM are correctly set up.
  Increase System Resources: If resource limitations are suspected, consider increasing the available memory or processing power for the background job.
  Run in Foreground: If possible, try running the report in the foreground to see if it completes successfully. This can help identify if the issue is related to background processing.
  Check Authorizations: Ensure that the user has the necessary authorizations to execute the report and access the required data.
  Review Job Logs: Check the job logs for any additional error messages or warnings that can provide more context about the failure.
  Consult SAP Notes: Look for any relevant SAP Notes or updates that may address known issues with the Historical Spend Report.
  
  Related Information
  
  Transaction Codes: You may use transaction codes like SM37 to monitor background jobs and check their status.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps you have taken to resolve it.
  Documentation: Review the official SAP documentation for the Transportation Management module for any specific guidelines related to reporting and background processing.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the /SCMTMS/FAG_MSG799 error message.