Do you have any question about this error?
Message type: E = Error
Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation
Message number: 794
Message text: &1: Entry in original table ANEK with field BUDAT = 00.00.000
Data records with <AB>BUDAT</> = 00.00.0000 exist in table <AB>ANEK</> (
<LS>Asset Accounting document header</>).
The system checks whether data records exist in table <AB>ANEK</> in
which the field <AB>BUDAT</> (posting date) has <ZH>no</> entry.
If this is the case, as here, an error message is issued.
You must adjust the affected data records <ZH>before</> the data
migration. Otherwise you will trigger error message <AB>FINS_RECON 561
</> (<LS>&1: Posting period for line item is initial (ACDOCA)</>).
To add the required data before executing the document migration, use
the adjustment program in SAP Note 2209958.
*********************************************************************
Error message extract from SAP system. Copyright SAP SE.
FINS_RECON794
- &1: Entry in original table ANEK with field BUDAT = 00.00.000 ?The SAP error message FINS_RECON794 indicates that there is an issue with the entries in the asset accounting tables, specifically the table ANEK. The error message states that there is an entry with a field BUDAT (posting date) that is set to an invalid date format (00.00.0000). This typically occurs during reconciliation processes or when trying to post transactions related to asset accounting.
Cause:
- Invalid Date Entry: The primary cause of this error is that there is an entry in the ANEK table with a posting date (BUDAT) that is not valid. The date "00.00.0000" is not a valid date and can occur due to data corruption, incorrect data entry, or issues during data migration.
- Data Migration Issues: If data was migrated from another system or if there were manual entries that did not adhere to the date format, this could lead to such errors.
- System Configuration Issues: Sometimes, configuration settings in the asset accounting module may lead to incorrect postings.
Solution:
- Identify the Invalid Entry: Use transaction codes like SE16 or SE11 to access the ANEK table and search for entries with the BUDAT field set to "00.00.0000". You can run a query to find these entries:
SELECT * FROM ANEK WHERE BUDAT = '00000000'.
- Correct the Invalid Date: Once you identify the invalid entries, you will need to correct them. This may involve:
- Updating the BUDAT field to a valid date.
- Deleting the invalid entries if they are not needed.
- Consulting with your finance team to ensure that the correct dates are used.
- Check for Other Related Issues: After correcting the invalid entries, check if there are any other related issues in the asset accounting module that may need attention.
- Run Reconciliation Again: After making the necessary corrections, attempt to run the reconciliation process again to see if the error persists.
Related Information:
If the issue persists after following these steps, it may be necessary to consult with your SAP support team or a technical consultant for further investigation.
Get instant SAP help. Start your 7-day free trial now.
FINS_RECON793
&1: No entry in original table ANEP for leading depr. area
What causes this issue? Entries are missing in table <AB>ANEP</> for leading depreciation areas.System Response The system checks whethe...
FINS_RECON792
&1: No entry in original table ANEP for entry in original table ANEK
What causes this issue? <ZH>No</> data record exists in table <AB>ANEP</> (<LS>Asset Accounting Line Items</>) fo...
FINS_RECON795
&1: Line Items ANEP/ANEA differs from Totals ANLC
What causes this issue? The totals of the line items do <ZH>not</> match the totals records.System Response The system checks whether th...
FINS_RECON796
&1: Planned differ from posted values in original table ANLC
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.