Liquidity Planner - FLQAF - different logic

Hi,

I'm facing the following case. After activating FIN_FSCM_LP_DCF of Business Function FIN_GL_DIR_CASHFLOW (oss note 1826731), new t-code FLQAF for item evaluation became available. At the same time, old t-codes FLQAC and FLQAF became obsolete and it's possible to execute them in test mode only. However, the logic of FLQAF is different than FLQAD.

Example:

1 - vendor invoice:

31     vendor X           2 460

40     inf account 1      1 800     liquidity item A

40     inf account 2        200     liquidity item A

40     VAT                  460     liquidity item VAT

2 - credit note

21     vendor X           1 230

50     inf account 1        600     liquidity item B (due to specific field values)

50     inf account 2        400     liquidity item A

50     VAT                  230     liquidity item VAT

3 - payment

25     vendor X           1 230

50     cash in transit    1 230

4 - bank reconciliation

50     bank               1 230

40     cash in transit    1 230

Now, FLQAD shows the following:

liquidity item A          1 600-

liquidity item B            600

VAT                         230-

whereas FLQAF shows:

liquidity item A          1 000-

VAT                         230-

which is incorrect.

Function module FLQ_OFFSETTING_TECH returns table T_OFFSET which contains offset items for specific cleared item in the documents chain. For payment document item 1 (25 - vendor X - 1 230), it finds both vendor invoice and credit note. However, it distributes them between two internal tables (one with debit items, the other one with credit items). At some point their contents look like this:

LT_HI:

Document number     Acct type     Dt/Ct     Amount

<payment>           K             Dt        1 230

<credit note>       K             Dt        1 230

LT_LO:

<invoice>           K             Ct        2 460

At this point document chain is complete but for some reason in the next step, another table LT_PAIR is created. It contains the following entries (pairs):

<payment>          <invoice>     1 230

<credit note>      <invoice>     1 230

In the following step, 2nd entry is deleted (why?) and therefore only one entry remains in table T_OFFSET:

<invoice>          Ct            1 230

As a result, it looks as if payment document cleared partially the invoice, which is not true. Information about credit note is lost and liquidity items aren't derived correctly.

Has anyone of you met such a case? It looks like some wrong logic which should be fixed by SAP.

Kind regards,

Tomek