Top Banner
EHP4 for SAP ERP 6.0 June 2010 English Cash Management (160) SAP AG Dietmar-Hopp-Allee 16 Business Process Documentation
79
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 160 Bpp en Ae Cash Management

EHP4 for SAP ERP 6.0

June 2010

English

Cash Management (160)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

Page 2: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Copyright

© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 71

Page 3: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include Field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG Page 3 of 71

Page 4: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Contents

1 Introduction............................................................................................................................. 5

1.1 Purpose........................................................................................................................... 5

2 Prerequisites.......................................................................................................................... 5

2.1 Master Data..................................................................................................................... 5

2.2 Roles............................................................................................................................... 6

2.3 Creating Demo Data........................................................................................................7

2.3.1 Posting a Customer Invoice (in Domestic Currency)................................................7

2.3.2 Posting a Vendor Invoice (in Domestic Currency)....................................................7

2.3.3 Posting a Vendor Invoice (in Foreign Currency).......................................................8

2.3.4 Clearing of Vendor Invoices by the F110-Payment Run.........................................10

2.3.5 Simulating Bank Statement and Opening Customer Item for Electronic Bank Statement Processing..........................................................................................................10

3 Process Overview Table.......................................................................................................12

4 Process Steps...................................................................................................................... 13

4.1 Posting of a Planning Memo Record for Recurring Payments (Manual Planning).........13

4.2 Archiving the Memo Record..........................................................................................15

4.3 Bank Statement.............................................................................................................16

4.3.1 Importing Bank Statement (Electronic Bank Statement)........................................16

4.3.2 Entering a Manual Bank Statement........................................................................17

4.3.3 Reprocessing an Account Statement.....................................................................23

4.4 Cash Concentration.......................................................................................................24

4.4.1 Creating a Concentration Proposal........................................................................24

4.4.2 Generation of Payment Requests..........................................................................27

4.4.3 Clearing the Payment Requests by the F111-Payment Run..................................28

4.5 Financial Overview / Cash Position & Liquidity Forecast...............................................30

5 Appendix.............................................................................................................................. 32

5.1 Reversal of Process Steps............................................................................................32

© SAP AG Page 4 of 71

Page 5: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Cash Management

1 IntroductionCash Management in SAP ERP Financials provides three basic functions:

Quickly and reliably transfers all cash-relevant information from internal and external sources into the cash management system (inbound data)

Performs analysis and reporting of current and future cash flows to help you make cash management decisions (analysis and decision)

Communicates with banks and other business partners based on the results of the decision process (outbound data)

SAP ERP Financials offers the following tools, designed to make cash flows clear:

- The cash position, which illustrates short-term movements in the bank accounts

- The liquidity forecast, which illustrates medium-term movements in subledger accounts

The cash position shows how your bank accounts will move in the next few days. Meanwhile, the liquidity forecast illustrates liquidity changes in the subledger accounts. Functions are also supported which can be used to obtain relevant information on forecast payment flows. This information appears in the form of memo records in the cash position, or as planned items in the liquidity forecast.

This document will give you an overview how to use the SAP ERP Cash Management-functionality. The scenario includes the following sequence:

Posting of a vendor invoice in local and foreign currency Posting of a customer invoice in local currency (from a sales order) Posting of planning items and memo records Execution of the report showing cash position and the liquidity forecast. All posted

documents will be displayed on the value date basis. After posting the manual bank statement, the flow between the planning levels will be

demonstrated Due to the actual postings of the bank statement, the memo records will be archived

automatically (by using a special report). The function of cash concentration will illustrate how to identify the relevant amounts and

transfer them from one account to another.

1.1 PurposeThe cash position overview provides information on the current financial state of the bank accounts. It is the starting point for cash concentration in which the balances from various bank accounts are concentrated in one target account, taking minimum balances and payment optimization into consideration.

The example in this document shows a posting process that affects liquidity (customer invoice and incoming payment). It presents the main functions for retrieving information about the liquidity status.

2 Prerequisites

2.1 Master DataYou have entered the master data required to go through the procedures of this scenario. Ensure that the following scenario-specific master data exists before you test this scenario:

© SAP AG Page 5 of 71

Page 6: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Master Data Value Selection Comment

Customer * All Cash management planning group needs to be assigned to a customer.

For master data creation compare Central Master Data (152) scenario

Vendors * All Cash Management Planning Group needs to be assigned to a vendor.

For master data creation compare Central Master Data (152) scenario

G/L Accounts * 280000-281015 Cash Management Planning Level needs to be assigned to all bank G/L accounts which should be included in the Cash Position Overview

© SAP AG Page 6 of 71

Page 7: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2.2 Roles

UseThe following roles must have been installed to allow the relevant activities to be carried out in the SAP Netweaver Business Client (NWBC). In addition, they must be assigned to the user or users who will perform the process steps described in this document. You do not need these roles if you are not using the NWBC interface, but the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user(s) who perform the process steps described in this document.

Business Role Technical Name Process Step

