Do you have any question about this error?
Message type: E = Error
Message class: FARR_INFLIGHT_CHECK -
Message number: 052
Message text: C26: Incorrect pro. split amount on def. items 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
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, that represents the revenue amount posted in periods
prior to the current change, is stored on all deferral items beginning
from the period in which the contract change was performed.
The example below illustrates this:
RECON_KEY,,POB_ID,,CONDITION_TYPE,,REV_QTY_DELTA,,REV_QTY_POSTED,,
PRO_QTY_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 on the last deferral item in the contract change
period (here 2018/03) deviates from the split amount on the latest
deferral item, a C26 inflight check 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 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_CHECK052
- C26: Incorrect pro. split amount on def. items for POB &1 in contract &2 ?The SAP error message FARR_INFLIGHT_CHECK052 C26 indicates that there is an issue with the distribution of amounts in a contract related to a Purchase Order (POB). Specifically, it suggests that the amount split for the defined items in the contract does not match the expected values.
Cause:
The error typically arises due to one or more of the following reasons:
Incorrect Amount Distribution: The amounts allocated to the defined items in the contract do not match the expected or required distribution. This could be due to manual entry errors or incorrect calculations.
Contract Configuration Issues: There may be issues with how the contract is set up, including incorrect settings for the pricing conditions or the way the items are defined.
Changes in Contract Terms: If there have been recent changes to the contract terms or conditions, it may lead to discrepancies in the amount split.
Incomplete Data: Missing or incomplete data in the contract or related documents can also trigger this error.
Solution:
To resolve the error, you can take the following steps:
Review the Contract: Check the contract referenced in the error message (contract &2) and ensure that the amount split for the defined items (POB &1) is correct. Verify that the amounts are distributed according to the terms of the contract.
Adjust Amounts: If you find discrepancies, adjust the amounts in the contract to ensure they match the expected values. This may involve recalculating the amounts based on the contract terms.
Check Configuration: Review the configuration settings for the contract and ensure that they are set up correctly. This includes checking pricing conditions and item definitions.
Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling this error. There may be additional notes or updates related to this error message.
Test Changes: After making adjustments, test the changes to ensure that the error is resolved and that the contract processes correctly.
Seek Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the error message FARR_INFLIGHT_CHECK052 C26.
Get instant SAP help. Start your 7-day free trial now.
FARR_INFLIGHT_CHECK051
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 a...
FARR_INFLIGHT_CHECK050
C02: TRX price (defitem) &4 <> scheduled rev. &3 for cond. &2 for POB &1
What causes this issue? The sum of DOC_AMT_CUMULATE and PRO_AMT_CUMULATE for latest deferral items for a condition type is not equal to the sum of RE...
FARR_INFLIGHT_CHECK053
C26: Qty from pro. split inconsistent with fulf. qty 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_CHECK054
C27: Scheduled revenue &1 <> posted revenue &2 for cond. &3 for POB &4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.