How To Fix FARR_INFLIGHT_CHECK042 - C26: No change type records for contr. modification for POB &1 contr. &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 042

• Message text: C26: No change type records for contr. modification for POB &1 contr. &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
In any case, the POB must have a corresponding record inserted into the
database table FARR_D_CHANGE_TYPE for the fiscal year and period in
which the contract change has taken place. If this entry is missing then
an error is raised.

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

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_CHECK042 - C26: No change type records for contr. modification for POB &1 contr. &2 ?

  The SAP error message FARR_INFLIGHT_CHECK042 C26 indicates that there are no change type records for a contract modification related to a specific Purchase Order (POB) and contract number. This error typically arises in the context of contract management and can occur during processes such as contract modifications or updates.
  Cause:
  
  
  Missing Change Type Records: The primary cause of this error is that the system cannot find any change type records associated with the specified contract modification. This could happen if:
  
  The contract has not been modified yet.
  The change type records were not created or were deleted.
  There is a mismatch in the data being processed (e.g., incorrect contract number or POB).
  
  
  
  Data Inconsistencies: There may be inconsistencies in the data related to the contract or the associated change types, which can lead to the system being unable to locate the necessary records.
  
  
  Configuration Issues: There might be configuration issues in the contract management module that prevent the creation or retrieval of change type records.
  
  
  Solution:
  
  
  Check Contract Modifications: Verify if there have been any modifications made to the contract. If not, you may need to create a modification before proceeding.
  
  
  Review Change Type Configuration: Ensure that the change types are correctly configured in the system. You can check the configuration settings in the SAP Customizing Implementation Guide (IMG) under:
  
  Materials Management > Purchasing > Contract Management > Define Change Types.
  
  
  
  Data Validation: Validate the data being used in the transaction. Ensure that the contract number and POB are correct and exist in the system.
  
  
  Create Change Type Records: If necessary, manually create the required change type records for the contract modification.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to contract management and change types for any specific instructions or known issues.
  
  
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant transaction codes or steps that led to the error.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME31K (Create Contract), ME32K (Change Contract), and ME33K (Display Contract) to navigate contract management effectively.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal, as there may be specific patches or updates that address this issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to diagnose and resolve the error message FARR_INFLIGHT_CHECK042 C26 effectively.