Employee (Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role is necessary for basic functionality.

Treasurer SAP_NBPR_TREASURER-S Posting of a Planning Memo Record for Recurring Payments (Manual Planning)

Archiving the Memo Record

Cash Concentration

Financial Overview / Cash Position & Liquidity Forecast

Bank Accountant SAP_NBPR_BANKACC-S Import Bank Statement (Electronic Bank Statement)

Entering a Manual Bank Statement

Reprocess Bank Statement

Accounts Payable Accountant

SAP_NBPR_AP_CLERK-S Create demo data: Posting a Vendor Invoice (in domestic currency)

Create demo data: Posting a vendor invoice (in foreign currency)

IT Administrator (Professional User)

SAP_NBPR_IT_ADMIN-S Create demo data: Simulate Bank Statement and Open Customer Item for Electronic Bank Statement Processing

© SAP AG Page 7 of 71

Page 8: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2.3 Creating Demo Data

2.3.1 Posting a Customer Invoice (in Domestic Currency)

UseThe following example describes how to enter a customer invoice.

PrerequisitesThe customer has been created. The master data of the general ledger account is maintained.

Procedure

To execute this activity, run the processes in the Sales Order Processing: Sale from stock (109) scenario, using the master data from this document.

ExampleField name Description User action and values Comment

Material F126

Customer 100000

Amount in LC 20.000

Currency AED

Reference DR00001

© SAP AG Page 8 of 71

Page 9: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2.3.2 Posting a Vendor Invoice (in Domestic Currency)

UseThe following example describes how to enter a vendor invoice in local currency into financial accounting. This procedure is used when purchasing for example office materials.

PurposeCompany has received a vendor invoice to be paid. The invoice must be posted.

Procedure

1. Access the activity using one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Accounting Accounts Payable Document Entry Invoice

Transaction code FB60

© SAP AG Page 9 of 71

Page 10: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Accounts Payable Accountant

(SAP_NBPR_AP_CLERK-S)

Business role menu Accounts Payable Posting Invoices Enter Vendor Invoices w/o PO Reference

© SAP AG Page 10 of 71

Page 11: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. Enter the following data on the Enter Vendor Invoice: Company Code 1000 screen, Basic data tab page.

Field name Description User action and values Comment

Company code 1000

Vendor <any domestic vendor>

for example 300000

Invoice date Current date

Posting Date Current date

Amount 3.000

Currency AED

Calculate tax Select

Tax Code V0

GL acct 476000

Cost center 1101

Amount in doc.curr.

*

© SAP AG Page 11 of 71

Page 12: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Select Payment tab page, and enter the following data:

Field name Description User action and values Comment

Pmt Method H H represents Bank transfer outgoing

Payt Terms 0001 If a cash discount is to be deducted for this payment, this must be taken into consideration when you enter the bank statement.

© SAP AG Page 12 of 71

Page 13: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

4. Choose Post (Ctrl+S).

5. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

2.3.3 Posting a Vendor Invoice (in Foreign Currency)

UseThe following example describes how to enter a vendor invoice in foreign currency into financial accounting. This procedure is used when purchasing for example office materials.

PurposeCompany has received a vendor invoice to be paid. The invoice must be posted.

Procedure

1. Access the activity using one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Accounting Accounts Payable Document Entry Invoice

Transaction code FB60

© SAP AG Page 13 of 71

Page 14: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Accounts Payable Accountant

(SAP_NBPR_AP_CLERK-S)

Business role menu Accounts Payable Posting Invoices Enter Vendor Invoices w/o PO Reference

© SAP AG Page 14 of 71

Page 15: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. Enter the following data on screen Enter Vendor Invoice: Company Code 1000, Basic data tab page.

Field name Description User action and values Comment

Company code 1000

Vendor <any foreign vendor> for example 300011

Invoice date Current date

Posting Date Current date

Amount 10.000

Currency USD

Calculate tax Select

Tax Code V0

G/L acct 476000

Cost center 1101

Amount in doc.curr.

*

© SAP AG Page 15 of 71

Page 16: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Select Payment tab page, and enter the following data:

Field name Description User action and values Comment

Pmt Method H H represents Bank transfer outgoing

Payt Terms 0001 If a cash discount is to be deducted for this payment, this must be taken into consideration when you enter the bank statement.

© SAP AG Page 16 of 71

Page 17: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

4. Choose Post (Ctrl+S).

5. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

2.3.4 Clearing of Vendor Invoices by the F110-Payment Run

Procedure

To execute this activity, run the processes in the Accounts Payable: Automatic Payment (158) scenario, using the master data from this document.

Field name Description User action and values Comment

Run Date Current date

Identification Any Identification of the payment run

for example your initials + sequential number (XX01)

Posting Date Current date

Docs entered up to

Current date

Customer items due by

Current date + 1 month Enter date in future

Company codes 1000

Pmt meths H

Next p/date Date of next Payment run execution

Current date + 1 month Enter date in future

Vendor Enter vendors of previous steps, 300000 and 300011

© SAP AG Page 17 of 71

Page 18: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

While maintaining the parameters of automatic payment program, choose the tab page Additional Log and make the following entries:,

Field name Description User action and values Comment

Due date check X

Payment method selection in all cases

X

Line items of the payment documents

X

Vendors (from/to) 300000 and 300011

© SAP AG Page 18 of 71

Page 19: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

After the payment run has been executed, Choose Display payment run log and write down the payment clearing document number 20000000XX and the clearing amount.

2.3.5 Simulating Bank Statement and Opening Customer Item for Electronic Bank Statement Processing

UseThe following example describes how to simulate a bank statement and a linked open customer item.

PrerequisitesThe customer has been created. The master data of the general ledger account is maintained.

RFEBKATX is an implementation tool for the Electronic Bank Statement and is designed to help you make the customization settings required when you implement the electronic bank statement.

To use the program you must create a substitute account for the postings, which leads to the creation of open items in customer accounts. The number of this G/L account must be the same as that of the G/L account for the house bank account, except that the last two digits must be replaced with "19".

Example: G/L account:           113100Substitute account:     113119

Procedure

1. Access the activity using one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu System (from menu bar) Services Reporting

Transaction code SA38

© SAP AG Page 19 of 71

Page 20: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role IT Administrator (Professional User)

(SAP_NBPR_IT_ADMIN-S)

Business role menu IT Administration Administration ABAP Workbench ABAP Reporting

© SAP AG Page 20 of 71

Page 21: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. Enter the following data on the ABAP: Program Execution screen:

Field name Description User action and values Comment

Program RFEBKATX

© SAP AG Page 21 of 71

Page 22: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Choose Execute.

4. Enter the following data on the next screen Test Tool RFEBKATX: Create Open Items and Bank Statement Files:

Field name Description User action and values Comment

Download to PC Tick box

Statement file statement.txt

Line item file lineitem.txt

Company code 1000

House bank (ID) 1000

Account (ID) 1000

Statement date Today

Invoice date Today minus 2 days

Posting method Display all posting screens

Customers to be posted to

Enter customer of previous steps

For example 100000

Number of open items

1

First amount ‘any’

© SAP AG Page 22 of 71

Page 23: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

All other values can remain unchanged.

5. Choose Execute.

6. Confirm the screen Post Document: Header Data with Enter.

7. Enter the following data on the Enter Customer invoice: Add Customer item screen (item 1/Invoice 01):

Field name Description User action and values Comment

Customer <Customer entered in previous screen>

for example 100000

Company Code 1000

Amount ‘higher amount than first amount’

© SAP AG Page 23 of 71

Page 24: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

8. Choose Enter.

9. Confirm the information and warning messages with by choosing Enter.

10. Enter the following data on the Enter Customer invoice: Add customer item screen (item 2/Credit Entry/50:

Field name Description User action and values Comment

G/L account Substitute account for example 113119

Company Code 1000

Amount ‘*’

Value Date for example <current date>

Due on for example <current date>

© SAP AG Page 24 of 71

Page 25: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

11. Confirm the following screens with Enter until the document is posted.

12. Write down the document number 18000000XX generated in the system for the subsidiary ledger.

13. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

3 Process Overview TableProcess step

External process reference

Business condition

Business role

Transaction code Expected results

Posting of a Planning Memo Record for Recurring Payments

A memo record will give forecast information

Treasurer FF63 Memo record posted

Archiving the memo record

After the Memo record expires it should be archived

Treasurer FF6B

Import Bank Statement (Electronic Bank Statement)

Bank accountant

FF_5 Bank Statement posted

Entering a Manual Bank Statement

Bank accountant

FF67 Clearing the customer invoice and the clearing account

Reprocess Bank Statement

Bank accountant

FEBA_BANK_STATEMENT

Residual Item settled

Cash concentration

Concentrate all your account balances in one target account

Treasurer FF73

F111

Create a concentration proposal.

Generation of payment requests.

Execution of F111 – payment program.

Financial overview / Cash

Cash Position and

Treasurer FF7A or FF7B Financial Status updated

© SAP AG Page 25 of 71

Page 26: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Process step

External process reference

Business condition

Business role

Transaction code Expected results

Position & Liquidity Forecast

Forecast

© SAP AG Page 26 of 71

Page 27: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

4 Process Steps

4.1 Posting of a Planning Memo Record for Recurring Payments (Manual Planning)

UseThe following example describes how to enter a memo record. This example illustrates a monthly recurring payment. Since there is no invoice existing in FI, this memo record needs to be created, so the cash management report will include these expenses.

For archiving the advice, a report will compare the bank statement with the memo record. The memo item will be identified because of the amount and archived.

In case of differences, the result will be represented. Due to this functionality, the user has the possibility to decide whether the line item will be archived or not.

ProcedureEnter the memo record manually as described below:

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Incomings Memo Record Create

Transaction code FF63

© SAP AG Page 27 of 71

Page 28: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Treasurer (SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Planning Create Planning Memo Record

© SAP AG Page 28 of 71

Page 29: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Create Memo Record: Initial Screen, make the following entries:

Field name Description User action and values Comment

Company code 1000

Planning type any planning type <DI>

3. Choose Enter.

4. Enter the following data on the next screen Create Memo Record: Planned items:

Field name Description User action and values Comment

Planning Day any date < current day>

Planning Group any planning group < A6>

Amount any amount < 15.000

Currency any currency < AED>

Assignment any text < Recurring tax>

5. Choose Enter and Copy.

6. Enter the following data on the next screen Create Memo Records: Copy Amount:

Field name Description User action and values Comment

Number any number Enter number of memo records to be created (recurring payments) for example, 12

Increment in days/weeks/months

any number Determines the increment in days, weeks or months for the memo record copy function.

for example, 1 in the field for the month

Set to previous Friday/working day instead of skipping

select When selected, the date is shifted to the previous Friday instead of skipping the weekends (skipping to Monday).

© SAP AG Page 29 of 71

Page 30: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

7. Choose Enter.

8. Choose Save.

9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultThe selected number of memo records (for example, 12) is generated and posted. The memo records have updated the financial status in cash management and can be found under the corresponding planning level (for example, DI).

4.2 Archiving the Memo Record

UseThe planning memo records of the cash position and the liquidity forecast are managed with this transaction. The system displays the memo records in a list. You can select an individual record for display and modification.

In the list, you can select memo records in order to transfer them afterwards into an archive. After they are archived, the records are no longer relevant to the cash position and liquidity forecast, but are still available for evaluations (for example, for calculating the average interest on fixed-term deposits from last year).

Memo records in the archive can be processed in a similar manner. To list these records, specify the required archive category during the transaction. The system displays a list of the memo records stored in this archive.

If such records are selected, they can then be reactivated later.

PrerequisitesThe bank statement has been processed.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Planning Memo Record Change Using List

Transaction code FF6B

© SAP AG Page 30 of 71

Page 31: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Treasurer

(SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Planning Change Memo Record

© SAP AG Page 31 of 71

Page 32: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Memo Records: List screen, make the following entries:

Field name Description User action and values Comment

Company code 1000

Cash Position select

Liquidity Forecast select

© SAP AG Page 32 of 71

Page 33: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Choose Execute (F8).

4. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultThe entered memo records are listed. By choosing Convert the selected memo records are sent to the archive and are no longer relevant for the Cash Management.

4.3 Bank Statement

4.3.1 Importing Bank Statement (Electronic Bank Statement)

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Accounting Banks Incomings Bank Statement Import

Transaction code FF_5

© SAP AG Page 33 of 71

Page 34: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Bank Accountant (SAP_NBPR_BANKACC-S)

Business role menu Bank Accounting Incomings Import Electronic Bank Statement

© SAP AG Page 34 of 71

Page 35: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Bank Statement: Various Formats (SWIFT, MultiCash, BAI…) screen, make the following entries:

Field name Description User action and values Comment

Import data Tick Box

Statement File statement.txt

Line item file lineitem.txt

BELNR number internal

Enter the document number you’ve recorded in step 2.3.5.

© SAP AG Page 35 of 71

Page 36: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

All other values should remain unchanged.

3. Choose Execute (F8).

4. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

4.3.2 Entering a Manual Bank Statement

UseThe incoming payment for customer invoices is posted by entering and posting the manual bank statement.

PrerequisitesThere is an open customer invoice in the system.

The following transactions are available for bank statement processing:

Transaction Text Details

001+ Cash receipt via interim account

The Customer pays an invoice with a credit transfer. This cash receipt is visible in the bank statement. As the linked customer item is still open, the interim account will be used for clearing.

002+ Check deposit An incoming check was given to the bank. The check deposit is visible in the bank statement.

Posting:

Debit: ‘Bank’ Credit: ‘Check In’ (Interim Account)

003- Cashed check The check was cashed from the vendor. The corresponding amount is visible in the bank statement.

Posting:

Debit: ‘Check Out’ (Interim Account)

Credit: ‘Bank’

004- Domestic transfer

Outgoing Domestic bank transfer in local currency

005- Foreign transfer Outgoing Foreign bank transfer in any currency

006- Other disbursements

Outgoings which don’t fit to the other transactions.

007+ Other receipts Incomings which don’t fit to the other transactions.

008- Cash payment Any cash outgoing payment

009+ Cash receipt Any cash incoming payment

010+ Collection/direct debit

The cash receipt of the automatic debit was successful and is now visible in the bank statement. The clearing of the open customer item already took place with the processing of the payment order (F110).

011- Returns collection/direct debit

Automatic debit which was returned by the customer

© SAP AG Page 36 of 71

Page 37: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Transaction Text Details

012- Bank fee Bank fee

013+ Interest received Interest received for credit on bank account

014- Interest paid Interest paid for debit on bank account

016- Vendor direct debit

The vendor executed an automatic debit. The bank account will be debited and the open vendor item will be settled.

© SAP AG Page 37 of 71

Page 38: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Incomings Manual Bank Statement Enter

Transaction code FF67

© SAP AG Page 38 of 71

Page 39: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Bank Accountant

(SAP_NBPR_BANKACC-S)

Business role menu Bank Accounting Incomings Manual Account Statement

© SAP AG Page 39 of 71

Page 40: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. When you call up the transaction for the first time, the Specifications dialog box appears for you to enter the following data and choose Continue (Enter):

Field name Description User action and values Comment

Int. bank determin.

select If this indicator is set, you can enter the house bank ID and the account ID. If the indicator is not set, you have to enter the bank number and the bank account number.

Import advices select

Start variant YB01

Processing Type

4 If you choose this processing type, you have to use transaction FEBA for further processing.

Transfer value date

select

© SAP AG Page 40 of 71

Page 41: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

You can also display this dialog box by choosing (NWBC: More…) Settings Specifications. Check that the correct data is entered.

3. On the Process Manual Bank Statement screen, make the following entries:

Field name Description User action and values Comment

Company Code 1000

House Bank House bank ID The House bank ID of the House Bank for which the bank statement is being entered.

for example, 1000

Account ID Account ID The account ID of the bank account for which the bank statement is being entered.

for example, 1000

Statement number

Bank statement number

If you have forgotten the number of your previous statement for the selected account, you can choose Overview to call up all previous bank statements. You can then transfer the last statement from the overview or create a new statement. In this way, the statement number, statement date, and beginning balance are filled automatically.

Statement date Date of bank statement

<Today’s date>

Opening Balance

Opening balance Opening balance = Ending balance of previous statement

for example, 0

Closing Balance

Closing balance Closing balance = Opening balance - all debit amounts + all credit amounts

for example, 0 + 20000 – 3000 – 4000 = 13000

© SAP AG Page 41 of 71

Page 42: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

4. Choose Enter.

5. On the Process Manual Bank Statement screen, make the following entries:

Field name Description User action and values Comment

Transaction * Process code for cash receipts

for example, 001+

Value date value date Value date of credit transaction

for example, Today’s date

Amount amount Transaction amount

for example, 20.000

Bank refer. reference from customer invoice

Enter reference from customer invoice

for example, DR00001

Customer * Customer number

for example, 100000

© SAP AG Page 42 of 71

Page 43: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Transaction 001+ is for ‘Cash receipts’ and contains the posting logic for the document to be posted. In this case, the following documents are posted:

Bank account / Bank Subaccount (without clearing)Bank Subaccount / Customer Invoice (with clearing)

Field name Description User action and values Comment

Transaction * Process code for domestic transfer

for example, 004-

Value Date value date Value date of debit transaction

for example, Today’s date

Amount any amount Transaction amount

for example, 3.000-

Bank Ref. Enter the payment clearing document number got in step 2.3.4 for vendor 300000.

© SAP AG Page 43 of 71

Page 44: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Transaction 004- is for Domestic transfer and contains the posting logic for the document to be posted. In this case, the following documents are posted:

Bank Subacc. (outg. Dom. payments) / Bank Account (with clearing)

Field name Description User action and values Comment

Transaction * Process code for bank transfer (debit memo)

for example, 006-

Value Date value date Value date of debit transaction

for example, Today’s date

Amount any amount Transaction amount

for example, 4000-

6. Choose Save and then Post statement.

When you only choose Save the account statement is included in the system, but is not posted yet.

Transaction 006- is for Other disbursements and contains the posting logic for the document to be posted. In this case, the following documents are posted:

Bank Subaccount / Bank Account

A different step will be necessary for clearing the open item against the correct expense account. But this is not part of the further scenario.

7. Repeat this process step and enter another bank statement. Use the same data but change the entry for the account-id to USD. On the Process Manual Bank Statement screen, make the following entries:

© SAP AG Page 44 of 71

Page 45: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Field name Description User action and values Comment

Company Code 1000

House Bank House bank ID The House bank ID of the House Bank for which the bank statement is being entered.

for example, 1000

Account ID Account ID The account ID of the bank account for which the bank statement is being entered.

for example, 1002

Statement Number

Bank statement number

If you have forgotten the number of your previous statement for the selected account, you can choose Overview to call up all previous bank statements. You can then transfer the last statement from the overview or create a new statement. In this way, the statement number, statement date, and beginning balance are filled automatically.

Statement Date Date of bank statement

for example, Today’s date

Opening Balance

Opening balance Opening balance = Ending balance of previous statement

for example, 0

© SAP AG Page 45 of 71

Page 46: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Field name Description User action and values Comment

Closing Balance

Closing balance Closing balance = Opening balance - all debit amounts + all credit amounts

for example, 0 - 10000 = -10000

© SAP AG Page 46 of 71

Page 47: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

8. Choose Enter.

9. On the Process Manual Bank Statement screen, make the following entries:

Field name Description User action and values Comment

Transaction * Process code for foreign transfer

for example, 005-

Value Date value date Value date of debit transaction

for example, Today’s date

Amount any amount Transaction amount

for example, 10000-

Bank Ref. Enter the payment clearing document number got in step 2.3.4 for vendor 300011

© SAP AG Page 47 of 71

Page 48: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

10. Choose Save and then Post statement.

11. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

Transaction 005- is for Foreign transfer and contains the posting logic for the document to be posted. In this case, the following documents are posted:

Bank Subaccount (outg. foreign payments) / Bank Account (with clearing)

ResultThe bank statement has been entered manually and all corresponding transactions have been posted. The customer invoice was cleared automatically (using the unique reference). The open items on the bank subaccounts have been cleared.

4.3.3 Reprocessing an Account Statement

UseEvery time you post a manual account statement you must reprocess it, because the system cannot always clear all the items automatically. This is particularly important if the customer has not paid the total amount, or has quoted the wrong reference. In this particular case, no clearing posting is carried out and, consequently, reprocessing is necessary.

PrerequisitesThe manual account statement has been posted.

Procedure

1. Access the transaction by choosing one of the following navigational options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Accounting Banks Incomings Bank Statement Reprocess

Transaction code FEBA_BANK_STATEMENT

© SAP AG Page 48 of 71

Page 49: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Bank Accountant

(SAP_NBPR_BANKACC-S)

Business role menu Bank Accounting Incomings Postprocessing Bank Statement

© SAP AG Page 49 of 71

Page 50: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Selection of Bank Statements by Banks and Account Nos screen, enter the required data.

Field name Description User action and values Comment

Company Code 1000

House Bank House bank for which bank statement is being processed

For example, 1000

Account ID House bank account for which bank statement is being processed

For example, 1000

© SAP AG Page 50 of 71

Page 51: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Choose Execute.

4. The corresponding statements from this bank, and the statement items, are displayed.

5. On the Edit Bank Statement screen, select the bank row with a double-click you want to post.

6. On the Edit Bank Statement screen, all the statement numbers are displayed.

A green light next to the statement item indicates that the postings have been processed without errors. You can see the posted document number in the individual statement items. Double-click an item to display further information, such as the reference, business partner, bank details, external transaction, note to payee, and so on. To display the document that was created, double-click the document number. A red light next to the statement item indicates that the account statement items could not be posted. You have to reprocess these items.

The following steps need only to be carried out if a red light appears

7. On the Edit Bank Statement screen, select the statement number with a double-click you want to post (statement with the red light).

8. On the Edit Bank Statement screen, select the amount row which has to be posted.

9. On the Edit Bank Statement screen choose (NWBC: More…) Statement Items Post.

10. On the Post with Clearing Select open items screen, make the following entries:

Field name Description User action and values Comment

Company Code 1000

Account <account number from the customer>

For example, 100000

Account Type D Customers

© SAP AG Page 51 of 71

Page 52: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

11. If you can select additional selections (for example amount or document number or reference) you can clear with selection criteria. Choose the relevant additional selection. In this case on the Post with Clearing Enter selection criteria screen, enter the relevant selection and choose Process open items.

12. If no selection criteria are needed, choose Enter.

13. On the Post with Clearing Process open items screen, select the document number(s) you want to clear.

14. In the field Amount entered you can see the bank statement amount which has to be cleared. When you pick the relevant document number(s) the field Assigned shows the total amount.

15. For assigning the amount, double-click the amount (AED Gross).

16. In the Not assigned field, you can see the difference between Amount entered and Assigned. When the field is zero you can post and clear the statement.

17. Choose Post (Crtl+S).

18. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultThe items are posted which could not be cleared automatically

4.4 Cash Concentration

UseBefore making cash management decisions, it is often advisable, for business reasons, to concentrate all your account balances in one target account.

Cash concentration is based on specified bank G/L accounts that are summarized under a dedicated grouping (for example, YCASHCONC).

4.4.1 Creating a Concentration Proposal

UseThe system generates a proposal for concentrating cash based on your grouping. This proposal contains the end-day-balance and the cash planning results, that is, the expected account transfers. You can correct the proposal at any stage manually by changing for example, the minimum amount, planned amount related to a certain bank account.

The system prints the outcome of the cash concentration process in the form of payment orders to banks. It also creates the payment advices needed for determining the new bank account balances.

PrerequisitesThe general ledger master data is maintained accordingly. The bank accounts show balances which are relevant for cash concentration (which excess the minimum balance specified during the cash concentration execution).

Procedure

© SAP AG Page 52 of 71

Page 53: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Planning Cash Concentration Create

Transaction code FF73

© SAP AG Page 53 of 71

Page 54: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Treasurer

(SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Planning Cash Concentration

© SAP AG Page 54 of 71

Page 55: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Automatic Cash Concentration screen, make the following entries:

Field name Description User action and values Comment

Company Code 1000

Planned date any date for example, Today’s date

Grouping YCASHCONC Selection of accounts for the cash concentration

Account Currency

AED Cash concentration is set up only for local currency bank accounts

Minimum balance

any amount Accounts with a balance less than the value specified here are not included in the cash concentration process.

for example, 1000

Target account name

any main bank account assigned to grouping YCASHCONC

Cash Management account name of target account

for example, AE-AED-BNK

Target Company Code

1000

Value date any date for example, Today’s date

Expiration date any date for example, Today’s date

Planning type CL Planning type for the payment advices to be created during the cash concentration process

Minimum amount

any amount No bank transfers with an absolute amount less than the minimum amount specified here are created during the cash concentration process.

for example, 1000

© SAP AG Page 55 of 71

Page 56: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Choose Execute.

4. On the Display Balances from Cash Concentration screen, you can see the concentration proposal created by the system and revise it.

5. Choose Edit Payment Advices.

6. On the Edit Payment Advice for Cash Concentration screen, you can change the amounts available for planning as required.

7. To create the payment advices for the concentration proposals, choose Save Payment Advices.

8. Confirm information Do you want to create payment advices? with Yes.

9. The system displays the message Payment advices generated. You can display the newly created payment advices in the cash position in order to analyze the cash concentration result.

10. To exit the transaction, choose Back.

11. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultYou make internal preparations for clearing the bank accounts by executing a concentration proposal and generating the corresponding payment advices.The next step is to generate payment requests from the payment advices that were created by the cash concentration proposal. The payment requests will subsequently be regulated by the payment program F111.

You can also create the payment advices for the cash concentration manually.

4.4.2 Generation of Payment Requests

UseOnce you have created the payment advices by the concentration proposal, the corresponding payment requests needs to be created from this payment advices. Payment requests are in the next step read by the payment program and used of execution of the outgoing payment and creation of the payment file.

PrerequisitesPayment advices have been created by the cash concentration proposal.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Planning Generate Payment Request From Payment Advice Notes

Transaction code FF.D

© SAP AG Page 56 of 71

Page 57: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Treasurer

(SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Planning Generate payt req. from advices

© SAP AG Page 57 of 71

Page 58: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Generate Payment Request from Cash Management Advices screen, make the following entries:

Field name Description User action and values Comment

Company Code 1000

Planning type CL

Test Run Deselect

Payment method H Payment method for domestic transfer.

© SAP AG Page 58 of 71

Page 59: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Choose Execute.

4. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultThe payment requests have been created. The corresponding payment advices have been archived.

4.4.3 Clearing the Payment Requests by the F111-Payment Run

UseYou can use this payment program to make payments to customers and vendors, or between G/L accounts. Unlike the standard payment program, the payments are not based on open items (FI documents) but on payment requests.

PrerequisitesThe payment requests have been created within the previous step.

Procedure

1. Access the activity using one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Planning Payment Program Payment Requests

Transaction code F111

© SAP AG Page 59 of 71

Page 60: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Treasurer

(SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Planning Automatic Payment of PRequest

© SAP AG Page 60 of 71

Page 61: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Automatic Payment Transactions for Payment Requests screen, enter the following data:

Field name Description User action and values Comment

Run Date any date for example, current date

Identification any identification for example, your initials

© SAP AG Page 61 of 71

Page 62: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Choose Parameters.

Field name Description User action and values Comment

Posting Date any date for example, current date

Next payment run on

any date in future The next payment date must be after the due date (value date) of the payment request, otherwise the payment requests will not be regulated by this run. The value date was derived from the payment advices created during the cash concentration proposal.

for example, current date + 1 month

Company code 1000

Payment methods

H The payment method must correspond to the payment method of the payment request (otherwise the payment request will not be regulated by this run).

© SAP AG Page 62 of 71

Page 63: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

4. Choose Additional Log.

Field name Description User action and values Comment

Payment method selection in all cases

select

Line items of the payment documents

select

Due date check select

© SAP AG Page 63 of 71

Page 64: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

5. Choose Continue, and confirm the information Log created for all accounts if necessary with Enter.

6. Choose Save, go back to the tab page Status.

7. Schedule proposal by choosing Proposal.

8. Select Start immediat. and choose Enter. By choosing Status, you can see the status of the payment proposal. The payment proposal is generated when the system displays message Payment proposal has been created.

9. Choose Display proposal log and check the selection of your document.

10. If there are no errors, schedule payment run by choosing Pmnt run.

11. Select Start immediat. and choose Enter.

12. Choose Display payment log to display the executed payments.

13. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultThe payment document has been created.

The FI document 20000000XX that was created contains two line items. One line item has been posted to the account for outgoing domestic transfers (bank subaccounts ending with character 2). The posting was allocated to the planning level B2 (resulting from the assignment of the planning level B2 to all bank subaccounts ending with the digit 2).

The other line item has been posted to the subaccount of the recipient bank, which has an account number that ends with the digit 5. The account has been assigned to the planning level B5.

The impact of the outgoing cash concentration payment on Cash Position is visible in the Cash Management Report.

4.5 Financial Overview / Cash Position & Liquidity Forecast

UseThe cash position gives you an overview of daily cash inflow and outflow on the selected bank accounts. The cash position is suitable to plan short-term liquidity.

You can use the liquidity forecast to identify the medium-term cash inflows and outflows generated by the posted debit-side and credit-side invoices.

In customizing you define the grouping structures that group together particular bank and/or subledger accounts in the cash position or the liquidity forecast display. The selection of a certain grouping during execution of Cash position & Liquidity Forecast, influences the result of this report.

The following groupings are defined:

Grouping Purpose

YALL includes all customer and vendor accountsprovides an overview categorized according to the planning groups

YTOTAL includes all bank accounts and vendor/customer accounts

© SAP AG Page 64 of 71

Page 65: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

YBANK-BK1 Including all bank accounts - bank 1

YBANK-BK2 Including all bank accounts - bank 2

YBANKS includes all house bank accounts and subaccountsprovides an overall overview of the short-term cash position

YCASHCONC Includes all main bank accounts and selected bank subaccounts that are managed in a local currency and that are to be included in the cash concentration process

© SAP AG Page 65 of 71

Page 66: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting Financial Supply Chain Management Cash and Liquidity Management Cash Management Information System Reports for Cash Management Liquidity Analyses Cash Position

Transaction code FF7A

© SAP AG Page 66 of 71

Page 67: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Treasurer

(SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Reporting Cash Position

© SAP AG Page 67 of 71

Page 68: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

2. On the Cash Management and Forecast: Initial Screen, make the following entries:

Field name Description User action and values Comment

Company Code 1000

Cash Position select Analysis of the bank accounts

Liquidity Forecast

select Analysis of cash inflows and outflows or planned items in subledger accounts.

Grouping YTOTAL This grouping provides a total overview of the accounts.

Display as of any date for example, today’s date

Display in AED Display Currency should be local currency of company code in this case - cash concentration was executed in the local currency

© SAP AG Page 68 of 71

Page 69: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

3. Choose Execute.

4. The Cash Mgmt and Forecast: Currency Overview screen appears. This provides an overview of the liquidity trend for a longer period of time.

5. To change the current display, select New Display.

6. In the New Display dialog box, select Delta Display w / Balances and choose Continue.

The data is displayed in accordance with the control parameters selected in the form of a delta display with the beginning and ending balance.

6. Choose Back (F3) to the SAP Easy Access screen (SAP GUI)

Or

Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultOpen Invoices and memo records

All open vendor invoices are visible within the A* planning group.

All open customer invoices are visible within the E* planning group.

The memo records are visible under the corresponding planning group.

Bank Accounts

The bank accounts are visible under planning level F0.

The following relationship exists between the bank accounts and the cash management accounts:

Bank account Description Cash Management account

113100 Bank 1 - AED account AE-AED-BNK

113150 Bank 1 - EUR account AE-EUR-BNK

113160 Bank 1 - USD account AE-USD-BNK

113200 Bank 2 – AED account AE-AED-DEB

© SAP AG Page 69 of 71

Page 70: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Cleared Open Vendor Items

The cleared amounts for open vendor items are displayed on the corresponding bank subaccounts (G/L accounts for outgoing payments), for example, under planning level B2 - Domestic transfer or B3 – Foreign Transfer.

Depending on the house bank & account that was determined by the payment run and the used payment method (U= domestic transfer, L= foreign transfer) the amount should be visible on one of the following bank subaccounts:

Bank account Description Cash Management account

113102 Bank 1 - AE outgoing payment DB-AED-TRD

113155 Bank 1 - other interim posting (EUR) AE-EUR-TRD

113165 Bank 1 - other interim posting (USD) AE-USD-TRD

113202 Bank 2 - outgoing payment AE-AED-INC

© SAP AG Page 70 of 71

Page 71: 160 Bpp en Ae Cash Management

SAP Best Practices Cash Management (160): BPD

Cleared Open Customer Items

The cleared amounts for open customer items are displayed on the corresponding bank subaccounts (G/L accounts for incoming payments) for example, under planning level B4 - Automatic Debit or B9 – Customer Incoming Payment.

Depending on the house bank and account, the cleared open items should be visible on one of the following bank subaccounts:

Bank account Description Cash Management account

113104 Bank 1 - automatic debit AE-AED-DIS

113204 Bank 2 - automatic debit AE-AED-BAD

5 Appendix

5.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Archiving the Memo Record

Transaction code ( SAP GUI) FF6B

Reversal: Reactivate archived Memo Records

Transaction code ( SAP GUI) FF6B

Business role Treasurer

(SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Planning Change Memo Record

Comment When on the selection screen of the report a Archiving Category is chosen, all archived memo records are displayed. The function Convert can be used to reactivate a previously archived memo record.

Creating a Concentration Proposal

Transaction code ( SAP GUI) FF73

Reversal: Archiving the Memo Record

Transaction code ( SAP GUI) FF6B

Business role Treasurer

(SAP_NBPR_TREASURER-S)

Business role menu Cash Management Cash Management Planning Change Memo Record

Comment To reverse the result of a cash concentration run, all generated payment advices need to be archived.

(compare step 4.6).

© SAP AG Page 71 of 71