Robert Bieber (Developer ERP FIN) SAP Liquidity Planner Implementation Cookbook FLQAF = RFLQ_ASSIGN_CCR Update July 02, 2014 ‘Attachment to SAP note 1688721 Copyright 2014 SAP AG. All Rights reserved‘SAP Liquiity Planner Implementation Cookbook FLOAF = RFLG_ASSIGN_CCR Contents 1 Introduction 4.1 Our Case Study. 2 Key Concepts of Transaction FLQAF .. 2.1 Classification of GL Accounts. 2.1.1 Actual Accounts. 2.1.2 IMfO ACCOUNS sss 2.1.3 Remaining Accounts 2.2 Offsetting Items. 2.3 Document Chains from Actual to Info .. 2.3.1 First Part of the Document Chain 2.3.2 Second Part of the Document Chain. 2.3.3 An Example 2.4 Liqui y Item Derivation 3 Getting Started - Settings 3.4 Liqui y Items, 3.2 General Settings. 3.3 GL Accounts. 4 First part of the Document Chain. 4.1 Process Description 4.2 LP Bank Clearing Redefinition 5 Second part of the Document Chain. 6 Summary 1 Introduction ‘Sometimes customers are asking about the relationship between SAP Cash Management (CM) and Liquidity Planner (LP), and which of them to use. Actually there is an analogy to the relationship between Balance Sheet reporting and Profit&Loss statement: ‘The Balance Sheet Report shows Balances/Positions at a certain point in time (e.g. end of a quarter). The P&L statement shows how the Balance sheet item ‘Equity’ changed in a period (e.g. during the quarter) © 2014 SAP AG. Allighis reserved Poge 2‘SAP Liquidity Planner Implementation Cookbook FLOAF = RFLG_ASSIGN_CCR CM reports (TA FF7AVB) reports are ‘Position’ reports (like the Balance sheet), they show the amount of Cash on Bank and expected Cash at a given point in time, today or in the future, The LP Actual report is a ‘Flow’ report (like P&L), it explains the change in total Cash during a period, showing the ‘uses and sources’ In the Paper ‘Direct Cash Flow with the SAP Liquidity Planner’ (attached to SAP note 412605 as file LQ_DCF_EN.paf; German version LQ_DCF_DE-paf) you find the principles how the SAP Liquidity Planner (LP) gets this Direct Cash Flow information out of SAP Financials. Here we give an example how to implement these principles. At the same time, we introduce the new (notes 1688721 and 1826731) assignment mechanism TA FLQAF and describe where it differs from the old chain- based assignment mechanisms. 14 Our Case Study ‘Suppose you have a system where you'd like to get Liquidity item (LI) assignment running, with the new mechanism FLQAF. This mechanism follows and evaluates the document chains that go from the Actual (Cash) line items into Vendor, Customer, Expense, Revenue and other Info line items. You will probably not start directly in the production system but in a test system that has fairly realistic FIN data (best a recent copy of production) and where you have the authorisation to change customizing data. If you want to set up LP in several Company Codes, it makes sense to start with one and roll out later Many LP settings can either be made per company code, or general, valid for all company codes, It is usually a good approach to work with general settings. 2 Key Concepts of Transaction FLQAF LLP offers a variety of mechanisms for a rule-based assignment of Liquidity Items (that describe the uses and sources of Cash) to the individual payments that make up the total Cash Flow. Transaction FLQAD (program RFLQ_ASSIGN_REX) was traditionally the most widely used, and the natural successor to the TR-CB Cash Budget Management application that was supported until SAP_APPL 470. Here is an overview of the mechanisms that evaluate document chains, three old and oné new: FLQAD RFLQ_ASSIGN_REX__| Two step, chains in transaction currency FLOAL RFLQ@_ASSIGN REL __| Two step, chains in local currency FLOAC. RFLQ_ASSIGN FI First step of FLQAD. FLQAF (new) | RFLQ_ASSIGN_CCR__| Two step, in local currency, can handle extension fields FLQAF is the only one that can populate the new extension Include FLQ_EXTENSION in the LP items and totals tables. This is the new way of getting additional (to the given: Liquidity Item, Company Code, Business Area) reporting dimensions into LP data. The old way was to work with a technical key for the Business Area field, and a translation table — note 763985. The old workaround works in principle also with FLQAF but the new way is definitely better. FLOAF has the local currency as leading currency (there are some plans to offer alternatively transactional currency, not yet realized), so it is closest to old FLQAL. This in turn is (apart from the leading currency) identical with FLQAD. We will below every now and then provide a comment box that explains differences between FLQAF and FLAD. 2.1 Classification of GL Accounts This Is the basis for document chains. We still distinguish four classes of GL accounts: © 2014 SAP AG. Allighis reserved Poge 3