Do you have any question about this error?
Message type: E = Error
Message class: FARR_INFLIGHT_CHECK -
Message number: 012
Message text: C06: Def. item rev. <> 0 despite rev. block for cond. &1 POB &2 contr. &3
This error is raised because a performance obligation with a revenue
recognition block has associated deferral items with revenue to be
recognized.
A revenue recognition block can be the result from for example:
The POB is pending review and the review reason has the 'Suspend
Posting' flag
The POB is in the error worklist
Posting revenue is manually suspended (via the UI) for that POB
This is valid for all types of POBs:
Time-based POBs
Event-based POBs
CI (customer invoice) triggered, value-relevant POBs
Given the POB has a revenue recognition block, the associated deferral
items are only checked if they have an open reconciliation key and are
associated with a non-statistical price condition.
The following special cases are also excluded from the check:
There has been a prospective splitout resulting from a contract
modification and the deferral item to be checked is affected by this
splitout. In this case the deferral item can have revenue despite of the
POB having a rev. rec. block
The deferral item in question has a deletion flag
In a case of impairment of asset, revenue is recognized immediately even
there is no fulfillment. This means that even if the POB has a revenue
recognition block, the revenue must be recognized and hence the deferral
items can have revenue to be recognized.
Example
The performance obligation POB1 has a deferral item for a scheduled
revenue of EUR 100 in the period January 2016.
Reconciliation Key,,POB ID,,Condition,,Revenue Amount Delta (EUR)
2016001000001,,POB1,,PR00,,100
At the same time, POB1 has posted revenue with a total of EUR 120 for
the same period. This is incorrect because the scheduled revenue and the
posted revenue must be equal.
Reconciliation Key,,POB ID,,Condition,,Posting Category,,Posted Revenue
in Transaction Currency (EUR)
2016001000001,,POB1,,PR00,,RV,,120
Buffers Checked
Deferral item buffer:,,MTS_DEFITEM_DATA_BUFFER
Posting data buffer:,,MT_POSTING_DATA_INST
POB data buffer:,,MTS_POB_DATA_BUFFER
The RAI processing is stopped or the manual transaction from the UI is
stopped.
You can search for SAP notes related to inflight check C06 by using the
terms FARR_INFLIGHT_CHECK and C06.
You can also check if there is inconsistent data already in the system.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
FARR_INFLIGHT_CHECK012
- C06: Def. item rev. <> 0 despite rev. block for cond. &1 POB &2 contr. &3 ?The SAP error message FARR_INFLIGHT_CHECK012 C06 indicates that there is a discrepancy in the revenue recognition process for a specific condition item in a contract. The message states that the defined item revenue is not equal to zero, even though there is a revenue block in place for the specified condition.
Cause:
This error typically arises in the context of contract accounting or revenue recognition processes, particularly when dealing with condition items in contracts. The possible causes include:
Revenue Block Misconfiguration: The revenue block may not be correctly set up for the condition item, leading to the system expecting the revenue to be zero but finding a non-zero value instead.
Incorrect Condition Item Settings: The condition item may have been incorrectly configured, leading to unexpected revenue postings.
Data Inconsistencies: There may be inconsistencies in the data related to the contract, such as incorrect postings or updates that have not been properly reflected in the system.
Timing Issues: The error may occur if there are timing issues with the revenue recognition process, such as trying to recognize revenue before the conditions for recognition are met.
Solution:
To resolve this error, you can take the following steps:
Check Revenue Block Settings: Verify the configuration of the revenue block for the condition item in question. Ensure that it is correctly set up to prevent revenue recognition.
Review Condition Item Configuration: Check the settings for the condition item in the contract. Ensure that it is configured correctly and that it aligns with the intended revenue recognition rules.
Analyze Contract Data: Review the contract data for any inconsistencies or errors. Look for any postings that may not have been processed correctly.
Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the error message and the related configuration settings.
Test in a Development Environment: If possible, replicate the issue in a development or test environment to better understand the cause and test potential solutions without affecting production data.
Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. Provide them with the error message details and any relevant context.
Related Information:
FARR
(for contract accounting) and FBL1N
(for vendor line items) that may help in troubleshooting.By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FARR_INFLIGHT_CHECK011
C0501: Incorrect latest flag for condition &3 for POB &2 in contract &1
What causes this issue? The deferral item with the LATEST_DEFITEM flag is not in the largest reconciliation key in the deferral item table FARR_D_DEF...
FARR_INFLIGHT_CHECK010
C09: Alloc Amt &3 <> DEFITEM Amt &4, Contract &1/POB &2
What causes this issue? Sum of DOC_AMT_CUMULATE + PRO_AMT_CUMULATE in the deferral item(FARR_D_DEFITEM) with latest deferral item(LATEST_DEFITEM) on ...
FARR_INFLIGHT_CHECK014
C13: Invoice Amt <> POSTING IC, Contract &1/POB &2
What causes this issue? Invoice amount to be updated in the FARR_D_INVOICE is not the same as the invoice correction posting entries in FARR_D_POSTI...
FARR_INFLIGHT_CHECK015
C15: No DEFITEM found, Contract &1/POB &2
What causes this issue? A POB that is not listed in the following case shall always have a deferral item: -,,Soft deleted -,,marked to be deleted -,,...
Click on this link to search all SAP messages.