How To Fix FARR_MSG_CUSTOM020 - Multiple perf. oblig. are marked as residual in the same group (incl. &1)

FARR_MSG_CUSTOM020 - Overview

• Message type: E = Error

• Message class: FARR_MSG_CUSTOM - Customizable Messages for Revenue Accounting

• Message number: 020

• Message text: Multiple perf. oblig. are marked as residual in the same group (incl. &1)

What causes this issue?

More than one performance obligation is marked as residual in the same
group of performance obligations. Either under the same higher-level
performance obligation or under the root level of the contract, only one
performance obligation is allowed to be marked as residual.
One of such performance obligations is &V1&.

System Response

The system prevents the performance obligations from being created.

How to fix this error?

Contact your system administrator.

Procedure for System Administrators

[Editor's note: placeholder for information regarding configuration of
"residual."]
&SEE_ALSO&
For more information, see the field help of
<DS:DE.FARR_RESIDUAL_POB>Residual</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_MSG_CUSTOM020 - Multiple perf. oblig. are marked as residual in the same group (incl. &1) ?

  The SAP error message FARR_MSG_CUSTOM020 indicates that there are multiple performance obligations marked as residual within the same group. This typically occurs in the context of revenue recognition and accounting for contracts in SAP, particularly when using the SAP Revenue Accounting and Reporting (RAR) module.
  
  Cause:
  The error arises when:
  
  Multiple Performance Obligations: There are several performance obligations that are marked as residual in the same group. This can happen if the system detects that more than one obligation is set to be residual, which is not allowed.
  
  Configuration Issues: There may be issues with the configuration of the performance obligations or the way they are grouped.
  Data Entry Errors: Incorrect data entry or setup of performance obligations in the contract can lead to this error.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review Performance Obligations:
  
  Check the performance obligations associated with the contract or transaction that triggered the error.
  Ensure that only one performance obligation