How To Fix FARR_INFLIGHT_CHECK027 - C19: Defitem changed in closed key &1 contr &2 POB &3 cond. type &4

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 027

• Message text: C19: Defitem changed in closed key &1 contr &2 POB &3 cond. type &4

What causes this issue?

A deferral item in a closed reconciliation key is not
created/updated/deleted.
Example
The system wants to update a deferral item of the performance obligation
with ID 1234. This deferral item has reconciliation key 201601000001.
Contract ID,,POB ID,,Reconciliation Key,,Creation Flag,,Update Flag,,
Deletion Flag
001,,1234,,201601000001,,,,X,,
You can see in the reconciliation key table that this key is already
closed (status = 'C'). A closed reconciliation key is invalid for a
deferral item which is to be updated.
Contract ID,,Reconciliation Key,,Status
001,,201601000001,,C
Exceptional cases
You can delete the non-transferred deferral item of a time-based
performance obligation (TM_CONVERT = false) when the reconciliation key
status is set to Migration.
You can delete the deferral item of a performance obligation with
deletion flag DEL_FLAG = true, provided that no invoices have been
issued and no revenue has been recognized for this performance
obligation, yet.
You can change the latest entry flag of the deferral item.
You can change DOC_AMT_DELTA.
If the fulfillment is pending, you can change REV_QTY_POSTED as well as
the numerator and/or denominator.
For a changed deferral item, the corresponding reconciliation key is in
a later period than the end date of the time-based performance
obligation.
If all amounts for a deferral item are zero, the check will not be
performed.
Buffers Checked
Deferral item:,,MTS_DEFITEM_DATA_BUFFER
POB data buffer:,,MTS_POB_DATA_BUFFER
Fulfillment buffer:,,MTS_FULFILLMENT_PENDING

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 C19 by using the
terms FARR_INFLIGHT_CHECK and C19.
You can also check if there is inconsistent data already in the system.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_INFLIGHT_CHECK027 - C19: Defitem changed in closed key &1 contr &2 POB &3 cond. type &4 ?

  The SAP error message FARR_INFLIGHT_CHECK027 typically indicates that there has been a change to a definitive item (Defitem) in a closed key date, which is causing a conflict in the system. This error is often related to the processing of financial documents, particularly in the context of contract management or condition types in SAP.
  Cause:
  
  Change in Closed Document: The error arises when there is an attempt to modify a definitive item in a document that has already been closed. This could happen if someone tries to update or change a condition type or other related data after the document has been finalized.
  Inconsistent Data: The system detects that the data being modified is inconsistent with the current state of the document, leading to this error message.
  Contract Management Issues: It may also relate to issues in contract management where the contract has been closed, but there are attempts to make changes to it.
  
  Solution:
  
  Review Changes: Check the changes that are being attempted on the definitive item. Ensure that you are not trying to modify a closed document. If changes are necessary, consider reopening the document if your business process allows it.
  Consult with Stakeholders: If the change is essential, consult with relevant stakeholders (e.g., finance, contract management) to understand the implications of reopening a closed document.
  Use Transaction Codes: Utilize transaction codes like VA02 (Change Sales Order) or ME22N (Change Purchase Order) to review the document and its status.
  Check Configuration: Ensure that the configuration settings for the condition types and contract management are correctly set up to prevent such issues in the future.
  SAP Notes: Check for any relevant SAP Notes or updates that may address this specific error. Sometimes, SAP releases patches or notes that provide solutions or workarounds for known issues.
  
  Related Information:
  
  Documentation: Refer to SAP documentation for detailed information on condition types and contract management processes.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Support: If the issue persists, consider reaching out to SAP support for assistance, providing them with the error message details and the context in which it occurs.
  
  By following these steps, you should be able to address the error message FARR_INFLIGHT_CHECK027 effectively.