How To Fix FARR_CONTRACT_MAIN748 - The new condition type &1 for perf. oblig. &2 does not exist in RevAcc.

FARR_CONTRACT_MAIN748 - Overview

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 748

• Message text: The new condition type &1 for perf. oblig. &2 does not exist in RevAcc.

What causes this issue?

The new condition type &v1& for performance obligation &v2& does not
exist in Revenue Accounting. Normally new condition types should be
passed from <ZK>IT_COND_TYPE_NEW</>. It will be ignored automatically If
it comes from <ZK>IT_COND_TYPE_UPD</>.

System Response

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

How to fix this error?

Contact system administer.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_CONTRACT_MAIN748 - The new condition type &1 for perf. oblig. &2 does not exist in RevAcc. ?

  The SAP error message FARR_CONTRACT_MAIN748 indicates that there is an issue with a condition type related to a performance obligation in the Revenue Accounting and Reporting (RAR) module. Specifically, the error states that the new condition type specified does not exist in the Revenue Accounting configuration.
  
  Cause:
  
  Missing Condition Type: The condition type referenced in the error message (&1) is not defined in the Revenue Accounting configuration for the performance obligation (&2).
  
  Configuration Issues: There may be a misconfiguration in the RAR settings, where the condition type is expected but not set up correctly.
  Data Entry Error: There could be a typo or incorrect entry when creating or modifying the performance obligation or related conditions.
  
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the RAR configuration settings in SAP.
  Verify if the condition type mentioned in the error message exists in the system.
  If it does not exist, you may need to create it or adjust the configuration to include