How To Fix FARR_INFLIGHT_CHECK053 - C26: Ctd.de div.pr.inconsistente p.ct.dcompl.p.obl.prest.&1 contr.&2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INFLIGHT_CHECK -

• Message number: 053

• Message text: C26: Ctd.de div.pr.inconsistente p.ct.dcompl.p.obl.prest.&1 contr.&2

¿Qué causa este problema?

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 quantity, that represents the revenue quantity 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
201801001,,POB1,,PR00,,2,,0,,0,,-,,-
201802001,,POB1,,PR00,,2,,2,,0,,-,,-
201803001,,POB1,,PR00,,2,,4,,0,,-,,-
201804001,,POB1,,PR00,,2,,6,,0,,-,,-
201805001,,POB1,,PR00,,2,,2,,8,,X,,X

El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.

In this example, a contract modification was performed in period
2018/05. Therefore the split quantity (PRO_QTY_CUMULATE) is calculated
and the prospective split flag set. The split quantity has to be equal
to the total reported quantities from all non-pending fulfillment
entries in periods prior to that of the current contract change.
Continuing the example above, consider the following fulfillment table:
RECON_KEY,,POB_ID,,,,REPORTED_QTY,,FULFILL_STATUS
201801001,,POB1,,2,,-,,
201802001,,POB1,,2,,-,,
201803001,,POB1,,2,,-,,
201804001,,POB1,,2,,-,,
201805001,,POB1,,2,,-,,
Since in this example, the contract modification took place in period
2018/05, the split quantity (in this case PRO_QTY_CUMULATE = 8) must be
equal to the total reported quantites from the fulfillments from all
periods prior to period 5 (in this case periods 1-4 in 2018).
If the split quantity is not consistent with the fulfillment quantities,
a C26 inflight check error is raised.

Respuesta del sistema

The RAI processing is stopped or the manual transaction from the UI is
stopped.

¿Cómo arreglar este 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.

Procedimiento para Administradoras de Sistemas

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.