How To Fix FARR_APPLICATION112 - POB &1: Invoice exists with open recon key in migration period

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_APPLICATION - General Revenue Accounting Applications and Code

• Message number: 112

• Message text: POB &1: Invoice exists with open recon key in migration period

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_APPLICATION112 - POB &1: Invoice exists with open recon key in migration period ?

  The SAP error message FARR_APPLICATION112 with the description "POB &1: Invoice exists with open recon key in migration period" typically occurs in the context of the SAP Flexible Real Estate Management (RE-FX) module, particularly during the migration of data or when processing invoices.
  Cause:
  This error indicates that there is an invoice that is linked to an open reconciliation key during a migration period. The reconciliation key is used to ensure that financial transactions are properly accounted for, and if there are open items (like invoices) that have not been reconciled, the system will prevent further processing to maintain data integrity.
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the Invoice: Use the invoice number provided in the error message (represented by &1) to locate the specific invoice in the system.
  
  
  Check Reconciliation Keys: Review the reconciliation keys associated with the invoice. You can do this by navigating to the relevant transaction in SAP that allows you to view invoices and their reconciliation status.
  
  
  Reconcile Open Items: If there are open items linked to the reconciliation key, you will need to either:
  
  Reconcile the open items if they are valid and should be closed.
  If the invoice is incorrect or should not be processed, consider reversing or deleting the invoice.
  
  
  
  Adjust Migration Period Settings: If the migration period is incorrectly set, you may need to adjust the settings to allow for processing of the invoice. This may involve changing the migration period or ensuring that all necessary data has been migrated correctly.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling reconciliation keys and invoices in the RE-FX module.
  
  
  Contact Support: If the issue persists after attempting the above solutions, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL1N (Vendor Line Item Display) or FB03 (Display Document) to help you investigate the invoice and reconciliation key.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that could resolve the issue.
  Migration Process: Review the overall migration process to ensure that all necessary steps have been followed and that data integrity is maintained throughout the migration.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.