How To Fix FARR_INFLIGHT_CHECK025 - C19: New defitem create 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: 025

• Message text: C19: New defitem create in closed key &1 contr &2 POB &3 cond. type &4

What causes this issue?

In RAR, defitem with closed reconekey shall not be
created/updated/deleted.

System Response

The RAI processing is stopped or manual interaction is stoppted.

How to fix this error?

You can search for SAP Note by the term FARR_INFLIGHT_CHECK and C19, and
implement related notes

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_CHECK025 - C19: New defitem create in closed key &1 contr &2 POB &3 cond. type &4 ?

  The SAP error message FARR_INFLIGHT_CHECK025 typically occurs in the context of the SAP Flexible Real Estate Management (RE-FX) module, particularly when dealing with contract management and condition types. This error indicates that there is an attempt to create a new condition item (defitem) in a closed contract or key date, which is not allowed.
  Cause:
  The error message is triggered when:
  
  You are trying to create or modify a condition item for a contract that is already closed.
  The key date specified for the operation is in the past or corresponds to a closed period for the contract.
  The condition type being used does not allow changes after the contract has been closed.
  
  Solution:
  To resolve this error, consider the following steps:
  
  
  Check Contract Status: Verify the status of the contract (key &2) you are trying to modify. If it is closed, you will need to either:
  
  Reopen the contract if your business process allows it.
  Create a new contract or condition item instead of modifying the closed one.
  
  
  
  Review Key Date: Ensure that the key date (&1) you are using for the operation is valid and corresponds to an open period. If it is in the past or corresponds to a closed period, you will need to adjust it.
  
  
  Condition Type Restrictions: Check the configuration of the condition type (&4) to see if it allows changes after the contract is closed. If it does not, you may need to use a different condition type or follow a different process for handling closed contracts.
  
  
  Consult Documentation: Review the SAP documentation or consult with your SAP support team for specific guidelines related to the RE-FX module and the handling of closed contracts.
  
  
  Error Logs: Check the application logs for more detailed information about the error, which may provide additional context or related issues.
  
  
  Related Information:
  
  SAP Notes: Look for relevant SAP Notes that may address this specific error or provide updates and patches.
  Transaction Codes: Familiarize yourself with transaction codes related to contract management in RE-FX, such as:
  
  RECN: Contract Management
  REIS: Real Estate Information System
  
  
  User Exits and BAdIs: If you have custom logic implemented, check if there are any user exits or BAdIs that might be affecting the behavior of contract modifications.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution. If the issue persists, consider reaching out to SAP support for further assistance.