How To Fix FARR_INFLIGHT_CHECK345 - C09:POB &1 Trx_price &2 <> Alloc_amt &3 even if prevent allocation is set

FARR_INFLIGHT_CHECK345 - Overview

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 345

• Message text: C09:POB &1 Trx_price &2 <> Alloc_amt &3 even if prevent allocation is set

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_INFLIGHT_CHECK345 - C09:POB &1 Trx_price &2 <> Alloc_amt &3 even if prevent allocation is set ?

  The SAP error message FARR_INFLIGHT_CHECK345 C09:POB &1 Trx_price &2 <> Alloc_amt &3 even if prevent allocation is set typically occurs in the context of the SAP Flexible Real Estate Management (RE-FX) module, particularly when dealing with allocation and pricing in contracts or agreements.
  
  Cause:
  This error indicates a mismatch between the transaction price and the allocated amount for a particular object (POB - Point of Business). Specifically, it suggests that the transaction price (Trx_price) does not match the allocated amount (Alloc_amt), even though the system is configured to prevent allocation.
  The potential causes for this error include:
  
  Data Entry Errors: Incorrect values entered for transaction price or allocation amounts.
  
  Configuration Issues: Misconfiguration in the allocation settings or pricing conditions.
  Timing Issues: The transaction might be in a state where it is being processed, leading to temporary inconsistencies.
  Business Logic: The business rules defined in the system may not allow for the current transaction to proceed due to