How To Fix FARR_INFLIGHT_CHECK007 - C06: DEFITEM rev <> POSTING rev,Contract &1/POB &2/Cond &3

FARR_INFLIGHT_CHECK007 - Overview

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 007

• Message text: C06: DEFITEM rev <> POSTING rev,Contract &1/POB &2/Cond &3

What causes this issue?

When the deferral item in FARR_D_DEFITEM is being created, updated and
deleted, the corresponding REV_AMT_DELTA is not the same as the BETRW of
RV posting category.
Example
FARR_D_DEFITEM
Reconkey POB ID Condition
REV_AMT_DELTA
2016001000001 POB PR00,,
100.00
FARR_D_POSTING
Reconkey POB ID Condition
POSTING_CATEGORY BETRW
2016001000001 POB1 PR00 RV
120.00
Wrong!!! SUM is 300 IN DEFITEM table and POSTING table is 250

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

System Response

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

How to fix this error?

Check if there is already inconsistent data in the system
You can search for SAP Note by the term FARR_INFLIGHT_CHECK and C06, and
implement related notes

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_CHECK007 - C06: DEFITEM rev <> POSTING rev,Contract &1/POB &2/Cond &3 ?

  The SAP error message FARR_INFLIGHT_CHECK007 C06 indicates a discrepancy between the revision levels of a condition record and the associated contract or purchase order. Specifically, it suggests that the revision of the condition item does not match the revision of the posting item in the context of a contract or purchase order.
  
  Cause:
  
  
  Revision Mismatch: The error typically arises when there is a mismatch between the revision levels of the condition records and the associated contract or purchase order. This can happen if:
  
  The condition record was updated or changed after the contract or purchase order was created.
  The contract or purchase order is referencing an outdated condition record.
  
  
  
  Data Inconsistency: There may be inconsistencies in the data due to manual changes, system updates, or incorrect data entry.
  
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Condition Records:
  
  Go to the condition records in the pricing procedure and verify the revision level of the condition