How To Fix FARR_RAI744 - Transfer date must be in the past (comp.code &1/acct.princ. &2)

FARR_RAI744 - Overview

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 744

• Message text: Transfer date must be in the past (comp.code &1/acct.princ. &2)

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_RAI744 - Transfer date must be in the past (comp.code &1/acct.princ. &2) ?

  The SAP error message FARR_RAI744 indicates that there is an issue with the transfer date specified in a financial transaction, specifically in the context of Asset Accounting (FI-AA). The error message states that the transfer date must be in the past, which means that the date you are trying to use for the transfer is either today or a future date, which is not allowed.
  
  Cause:
  
  Incorrect Transfer Date: The transfer date you have entered is set to a date that is either today or in the future.
  System Configuration: There may be system settings or configurations that enforce this rule, ensuring that transfers can only be processed for dates that have already occurred.
  User Input Error: The user may have mistakenly entered the wrong date or format.
  
  
  Solution:
  
  
  Change the Transfer Date: 
  
  Go back to the transaction where you encountered the error and change the transfer date to a date that is in the past.