How To Fix FARR_RAI155 - Test data has not been saved; data saved in update run only

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 155

• Message text: Test data has not been saved; data saved in update run only

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 FARR_RAI155 - Test data has not been saved; data saved in update run only ?

  The SAP error message FARR_RAI155 indicates that test data has not been saved and that the data is only saved in an update run. This typically occurs in the context of the SAP Asset Accounting (FI-AA) module, particularly when dealing with asset transactions or postings.
  Cause:
  
  
  Test Run Mode: The error usually arises when a transaction is executed in test mode. In this mode, the system simulates the transaction but does not commit any changes to the database. This is often used for testing purposes to ensure that the transaction will work correctly before executing it in a live environment.
  
  
  Update Run: The message indicates that the data is only saved in an update run, meaning that the actual posting will occur later, typically during a batch job or a scheduled update process.
  
  
  Solution:
  
  
  Switch to Update Mode: If you intend to save the data permanently, ensure that you are running the transaction in update mode rather than test mode. This can usually be done by unchecking any "Test Run" options in the transaction screen.
  
  
  Check Transaction Settings: Review the settings of the transaction you are executing. Ensure that you are not inadvertently running it in a test mode.
  
  
  Execute Update Run: If the transaction is designed to save data in an update run, ensure that the update job is scheduled and executed properly. You may need to check the job logs to confirm that the update run has completed successfully.
  
  
  Consult Documentation: Refer to the SAP documentation or help files related to the specific transaction you are using to understand its behavior regarding test and update runs.
  
  
  Contact Support: If you are unsure about the settings or if the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with the transaction codes related to asset accounting and their respective settings.
  Batch Jobs: Understand how batch jobs work in SAP and how they can affect data posting.
  Testing Procedures: Review your organization's procedures for testing transactions in SAP to ensure compliance with best practices.
  
  By addressing the cause of the error and following the suggested solutions, you should be able to resolve the issue and successfully save your data in SAP.