SAP BLOG Cash and Liquidity Management End-User steps

SAP Blog

Kayıtlı Üye
Katılım
22 Ara 2017
Mesajlar
1,442
Tepki puanı
7
Puanları
6

Overview


I would like to give an overview of the cash and liquidity management End-User steps in this blog post. It will help you to understand how the cash flows like cash inflow and cash outflow as well as liquidity position in your system. It helps businesses to take the decision to manage funds. The Treasury Department can take the decision whether to adjust funds internally or take a working capital loan from the bank to manage their funds by verifying Cash and Liquidity management reports.

A) Introduction


Cash Management and Liquidity Management both are subcomponents of Financial Supply Chain Management (FSCM). Cash Management is used to verify the cash position of all the bank accounts and liquidity Management is used to verify the liquidity position of the sub-ledgers like Accounts payable and Accounts receivable. We can also use Memo records, Payment requests, Parked documents to verify the Cash and Liquidity position. It is used by the Cash Management operations team and the Treasury department. We use T-code: “FF7A /FF7B” to verify the cash and Liquidity position report. This document is developed using SAP ECC 6.0 version.
I would like to give a quick summary of the End-user steps in this document.

I have posted all the configuration steps for cash and liquidity management In my previous blog post. This is the continuation of my previous blog post, I am going to show few end-user steps to verify the cash and liquidity position of the organization. In the previous blog post, I have explained the planning levels, Planning groups/Cash management groups. We have to assign the planning levels and planning groups in the respected master data (G/L, Vendor, and Customer) if you want to verify the Cash and Liquidity positions.

Cash and Liquidity Management Configuration | SAP Blogs

Quick KDS Information

Planning Levels

Planning levelPlanning level descriptionSourceUsed for
L1Main BankBNKBank
L2Outgoing BankBNKBank
L3Incoming BankBNKBank
K1Unconfirmed VendorPSKVendors
K2Confirmed VendorPSKVendors
Y1Blocked VendorPSKVendors
D1Unconfirmed CustomersPSKCustomers
D2Confirmed CustomersPSKCustomers
Y2Blocked CustomersPSKCustomers
PRPayment request (B2B)BNKMemo Record-Bank
MPBank loansPSKMemo Record-Bank
MQSubledger transactionsPSKMemo Record-Vendor/Customer

Planning Groups

Planning GroupPlanning levelPlanning Group Description
V1K1Domestic Vendors
V2K1Foreign Vendors
C1D1Domestic Customers
C2D1Foreign Customers
MPMPBank loans
MQMQSubledger transactions

Planning Types

Planning TypePlanning Group Description
MPBank loans
MQSubledger transactions

If you want to verify the Cash Position of your bank then you have to update the Planning levels( For Bank G/L accounts) in the G/L Master.

If you want to verify the Liquidity Position for the Subledgers then you have to update the Cash management group in Vendor and Customer Master.

1. Assign Planning level in G/L Master (T.Code-FS00)


You need to assign the Planning level for all the Bank GL accounts under the company code segment and save it. Assign Planning level-L1 to the main bank account, L2 to Outgoing, and L3 to Incoming bank GL Account.

I am showing here only the assignment of one Planning level L1, but you need to assign all the Planning levels (Ex, L2, L3) to the Bank G/L’s.

15-8.png


2. Assign Cash Management Groups in Vendor & Customer Master (T.Code-FK02/XD02)


You need to assign a Cash management group (Planning group) for all the vendors and customers under the company code segment and save it. You need to assign Planning Group-V1 to Domestic vendors, V2 to Foreign Vendors, D1 to Domestic customers, and D2 to Foreign Customers as per my KDS mentioned in the configuration blog post.

I am assigning the Planning Group V1 here but you have to assign all the planning groups according to your configuration to all the vendors/customers.

16-6.png


3. Post Vendor Invoice (T.Code-F-43)


In the below screen I have posted one Vendor Invoice and just showing the posted document.

17-7.png


4. Vendor Line Item Report- FBL1N


In the Vendor line item report you can able to see the updated Planning Level- K1 and planning Group- V1.

18-9.png


Note:

  • If the invoice is blocked for payment, then the system will update planning level Y1/Y2 as soon as the invoice is posted for the customer/Vendor. You can verify the same in the vendor /customer line items reports (FBL1N/FBL5N).
  • If the invoice is not blocked, then the system will update planning level K1/D1(unconfirmed vendor/ unconfirmed customer) in the FBl1N/FBL5N report, until the user made a change to confirmed vendor/customer.
  • If the user removes the payment block manually, it will be changed from Unconfirmed to Confirmed item. Then the system will update the planning level from K1/D1 to K2/D2 in the invoice and you can verify it in the vendor/customer line item reports FBl1N/FBL5N report.
  • The system will derive planning levels from the planning groups, which are assigned in the business partner/vendor/customer master data.

5. Post Customer Invoice (T.Code-F-22)


I have posted one Customer Invoice and just showing the posted document.

19-6.png


6. Customer Line Item Report (T.Code-FBL5N)


In the Customer line item report you can able see the updated Planning Level- D1 and planning Group-C1.

20-6.png


7. Verify Liquidity Position (T.Code-FF7A/FF7B)


The system will only show open items, parked documents in the report. It will not show the cleared items.

21-6.png


20.1.png


If you double click on ‘sum. Group ‘you can able to see each Vendor / Customer wise report. The below screenshot shows the Liquidity items Inflow.

20.2.png


The below screenshot shows Liquidity items outflow.

20.3.png


8. Make Vendor Payment (T.Code-F-53/F110)


I have done Vendor Manual Payment- F-53 and showing the just posted document.

22-7.png


9. Check Vendor Line item report (T.Code-FBL1N)


The below screenshots shows the clearing documents, which will not be reflected in the liquidity forecast report.

23-5.png


10. Verify Liquidity Position and Cash Position Post Payment (T.Code-FF7A/FF7B)


Cleared sub-ledger line items will not appear in the liquidity position report. In the below example, I have selected the cash position group and liquidity position group to verify cash and liquidity forecast.

24-7.png


Execute to verify the output.

24.1.png


11. Verify Cash Position (T.Code-FF7A)


Verify the cash position report just to verify the cash position.

25-5.png


Execute to check the output.

25.1.png


Memo Records


It is used for tracking the transactions handled before actual postings into the SAP system. It will help you to manage your liquidity position. You can enter notified incoming payments, noted items, provisional bank statement postings, Payroll postings, fixed-term deposits, loan revenue, all bank fields, etc.

Memo records do not update your GL. They are just informational, and they expire as soon as the transaction is entered in SAP . Memo records can be deleted.

12. Post Memo record (T.Code-FF63)


SPRO-FSCM- Cash and Liquidity Management-Cash Managementàincomings- Memo record-FF63-Create

Enter the Co.Code and required planning type and Enter

26-6.png


Enter the below details and save it.

27-5.png


A memo record has been created.
28-7.png






Verify the Cash and Liquidity forecast report (FF7A)

29-3.png


Enter the above details and execute to get the output.

31-3.png


Double-click on the required line item to verify the line item information.

30-3.png


Conclusion


We have verified the different scenarios to verify the cash position, customer liquidity position, vendor liquidity position, and memo records in this blog post. In the same way, you can also try different scenarios using Memo records, Payment requests (Bank to Bank transfers), and Parked documents to verify the Cash and Liquidity position. I hope you understand the different business scenarios.

I am looking forward to your comments. I am happy to answer if you have any queries. Thank you so much for your time.

Okumaya devam et...
 
Üst