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

FARR_APPLICATION112 - Overview

• 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.

FARR_APPLICATION112 - Details

• 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