How To Fix FARR_RAI667 - Earlier date could not be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 667

• Message text: Earlier date could not be determined

What causes this issue?

The system could not determine the date on which the record was created
or changed.

System Response

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

How to fix this error?

Contact your system administrator.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_RAI667 - Earlier date could not be determined ?

  The SAP error message FARR_RAI667: "Earlier date could not be determined" typically occurs in the context of Asset Accounting (FI-AA) when the system is unable to find a valid date for a transaction or an asset that is being processed. This can happen for various reasons, often related to the configuration of the asset or the transaction being executed.
  Causes:
  
  Missing or Incorrect Asset Master Data: The asset master data may not have the necessary information, such as the acquisition date or the useful life, which is required for the system to determine the earlier date.
  Transaction Date Issues: The date of the transaction being processed may be outside the permissible range defined in the system settings.
  Depreciation Areas: If there are issues with the configuration of depreciation areas, it may lead to the system being unable to determine the earlier date.
  Posting Periods: The posting period may be closed or not open for the transaction date, preventing the system from processing the transaction correctly.
  Customizing Settings: Incorrect settings in the configuration of Asset Accounting can lead to this error.
  
  Solutions:
  
  Check Asset Master Data: Ensure that the asset master data is complete and accurate. Verify that all required fields, especially the acquisition date and useful life, are filled in correctly.
  Review Transaction Dates: Make sure that the transaction date falls within the allowed posting periods. If necessary, open the relevant posting period in the system.
  Examine Depreciation Areas: Check the configuration of depreciation areas to ensure they are set up correctly and that they align with the asset's master data.
  Adjust Customizing Settings: Review the customizing settings in Asset Accounting to ensure they are correctly configured. This may involve checking the settings for asset transactions and depreciation.
  Consult Documentation: Refer to SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like AS01 (Create Asset), AS02 (Change Asset), or AS03 (Display Asset) to check the asset master data.
  SAP Notes: Look for relevant SAP Notes in the SAP Support Portal that may provide additional insights or solutions for this error.
  Debugging: If the issue persists, consider debugging the transaction to identify the exact point of failure in the code.
  
  If the problem continues after checking these areas, it may be beneficial to consult with your SAP support team or a consultant who specializes in Asset Accounting for further assistance.