How To Fix FARR_INFLIGHT_CHECK043 - C26: Multiple change type records for contr. mod. for POB &1 contr. &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 043

• Message text: C26: Multiple change type records for contr. mod. 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 only one corresponding record in the
database table FARR_D_CHANGE_TYPE for the fiscal year and period in
which the contract change has taken place. If more than one entry is
found 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_CHECK043 - C26: Multiple change type records for contr. mod. for POB &1 contr. &2 ?

  The SAP error message FARR_INFLIGHT_CHECK043 C26 indicates that there are multiple change type records for a contract model associated with a particular Purchase Order (POB) and contract. This typically occurs in the context of contract management within SAP, particularly when dealing with contract modifications or changes.
  Cause:
  The error is usually caused by one of the following scenarios:
  
  Duplicate Change Records: There are multiple entries in the system for the same contract model and contract number, which can happen due to incorrect data entry or system errors.
  Inconsistent Data: The system may have inconsistent or conflicting data regarding the change types associated with the contract.
  Concurrent Modifications: If multiple users are trying to modify the same contract simultaneously, it can lead to this error.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check for Duplicate Records:
  
  Use transaction codes like SE16 or SE11 to check the relevant database tables (e.g., FARR_CONTRACT or similar) for duplicate entries related to the contract model and contract number.
  If duplicates are found, you may need to delete or correct the unnecessary entries.
  
  
  
  Review Change Logs:
  
  Check the change logs for the contract to identify any recent modifications that may have led to this issue.
  Ensure that all changes are valid and consistent.
  
  
  
  Data Consistency Check:
  
  Run any available consistency checks in the SAP system to identify and rectify any inconsistencies in the contract data.
  
  
  
  Locking Mechanism:
  
  Ensure that proper locking mechanisms are in place to prevent concurrent modifications to the same contract by multiple users.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking for duplicates and inconsistencies, consider reaching out to SAP support for further assistance. They may provide patches or additional troubleshooting steps.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME33K (Display Contract), ME32K (Change Contract), and SE16 (Data Browser) for checking contract details.
  Documentation: Review SAP documentation related to contract management and error handling for more insights.
  User Roles: Ensure that users have the appropriate roles and authorizations to make changes to contracts to avoid unauthorized modifications.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.