How To Fix FARR_INFLIGHT_CHECK051 - C26: Amt. fr. prospective split is inconsistent for POB &1 in contract &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 051

• Message text: C26: Amt. fr. prospective split is inconsistent for POB &1 in contract &2

What causes this issue?

Contract change can either be:
?Contract modification
?Change of estimates.

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

Depending on the Customizing ( 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
In case of a prospective change the system performs a prospective split
on the deferral items. The deferral item which corresponds to an open
reconciliation key in the period of the contract change is flaged with
the prospective split flag (PRO_SPLIT = 'X').
The split amount represents the revenue amount posted plus the scheduled
revenue amount from the period prior to the current change.
The example below illustrates this:
RECON_KEY,,POB_ID,,CONDITION_TYPE,,REV_AMT_DELTA,,REV_AMT_POSTED,,
PRO_AMT_CUMULATE,,HAS_PRO_SPLIT,,LATEST_DEFITEM
201802001,,POB1,,PR00,,1000.00,,0.00,,0.00,,-,,-
201803001,,POB1,,PR00,,1000.00,,1000.00,,0.00,,-,,-
201803002,,POB1,,PR00,,- 500.00,,1000.00,,1000.00,,X,,-
201804001,,POB1,,PR00,,1000.00,, 500.00,,1000.00,,-,,-
201805001,,POB1,,PR00,,1000.00,,1500.00,,1000.00,,-,,X
In this example, a contract modification was performed in period
2018/03. Therefore the split amount is calculated and the prospective
split flag set. All deferral items, beginning from the contract change
period, are updated with the split amount (PRO_AMT_CUMULATE).
If the split amount is not the total of the posted and scheduled revenue
from the previous period (not necessarily previous reconciliation key!),
a C26 inflight check error is raised.

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_CHECK051 - C26: Amt. fr. prospective split is inconsistent for POB &1 in contract &2 ?

  The SAP error message FARR_INFLIGHT_CHECK051 C26 indicates that there is an inconsistency in the amount for a prospective split in a contract. This typically occurs in the context of contract management and financial accounting, particularly when dealing with contracts that involve multiple parties or split payments.
  Cause:
  The error message is triggered when the system detects that the amount specified for a prospective split does not match the expected values based on the contract's configuration or the amounts already defined in the system. This can happen due to several reasons, including:
  
  Incorrect Amounts: The amounts entered for the prospective split do not align with the total amount of the contract or the amounts already allocated to other splits.
  Contract Configuration Issues: There may be issues with how the contract is set up, such as missing or incorrect data related to the split.
  Data Entry Errors: Manual entry errors when inputting amounts for splits can lead to inconsistencies.
  Changes in Contract Terms: If the contract terms have been modified after the initial setup, it may lead to discrepancies in the amounts.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Review Contract Details: Check the contract referenced in the error message (contract &2) and ensure that all amounts related to the prospective split (POB &1) are correctly defined and consistent.
  Verify Amounts: Ensure that the amounts for the prospective split match the total contract amount and any other related splits. Adjust any discrepancies.
  Check Configuration: Review the configuration settings for the contract to ensure that they are set up correctly for splits.
  Data Entry Validation: If the amounts were entered manually, double-check for any typographical errors or incorrect values.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on handling contract splits and prospective amounts.
  Test Changes: After making adjustments, test the changes in a development or test environment before applying them to the production system.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like FARR (Contract Management) or FBL1N (Vendor Line Item Display) to review contract details and line items.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  Support: If the issue persists after following the above steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify and correct the inconsistency causing the error message.