How To Fix FARR_INFLIGHT_CHECK041 - C26: Contract modification error occured for POB &1 in contract &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 041

• Message text: C26: Contract modification error occured for POB &1 in contract &2

What causes this issue?

Contract change can either be:
Contract modification
Change of estimates.
Depending on the Customizing (
<DS:SIMG.FARR_VC_ACCT_PR>Configure Accounting Principle-specific
Settings</>) for a company code and accounting principle, one or the
other is applied when the scope of a contract is changed.
The change mode for a POB is determined by the field CHANGE_MODE (only
in the buffer, not written to database) and can be one of the following:
'P' or 'V' prospective change
'R' retrospective change
' ' (empty) no change
Prospective change
When a POB has change mode 'P' or 'V', then it must also have the
following flag:
HAS_PRO_CHANGE = X
unless it is newly created (CRT_FLAG = X). The POB must also have a
corresponding record inserted into the database table FARR_D_CHANGE_TYPE
with the following flag:
PRO_EFFECTED = X
again, unless it is newly created.

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

Retrospective change
When a POB has change mode 'R', then the field HAS_PRO_CHANGE must be
empty.
The POB must also have a corresponding record inserted into the database
table FARR_D_CHANGE_TYPE with the field PRO_EFFECTED being empty.
Negative example:
The performance obligation POB1 has a prospective change but the field
CHANGE_MODE determines a retrospective change.
POB ID,,CHANGE_MODE,,HAS_PRO_CHANGE
POB1,,R,,X
The check is not performed for POBs with CHANGE_MODE = ' '.
Buffers checked:
POB data buffer : MTS_POB_DATA_BUFFER
Change type data buffer: MTS_CHANGE_TYPE_BUFFER

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

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_CHECK041 - C26: Contract modification error occured for POB &1 in contract &2 ?

  The SAP error message FARR_INFLIGHT_CHECK041 C26 indicates that there is a contract modification error related to a Purchase Order (POB) in a specific contract. This error typically arises during the processing of contract modifications in the SAP system, particularly in the context of the SAP Flexible Real Estate Management (RE-FX) module or similar contract management scenarios.
  Cause:
  The error can be caused by several factors, including but not limited to:
  
  Inconsistent Data: There may be inconsistencies in the data related to the contract or the purchase order, such as missing or incorrect information.
  Locked Objects: The contract or related objects may be locked by another user or process, preventing modifications.
  Validation Rules: The system may have validation rules that are not being met due to the changes being attempted.
  Status Issues: The contract or purchase order may be in a status that does not allow for modifications (e.g., completed or archived).
  Dependencies: There may be dependencies on other objects or transactions that are not satisfied.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Check Data Consistency: Review the contract and purchase order data for any inconsistencies or missing information. Ensure that all required fields are filled out correctly.
  Unlock Objects: If the contract or related objects are locked, check with your system administrator or the user who has locked the object to unlock it.
  Review Validation Rules: Check if there are any specific validation rules that need to be satisfied for the modification to proceed. Adjust the data accordingly.
  Check Status: Verify the status of the contract and purchase order. If they are in a status that does not allow modifications, you may need to change the status or create a new contract.
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional guidance.
  Contact Support: If the issue persists, consider reaching out to SAP support or your internal IT team for further assistance.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as ME32K (Change Contract) or ME33K (Display Contract) to review and modify contracts.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Authorizations: Ensure that you have the necessary authorizations to modify contracts in the system.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.