How To Fix FARR_INFLIGHT_CHECK050 - C02: TRX price (defitem) &4 <> scheduled rev. &3 for cond. &2 for POB &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 050

• Message text: C02: TRX price (defitem) &4 <> scheduled rev. &3 for cond. &2 for POB &1

What causes this issue?

The sum of DOC_AMT_CUMULATE and PRO_AMT_CUMULATE for latest deferral
items for a condition type is not equal to the sum of REV_AMT_DELTA for
the same condition type. This check is relevant for the following
performance obligations:
Time-based POB
Event-based POB with fully fulfilled status
Customer Invoice (CI) with value relevant and final invoice status
Example
There is a time-based POB with two condition types that spans three
periods. The revenue spreading is listed as follows:
Period ,,CONDITION_TYPE ,,DOC_AMT_CUMULATE ,,PRO_AMT_CUMULATE,,
REV_AMT_DELTA,,LATEST_DEFITEM,,
01 ,,PR00,,0.80,,0,,0.40,,,,
02,,PR00,,0.40,,0.40,,0.40,,,,
02 ,,CORR ,,-0.40,,0,,-0.40,,,,
03,,PR00,,0.40,,0.40,,0.40,,X,,
03 ,,CORR,,-0.40,,0,,-0.40,,X,,

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

<ZK>Sum revenue for the latest deferral items DOC_AMT_CUMULATE +
PRO_AMT_CUMULATE:</>
CONDITION_TYPE DOC_AMT_CUMULATE PRO_AMT_CUMULATE
PR00: 0.40 + 0.40 = 0.80 for latest deferral items
CORR: - 0.40 + 0 = - 0.40 for latest deferral items
<ZK>The total of REV_AMT_DELTA for all deferral items:</>
CONDITION_TYPE Sum (REV_AMT_DELTA)
PR00: 0.40 + 0.40 + 0.40 = 1.20
CORR: -0.40 + (-0.40) = -0.80
Sum revenue for the latest deferral items DOC_AMT_CUMULATE +
PRO_AMT_CUMULATE is not equal to the total of REV_AMT_DELTA for all
deferral items.
Exceptional Cases
The check will not be performed for the following cases:
Suspend from posting
Pending conflict
Error status in worklist
Overfulfilled event-based POB
Buffers Checked
Deferral item buffer: MTS_DEFITEM_NSTAT_PRICE
Performance obligation buffer: MTS_POB_DATA_BUFFER
Fulfillment Buffer: MTS_FULFILLMENT_BUFFER

System Response

The RAI processing is stopped or the manual transaction from the UI is
stopped.

How to fix this error?

You can search for SAP Notes related to Inflight Check C02 by using the
terms FARR_INFLIGHT_CHECK and C02.
You can check if there is inconsistent data already in the system.

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_INFLIGHT_CHECK050 - C02: TRX price (defitem) &4 <> scheduled rev. &3 for cond. &2 for POB &1 ?

  The SAP error message FARR_INFLIGHT_CHECK050 C02 typically occurs in the context of the SAP Revenue Accounting and Reporting (RAR) module. This error indicates a discrepancy between the transaction price (defitem) and the scheduled revenue for a specific condition in a Point of Balance (POB).
  Cause:
  The error arises when the system detects that the transaction price for a specific condition does not match the scheduled revenue amount. This can happen due to several reasons, including:
  
  Data Entry Errors: Incorrect data entry during the creation of the transaction or conditions.
  Changes in Pricing: Changes made to pricing conditions after the transaction has been created, leading to inconsistencies.
  Configuration Issues: Incorrect configuration in the pricing procedure or revenue recognition settings.
  Incomplete Data: Missing or incomplete data in the relevant master data or transaction data.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Verify Transaction Data: Check the transaction data for the specific POB and ensure that the transaction price and scheduled revenue are correctly entered and match each other.
  
  
  Review Pricing Conditions: Look into the pricing conditions associated with the transaction. Ensure that the conditions are set up correctly and that there are no discrepancies.
  
  
  Check for Changes: If there have been recent changes to pricing or conditions, ensure that these changes have been properly reflected in the transaction.
  
  
  Adjust Scheduled Revenue: If the transaction price is correct, you may need to adjust the scheduled revenue to match the transaction price.
  
  
  Consult Configuration: If the issue persists, consult with your SAP configuration team to review the pricing procedure and revenue recognition settings to ensure they are set up correctly.
  
  
  Use Transaction Codes: Utilize relevant transaction codes (like FARR for Revenue Accounting) to analyze the data and identify discrepancies.
  
  
  SAP Notes and Documentation: Check for any SAP Notes related to this error message for additional guidance or patches that may address the issue.
  
  
  Related Information:
  
  SAP RAR Documentation: Familiarize yourself with the SAP Revenue Accounting and Reporting documentation for a better understanding of pricing and revenue recognition processes.
  Transaction Codes: Common transaction codes related to RAR include FARR (Revenue Accounting) and FARR1 (Revenue Recognition).
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify and resolve the cause of the error message FARR_INFLIGHT_CHECK050 C02.