How To Fix FINS_RECON789 - &1: No entry in ANLZ with field ADATU = 01.01.1900 or BDATU = 31.12.9999

FINS_RECON789 - Overview

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 789

• Message text: &1: No entry in ANLZ with field ADATU = 01.01.1900 or BDATU = 31.12.9999

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 FINS_RECON789 - &1: No entry in ANLZ with field ADATU = 01.01.1900 or BDATU = 31.12.9999 ?

  The SAP error message FINS_RECON789 indicates that there is an issue with asset accounting, specifically related to the asset master data. The error message states that there is no entry in the asset master record (table ANLZ) for the specified asset with the given date conditions (ADATU = 01.01.1900 or BDATU = 31.12.9999). 
  
  Cause:
  
  Missing Asset Master Data: The asset you are trying to process does not have a valid entry in the asset master data table (ANLZ) for the specified date range.
  Incorrect Date Settings: The dates being used in the transaction may not correspond to valid entries in the asset master data.
  Data Migration Issues: If data was migrated from another system, there may have been issues with the asset data not being transferred correctly.
  
  Configuration Issues: There may be configuration settings in the asset accounting module that are not set up correctly.
  
  
  Solution:
  
  
  Check Asset Master Data: 
  
  Go to transaction code AS03 (Display