How To Fix FARR_FOUNDATION122 - Account detern f. recognized revenue for linked POB failed for CoC &1

FARR_FOUNDATION122 - Overview

• Message type: E = Error

• Message class: FARR_FOUNDATION - Revenue Accounting - Foundation

• Message number: 122

• Message text: Account detern f. recognized revenue for linked POB failed for CoC &1

What causes this issue?

The account determination for the <ZK>recognized revenue for linked POB
(performance obligation) </>account failed because the system found no
configuration entry for company code &v1&, accounting principle &v2&,
POB type &v3& and reference account &v4&.

System Response

The revenue accounting item was not processed for accounting principle
&v2&.

How to fix this error?

Maintain a matching entry in the
<DS:TRAN.FARR_ACCT_DETER_CUST>BRF+ Account Determination Rules</> on
the tab <ZK>Recognized Revenue for Linked POB</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_FOUNDATION122 - Account detern f. recognized revenue for linked POB failed for CoC &1 ?

  The SAP error message FARR_FOUNDATION122 indicates that there is an issue with the account determination for recognized revenue related to a linked Point of Billing (POB) in the context of SAP's Flexible Real Estate Management (RE-FX) or similar modules. This error typically arises when the system is unable to find the appropriate account for recognizing revenue for a specific condition or transaction.
  Causes:
  
  
  Missing Account Determination: The account determination for the recognized revenue might not be set up correctly in the system. This can happen if the necessary configuration for the revenue recognition process is incomplete.
  
  
  Incorrect Configuration: The configuration settings in the Financial Accounting (FI) or Controlling (CO) modules may not align with the requirements for the specific transaction or POB.
  
  
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the system from determining the correct account.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations