Skip to Content

Liquidity Planner Configuration

Liquidity planning in the sense of Liquidity Planner is the medium term planning (usually covering one year) of incoming and outgoing payments (in other words actual cash flows) in the original currency.

In the operative R/3 system, the liquidity calculation gets actual data for the amount, the use and the origin of payments.


Example:


02-03-2016 13-37-58.jpg


In Procure to Pay Process, the Vendor sends an Invoice (1a), you pay it (2a) and the process is finished with the Bank Statment (3a).


Configuration


IMG: Financial Supply Chain Management -> Cash and Liquidity Management -> Liquidity Planner



1. Create Liquity Item


Tx: FLQC1


A liquidity item stands for the actual origin or use of a payment (for example, incoming payment from sales or payment for salary).

It represents a:


  • Expense or Revenue
  • Vendor / Customer (only GL Accounts)
  • Taxes (If you want to open taxes in a document)
  • Other GL Accounts (ie: GR/IR Account, clearing accounts, others


02-03-2016 14-04-34.jpg


2. Set Global Data for Company Code


Tx: FLQC2


In this step you define FSCM-LP parameters for the Client. It is not possible to configure by Company Code.


  • Liquidity Items to use when no position could be assigned.   (N.Assign.In.Pmt , N.Assign.Out.Pmt)
  • Liquidity Items for default Incoming and Outgoing Cash.              
                           When the Liquidity Item has been identified as Incoming or Outgoing but can’t reach the next level. It’s on the Bank Statement Level.
  • Posting Date.   Use Posting Date instead of Value Date for the calculation
  • 3rd Currency    Another Currency for Analysis


02-03-2016 14-34-12.jpg

3. Add additional Real Accounts (Bank Accounts)


Tx: FLQC4


Liquidity Planner Real Accounts are GL Accounts taken from T012K table (Tx FI12) 

In case you need to add/exclude Real Accounts form the Liquidity Planner Analysis, you have to add them here


02-03-2016 14-40-24.jpg


4. Activate Company Code


Tx: FLQC3


Activate the funcionality of Liquidity Planner in the Company Code.

You will need Cash Management and Forecast Number Range for the company code (tx OT20)


04-03-2016 08-13-29.jpg


5. Settings for FI Mechanisms


tx: FLQC13


Configure how Liquitiy Planner will reconstruct FI document chain (from Bank Statement to Invoice)


  • Part Reassign:   Consider partial payments or “part of the payment line item is reassigned in cases where the payment amount is not fully covered”
  • N:M Treatment:  If various actual positions (N – Bank) are related to variuos vendor/customer positions ( M ), the system can reconstruct the information with artificial possitions
  • Inc.Transfer:       Bank Incoming for N:M Treatment
  • Out.Transfer:      Bank Outcoming for N:M Treatment
  • Info Accts in Appl:    Information for Accounts is maintained in each systema (tx FLQINFACC)
  • Down Pmt no-End:   In Downpayments, the system still tries to go to he expense/income generated by the payment.
  • Eval. Intermed.Stat:  In GL Accounts with “Line item Management” (tx FS00), if you set the further indicator for the GL Account in tx FLQINFACC , the system continues searching for the clearing account (i.e: GR/IR Accounts)


  • Reduction of Document Cluster in FI:  You can add exits, for example display invoice tax or withdholding tax (Pre EHP7) . sap note 994316, 1091325, 1092506

04-03-2016 07-50-40.jpg

5.1 Settings for FI mechanism EhP7 with Business Function FIN_GL_DIR_CASHFLOW

tx: FLQC13F

In ECC 6 EhP7 a new BF is available to display taxes (Separate Tax) and brings the possibility to incorpore new fields in LP Analiisys –

Additional Fields in Liquidity Planner .

04-03-2016 07-51-20.jpg

6. Create Accounts with assignment information


tx: FLQINFACC


Configure Liquidity Positions by assignning  the corresponding GL Accounts. All GL Accounts (except Bank Accounts) are listed here; vendor,customer, tax, expenses, incomes, clearing, etc

04-03-2016 08-22-14.jpg


7. Create Liquidty Information


tx: FLQAD  – pre EhP7

tx: FLQAF   – EhP7 with BF FIN_GL_DIRCASHFLOW active


The last step is to create Liquity Information

04-03-2016 07-53-01.jpg


“Query Sequence” is a step analysis for the line item where you set up conditions which wil redirect the natural flow of the Liquidity Item to a new Liquidity Item choosed by you.

The “1st Derivation Step” generally considers the payment document (Vendor/Customer objects).

The “2nd Derivation Step” generally considers the invoice (G/L Account).

You have to define a query sequence (tx FLQQC5 or FLQQD5) which contains all queries for the corresponding step (tx FLQQC1 or FLQQD1).

The “Buffer Item” is the intermediate position for the payment and the invoice, in general Customer/Vendor reconciliation account

The “Exit Module” contains user exits for each step where you can add liquity item information ( Additional Fields in Liquidity Planner ).


You can use additional selection parameters to analyze the Liquidity Item.

04-03-2016 07-53-49.jpg


You can run in Test or with “Detail List” to analyze the liquidty item flow. In EhP7 you have a new radio button “Analysis List” to


04-03-2016 07-53-29.jpg


04-03-2016 08-29-16.jpg


8. Display Liquidity Item Report


Tx: FLQREP  – Payments per Liquidity Item

      FLQLS      – Liquidity Calculations – Totals list

      FLQLI       – Liquidity Calculation: Line item List


These reports shows totals ( FLQREP, FLQLS ) or individual line items ( FLQLI )


04-03-2016 13-24-07.jpg

9. Correct manual positions


tx: FLQAM


Reassign manually the Liquidity Items detected by FLQAD/F to a new Liquidity Item.


04-03-2016 13-20-21.jpg


20 Comments
You must be Logged on to comment or reply to a post.
  • Hi, pretty nice and simple explanation. I’m just bit missing how to maintain/create conditions and how to work with items with special indicator. But whatever, well done.

    Jan

    • Thanks for your comments. Good to hear it helped.=)

      Conditions are maintained with FLQQC1 (Vendor/Customer) and FLQQD1 (Expenses/Incomes).

      There are different types of conditions, based on Master Data (G/L Account, Vendor) or document (Header , Line Item).

      Supposed you have a Liquidity Item for “Maintenance Services” but your company has a special project to expand a section of a factory. You post expenses to the same account but this is posted to a WBS Element. You would like to separate WBS element from normal operations. You should use a query. 

      Try with t FLQQC7 or FLQQD7 and try if the query works.

      I worked with Sp.G/L Indicators through the G/L Account,

      Kind Regards

      • Back to spec. gl indicator… You mean, you assign GLs for e.g. down payments direct without indicator?

        My problem exactly now is, that my qry just want not to work if I specify spec. gl indicator with GL but also with account type D/K/S. I’ve tried also different sequences of qrys.. It just not work.

        The only way I’m able to assign such items to liqui item is using dirct mapping using FLQINFACC.

        I’m just curious why it does not work by me with qry. ūüôā

        In FLQC13 I marked partial reassignment, N:M, Info Accnt apply and order inf.

        Even I tried all possible combination, this combination works for me. But anyway, no assignment of DPs or other spec.ind. will follow if I will not specify them direct in FLQINFACC

        Do you have some experiences with that?

        Do you prefer to map reconciliation GLAs in FLQINFACC or rather use qry?

        I guess for recon. and so for spec. ind. GLAs will be always FLQINFACC better one, do you agree?

        Thank you a lot

        Jan

        • Hi Jan,

          You need the SpGL account in FLQINFACC to be recongnized by Liq. Planner and then you could use a query.

          I haven’t used a query as you suggested, with SpGl, it should work but no promises ūüôā

          Kind regards

          • Hi Gustavo,

            thanks for confirmation ūüôā

            Yes, with spec.GL.indicator it does not work properly. ūüėČ

            Thank you again

            Jan

  • Dear Gustavo,

    awesome blog ! thanks for sharing it.

    I have a question, Currently we are in 1503 SP5  version and need cash and liquidity management function however we are not opted for BPC system  licence. Could you please tell me whether this version will work for cash & liquidity without  BPC licence, I read somewhere its not possible to have cash & liquidity without BPC. Could you please share you thoughts.

  • Dear Gustavo,

     

    Thanks for sharing this nice piece of work.

    I’m currently working on S/4 HANA on premise version 1709.

    Would like to find out if you are aware that the function of manual reassign liquidity item (tx: FLQAM) in ECC6 is no longer available in S/4 Hana on premise (1709) version?

    Do you know how to re-assign the liquidity item in S/4 Hana CM on premise version 1709 ?

    Many thanks in advance!

    Kind regards,

    Ling

     

     

     

  • Dear¬†Gustavo,

    Could you please let me how to use “buffer item” in the S/4 Cash management? It seems the logic has been changed already. Currently I am using S/4 HANA 1709.

    I would like to use “buffer item” to define liquidity item via FI document chains (from FI payment to invoice in MM).

    Best regards,

    Yipeng

  • Dear Gustavo,

    Thank you for providing these great blogs.

    Now I understand that based on flow types, the Flow Builder traces the document chain back to its source (FI invoice). But I still have problem that I have the FI document posted from MM Good receipt. Cr: GR/IR, Dr: Expense G/L account.  because Flow builder doesn’t drill down to MM from FI to get the liquidity item. At this point, the final quilidity item will stop at GR/IR, not the liquidity item for Expense G/L account.  Now I have 2 questions.

    1. I defined query for liquidity item derivation: expense G/L account was assigned to a new liquidity item. The GR/IR was cleared when goods movements with MIGO. Cr. Expense G/L account, Dr. GR/IR. But because flow type was not assigned in the BSEG, derivation does not work. Does I miss something?
    2. I am still wondering additional field: buffer item. how can I use buffer item?

    Thanks for your advise.

    Best regards,

    Yipeng

     

     

    • There is no buffer item as used before. It has been replaced by Flow Types which have a defined funciton, however you could try on FLQINFACC to add the further checkbox.

      Check table FQM_FLOW on data.

      Here are some recomendations on what I would do. h

      1) 2512327 – One Exposure: Assign Flow Types To G/L Accounts

      To update flow Types inn BSEG -> tx FQM_UPD_LITEM

      FQM_UPD_FLOW_TYPE  all documents

      2) Activte MM in FQM -> FQM_ACTIVATE

      3) Check tx FLQINFACC with further

      4) Rebuild FQM

      5) Analize logs -> tx FQM_APPLICATION_LOG

      6) read some notes :-s

      2369432 – Flow Builder: Generate and Assign Loading Class

      2518457 – One Exposure: Rebuild flow type, Part II

      2559374 – Flow Builder: Logic Refine for Delta Run

      2560395 – Flow Builder: Setup Background Job listen to Event

      2580031 – FAQ : Liquidity item assignment into one Exposure( FQM_FLOW )

      2684381 – FI Flow Builder: Built-In Packaging Support for Delta Run

      2729344 – Flow Builder MM: Avoid processing MM procedures when MM is not active

       

      Hope it helps

      Kind Regards

  • Dear Gustavo,

    Thank you for the advice.

    I did some attempt, and still failure to derivate the “liquidity item” for MM document (Purchase order).¬†I think that is why I could not show the final liquidity item in the “cash flow analyzer” fiori report.

    What I have done for the configuration.

    1. FLQQA1: add a query with “X” for expense liqudity item. The condition is to map¬†the G/L account, which I set in the purchase order document.
    2. FLQC15: create a sequence
    3. FLQQA5: assign query to sequence
    4. FCLM_FB_UTIL: generate the loading class with “ZXXXX…”, then assign as default class.

    WHen I create a Purchase order for expense account, the data was loaded in the FQM_FLOW, but no liquidity item was assigned in the data.

    Do you have any suggestions?

    Best regards,

    Yipeng

     

  • Dear Gustavo,

    Thank you for the following up.

    Please let me update.

    1. Now I was able to derive the liquidity item for purchase order in the FQM_FLOW, with the steps I mentioined above. Just I had to specify sequence id when generating loading class. I think this is strange, might be a bug.
    2. I was able to derive final liquidity item for expense account. After GR/IR cleaing run, the document chain was linked via clearing document completely, then I can derive to the source document, means Bank acount > Bank clearing acount > Paybles > GR/IR > Expense acount.
    3. Using the query function, I can differentiate the expense acount for the liquidity item for Sales cash flow or for Invenstment cash flow .

    Thank you for your support. Your blogs are valuable!!! I appreciated.

    Best regards,

    Yipeng