How To Fix FMSPLIT036 - No stored trace available to display

FMSPLIT036 - Overview

• Message type: E = Error

• Message class: FMSPLIT - Rule-Based Distributions to Multiple Account Assignments

• Message number: 036

• Message text: No stored trace available to display

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 FMSPLIT036 - No stored trace available to display ?

  The SAP error message FMSPLIT036: No stored trace available to display typically occurs in the context of the Financial Management (FM) module when a user attempts to access a trace or log that does not exist or has not been generated. This can happen for various reasons, including:
  Causes:
  
  No Trace Generated: The system may not have generated a trace for the specific transaction or process you are trying to analyze.
  Trace Deletion: The trace data may have been deleted or purged from the system.
  Incorrect Selection: The user may be trying to access a trace for a transaction that does not have any associated logs.
  Authorization Issues: The user may not have the necessary authorizations to view the trace data.
  System Configuration: The system may not be configured to store traces for the specific operations or transactions.
  
  Solutions:
  
  Check Trace Settings: Ensure that the trace settings in the system are correctly configured to capture the necessary logs.