How To Fix FARR_INFLIGHT_CHECK006 - C0502: Multi latest flags found,Contract &1/POB &2/Cond &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 006

• Message text: C0502: Multi latest flags found,Contract &1/POB &2/Cond &3

What causes this issue?

There are more than 1 entry for each POB and each condition with the
LATEST_DEFITEM in the FARR_D_DEFITEM.
Example
Reconkey POB ID Condition
DOC_AMT_CUM LATEST_DEFITEM
2015012000001 POB1 PR00
100.00,,
2016001000001 POB1 PR00
100.00 X (WRONG!!!)
2016002000001(biggest) POB1 PR00 100.00
X (WRONG!!!)

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 C0502,
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_CHECK006 - C0502: Multi latest flags found,Contract &1/POB &2/Cond &3 ?

  The SAP error message FARR_INFLIGHT_CHECK006 C0502: Multi latest flags found, Contract &1/POB &2/Cond &3 typically occurs in the context of contract management or condition records in SAP, particularly when dealing with pricing conditions or agreements. This error indicates that there are multiple entries marked as the "latest" for a specific condition, which creates ambiguity in the system.
  
  Cause:
  
  Duplicate Latest Flags: The primary cause of this error is that there are multiple condition records for the same contract and Purchase Order (POB) that are marked as the latest. This can happen due to incorrect data entry or system inconsistencies.
  Data Inconsistencies: If the data in the condition records is not properly maintained or if there are issues during data migration or updates, it can lead to multiple records being flagged as the latest.
  
  Configuration Issues: Sometimes, the configuration settings in the pricing procedure or condition types may lead to this issue if not set