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
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 changeThe RAI processing is stopped or the manual transaction from the UI is
stopped.
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.
Error message extract from SAP system. Copyright SAP SE.
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
Get instant SAP help. Sign up for our Free Essentials Plan.
FARR_INFLIGHT_CHECK040
C25: Source of Price flag is incorrect for POB &1 in contract &2
What causes this issue? A POB must have the source of price (SOURCE_OF_PRICE) flag if it has a latest deferral item for a main price and whenever a p...
FARR_INFLIGHT_CHECK039
C25: Source of Price flag is missing for POB &1 in contract &2
What causes this issue? A POB must have the source of price (SOURCE_OF_PRICE) flag if it has a latest deferral item for a main price and whenever a p...
FARR_INFLIGHT_CHECK042
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_...
FARR_INFLIGHT_CHECK043
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_...
Click on this link to search all SAP messages.