How To Fix FARR_CONTRACT_MAIN157 - Derived account &1 for performance obligation &2 does not allow posting

FARR_CONTRACT_MAIN157 - Overview

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 157

• Message text: Derived account &1 for performance obligation &2 does not allow posting

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_CONTRACT_MAIN157 - Derived account &1 for performance obligation &2 does not allow posting ?

  The SAP error message FARR_CONTRACT_MAIN157 indicates that there is an issue with posting to a derived account for a performance obligation in the context of contract accounting or revenue recognition. This error typically arises when the derived account is not configured correctly or does not allow postings due to certain restrictions.
  
  Cause:
  
  Account Configuration: The derived account (represented by &1) may not be set up to allow postings. This could be due to settings in the chart of accounts or account type.
  Account Type Restrictions: The account may be a balance sheet account or a non-postable account type, which restricts posting transactions.
  Performance Obligation Issues: The performance obligation (represented by &2) may not be correctly linked to the derived account, or there may be issues with the status of the performance obligation.
  Authorization Issues: The user may not have the necessary authorizations to post to the derived account.
  
  
  Solution:
  
  
  Check Account Configuration:
  
  Go to the account master data