Do you have any question about this error?
Message type: E = Error
Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation
Message number: 390
Message text: CoCd &1: Check for shifted buzei started at &2 and ended at &3
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.
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.
FINS_RECON390
- CoCd &1: Check for shifted buzei started at &2 and ended at &3 ?The SAP error message FINS_RECON390 typically indicates an issue with the reconciliation of financial documents in a specific company code (CoCd). The message suggests that there are discrepancies or inconsistencies in the document postings that need to be addressed.
Cause:
The error message usually arises due to one or more of the following reasons:
- Shifted Document Numbers: The error indicates that there are document numbers that have been shifted or are out of sequence, which can happen due to manual adjustments or incorrect postings.
- Inconsistent Data: There may be inconsistencies in the financial data, such as missing or incorrect entries in the General Ledger (G/L) accounts.
- Posting Period Issues: The documents may be posted in different periods, leading to reconciliation issues.
- Configuration Issues: There could be configuration problems in the financial settings of the SAP system.
Solution:
To resolve the FINS_RECON390 error, you can follow these steps:
Check Document Numbers: Review the document numbers mentioned in the error message. Ensure that they are in the correct sequence and that there are no gaps or duplicates.
Review Posting Periods: Verify that all documents are posted in the correct accounting periods. If there are discrepancies, you may need to adjust the posting periods accordingly.
Analyze Financial Data: Use transaction codes like FB03 (Display Document) or FBL1N (Vendor Line Item Display) to check the details of the documents involved. Look for any inconsistencies or missing entries.
Run Reconciliation Reports: Use the appropriate reconciliation reports to identify discrepancies. You can use transaction codes like F.01 (Financial Statement) or F.16 (Reconciliation of G/L Accounts) to help identify issues.
Consult Configuration Settings: Check the configuration settings in the Financial Accounting (FI) module to ensure that everything is set up correctly. This may involve reviewing the settings for document types, number ranges, and posting rules.
Seek Help from SAP Support: If the issue persists after performing the above checks, consider reaching out to SAP support for further assistance. They may provide specific guidance based on your system configuration and the nature of the error.
Related Information:
By following these steps, you should be able to identify and resolve the underlying issues causing the FINS_RECON390 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
FINS_RECON389
Entry in FAGLBSAS_BCK without BKPF and no archiving flag: &1 message(s)
What causes this issue? There are line items in the index table FAGLBSAS_BCK without header information in table BKPF which are not marked as partial...
FINS_RECON388
Entry in FAGLBSIS_BCK without BKPF and no archiving flag: &1 message(s)
What causes this issue? There are line items in the index table FAGLBSIS_BCK without header information in table BKPF which are not marked as partial...
FINS_RECON391
&1: Shifted BUZEI between BSEG and NewGL Line item
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_RECON392
&1: Shifted BUZEI, but no matching account
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.