AC805-CashManagement

AC805 Cash Management AC805

R/3 System Release 46C 04/05/2001

0

AC805 Cash Management.................................................................................................................................................1 Copyright.......................................................................................................................................................................2 Treasury.....................................................................................................................................................................4 Course Prerequisites...................................................................................................................................................5 Target Group..............................................................................................................................................................6 Course Overview...........................................................................................................................................................1 Course Goal...............................................................................................................................................................2 Course Objectives......................................................................................................................................................3 Table of Contents (1).................................................................................................................................................4 Table of Contents (2).................................................................................................................................................5 Overview Diagram (1)...............................................................................................................................................6 Overview Diagram (2)...............................................................................................................................................7 Main Business Scenario.............................................................................................................................................8 Chart of Accounts (1).................................................................................................................................................9 Chart of Accounts (2)...............................................................................................................................................10 Chart of Accounts (3)...............................................................................................................................................11 Overview of Cash Management.....................................................................................................................................1 Overview of Cash Management:Unit Objectives......................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Overview of Cash Management Business Scenario..................................................................................................5 Overview of SAP Treasury........................................................................................................................................6 Problems and Objectives............................................................................................................................................7 Instruments in SAP R/3 Cash Management...............................................................................................................8 Overview....................................................................................................................................................................9 Concepts in SAP R/3 Cash Management.................................................................................................................10 Procedure for Day-to-Day Planning........................................................................................................................11 Overview of Cash Management: Unit Summary.....................................................................................................12 Overview of Cash Management: Exercises.............................................................................................................13 Overview of Cash Management: Solutions.............................................................................................................14 Cash Position.................................................................................................................................................................1 Cash Position: Unit Objectives..................................................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Cash Position: Business Scenario..............................................................................................................................5 Features of the Cash Position.....................................................................................................................................6 Integration: Cash Position..........................................................................................................................................7 Prerequisites Bank Account Organization.................................................................................................................8 Prerequisites: Bank Accounting................................................................................................................................9

Prerequisites: Bank Accounts.................................................................................................................................10 Prerequisites: Planning Levels................................................................................................................................11 Cash Position: Display.............................................................................................................................................12 Cash Position: Accounts and Levels........................................................................................................................13 Currency Display.....................................................................................................................................................14 Cash Position: Unit Summary..................................................................................................................................15 Tagesfinanzstatus Exercises.....................................................................................................................................16 Cash Position Solutions...........................................................................................................................................17 Cash Position Customizing............................................................................................................................................1 Cash Position Customizing: Unit Objectives.............................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Cash Position Customizing: Business Scenario.........................................................................................................5 G/L Accounts: Account Groups.................................................................................................................................6 Documents: Field Status and Value Date..................................................................................................................7 Bank Account: Configuration....................................................................................................................................8 House Banks - Correspondence Banks......................................................................................................................9 Bank Accounts.........................................................................................................................................................10 Planning Levels........................................................................................................................................................11 Cash Management Account Name...........................................................................................................................12 Grouping: Setup.......................................................................................................................................................13 Grouping: Functions................................................................................................................................................14 Cash Position Customizing: Unit Summary............................................................................................................15 Cash Position Customizing: Exercises.....................................................................................................................16 Cash Position Customizing: Solutions.....................................................................................................................18 Manual Memo Records..................................................................................................................................................1 Manual Memo Records: Unit Objectives..................................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Manual Memo Records: Business Scenario..............................................................................................................5 Manual Planning........................................................................................................................................................6 Creating Memo Records............................................................................................................................................7 Changing Memo Records Using Lists.......................................................................................................................8 Loading External Memo Records..............................................................................................................................9 Payment Advice Journal..........................................................................................................................................10 Manual Memo Records: Unit Summary..................................................................................................................11 Manual Memo Records: Exercises..........................................................................................................................12 Manual Memo Records: Solutions...........................................................................................................................14 Customizing Manual Memo Records............................................................................................................................1

Customizing Manual Memo Records: Unit Objectives.............................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Customizing Manual Memo Records: Business Scenario.........................................................................................5 Planning Types...........................................................................................................................................................6 Archive: Retention Period..........................................................................................................................................7 Archive / Automatic Expiration - Examples..............................................................................................................8 Customizing Manual Memo Records: Unit Summary...............................................................................................9 Customizing Manual Memo Records:Exercises......................................................................................................10 Customizing Manual Memo Records: Solutions.....................................................................................................11 Check Deposit................................................................................................................................................................1 Check Deposit: Unit Objectives.................................................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Check Deposit: Business Scenario............................................................................................................................5 Check Deposit: Procedure........................................................................................................................................6 Account Assignment..................................................................................................................................................7 Check Deposit: Initial Specifications.........................................................................................................................8 Check Deposit: Initial Specifications (2)...................................................................................................................9 Check Deposit List...................................................................................................................................................10 Check Deposit: Printing and Overview...................................................................................................................11 Generating Postings.................................................................................................................................................13 Check Deposit: Unit Summary................................................................................................................................14 Check Deposit Exercises..........................................................................................................................................15 Check Deposit Solutions..........................................................................................................................................17 Check Deposit: Customizing.........................................................................................................................................1 Check Deposit Customizing: Unit Objectives...........................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Check Deposit Customizing: Business Scenario.......................................................................................................5 Customizing Process - Transactions / Posting Rules.................................................................................................6 Postings and Account Determination.........................................................................................................................7 Simulating Postings...................................................................................................................................................8 Creating Screen Variants...........................................................................................................................................9 Check Deposit Customizing: Unit Summary...........................................................................................................10 Check Deposit Customizing: Exercises...................................................................................................................11 Check Deposit Customizing: Solutions...................................................................................................................12 Bank Statement: Manual Entry......................................................................................................................................1 Bank Statement - Manual Entry: Unit Objectives.....................................................................................................2

Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Bank Statement - Manual Entry: Business Scenario.................................................................................................5 Manual Bank Statement: Procedure...........................................................................................................................6 Entering the Bank Statement.....................................................................................................................................7 Processing the Bank Statement (1): Bank and Payment Advices..............................................................................8 Processing the Bank Statement (2): Bank Document / Selection..............................................................................9 Processing the Bank Statement (3): Further Processing..........................................................................................10 Manual Bank Statement Posting Examples.............................................................................................................11 Manual Bank Statement Posting Examples.............................................................................................................12 Manual Bank Statement Posting Examples.............................................................................................................13 Bank Statement - Manual Entry: Unit Summary.....................................................................................................14 Bank Statement - Manual Entry Exercises..............................................................................................................15 Bank Statement: Manual Entry Solutions................................................................................................................18 Manual Bank Statement: Customizing..........................................................................................................................1 Manual Bank Statement Customizing: Unit Objectives............................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Manual Bank Statement Customizing: Business Scenario........................................................................................5 Posting Rules and Transactions.................................................................................................................................6 Posting Details...........................................................................................................................................................7 Determining Accounts from House Bank Data.........................................................................................................8 Posting Rule and Account Determination..................................................................................................................9 Manual Bank Statement Customizing: Unit Summary............................................................................................10 Manual Bank Statement - Customizing: Exercises..................................................................................................11 Bank Statement: Electronic Entry..................................................................................................................................1 Bank Statement - Electronic Entry: Unit Objectives.................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Bank Statement - Electronic Entry: Business Scenario.............................................................................................5 Electronic Bank Statement: Features (1)...................................................................................................................6 Electronic Bank Statement: Features (2)...................................................................................................................7 Electronic Bank Statement - Various Formats Supported.........................................................................................8 Generating Test Data - RFEBKATX.........................................................................................................................9 Importing Bank Statement Data...............................................................................................................................10 MultiCash Files........................................................................................................................................................11 Electronic Bank Statement: Printout........................................................................................................................12 Electronic Bank Statement: Postprocessing.............................................................................................................13 Processing Incomings: Postings on Account...........................................................................................................14

Important Criteria.....................................................................................................................................................15 Bank Statement - Electronic Entry: Unit Summary.................................................................................................16 Electronic Bank Statement: Exercises.....................................................................................................................17 Solutions..................................................................................................................................................................19 Electronic Bank Statement: Customizing......................................................................................................................1 Electronic Bank Statement - Customizing: Unit Objectives......................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Electronic Bank Statement - Customizing: Business Scenario..................................................................................5 Transactions...............................................................................................................................................................6 Account Determination..............................................................................................................................................7 Interpretation Algorithm............................................................................................................................................8 Electronic Bank Statement - Customizing: Unit Summary.......................................................................................9 Extended Bank Processing: Checking Programs...........................................................................................................1 Extended Bank Processing: Checking Programs Unit Objectives............................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Extended Bank Processing: Checking Programs Business Scenario.........................................................................5 Comparing Payment Advices with the Bank Statement or Account.........................................................................6 Comparing Value Dates.............................................................................................................................................7 Cashed Checks Analysis: G/L Account / Vendor......................................................................................................8 Extended Bank Processing: Checking Programs Unit Summary..............................................................................9 Extended Bank Processing - Checking Programs: Exercises..................................................................................10 Extended Bank Processing: Solutions.....................................................................................................................11 Cash Concentration........................................................................................................................................................1 Cash Concentration: Unit Objectives.........................................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Cash Concentration: Business Scenario.....................................................................................................................5 Cash Concentration: Overview..................................................................................................................................6 Cash Concentration: Program....................................................................................................................................7 Cash Concentration: Posting Processes.....................................................................................................................8 Cash Concentration and Payment Program...............................................................................................................9 Payment Program Parameters..................................................................................................................................10 Source Indicators.....................................................................................................................................................11 More New Features in the Payment Program..........................................................................................................12 Cash Concentration: Unit Summary........................................................................................................................13 Cash Concentration: Customizing.................................................................................................................................1 Cash Concentration - Customizing: Unit Objectives.................................................................................................2

Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Cash Concentration - Customizing: Business Scenario.............................................................................................5 Cash Concentration - Specifications..........................................................................................................................6 Concentration - Configuration Examples..................................................................................................................7 Cash Concentration - Correspondence.......................................................................................................................8 Confirmation: Address / Account No........................................................................................................................9 Field Selection Control in the Payment Program....................................................................................................10 Customizing Source Symbols..................................................................................................................................11 Cash Concentration - Customizing: Unit Summary................................................................................................12 Cash Concentration Exercises..................................................................................................................................13 Cash Concentration: Solutions.................................................................................................................................15 Liquidity Forecast..........................................................................................................................................................1 Liquidity Forecast: Unit Objectives...........................................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Liquidity Forecast: Business Scenario.......................................................................................................................5 Characteristics of the Liquidity Forecast...................................................................................................................6 Integration: Liquidity Forecast..................................................................................................................................7 Requirements (1): Planning Groups...........................................................................................................................8 Requirements (2): Master Record..............................................................................................................................9 Payment History - Planning Date............................................................................................................................10 Integration: Payment Block.....................................................................................................................................11 Integration: Special Transactions.............................................................................................................................12 Liquidity Forecast: Unit Summary..........................................................................................................................13 Liquidity Forecast: Exercises...................................................................................................................................14 Liquidity Forecast: Solutions...................................................................................................................................16 Liquidity Forecast Customizing: Unit Objectives.........................................................................................................1 Liquidity Forecast: Customizing................................................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Liquidity Forecast Customizing: Business Scenario.................................................................................................5 Master Data: Subledger Accounts.............................................................................................................................6 Percentage Distribution..............................................................................................................................................7 Planning Data: Screen Control...................................................................................................................................8 Blocked Documents...................................................................................................................................................9 Integration: Special General Ledger (SGL).............................................................................................................10 Integrating Orders and Purchase Orders..................................................................................................................11 Integrating Orders and Purchase Orders..................................................................................................................12

Integration with Other SAP Modules......................................................................................................................13 Selection of Financial Instruments...........................................................................................................................14 Treasury Management: Functions............................................................................................................................15 Transaction and Balance Management Process.......................................................................................................16 Trading: Create Fixed-Term Deposit.......................................................................................................................17 Postings Using Bank Clearing Accounts Interaction of TR-TM and TR-CM........................................................18 Transfer to Financial Accounting: Logical Process.................................................................................................19 Liquidity Forecast Customizing: Unit Summary.....................................................................................................20 Data Transfer and Reorganization.................................................................................................................................1 Data Transfer and Reorganization: Unit Objectives..................................................................................................2 Overview Diagram (1)...............................................................................................................................................3 Overview Diagram (2)...............................................................................................................................................4 Data Transfer and Reorganization: Business Scenario..............................................................................................5 Implementation Support.............................................................................................................................................6 Transferring Data from Accounts With/Without Open Items...................................................................................7 Data Reconciliation....................................................................................................................................................8 Reorganization...........................................................................................................................................................9 Data Transfer and Reorganization: Unit Summary.................................................................................................10

0 AC805 Cash Management

AC805 Cash Management  SAP AG 1999

   

SAP R/3 System Release 4.6A September 1999 Material No. 5003 4193

0.2 Copyright

Copyright 2000 SAP AG. All rights reserved. Neither this training manual nor any part thereof may be copied or reproduced in any form or by any means, or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to change and supplement without prior notice. All rights reserved.

 SAP AG 1999

       

  

Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM are registered trademarks of Informix Software Incorporated. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139. JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP™, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countries all

over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.  Design: SAP Communications Media

0.3 Treasury Level 2

Level 3 AC815 5 days Loans Management for Financial Services

AC030

3 days

Treasury Overview

AC810 3 days Basic Functions in Treasury Management

AC816 3 days Loans Management for Corporates AC820

4 days

Securities Management AC825 3 days Money Market, Foreign Exchange and Derivatives AC830

3 days

Market Risk Management AC805 AC010

5 days

Financial Accounting and Reporting

 SAP AG 1999

3 days

Cash Management AC215 Cash Budget Management

1 day

0.4 Course Prerequisites

 Practical knowledge of R/3 FI Financial

Accounting  Recommended:

Attendance at AC010 - Overview of Financial Accounting and Reporting Attendance at AC030 - Overview of Treasury

 SAP AG 1999

0.5 Target Group

 Participants: 

Members of the project team



System managers



Personnel from the user department and Controlling

 Duration: 3 days

 SAP AG 1999

Advice for Users  The training documentation is not designed to be a teach-yourself course. You will only have complete information if you have the documentation and listen to the course instructor. The documentation includes space for you to write your own notes.

1 Course Overview

Contents  Course goal  Course objectives  Course content  Course overview diagram  Main business scenario  Extract from FI chart of accounts

 SAP AG 1999

(C) SAP AG

AC805 1

1.2 Course Goal

This course will prepare you to:  Understand how and where you can use

SAP Cash Management  Use the detailed functions available for liquidity

monitoring and Electronic Banking

 SAP AG 1999

(C) SAP AG

AC805 2

1.3 Course Objectives

At the conclusion of this course, you will be able to:  Describe how and where SAP Cash Management can be used  Set up the structures required for short- and medium-term liquidity monitoring in your business  Explain the various options available for integrating external bank data with SAP Cash Management  Define the system settings needed to control internal processing

 SAP AG 1999

(C) SAP AG

AC805 3

1.4 Table of Contents (1)

Preface Unit 1

Course Overview

Unit 7

Check Deposit

Unit 2

Overview of Cash Management

Unit 8

Check Deposit: Customizing

Unit 3

Cash Position

Unit 9

Unit 4

Cash Position: Customizing

Bank Statement Manual Entry

Unit 10

Unit 5

Manual Memo Records

Manual Bank Statement Customizing

Unit 6

Manual Memo Records Customizing

 SAP AG 1999

(C) SAP AG

AC805 4

1.5 Table of Contents (2)

Unit 11

Bank Statement Electronic Entry

Unit 12

Electronic Bank Statement Customizing

Unit 13

Extended Bank Processing Checking Reports

Appendix  SAP AG 1999

(C) SAP AG

AC805 5

Unit 14

Cash Concentration

Unit 15

Cash Concentration: Customizing

Unit 16

Liquidity Forecast

Unit 17

Liquidity Forecast: Customizing

Unit 18

Date Transfer and Reorganization

1.6 Overview Diagram (1)

Course Overview Overview of Cash Management Cash Position Cash Position Customizing Manual Memo Records Customizing Manual Memo Records Check Deposit Check Deposit: Customizing Bank Statement: Manual Entry Manual Bank Statement: Customizing  SAP AG 1999

(C) SAP AG

AC805 6


Bank Statement: Electronic Entry Electronic Bank Statement: Customizing Extended Bank Processing: Checking Programs Cash Concentration Cash Concentration: Customizing Liquidity Forecast Liquidity Forecast: Customizing Data Transfer/Reorganization

 SAP AG 1999

(C) SAP AG

AC805 7

1.8 Main Business Scenario

 You have successfully implemented the R/3 FI

application component. You now want to activate short- and medium-term liquidity monitoring and use the Electronic Banking facilities.

 SAP AG 1999



You are a member of a project team whose task is to supply the decision makers in your company with information on movements in company liquidity.

(C) SAP AG

AC805 8

1.9 Chart of Accounts (1)

Index of account numbers used in FI training courses in Germany. The chart of accounts is called INT. Account name

Account number

Costs from exchange rate differences Costs from currency revaluation Output tax Bills of exchange receivable Office supplies Customer receivables Customer receivables - correction account DEUBA-0 (Current) DEUBA-1 (Outgoing checks) DEUBA-5 (Misc. clearing) DEUBA-8 (Incoming checks) DEUBA-9 (Cash receipts) DEUBA USD account DREBA-0 (Current) ...

0000230000 0000230010 0000175000 0000125000 0000476000 0000140000 0000140099 0000113100 0000113101 0000113105 0000113108 0000113109 0000113150 0000113200 ...

 SAP AG 1999

(C) SAP AG

AC805 9



Account number

Customer 1 Result carried fwd from previous year Down payments received Sales deductions Revenue from exchange rate differences Revenue from currency revaluation Guarantees given by customers Down payments made Cash Customer 1 Vendor payables Collection charges VAT clearing re customer down payment

T-T05Axx 0000900000 0000170000 0000889000 0000280000 0000280010 0000196100 0000159000 0000100000 T-T05Axx 0000160000 0000275300

 SAP AG 1999

(C) SAP AG

AC805 10

0000170010



Account number

Cash transaction incidental costs Cash discount paid Cash discount received Raw materials Net sales - without CO-PA Unauthorized deduction of cash discount Materials usage Input tax

0000479000 0000880000 0000276000 0000300000 0000800200 0000881000 0000400020 0000154000

 SAP AG 1999

(C) SAP AG

AC805 11

2 Overview of Cash Management

Contents  Instruments  Overview of functions  Concepts

 SAP AG 1999

(C) SAP AG

AC805 1

2.2 Overview of Cash Management: Unit Objectives

At the conclusion of this unit, you will be able to:  Give colleagues an overview of SAP R/3 Treasury  Distinguish between the cash position and the liquidity forecast in Cash Management, and what they do  Distinguish between levels, groups, and accounts

 SAP AG 1999

(C) SAP AG

AC805 2


Introduction Overview of Cash Management Cash Position Cash Position Customizing Manual Planning Manual Planning: Customizing Check Deposit Check Deposit: Customizing Bank Statement: Manual Entry Manual Bank Statement: Customizing  SAP AG 1999

(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

2.5 Overview of Cash Management Business Scenario

 Before starting work in your project team, you

want to obtain an overview of SAP R/3 Treasury.  What are the objectives of the new financial

planning system, and what instruments are available for safeguarding short- and medium-term liquidity?  What is the significance of accounts, groups,

and levels in planning?

 SAP AG 1999




(C) SAP AG

AC805 5

2.6 Overview of SAP Treasury Download

Market data

TM

Business partners

Derivatives Securities Loans Money market Forex

Market Risk Management • Interest/currency exposure • Sensitivity • Market-to-Market • Risk analysis/simulation • Value-at-Risk Transaction Management • Management of financial transactions and balances • Transfer to financial accounting • Flexible reporting • Datafeed interface Cash Management • Electronic Banking • Liquidity status • Integration with operative systems • Control functions

Bank data

Financial Accounting

Logistik

D

C

D

100

C 100

 SAP AG 1999



The objective of SAP Treasury is to ensure an efficient, commercial system of liquidity, portfolio, and risk management.



SAP Treasury is divided accordingly, as follows: Cash Management (CM) offers functions aimed at achieving efficient liquidity analysis. Treasury Management / Loan Management (TM/LO) supports management of financial transactions and balances. Market Risk Management (MRM) includes methods and processes for assessing risk positions.

(C) SAP AG

AC805 6

2.7 Problems and Objectives

Business Objectives

Current Problems 1. Too many bank accounts 2. Accounting by value date is required

1. Ensuring optimum liquidity for maturing obligations

3. Unreliable planning tools

2. Preparing and transferring short, medium, and long-term funds at maturity

4. Investment instruments not used to their fullest potential

3. Control over incoming and outgoing payments

5. Lack of payment strategy

4. Information on managing short-term cash investments or borrowings

Outcome All necessary information must be accessible in the cash management system

 SAP AG 1999

Most businesses have too many bank accounts, held at too many different banks. This makes it difficult to keep an overview of the relevant account balances.  As banks send statements daily, precise, value-date accounting does not take place often. Businesses miss out on the full benefits of investment instruments because value date information is lacking.  Payments are often made from one account only, regardless of whether it contains sufficient funds.  The tasks of a cash management system are to:  Analyze financial transactoins in completed accounting periods  Identify and reproduce future movments in financial budgeting as precisely as possible 

(C) SAP AG

AC805 7

2.8 Instruments in SAP R/3 Cash Management

Instrument 1. Cash position - Short term - By value date

Data - Bank accounts - Bank clearing accounts - Memo records

Typical Time Horizon 1 - 2 days

2. Liquidity forecast - Customers - Medium term - Projection of flows in and out - Taxes

- Vendors - FI, MM, SD - Planned items

1 - 24 weeks

 SAP AG 1999



SAP R/3 Cash Management 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 movments in subledger accounts too



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 you can use 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.



Financial budgeting and the long-term view of cash flow (target/actual comparison) at G/L account level are not supported by SAP R/3 Cash Management, but are included instead in SAP R/3 Cash Budget Management.

(C) SAP AG

AC805 8

2.9 Overview

Cash Position UpUp-toto-date presentation of bank accounts, and presentation by value date Daily liquidity forecast Liquidity movements Data input eliminates redundancy All cash management transactions can be documented or revised

Liquidity Forecast Inclusion of all data resident in the system (Example: purchase orders) Project of flows in and out over a given period Help in optimizing investments and borrowings Safeguarding company liquidity

Basis for cash concentration

 SAP AG 1999



SAP Cash Management has the same goals as conventional cash management systems, namely to: •

Safeguard company liquidity so that payment obligations can be met

•

Monitor payment flows



SAP Cash Management uses the cash position to reflect movements in bank accounts, while movements in the subledger accounts are represented using the liquidity forecast.



The liquidity forecast is based on payments in and out from/to customers and vendors, per the open items. As planning for incoming and outgoing payments covers a larger timeframe, the probability of the payments occurring on the day given is less than in the cash position.

(C) SAP AG

AC805 9

2.10 Concepts in SAP R/3 Cash Management

Cash Position

Source of data = Level

Account / Group

Outcome:

Level

Manual memo records Bank postings

Bank accounts Bank clearing accounts

Liquidity Forecast Manual planning records Invoices Orders Purchase orders Planned items, Planned items, Customer groups Customer groups Vendor groups Vendor groups (Examples: personnel (Examples: personnel expenses,taxes) expenses, taxes)

Permits a high-quality statement on balances in accounts/groups ("Levels explain accounts/groups.")

 SAP AG 1999

The format of the cash position and the liquidity forecast is determined by two features: Both reports contain levels. These supply high-quality information on the commercial reasons for a movement in an account - that is, they explain how the account opening and closing balances came about. For example, levels give information on whether a balance in a bank account is the result of a bank posting or of a memo record entered manually. They can also be classified according to how secure the receipt is - for example, by confirmed or unconfirmed memo record.  In the cash position, accounts (bank and bank clearing accounts) supply information on the current balance.  The liquidity forecast contains groups instead of accounts. Vendors and customers are assigned to a planning group by means of an entry in the master records. Each group reflects certain features, procedures, or risks.  

(C) SAP AG

AC805 10

2.11 Procedure for Day-to-Day Planning NextNext-day preparation (Payment advices, advices, print output, documentation) Invest/Borrow Cash

Correspondence (Bank orders, documents)

Execute Cust.friendly Cust.friendly liquidity forecast (liquidity trend)

Payments Made (Checks, bank transfers, . . . ) . . )

Planning Decision Basic Planning Data

Bank Statements - Electronic - Manual  SAP AG 1999



The main tasks of an MRP controller are to:  Maintain company liquidity  Clear deficits  Invest surpluses profitably

(C) SAP AG

AC805 11

Cash Concentration (Permanent average balances)

Money Market (Interest terms)

Manual Planning - Payment advices - Forecast values - Subaccounts (Example: check deposit)

2.12 Overview of Cash Management: Unit Summary

 Cash position: liquidity monitoring in bank accounts and bank subaccounts  Liquidity forecast: safeguarding/monitoring liquidity, including movements in vendor/customer accounts  Structure by groupings, levels, and accounts/groups

 SAP AG 1999

(C) SAP AG

AC805 12

2.13Overview of Cash Management: Exercises Unit: Overview of Cash Management Topic: Overview of Functions and Concepts

At the conclusion of these exercises, you will be able to: •

Give colleagues an overview of SAP R/3 Treasury

•

Distinguish between the cash position and the liquidity forecast in Cash Management, and what they do

•

Distinguish between levels, groups, and accounts

Before starting work in your project team, you want to obtain an overview of SAP R/3 Treasury. What are the objectives of the new financial planning system, and what instruments are available for safeguarding short- and medium-term liquidity?

1-1 Are the following statements true (T) or false (F)? 1-1-1 The liquidity forecast works with bank value dates. 1-1-2 The typical timeframe for the cash position is 1-2 days. 1-1-3 The main objective of the cash position is to safeguard company liquidity. 1-1-4 Levels in the cash position provide information on the origin of account movements. 1-1-5 Groups in the liquidity forecast permit high quality statements on the account balance.

(C) SAP AG

AC805 13

2.14Overview of Cash Management: Solutions Unit: Overview of Cash Management Topic: Overview of Functions and Concepts

1-1 Solutions for the statements: 1-1-1 False - The liquidity forecast works with bank value dates. The liquidity forecast, on the other hand, works with customer and vendor groups. 1-1-2 True - The typical timeframe for the cash position is 1-2 days. 1-1-3 False - The main objective of the cash position is to give you a current overview, correct by value date, of short term developments in your bank accounts. The main objective of the liquidity forecast, on the other hand, is to safeguard company liquidity. 1-1-4 True - Levels in the cash position provide information on the origin of account movements. 1-1-5 False - It is the levels, not the groups, that enable a qualitative statement on the account balance. The groups, on the other hand, reproduce the account balance.

(C) SAP AG

AC805 14

3 Cash Position

Contents  Features  Organizational and technical requirements for integration  Accessing the cash position  Grouping function  Currency display and currency risk

 SAP AG 1999

(C) SAP AG

AC805 1

3.2 Cash Position: Unit Objectives

At the conclusion of this unit, you will be able to:  Recognize the specific features of the cash position  Outsort bank accounts  Access the flexible display structures and set up the various currency displays

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

3.5 Cash Position: Business Scenario

 First, you want to create an instrument which will give you useful information about your bank accounts.  You use the cash position for this, considering first its specific attributes and aspects of integration.  To be able to use the cash position effectively, you must first set up your FI bank accounts in a particular structure, and configure them accordingly.  This unit surveys the flexible configuration options available in the cash position.  SAP AG 1999




(C) SAP AG

AC805 5

3.6 Features of the Cash Position

Cash Position  Bank account balances by value date  Parallel management of foreign currencies  Cash position covering the next few days  Manual memo records as plan items  Automatic payment using expected value days  Cashed check monitoring

 SAP AG 1999



The cash position is the result of the entry, by value date, of all the payments in a given, short time horizon.



There are three sources of data for the cash position: •

FI postings to cash-management-relevant G/L accounts

•

Memo records entered manually

• Cash flows from business transactions managed with the Treasury Management application component. 

You use the grouping to set up the display.

(C) SAP AG

AC805 6

3.7 Integration: Cash Position

Electronic bank statements

FI


Planning Analyses

CM

Bank accounting

Cash Management Cash position

FI

Correspondence

 SAP AG 1999

After the bank statements are posted in FI, the account transactions can be displayed in the cash position. The balances in the bank accounts, which you can display using the cash position, form the basis for planning decisions.  Treasury transactions can also be displayed in the cash position, under certain conditions.  

(C) SAP AG

AC805 7

3.8 Prerequisites Bank Account Organization

USD UNI account Bank account account Risks

CHF

USD Risks UNI Risks Contingent liability Bill of exchange liability

Investments CHF Investments USD Investments UNI Overnight Long-term investments

CHF

Processing

CHF Processing USD Processing UNI Daily operations Check deposit Outgoing checks Bank transfer Bank collections

 SAP AG 1999

Bank accounting is to provide a bank (current) account for each currency and, in each case, a clearing account, on a lower level and per processing type.  You can tailor the clearing accounts to the needs of your business.  Objectives: - Accounts can be reconciled at any time - Foreign currency and local currency are managed in parallel - Can be managed by value date - Interest can be calculated - Line item analysis possible - Contingent liabilities can be monitored - Items posted automatically using automatic payment transactions - Automatic breakdown using electronic banking transactions  Only transactions which are, according to the bank statement, active are posted in the bank (current) accounts. 

(C) SAP AG

AC805 8

3.9 Prerequisites: Bank Accounting 113100 BANKA Current account

1. Payment transactions

01

Outgoing checks

02 03

Bank transfer

04

Foreign BTfr

09

.......... 2. Bank statements

Cash receipt

Cash Management  SAP AG 1999

 

You want to implement SAP Cash Management and have to configure the chart of accounts. You need to create a general ledger account for each active account you have at the bank, by currency if applicable. In addition, you need to create bank clearing accounts for each bank account, also by currency if applicable. In this connection, we recommend the following grouping:         



113100 113101 113102 113103 113104 113105 : 113108 113109

Bank 1 (current account - domestic - currency UNI) Bank 1 (outgoing checks) Bank 1 (outgoing bank transfer, domestic) Bank 1 (outgoing bank transfer, foreign) Bank 1 (automatic deposit) Bank 1 (miscellaneous interim postings) Bank 1 (incoming checks) Bank 1 (customer cash receipts)

Processing sequence 1. Payment transactions: are posted against the clearing accounts using the payment program. 2. Bank statements: balance the clearing entries against the bank account. 3. Cash Management: displays or monitors postings, with the help of various groupings.

(C) SAP AG

AC805 9

3.10 Prerequisites: Bank Accounts

Field Control Sort key

Bank Account

027

Planning level

005 X

Open item management Line item display

Subaccount

X

X

F0

B?

Customizing: Field status - payment transactions Value date

X

X

 SAP AG 1999

Bank accounts must be configured so that the bank postings are included in planning. If you want to derive the balance in the cash position, which is always managed by value date, you should managed the bank (current) accounts by value date also. It is not necessary to manage open items. Data is recorded in G/L account currency. All bank (current) accounts should be assigned to a unique planning level, where bank statements and, with them, the actual bank balance are represented.  On the other hand, you should manage bank clearing accounts on an open item basis. They can, for example, be sorted by local currency amount. Depending on the type of bank clearing account, a specific planning level is then assigned - for example, for:  

 113102  113109

(C) SAP AG

Bank 1 (outgoing bank transfer, domestic): B2 level Bank 1 (customer cash receipts): a B9 level

AC805 10

3.11 Prerequisites: Planning Levels Master record 113101 : Planning level: B1 :

Customizing table B1: Outgoing checks : F0: FI bank posting :

Master record 113100 : Planning level: F0 :

Cash Position DEUBA Level

MM/DD/YY

-----------------------------------F0 60000 B1 10000

 SAP AG 1999



Planning level explain the beginning and ending balances in an account and supply information on what brought them about. You can define them in a customizing table.



The planning level field (FD-EBENE) must be activated in the bank account master record using the field status group.



The balances are displayed at the appropriate level in the cash position.

(C) SAP AG

AC805 11

3.12 Cash Position: Display

Company code . . . . . . . . . . AC01 : X Cash position : Grouping . . . . . . . . . . . . . . Banks Display by . . . . . . . . . . . . . Date Display in . . . . . . . . . . . . . UNI : Display type . . . . . . . . . . . . . .

K/D

 SAP AG 1999



You use the grouping to set up the display. The grouping determines which levels and accounts are displayed.



On the initial screen specify the selection options for the following accounts analysis: Company code: company code whose bank data you want to display Cash position: X displays bank data Grouping: Special view - selects the accounts Display by: (aggregated) starting date of the account forecast Planned currency: Display in: Currency code. Affects selection of the documents to be totaled and the currency translation (currency risk) Increment: Increment: time frame (1-99) in days (T), weeks (W) or months (M) Display type: As wells as the accumulated display, you can access a delta display showing disbursements and receipts. The beginning and end balances can also be selected for the delta display. Scaling This is where you determine the number of decimal places for the display.



The first thing you see is a partial selection, showing the most important entries. Choose All selections to view the other selections too. Use Variants.

(C) SAP AG

AC805 12

3.13 Cash Position: Accounts and Levels Grouping: Banks BANKA BANKB : Accounts: BANKA Account 1 Account 2 Account 3 Level: Account 1 CA Confirmed advice B2 Incoming check F0 Bank posting Line Item Display Assignment YYYY0801

08/01/YY

08/02/YY

08/03/YY

50 4040-

70 2020-

60 3030-

08/01/YY

08/02/YY

08/03/YY

60 1010-

60 101020

60 202020

08/01/YY

08/02/YY

08/03/YY

20 40

10 50

10 30 20

Doc. no.

..........

Amount

1

40000

 SAP AG 1999

The grouping term specifies how the system summarizes the data. The next screen after the initial screen is a basci screen, whose format is determined by the grouping and summarization terms entered in customizing. From here, you can branch to the levels, and from there to the relevant accounts, or vice versa. Various information appears, depending on the settings.  The overall balance for a bank appears by - Group (= account) where postings are made. They are listed along with their cash management account names. - Level (= source) of a bank or account transaction.  You can branch to the FI line items (top down).  Note: When you migrate from to 4.5B from an earlier release, you must completely reconstruct cash management because the update logic is different. In the case of the G/L account, the G/L account currency is not always adopted. Now, either the document currency (for G/L accounts managed on an open item basis) or the G/L account currency (for other G/L accounts) is used. Use the Data Setup function in transaction FDFD to delete the data and reconstruct it. See the last unit of this course documentation for details.  

(C) SAP AG

AC805 13

3.14 Currency Display

Cash Position Company code Business area: : Display in: LC Rate FC/LC : Rate LC/FC : :

AC00 **

In the list of examples below, "LC" means "local currency. That is, when posted, an amount in foreign currency (FC) is automatically translated into LC.

Planned currency

Display in

FC/LC

LC

-

LC/FC

Result

-

Amounts posted in local currency

LC

LC

-

-

Amounts posted in LC, no FC

FC

FC

-

-

Amounts posted in FC, no translation

FC

HC

-

-

Forex accounts: Amounts posted in FC translated at rate on day of posting (TCURR)

FC

LC

1.84

-

Posted FC amounts, translated at 1.84

FC1

FC2

1.84

1.20

Posted FC1 amounts translated into FC2 via local currency: 1.84 / 1.20 = 1.52

 SAP AG 1999



Amounts entered are shown in the currency you specified in the Display field. You can use the currency fields to display the foreign exchange risk.



On the one hand, you can show the cash position split by currency, depending on the specifications entered in the initial screen. However, you can also display the extent of your currency exposure from the cash position.



The average rate is usually used for the translation from planning currency to display currency. If you want to use a different rate for the translation, make the appropriate specification in the rate type field.

(C) SAP AG

AC805 14

3.15 Cash Position: Unit Summary

 Cash Position: overview of cash activity in bank accounts and bank clearing accounts  Top-down analysis to the document level  Currency analysis  Detailed account balance analysis by breaking down levels

 SAP AG 1999

(C) SAP AG

AC805 15

3.16Tagesfinanzstatus Exercises Unit: Cash Position Topic: Setup and Display Options At the conclusion of these exercises, you will be able to: • Check G/L accounts and correct them as necessary. • Enter G/L account postings so that you can see them in the cash position. To obtain an overview of the structure and display capabilities of the cash position, you will now enter a number of G/L account postings. These simulate postings in the bank accounts which are generated when the bank statement is imported. Any earlier postings are ignored.

1-1 Check and correct the following account masters to ensure that the field contents required for cash management are complete and correct (sort key, open item management, planning level: 113100, 113101, 113108, 113109, and 113200). 1-2 Today's bank statement results in the following G/L account postings: Outgoing check, vendor: 30,000 Value date: Today Transfer from customer: 50,000 Value date: Today Post against the clearing accounts 113101 and 113109 (posting records: 113101/113100 or 113100/113109).

1-3 Check the cash position (grouping "Bank, actual") to see how the postings look there. This display contains only the bank accounts, without bank clearing accounts.

(C) SAP AG

AC805 16

3.17Cash Position Solutions Unit: Cash Position Topic: Setup and Display Options

1-1 Solution: Check and correct account masters 113100, 113101, 113108, 113109, 113200 in respect of the field contents required for Cash Management.

 Accounting  Financial Accounting  General Ledger  Change Master Records  Enter Account Number and Company Code The type/description header shows the description of the accounts and the designation of this account as a balance sheet account. The control data shows, among other things, the account currency and the data needed to manage the account in the company code. Unlike bank clearing accounts, bank accounts are not managed on an open item basis. Similarly, whereas the local currency is used as the sort key for clearing accounts, the value date is used in the bank accounts. The entry, bank, and interest information contains the planning level and the assignment of the house bank ID and account ID. 1-2 Solution: Posting against the Clearing Accounts 113101 and 113109 (113101/113100 or 113100/113109).

 Accounting  Financial Accounting  General Ledger  Postings  G/L Account Posting (company code ACxx) Enter your data. Pay attention also to the value dates specified for the debit and credit postings. Example: 113101 - Debit - 30000 - Value date: Today 113100 - Credit - 30000 - Value date: Today

1-3 Solution: Checking Entries in the Cash Position (grouping: "BANKS"). (C) SAP AG

AC805 17

 Accounting  Treasury  Cash Management  Information System  Reports on Cash Management - Liquidity Analyses  Cash Position

Now enter your data (company code ACxx, grouping, "Bank, actual", display as of "Today", display in UNI). Press the "All selections" button. You can make further selections here. Enter the required increment (for example, in days) and choose "Delta display with balances" as the display type, so that you can identify your postings more easily. Run the program, ignoring the warning that the date is in the past. You now see your postings under the appropriate bank account. Navigate through the cash position.

(C) SAP AG

AC805 18

4 Cash Position Customizing

Contents  Bank account configuration  Bank accounting and house banks  Planning level structure  Cash management account name  Groupings structure

 SAP AG 1999

(C) SAP AG

AC805 1

4.2 Cash Position Customizing: Unit Objectives

At the conclusion of this unit, you will be able to:  Integrate a new house bank into your Cash Management setup  Set up and configure the G/L accounts (bank and bank clearing accounts) you need for short term cash management  Set up the grouping structures used in the cash position and assign the new G/L accounts to them

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

4.5 Cash Position Customizing: Business Scenario

 You now want to reproduce a house bank- that is, a bank where you hold customer/vendor accounts and from which you want to call up bank statement information - in your SAP Cash Management installation. You may already have created the bank when you implemented SAP FI Financial Accounting.  You must also create the relevant G/L accounts in the system and configure them according to defined criteria.  To reproduce these accounts in the cash position, give them a suitable description and assign them to a grouping term which is responsible for setting up the cash position.  SAP AG 1999




(C) SAP AG

AC805 5

4.6 G/L Accounts: Account Groups

Menu G/L account

113100

Customizing

Short text . . . :

CITI

ChAc

Acct group . . .

CASH

INT :

ActG CASH

from .. .

to ...

Description Liquid funds accounts

Edit Field status

Edit

Use

Financial specifications Reqd : Cash mgt :

Opt.

CASH

X

: 113100 113200

... ...

 SAP AG 1999



Every G/L account is assigned to an account group. This determines the setup for the second master record screen. You format it using the field status. Each account group within a chart of accounts can have a different field status.

(C) SAP AG

AC805 6

4.7 Documents: Field Status and Value Date

FStV

Field Status Group

0001 :

G005

Edit field status

Bank

Payment trans

Req.

Value date :

Opt.

X

Company code value date CC . . AC00 :

Default Value Date X

 SAP AG 1999

The field status group is responsible for the document format if you are posting to a particular account. For this reason, you must define the appropriate field status group for the bank account.  To manage bank postings by value date, you must enter the value date in all postings to the bank account. To this end, you can configure the relevant field status group in such a way that the "Value date" field is a required entry.  You can have the system automatically propose the current date as the value date. This makes things easier in training courses and system demonstrations, but not in commercial use because errors occur frequently. 

(C) SAP AG

AC805 7

4.8 Bank Account: Configuration

Acct no. : CC :

113700 AC00

Template: :

113100

: Open item mgmt ( ) Line item display : X Sort key : 027 :

:

Planning level : F0 House bank : WABA Bank acct : Current

 SAP AG 1999

The configuration of bank accounts determines how account transactions are allocated in the cash position: Open item managagement in subaccounts Line item display in bank accounts and subaccounts Sort key 005 (local currency amount) or 027 (value date), The planning level is copied to the documentation, is an assignment characteristic, and qualifies the account movement.  In Cash Management, correspondence with banks is triggered by means of the house bank and account ID (cash concentration). 

(C) SAP AG

AC805 8

4.9 House Banks - Correspondence Banks Company code

AC00

House Banks House bank Ctry Bank keys HOBA 1

US

HOBA 2 ...

US

500 200 10 ...

600 300 10 ...

Bank data House bank data Bank 1 Bank country DE Bank key 600 300 10 Address ______________ Institution ___ Region ___ Street ___ Town ___ Control data ______________ Swift code ___ Bank group ___ Post off. bank branch ___ Bank number 600 300 10  SAP AG 1999

 

House banks for each company code are stored under a freely definable ID (maximum five characters). All details of the house banks are managed in the bank directory.

(C) SAP AG

AC805 9

4.10 Bank Accounts

Company Code AC00 Bank Accounts House bank Acct-ID Citi 1 Citi 1 Citi 2 ...

Check USD GIRO ...

Bank Accounts Bank Account Data House bank Acct-ID

Text... Check acct USD acct Current acct ...

12345678 Check acct UNI USD acct Current acct 113200 ...

Bank Directory

G/L account Current account Company code

Bank account Citi 1 Check Currency Citi 1 USD Control key Citi 2 GIRO G/L account ... ... ...

Text...

House bank data Bank country Bank key

Citi 2 AC00

House bank

CITI 2

Bank acct key

CURR

Address ... Control ...

 SAP AG 1999

The company code bank accounts are stored under an account ID for the house banks that you define. You enter the external account number and its currency with the bank, along with the relevant G/L account number, thereby ensuring that postings go to the right accounts.  A G/L master record is created for each bank account.  In the G/L account master record, you can enter the house bank key and the account ID, so as to have access from the general ledger to the address data store for the house bank. This is necessary for bank correspondence, for example during cash concentration: the system uses the bank ID and account ID to obtain the address information from the bank directory.  If you maintain foreign exchange accounts, the currency key in the G/L master record must be the same as the currency in the foreign currency account. 

(C) SAP AG

AC805 10

4.11 Planning Levels

Level . . . Source Short text Long text _______________________________________________________ CA UA B1 DI F0 :

Source

BNK BNK BNK PSK BNK

Advice Advice OCheck Planning Fi-Banks

Description

Advice (confirmed) Advice(unconfrmd) Outgoing check General planning Bank acct posting

Cash position

_________________________________________________ BNK

Bank accounting

PSK

Subledger accounting :

X

 SAP AG 1999

You define a planning level in the G/L account master record, so that postings to this account can be seen in the cash position.  Planning levels provide information on the type of account transaction and the reason for the transaction. They are freely definable.  The Source indicator checks verifies that the data for the specified level is permitted in the cash position. The BNK source symbol is so define that all planning levels assigned to it are displayed in the cash position and not the liquidity forecast.  You can define new planning levels by selecting and copying the standard entries or by entering a completely new level. 

(C) SAP AG

AC805 11

4.12 Cash Management Account Name

Bk no. CM act name Bank account External acct no. ... _________________________________________________________ AC01 CICURR :

113100

110113100

...

Cash Position/Account Acct CC 08/01/YY 08/02/YY ... _________________________________________________________ AC01 CICURR :

11

11

...

 SAP AG 1999

In Cash Management, the cash management account name is a mnemonic name that replaces the account number.  The system uses the cash management account name in all transactions and reports (for example, the cash position) instead of the account number.  The account name is unique in each company code. Within Cash Management, it enables you to differentiate the same account numbers in different company codes.  It is a good idea to use cash management account names when you are planning across several company codes. You must use them when working with manual memo recordes or with cash concentration. 

(C) SAP AG

AC805 12

4.13 Grouping: Setup

Grouping Type Selection CoCode Chart SummztnTerm _______________________________________________________________ Bank-Act Bank-Act :

L G

++ 0000113+00

** CITIBANK

Grouping Header Additional header _______________________________________________________________ Bank-Act :

Bank acct history

Bank accounts

 SAP AG 1999



  

 

Groupings are used to combine accounts and assign summarization terms to them. Their balances can be displayed per account or as an aggregate. You can restrict the display to particular company codes and charts of accounts. Grouping terms are freely definable. This means you can tailor the cash position display to your own individual requirements. The levels selected appear in the display. The type shows whether levels (L) or groups (G) are displayed. In each grouping, you must configure at least one line of type L and one of type G. The selection determines which levels (2 digits) or groups (10 digits) are combined. You can configure maskings or partial maskings for individual values. Groups must be ten characters long and, if necessary, entered with leading zeros. The summarization term determines whether the individual value or the cumulative value is displayed. When you create new grouping entries, you have to define headings for them.

(C) SAP AG

AC805 13

4.14 Grouping: Functions Grouping

Type

Banks

Selection

L

All levels Banks Banks

G G

++++++++++ 00001131++

Groups: first identified, then grouped without identification

Level

Summarization term ´**´ =No specific identification, but summarized Usual CITIBANK

Specific identification summarized

L

L = levels (2 characters) G =Group (10 characters) SAP AG 1999

 

Summarization term

Immediate, itemized listing, not summarized

You use grouping terms to combine accounts and display them cumulatively, or as individual values. You can enter partial maskings (example: 113++0) wherever you like.

(C) SAP AG

AC805 14

4.15 Cash Position Customizing: Unit Summary

 Planning levels integrate the cash position with bank accounting.  The cash management account name enables you to differentiate bank accounts that have the same G/L account number in different charts of accounts.  Groupings select and structure the required dataset and are responsible for setting up the cash position.

 SAP AG 1999

(C) SAP AG

AC805 15

4.16Cash

Position Customizing: Exercises Unit: Cash Position Customizing

At the conclusion of these exercises, you will be able to: • Set up a new house bank. • Set up the accompanying G/L accounts and their cash management account names. • Add the new G/L accounts to your groupings. You now want to set you a house bank in your system. A house bank is a bank where you hold a customer/vendor account for which you receive external bank data. House banks are usually set up as part of the FI project. However, you may need to integrate new house banks after going live. You have entered a new bank for your company code (house bank GRxx, account key CURRENT. You use this bank to process ongoing transactions and check payments. 1-1 You decide to reserve accounts 11xx00 and 11xx01 for this bank. Create the appropriate G/L accounts, taking accounts 113100/113101 as your guide. Check and change the cash management-relevant fields in the current account (bank ID: GRxx, Account ID: CURRENT). Delete the alternative account numbers as no old system exists.

1-2 Add the new bank details to the house banks for your company code (bank ID: GRxx, Account ID: CURRENT). Take the existing entries as your guide. Note that, when creating the relevant account, you must also specify G/L account 11xx00. 1-3 Add the new bank accounts to the cash management account names for your company code.

1-4 Add the new accounts to the groups "Banks" and "Bank - actual". Take the existing entries as your guide.

1-5 The first bank statement for the new account shows a debit for an outgoing check. (C) SAP AG

AC805 16

Post this transaction (11xx01/11xx00).

1-6 Look at the new accounts in the cash position. Choose grouping "Bank - actual" first, then "Banks".

(C) SAP AG

AC805 17

4.17Cash Position Customizing: Solutions Unit: Cash Position Customizing

1-1 Solution: creating new G/L accounts.

 Accounting  Financials  General ledger  Master data  Create (11xx00 and 11xx01) Now enter the data (example: 11xx00) and choose "Create Using Template". Use accounts 113100 and 113101 as templates. Change the name (to, for example, GrxxBank). Under "Control data" take the alternative account number and check the account management and planning level entries. In the "Bank" section, change the house bank ID and account ID for the current account. You can enter your house bank ID (GRxx) and account ID (CURRENT) here, even though you have not yet defined them. Press Return and ignore the warning.

1-2 Solution: creating a new house bank (Bank ID: GRxx) and new bank details (account ID: Current).

→ Tools → AcceleratedSAP → Customizing - Project Management → SAP Reference IMG → Financial Accounting → Bank Accounting → Bank Accounts → Define House Banks - Company Code ACxx Enter your data. Choose "House Banks", then "Create Bank". Enter House Bank GRxx, country USA, then an 8-digit bank key. Press Return, then enter address data. If the FI bank directory has already been imported and you enter an existing bank number, the system enters the relevant address data automatically. (C) SAP AG

AC805 18

As your bank account, choose account ID CURRENT, enter a 6-digit account number, the currency UNI, and the G/L account 11xx00 (which you just create).

1-3 Add the new bank accounts to the cash management account names for your company code.

→ Tools → Customizing → SAP Reference IMG → Treasury → Cash Management → Structuring → Define Cash Management Account Name Now add cash management account names to your new accounts (example: xxCURR for 11xx00 and xxCheck for 11xx01). 1-4 Add the new accounts to the groups "Banks" and "Bank - actual".

→ Tools → AcceleratedSAP → Customizing - Project Management → SAP Reference IMG → Treasury → Cash Management → Structuring → Groupings → Maintain Structure Now add your new accounts to the groupings. (11xx00 to "Banks" and 11xx00 to "Bank - actual". Use the copy functions to do this. Choose a grouping term, such as xxBank. Do not forget the leading zeros for the G/L account 1-5 Post this transaction (11xx01/11xx00)

→ Accounting → Financial Accounting → General Ledger → Document entry → G/L Account Posting Now enter your data (11xx01/11xx00).

(C) SAP AG

AC805 19

1-6 Solution: cash position display.

→ Accounting → Treasury → Cash Management → Information System → Reports on Cash Management - Liquidity Analyses → Cash Position

Enter your selections.

(C) SAP AG

AC805 20

5 Manual Memo Records

Contents  Features  Definition of memo records  Archiving/Reactivation/Expiration/Deletion  Loading external memo records

 SAP AG 1999

(C) SAP AG

AC805 1

5.2 Manual Memo Records: Unit Objectives

At the conclusion of this unit, you will be able to:  Use memo records to reproduce planned payment flows in bank accounts  Process and display these paymentadvices  Import external memo records into the SAP system

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

5.5 Manual Memo Records: Business Scenario

 Now that you know how actual bank postings can be reproduced in planning, you want to know how planned incoming and outgoing payments can be displayed in the bank accounts.  How can you process memo records already entered, and how can you obtain a list showing all the memor records or a selection?

 SAP AG 1999




(C) SAP AG

AC805 5

5.6 Manual Planning

Definition 

Individual records entered manually

Possible Uses   

Payment advices for cash receipts/disbursements Planned data entry Entry of noted items, correction postings

Maintenance

     

Individual archiving categories Automatic or manual expiration Selection options for rapid searches Easy to change Maintain additional information (texts, characteristics, .. .) Checks as to planning on Saturday / Sunday

 SAP AG 1999

You can use manual memo records to include additional information (additional, that is, to the liquidity information in the system) in short-term planning.  This additional information involves incoming and outgoing payments that do not trigger actual payments in Cash Management. 

(C) SAP AG

AC805 6

5.7 Creating Memo Records

Company code: AC00 Planning type: CA

Individual entry

Fast entry

Planning type : CA Confirmed advices 08/01/YY CM acct name : CICURR ______________________________________________ Amount Assignment Characteristics

: : :

10,000

 SAP AG 1999

 

You can enter cash management memo records as individual entries or using fast entry. The entry is split into three parts: 1. Planning data (date, account - cash management account name, expiration date if required) 2. Amount data (currency, rate, rate type, and so on) 3. Additional information (assigment, characteristics, and so on)

- The planning type controls the entry level, screen, and expiration. - The expiration date shows how long the payment advice is included in planning. Only in exceptional cases, such as the concentration payment advice, should it be changeable. - You can also define the characteristics yourself. They help you identify records quickly. - The transaction type accelerates the comparison of payment advices and bank statements.  The planning type is a unique classification characteristic, entered in all manual memo records. It controls the level to which a memo record is sent.  You can choose both an exchange rate and an exchange rate type. If you make no specification, the system uses the average rate. You can use field selection control to show or hide the rate type field.  Remember to enter a minus sign for outgoing payments advices.

(C) SAP AG

AC805 7

5.8 Changing Memo Records Using Lists

M COCD ACCT NAME PT DATE AMOUNT ___________________________________________________ X

AC01

CIGIRO

AU

09/04/YY

10,000.00

Convert UC = Archive A Archive A Retention prd: 12

 SAP AG 1999

The payment advices for editing can be changed, archived, or reactivated (=transfer). The wide range of selection options simplifies the search for specific payment advices. Archived payment advices are no longer included in planning. The planning type (example: UC) determines the archive (example:A) in which a payment advice is stored.  The archiving category is freely definable in Cash Management customizing. The various categories are differentiated by retention period. One archive is usually sufficient.  The retention period shows how many months a record remains in the system before it is deleted in a reorganization run.  Note: If you change the planning type, the system creates a new memo record and archives the original.    

(C) SAP AG

AC805 8

5.9 Loading External Memo Records

Personnel department Create structure

Import memo records

Create memo records: Company code Bank account Level Planning currency Date Currency amount Planning type Expiration date

 SAP AG 1999





   

Program Load Memo Records from File (in the application, choose Cash Management -> Memo record -> Load from file) imports payment advices created outside the SAP system and creates matching advices in the SAP system. The data can be stored on the application server or the presentation server. The payment advices are supplied in the FDES_IMPORT structure. You can use the program Create Structure for External Advices (in the application, choose Cash Management -> Tools -> Create structure for external advices) to generate this structure as a template. The following file formats are supported:  XLS (Excel), CSV, TXT, ASCII To use the Excel file format, you must have Excel installed on the presentation server. To import payment advice data to the SAP system, you need specify only the file name and format. Note: In the case of the bank account, you must enter the account number, not the cash management account name. You must also enter an expiration date, becase the import cannot set this to the initial value (December 31, 9999).

(C) SAP AG

AC805 9

5.10 Payment Advice Journal

Company code Cash position :

: AC00 : X

User :

: Smith

Execute Journal of April 8, YY ____________________________ Advice 1 5,000 Advice 2 4,000 ____________________________ Total

9,000

 SAP AG 1999

In the payment advice journal, the system lists payment advices according to the selection criteria you specify. You can print the journal.  Unlike in the worklist, the active and archived records can be displayed in a single list.  The program has been converted to the ABAP List Viewer (ALV). You can configure the output list to suit your specific requirements. The following functions are available in the ALV to this end:  Show or hide columns  Modify columns  Determine sort criteria  Insert or remove interim totals  You can save the current list display variant. You can then use it again the next time you use this program. 

(C) SAP AG

AC805 10

5.11 Manual Memo Records: Unit Summary

 Payment advices anticipate bank statement postings and create planned transactions that appear in the cash position. They are also used for adjustment entries.  When a payment advice is archived, deleted, or has automatically expired, its amount is no longer taken into account in your planning.

 SAP AG 1999

(C) SAP AG

AC805 11

5.12Manual

Memo Records: Exercises Unit: Manual Memo Records

At the conclusion of these exercises, you will be able to: Enter incoming and outgoing payments notified manually, so that they are visible in the cash position. •

Edit, archive, and select payment advices.

You do not want to see only the actual bank postings in the cash position, but the plan data too. For this reason, when your bank calls you during the day to tell you that a large cash amount has been received, you can enter this transaction in the form of a payment advice, even though no general ledger posting has yet taken place.

1-1 At 10.15, your bank calls you to inform you that payments in the amount of 250,000 have been received with today as the value date. Use the appropriate planning type (CA) to process this information. Shortly afterwards, your patent department calls to tell you that your company must pay a patent fee of 500,000 by tomorrow at the latest. Plan this amount in your current account at CitiBank.

1-2 Check your entries in the cash position (grouping: "BANKS").

1-3 You now want to archive a memo record. Have the system display the entries as a list ("Process Memo Record Using List"). Archive a planning record and check what effect this has on the cash position. You now want to display this archived record (archiving category A).

1-4 Reactivate the record and check what effect this has on the cash position.

(C) SAP AG

AC805 12

1-5 You now want to process/change a memo record. For example, change the planning date to a date in the future and check your entries again in the cash position.

(C) SAP AG

AC805 13

5.13Manual Memo Records: Solutions Unit: Manual Memo Records

1-1 Solution for Creating Manual Memo Records

→ Accounting → Treasury → Cash Management → Incomings → Memo Record → Create Enter planning type "CA" (Confirmed advice) and press either Return or Individual Entry. Choose either today or tomorrow as the value date. Enter the cash management account name and an amount. – Do not forget the minus sign if appropriate. You can also create a memo record from the cash position:

→ Environment → Create memo record

1-2 Solultion for checking entries in the cash position (grouping: "BANKS").

→ Accounting → Treasury → Cash Management → Information System → Reports on Cash Management - Liquidity Analyse → Cash Position

1-3 Solution for Archiving Manual Memo Records (C) SAP AG

AC805 14

Listing the Entries:

→ Accounting → Treasury → Cash Management → Incomings → Enter Enter your company code and execute the program. Now choose the payment advice you want to archive and press "Convert". Note the message telling you that a memo record has been archived. Displaying the Archived Record:

→ Accounting → Treasury → Cash Management → Incomings → Enter

Enter your company code and "Archiving category A", then execute the program.

1-4 Solution for Reactivating Manual Memo Records


Enter your company code and "Archiving category A", then execute the program. Now choose the payment advice you want to archive and press "Convert". Note the message telling you that a memo record has been reactivated. Viewing the Effects in the Cash Position:

→ Accounting → Treasury (C) SAP AG

AC805 15

→ Cash Management → Information System → Reports on Cash Management - Liquidity Analyse → Cash Position

1-5 Solution for Editing/Changing Memo Records Changing the Date:

 → Accounting → Treasury → Cash Management → Incomings → Enter

Enter your company code and execute the program. Select the advice you want to process, then press "Display Memo Record" and "Change Memo Record". Enter the new data and save it. Displaying the Changed Record


Enter the from-to selection you require, then execute the program again.

Viewing the Effects in the Cash Position:

→ Accounting → Treasury → Cash Management (C) SAP AG

AC805 16

→ Information System → Reports on Cash Management - Liquidity Analyses → Cash Position

(C) SAP AG

AC805 17

6 Customizing Manual Memo Records

Contents  Planning types  Assigning levels  Archive / archive duration  Automatic expiration

 SAP AG 1999

(C) SAP AG

AC805 1

6.2 Customizing Manual Memo Records: Unit Objectives

At the conclusion of this unit, you will be able to:  Defining planning types and assign levels accordingly  Create archiving categories and assign them to the individual planning types  Use the field for automatic expiration

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

6.5 Customizing Manual Memo Records: Business Scenario

 Before you can work with manual payment advices, you must make certain settings in customizing.  When you create planning types, which characterize the individual paymentadvices, you are making several assignments simultaneously.

 SAP AG 1999




(C) SAP AG

AC805 5

6.6 Planning Types

Structuring

Planning Level ArchivingAutom. Autom. Number type Category Expir. Range Expir.

CA :

CA :

A

()

01

... + ... 1 Plg type text

+++ . . . Confirmed advices

 SAP AG 1999



The planning type or payment advice type is freely definable. It determines further characteristics of the memo records (level, archiving category, possibly also expiration, number range, and field selection). It is the most important classification characteristic. You can use different planning types to indicate how likely transactions are to occur.  The level enables you to make a qualitative analysis about the value of a planned item. There should be a 1:1 relationship with the planning type, so that the type of memo record is clear.  The archiving category determines how long a manually planned item remains in the archive before it is reorganized/organization.  The Automatic expiration switch indicates whether memo records of a planning type become invalid automatically ("X") after they reach the expiration date or whether they become invalid when they are archived.  You must also define the number range in advance. It controls number assignment for memo records.  The field status definition is used to control which fields are ready for input.

(C) SAP AG

AC805 6

6.7 Archive: Retention Period Structuring

Archiving Category

Retention Period

A

12 months

B

6 months

:

 SAP AG 1999

The archiving category is freely definable in Customizing. The retention period is specified in months. Individual records that have been in the archive for longer than the retention period are eliminated during the next reorganization run.  One archive is usually sufficient.  

(C) SAP AG

AC805 7

6.8 Archive / Automatic Expiration - Examples

Planning type

Archive class

Value date

A1

A

01/25/YY

X

01/26/YY

1)

01/25/YY

X

01/26/YY

2)

01/25/YY

X

A2 A3

A

A4 A

A5

Expiration date Field protect.

Reorg.

Manually Not entered entered

(01/25/YY)

3)

01/25/YY

4)

01/25/YY

5)

 SAP AG 1999



 

 

1) If the CPU date is after the expiration date, the payment advice is no longer included in the cash position. You can archive manually or can reorganize when of the following has elapsed: a )Expiration date b) Archive duration The example demonstrates a "concentration advice" in the IDES system. 2) Same as 1) Archiving is not possible. Reorganization is carried out when the expiration date has elapsed. 3) Same as 1) The expiration date is automatically set as the value date if no manual entry is made. If the CPU date is after the expiration date, the payment advice is no longer included in the cash position. 4) The payment advice is effective until 12/31/9999 (expiration date set internally). However, it can be deleted. 5) The payment advice can be archived manually or can be reorganized when the archive duration has elapsed. The example demonstrates a "confirmed advice" in the IDES system.

(C) SAP AG

AC805 8

6.9 Customizing Manual Memo Records: Unit Summary

 Planning types represent the probability of cash receipt or cash disbursement that you plan.  The values of payment advices are eliminated by archiving or deleting the paymentadvices after the actual posting has been made.

 SAP AG 1999

(C) SAP AG

AC805 9

6.10Customizing

Manual Memo Records:Exercises

Unit: Customizing Manual Memo Records


Configure new planning types

You need to create additional planning types.

1-1 Create a planning level "xx" (memo records GRxx) for the cash position, and a planning type "xx" (memo record GRxx): (xx = your group number). -

Only one archiving should be possible - meaning no automatic expiration.

-

Archiving category A

-

Text entry (segment text) is not to be possible (field status).

1-2 Around 10.15, a customer calls to inform you that he has authorized payment of 1,000,000 to your bank account 11xx00 and is expecting a credit memo with tomorrow as the value date. Enter this payment advice with your new planning type.

1-3 Display this planning work in the cash position (grouping: BANKS).

(C) SAP AG

AC805 10

6.11Customizing Manual Memo Records: Solutions Unit: Customizing Manual Memo Records

1-1 Solution for Creating Planning Level "xx"and Planning Type "xx". Define the Planning Level:

→ Tools → AcceleratedSAP → Customizing - Project Management → SAP Reference IMG → Treasury → Cash Management → Master Data → G/L Accounts → Define Planning Levels Copy or enter your new data. Choose level "xx" and enter "Memorecord GRxx" as the name. Defining the Planning Type:

→ Tools → AcceleratedSAP → Customizing - Project Management → SAP Reference IMG → Treasury → Cash Management → Structuring  Manual Planning  Define Planning Types Copy or enter your new data. Give your planning type the same name as the planning level you have just created. Do not select automatic expiration.

(C) SAP AG

AC805 11

Use the field status definition button to regulate the display status of the individual input fields (for example, set "Segment text " to "Suppress"). Remember that copying an existing planning type copies its field status too. If you choose "New Entries" in the create transactions, you must set up the whole field status from scratch too.

1-2 Solution for Entering Manual Memo Records

→ Accounting → Treasury → Cash Management → Incomings → Create Payment Advices

Now enter your data (your new planning type "xx", value date "tomorrow") You can also enter the memo record starting from the cash position.

1-3 Solution: Displaying in the Cash Position

→ Accounting → Treasury → Cash Management → Information System → Reports on Cash Management - Liquidity Analyses → Cash Position

(C) SAP AG

AC805 12

7 Check Deposit

Contents  Technical procedure  Account assignment  Data entry  Posting

 SAP AG 1999

(C) SAP AG

AC805 1

7.2 Check Deposit: Unit Objectives

At the conclusion of this unit, you will be able to:  Explain the technical procedure for depositing checks  Enter checks using the check deposit list and print the list  Create and run batch input sessions  Postprocess postings (if batch sessions are defective)

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

7.5 Check Deposit: Business Scenario

 Checks are deposited in your business and these should clear items in accounts receivable. You decide to work with the check deposit facility in the SAP Cash Management, so that the open items in accounts receivable are cleared immediately.

 SAP AG 1999




(C) SAP AG

AC805 5

7.6 Check Deposit: Procedure

Check deposit list

(Check reader)

Electronic entry

General ledger documents

Checks

Manual entry

Temporary dataset

Subledger documents

 SAP AG 1999

You can use the check deposit facility in SAP Cash Management to enter checks received. The manual check deposit is a fast entry tool that subtantially reduces the manual work involved in entering checks. You enter only the checks received, not the posting records.  The system then automatically makes the postings to the bank clearing account and customer account, along with the payment clearing. You have two options here:  Immediate posting  Create a batch input session, then run it.  Postprocessing differs, according to which of these options you choose.  When you have finished entering checks, there are additional functions you can use to process them further. For example, you can print a check deposit list and give it to the bank, along with the checks.  



The check deposit list is written, but not posted, after the checks are saved in the database. You can make changes in the list while it has this status. Once the posting process has been initiated, no further changes are possible.

(C) SAP AG

AC805 6

7.7 Account Assignment

Cash management $, UNI, ...

Check One thousand two hundred

1200

Check deposit list

Automatic

Dover, 12/29 /98

1 Subl. session

Customer OI 100

1 100

1 Subl. session

Incoming check

1 100 +1 day

2 100

Bank statement - BkAc only-

Bank

2 100

 SAP AG 1999

Procedure:  1. Enter checks. Remember to include clearing information. Create a batch input session.  2. Run the subledger session. Postings to bank clearing accounts (incoming checks) and to subledger accounting (customer clearing).  3. Print the check deposit list and give it to the bank, along with the checks.  4. Import the bank statement: bank postings (clearing the clearing accounts as necessary).

(C) SAP AG

AC805 7

7.8 Check Deposit: Initial Specifications

CITI Current

X

Internal bank determtn

Start variant

:

SAP01

Cust. Cust.matchcode ID

:

D

Further processing type :

1

Summarization level

:

1

Form

:

 SAP AG 1999

 

 



  

This screen appears the first time you enter a bank statement. Here, you stipulate the account assignment variant. This is the start variant and determines which fields are displayed when you are actually entering checks. You can change the account assignment variant at any time during processing. The start variant specifies the account assignment variant for the individual postings. You can use customizing to create entry screens (variants) of your own. If you select internal bank determination, the system identifies the bank using the internal name instead of the bank number and external account number. You can use either, according to what is usual in your company. The matchcode ID D and the contents of the customer matchcode field on the next screen make up the matchcode of the customer account the system searches for (account determination for payment settlement). The further processing type determines whether the postings in the batch input session are made online or in the background. Transaction value date: The value date from the check entry is copied into the postings. Specify a form ID if you want to use a form that differs from the standard form for the check deposit list.

(C) SAP AG

AC805 8

7.9 Check Deposit: Initial Specifications (2)

Company code :

:

AC01

Group :

:

WA1115

Transaction Posting date Value date Currency

: : : :

0001 MM/DD/YY MM/DD/YY USD

 SAP AG 1999

Enter the following data in the initial screen:  Group: This indicator is used to differentiate between check deposit lists. For example, you can combine incoming checks into groups by house bank. You can choose any group you want for each list.  Transaction: The transaction controls the posting. The rules are entered when the system is customized.  Posting date: Of the documents for posting.  Value date: The expected value date in the bank statement (can be transferred to the documents for posting). Note: A separate list should be created for each currency (or value date) due to the various methods in fixing value dates.

(C) SAP AG

AC805 9

7.10 Check Deposit List Account assignment variant 1 Amount

Check number

1000 :

12345678

Drawer AC805

Bank key

Doc. no.

66350000

123456789

Edit Val.qty Other account assignments

Doc.no. :

Account assignment variant 2 Amount

CNo

Drawer

Bank key

Doc.no.

1000 :

123

AC805

66350000

123456789

Invoice amount 2000

 SAP AG 1999

The account assignment variants (start variants) determine which fields are displayed during entry. Different account assignment fields appear in the entry screen, depending on the account assignment variant being used. Among other things, the number of account assignment fields in a variant regulates whether 1, 2, or 3 lines are available for each memo record.  You define the variants in customizing and can change them at any time during processing. If you use more account assignment fields than are available in the current variant, this is shown in an additional field.  For example, you can enter several document numbers and different invoice amounts for a memo record. This is of use if a customer uses one check to clear a number of invoices. An account assignment field for which more than one value has been enterd is highlighted in the display. 

(C) SAP AG

AC805 10

7.11 Check Deposit: Printing and Overview Print

Spool

Print preview Check deposit

Bank 12/31/YY You receive . . . . Check number Drawer . . . :

Overview Bank CITIBank : :

Bank key 63350000 :

Bank account 12345678

 SAP AG 1999



You can print the check deposit list directly from the entry screen. You can also print a totals list coving a number of check deposits.



The Print option allows you to display the form for printing.



You can use the overview to gain a perspective over all your check deposits. It contains the following data:  Date entered  Entered by  Group name  Company code and currency  Total amount  Processing status



You can see how far check deposit posting has progressed by means of the processing status. If both postings and clearing postings have been made, the status will be "Posted in full". The incomplete

(C) SAP AG

AC805 11

posting status will appear if only the bank account postings have been made. If no posting has taken place, the status will be "Created".

(C) SAP AG

AC805 12

7.12 Generating Postings Batch Input

Posting

Batch Input Sessions

Post immediately

Overview Session name

Date

Time

SUBPST BNKPST

12/23/YY 12/23/YY

14:19:22 14:19:21

...

Process

Log  SAP AG 1999

You can generate the postings immediately or using batch input sessions. The Post option generates postings immediately or the batch input sessions, including postings for subledger accounts.  You can process the sessions individually or together, online or in the background (batch).  The log displays the processing statistics and any incorrect transactions.  Incorrect transactions, which were not processed due to inadequate clearing information, must be postprocessed.  If you are using batch input sessions, you must run these again online.  If you are using immediate postings, you must postprocess the payment advices.  

(C) SAP AG

AC805 13

7.13 Check Deposit: Unit Summary

 The check deposit transaction enables you to enter incoming checks into the system quickly. Postings are automatically generated for the bank accounts and subledger accounts.  Various algorithms support clearing the customer invoice items.

 SAP AG 1999

(C) SAP AG

AC805 14

7.14Check Deposit Exercises Unit: Check Deposit

At the conclusion of these exercises, you will be able to: • Enter a check deposit list in the system and post it.

Your company has a high volume of incoming checks. For this reason, you have decided to use the manual check deposit function.

1-1 Post an outgoing invoice: Document date: 11 days ago Posting date: -10 days ago Customer: T-T05Axx Amount: 10,000 Output tax: 16% - domestic (A1) Terms: 14 days 3% . (ZB01) Use account 800200( revenues, for example not passed on to CO-PA) for the offset posting. Make a note of the document number. 1-2 The customer pays by check, deducting 3% discount (9,700) and specifying the document number. Choose screen variant SAP01 and carry out further processing in batch input (generate online). Enter this check in your current account, using the internal bank designation (bank ID1000, account ID 1000). Group : Own description Posting date: : Today (C) SAP AG

AC805 15

Value date Session name

: Tomorrow : SUBLxx

Choose transaction 0002 "Direct check deposit". Remember to specify the document number. 1-3 Generate the session for subledger accounting.

1-4 Have the system display the print view for the check deposit list on your screen.

1-5 Update the batch input session by running it.

1-6 Check the transactions in the customer account T-T05Axx or the bank accounts. Make a note of the document number in account 113108.

1-7 Check the effects of all this on the cash position (grouping "BANKS").

(C) SAP AG

AC805 16

7.15Check Deposit Solutions Unit: Check Deposit

1-1 Solution: Posting an Outgoing Invoice

→ Accounting → Financial Accounting → Accounts Receivable → Document Entry → Invoice - company code ACxx Enter your data. Change the terms of payment to ZB01. Field Name or Data Type

Values

Customer

T-T05Axx

Invoice date

11 days ago

Posting date

10 days ago

Amount

10,000 UNI

Output tax

16% - domestic

Calculate tax

Set flag

Payment terms

14 days 3% . . . (ZB01)

G/L account

800200

Amount

10,000 UNI

1-2 Solution for enter check deposit lists

→ Accounting → Treasury → Cash Management → Incomings → Manual check deposit Enter (C) SAP AG

AC805 17

(AN)

Enter your data. Now enter your data (when entering the amount, remember to take account of the discount and enter either the document number or customer description "AC805" to clear the open item). Field Name or Data Type

Values

Internal bank determination

Set flag

Start variant

SAP01

Further processing type

1- As batch input

Company code

ACxx

House bank ID

1000

Acct ID

1000

Group

Own name

Transaction

0002 - Check deposit, direct

Posting date

Today

Value date

Tomorrow

Currency

UNI

Subledger session

SUBLxx

Amount

9,700

Check number

123

Document number

Document number for the invoice

Drawer

AC805

Saving the list creates the check deposit list. You are free to change or add to the list. 1-3 Solution: Creating Sessions Menu as in Solution 1-2: . . Saving the list a second time creates the subledger session SUBLxx.

(C) SAP AG

AC805 18

Alternatively, choose: Individual list

1-4 Solution for Displaying the Check Deposit List Menu as in Solution 1-2: . .

 Check deposit  Print individual list (Output device LP01)  "Print Preview" button

1-5 Solution: Updating Sessions

 System  Services  Batch-Input  Sessions  Select session SUBLxx  Process session The 9,700 UNI are now posted to bank clearing account 113108 (incoming checks) against customer T-T05Axx, whose account is cleared at the same time.

1-6 Solution for Checking Transactions in the Customer Account T-T05Axx or the Bank Accounts. Customer Account:

→ Accounting → Financial Accounting → Accounts Receivable → Account → Display/change line items Enter your account number. Select "Cleared Items: Clearing Date Today". G/L account

→ Accounting → Financial Accounting → General Ledger

(C) SAP AG

AC805 19

→ Account → Display line items Enter your account number. Select "Cleared Items: Up to Today".

1-7 Solution for Checking Effects in the Cash Position (grouping: "BANKS").

→ See previous exercises.

(C) SAP AG

AC805 20

8 Check Deposit: Customizing

Contents  Internal transactions (posting rules)  External transactions (user mask)  Posting  Entry screens

 SAP AG 1999

(C) SAP AG

AC805 1

8.2 Check Deposit Customizing: Unit Objectives

At the conclusion of this unit, you will be able to:  Make the customizing settings necessary for entering and posting check deposit transactions  Create screen variants

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

8.5 Check Deposit Customizing: Business Scenario

 Having decided to use the check deposit function in your business, you must make the necessary system settings.

 SAP AG 1999




(C) SAP AG

AC805 5

8.6 Customizing Process - Transactions / Posting Rules

Internal Transactions (Posting Rules) P.rule Text 0003 0004 :

Check deposit via interim account Direct check deposit

Assign Business Transactions Trans. P.rule Acct modif. modif. Transaction 0001 + 0003 0002 + 0004

Posting details for direct check deposit

P.rule 0004 Posting area 2 Debit 40 Credit Doc. type

Check deposit DZ

Posting type 8

SAP AG 1999

 

  

The first step is to define posting rules (internal transactions). The posting rules represent posting transactions typical of the check deposit. Assigning a posting rule to a transaction used in the application makes it possible to update the transaction for the check deposit too. You can define the transaction name as you want. You must specify the transaction name in the "Transaction" field in the check deposit detail screen. Transaction value date: name of the rule for determining the value date from the posting date (example: posting date + 2 days) You define the rule with the bank terms. Account determination is effected using the posting rules. The system uses the internal transaction to determine the information necessary for posting (posting keys, accounts, document type). Bank statement items selected for clearing but not yet cleared can now be posted to an account. This can be an advantage if the customer for the original clearing has been identified and the payment can be posted to the customer ledger for later clearance. In addition, bank clearing accounts can be accessed within the system for the account posting.

(C) SAP AG

AC805 6

8.7 Postings and Account Determination Posting Details for Check Deposit Using Interim Account

Posting Posting rule Posting area Debit Credit Doc.type

0003 1 40 50 SA

Incoming check Check clearing Posting type

Internal trans. trans. Posting area Debit Credit Doc.type

0003 2 40

Check clearing

Goto

Comp.  1 Comp.

DZ

Posting type

8

Accounts

: Acct symbol . . . Currency INCOMING CHECK CHECK CLEARiNG :

G/L account ++++++++8 +++++++++17

 SAP AG 1999

 

 

 

This graphic shows an example where, for organizational reasons, bank and subledger postings are to be generated when a check is deposited. Depending on whether a posting transaction affects general ledger accounting only or both G/L and subledger account, you enter posting rules for one or two posting areas. The system uses the posting area to determine whether it should post the items to the general ledger (1) or subledger (2). The posting type controls the data update. It determines the posting rule (examples: G/L posting, subledger posting, with or without clearing). The G/L accounts are found using the account symbols (example: INCOMING CHECK). Partially masked entries refer to the clearing account that belongs to the G/L account. The system uses the entry in the "Currency" field to send checks in foreign currency to the required foreign currency account. Select the compression indicator to have the system post the checks as a total rather than individually. A posting key or account is still free in posting area 2 (subledger accounting). The data required here for the clearing postings is taken from the check information (drawer, document number, and so on).

(C) SAP AG

AC805 7

8.8 Simulating Postings : Posting rule Posting area : Currency Acct to be replaced

0003 1 UNI 113100

Simulate Debit : G/L acct Acct symbol :

Credit 113108 Inc.check

G/L acct Acct symbol

113117 Check clearing

 SAP AG 1999

 

By simulating the postings, you can test the effects of postings on the new bank accounts you create. Account to be replaced: Enter the (new) bank account you want to test.

(C) SAP AG

AC805 8

8.9 Creating Screen Variants

Variant Description No. of lines

VAR1 Variant 1 1

Continue

: Fields in the variant Column Offset 1 3 2 18 : :

Column fields Amount Customers Check no.

Possible fields Amount Length 13

 SAP AG 1999

You can create your own account assignment variants for the check deposit, thereby tailoring the arrangement and/or selection of account assignment fields to your specific requirements. The standard we deliver contains one variant which you cannot change.  If you do not want to work with the standard variant, you can switch it off. If you create any new variants of your own, you must activate them.  The fields required for checks entry are selected in the order you want them displayed on the screen. To do this, place the cursor on a possible field, and double click the field or select it using the menu option. 

(C) SAP AG

AC805 9

8.10 Check Deposit Customizing: Unit Summary

 The allocation of internal transactions to external transactions makes account determination easier.  The posting type switch triggers the postings.  You can set up screen templates with selection fields according to your requirements.

 SAP AG 1999

(C) SAP AG

AC805 10

8.11Check

Deposit Customizing: Exercises Unit: Check Deposit: Customizing

At the conclusion of these exercises, you will be able to: • Configure your own start variant • Create more bank clearing accounts

You want to create a variant of your own to complement the standard variant delivered by SAP. This will enable you to specify additional information when you enter a check deposit list.

1-1 Add a new variant to the start variants. Make the following entries in the new variant: 3-digit check number, 8-digit bank key, customer bank account number, customer number, and reference document number. Create only one line with data entry fields. Remember to activate the new variant.

1-2 Use the new variant to display an overview of checks already deposited.

1-3 For your new bank account 11xx00, create clearing accounts 11xx08 and 11xx09. Use accounts 113108 and 113109 as templates.

(C) SAP AG

AC805 11

8.12Check Deposit Customizing: Solutions Unit: Check Deposit: Customizing

1-1 Solution for Adding a New Variant to the Start Variants. Customizing: Financials

→ Bank Accounting → Business Transactions → Check Deposit → Define Variants for Check Deposit Choose "Create" and enter the name of your new variant. Create only one line with data entry fields. Select the fields from the list of tasks. Save and activate the new variant. If the system requires it, create a new customizing request.

1-2 Use the new variant to display an overview of checks already deposited.

→ Accounting → Treasury → Cash Management → Incomings → Manual check deposit - enter Choose "Overview" and click the bank account accounts for which you have entered the check deposit list. Select the list and choose "Transfer". Choose Settings - Specifications to access the variant selection. Choose your new variant as the start variant, and confirm. Press Return to proceed to the check deposit list and view the structure controlled by your new variant. 1-3 Solution for Adding Clearing Accounts 11xx08 and 11xx09.

(C) SAP AG

AC805 12

→ Accounting → Financial Accounting → General Ledger → Master Data → Create Use accounts 113108 and 113109 as templates.

(C) SAP AG

AC805 13

Manual Bank Statement Customizing: Solutions

(C) SAP AG

AC805 14

9 Bank Statement: Manual Entry

Contents  Technical procedure  Data entry  Selection of open customer items

 SAP AG 1999

(C) SAP AG

AC805 1

9.2 Bank Statement - Manual Entry: Unit Objectives

At the conclusion of this unit, you will be able to:  Handle the technical procedure for entering bank statements manually  Enter bank statements manually  Carry out postings (batch sessions) andpostprocess them

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

9.5 Bank Statement - Manual Entry: Business Scenario

 Your company has the statements from some or all of its banks sent by mail.You now want to familiarize yourself with the options and procedure for entering these bank statements manually.  How, and under what conditions, can you postprocess bank statements entered manually?

 SAP AG 1999




(C) SAP AG

AC805 5

9.6 Manual Bank Statement: Procedure

General ledger documents Subledger documents

Statement

Manual entry

Temporary dataset

 SAP AG 1999

The account assignment process for the bank statement is the same as that for the check deposit. The manual bank statement is a fast entry tool that subtantially reduces the manual work involved in processing bank statements. You enter only the bank statement items, not the posting records.  The system then automatically makes the postings to the bank account, bank clearing account, and customer account, along with the payment clearing. You have two options here:  Immediate posting  Create a batch input session, then run it.  Postprocessing differs, according to which of these options you choose.  The manual bank statement is written, but not posted, after the checks are saved in the database. You can make changes regarding the statement while it has this status. Once the posting process has been initiated, no further changes are possible.  

(C) SAP AG

AC805 6

9.7 Entering the Bank Statement

X

Internal bank determtn

Start variant

:

SAP01

DR matchcode ID

:

D

CR matchcode ID

:

K

Further processing type :

1

 SAP AG 1999

 

 



 

This screen appears the first time you enter a bank statement. Here, you stipulate the account assignment variant. This is the start variant and determines which fields are displayed when you are actually entering bank statements. You can change the account assignment variant at any time during processing. The start variant specifies the account assignment variant for the individual postings. You can use customizing to create entry screens (variants) of your own. If you select internal bank determination, the system identifies the bank using the internal name instead of the bank number and external account number. You can use either, according to what is usual in your company. The matchcode IDs D and K and the contents of the customer and vendor matchcode fields on the next screen make up the matchcode of the customer/vendor account the system searches for (account determination for payment settlement). The further processing type determines whether the postings in the batch input session are made online or in the background. Transaction value date: The value date from the bank statement is copied into the posting if you select this.

(C) SAP AG

AC805 7

9.8 Processing the Bank Statement (1): Bank and Payment Advices

: House bank Bank account ID :

: :

CITI Current

Control: Opening balance Closing balance : Selection of payment advices Planning type : AU Statement date : Planning date : : Further processing Bank accounting session :

 SAP AG 1999

Enter the following data in the initial screen:  House bank or bank account ID: For internal bank determination, enter the house bank ID and the account ID. For external bank determination, enter the bank nubmer and external account number.  Statement number and date  Definition of payment advices As part of statement entry, payment advices which have come into Cash Management by way of memo records, can be copied to the bank statement automatically. This clears them. Various selection critieria are available for this purpose. For example, you can select all payment advices entered in a particular planning period or as of a particular bank statement date.  In Further processing, you can enter session names, if you are working with batch input sessions. You can also restrict processing to bank postings only (this improces performance in online posting).

(C) SAP AG

AC805 8

9.9 Processing the Bank Statement (2): Bank Document / Selection Bank acct 548333 G/L account 113100 C.code AC01 Currency USD Bank statement items Trans.

Val.dt Val.dt

Amount

Doc.no.

051 :

12/23/YY

10000

1800000000

Cust. Cust. MC AC805

Alloc. Alloc. Hugo

Master

Outgoing invoice

Sort field:

Doc. no. 1800000000

AC805

Outgoing invoice

Outgoing invoice

: Amount:

Allocation: cust. Hugo

 SAP AG 1999

You use the transaction to control which type of bank posting you are processing, for example, credit memo, wire transfer or check payment.  Individual documents are selected in subledger accounting by using certain criteria (such as the document number) or by using the matchcode (account determination) and additional information (document determination) such as the amount, allocation, posting date or document date. Which selection fieldl are queried depends on the account assignment variant and the interpretation variant.  You can select memo records relating to the bank statement in the inital screen by means of various characteristics. These are then defaulted in the detail screens for entering transactions. Selected memo records that do not agree with the bank account statements can be delated as part of entry screen processing.  If you accidentally entered incorrect beginning and end balances, you can correct them in the entry screen. 

(C) SAP AG

AC805 9

9.10 Processing the Bank Statement (3): Further Processing

FEB

Bank statemt : Post Deletion indicators Display Overview :

Process : Plg types

Temporary dataset

Settings Reqmts

 SAP AG 1999



Bank statements you enter can be displayed, changed, or deleted before posting.



Post Bank Statement You can either post bank statements separately or post all the bank statements entered in the current work session together.

The "Post" option generates the batch input sessions required for the bank account postings and subledger account postings, or posts them immediately.  The check by bank statement number ensures that postings cannot be made twice.  The system generates a posting log, showing the batch session name if appropriate. 



Display Overview You can use the overview to gain a perspective over all your bank statements. The processing status shows the stage bank statement posting has reached. For the next day, choose New Statement.

(C) SAP AG

AC805 10

9.11 Manual Bank Statement Posting Examples 1. Check credit (CC): 9,700 UNI Transaction: 070

Basis: Check Deposit (CD)

Incoming Check (113108) CD 9,700 (G/L)

9,700 CC

Customer Account OI 10,000

CD 9,700 (SUBS)

US/Check Clearing (113117) CD 9,700 (SUBS)

CD 9,700 (G/L)

Bank Account (113100) CC 9,700

* Customer receives an invoice, an open item (OI) is set up in the account. * Customer sends a check (with discount). Check deposit createstwo sessions (general ledger and subsidiary ledger). * The open item in the customer account is cleared. * You can see from the bank statement that the bank has creditedthe check. The incoming check is cleared, the credit goes to the bank account (113100).  SAP AG 1999

(C) SAP AG

AC805 11

9.12 Manual Bank Statement Posting Examples 2. Outgoing check (OC): 500,000 UNI Transaction: 001

Basis: Vendor payment (VP). Example: payment program

Vendor Account VP 500,000

OI 500,000

Outgoing Check Account (113101) OC 500,000

VP 500,000

Bank Account 113100 OC 500,000 * You receive an invoice from the vendor. You set up the payable open item (OI) in the appropriate account. * You can use the SAP payment program to regulate payments to vendors. The open item in the vendor account is cleared. The payment goes to the outgoing check account. * You can see from the bank statement that the vendor has deposited the check. The relevant amount has been deducted from your bank account.  SAP AG 1999

(C) SAP AG

AC805 12

9.13 Manual Bank Statement Posting Examples 3. Incoming bank transfer (IBT): 590,300 UNI Transaction: 051

Basis: Open item in the customer account

Customer Account OI 590,300

IBT 590,300

Cash Receipt Account (113109) IBT 590,300

IBT 590,300

Bank Account 113100 IBT 590,300 * The customer receives an invoice from you. You set up the receivable open item (OI) in the appropriate account. * You can see from the bank statement that the customer has cleared the invoice by means of a bank transfer. You process the G/L account session so that the cash receipt is posted in the bank account, offsetting the cash receipt account. * Run the subsidiary ledger session to clear the open item from the customer account. The posting in the cash receipt account is cleared.You can effect the clearing by executing program SAPF123.  SAP AG 1999

(C) SAP AG

AC805 13

9.14 Bank Statement - Manual Entry: Unit Summary

 The program for manual bank statement entry generates the postings for the bank accounts and subledger accounts.  Account determination and open item selection can be carried out using various criteria.

 SAP AG 1999

(C) SAP AG

AC805 14

9.15Bank Statement - Manual Entry Exercises Unit: Bank Statement - Manual Entry

At the conclusion of these exercises, you will be able to: • Post incoming and outgoing invoices. • Enter and post a manual bank statement.

Your company has the statements from some or all of its banks sent by mail. You now want to familiarize yourself with the options and procedure for entering these bank statements manually. 

1-1 Post the following transactions: Incoming invoice in the amount of 500,000 Vendor T-T05Axx; G/L account 400020; Invoice/Posting date Seven days ago; Terms of payment ZB00; Input tax 16%.

1-2 Pay this invoice by check; Bank account : 113101; Invoice/Posting date Six days ago Make a note of the document number. This clears the vendor account.

(C) SAP AG

AC805 15

1-3 Post the following transactions: Outgoing invoice in the amount of 590,300 Customer: T-T05Axx; G/L account 800200; Invoice/Posting date Seven days ago; Terms of payment ZB00; Output tax 16%.

1-4 Your bank 113100 sends you the following bank statement: External bank details: Bank number 20050000 Account no. 123456xx Statement no.: 1 Statement date: Today Old balance: New balance:

("xx" = group no.)

Zero 100,000

Enter this statement. Do not post it yet. Take account of any payment advices (patent). Account assignment will be effected using variant 1000.

No.

Transactio n

Value Date

Note to Payee

"070"

Yesterday

Check credit from check deposit

"001"

Today

Outgoing check for document number……..

"051"

Yesterday

Bank transfer 1 Customer T-T05Axx

Use the following session names: Bank postings BAACxx Subledger postings: (C) SAP AG

AC805 16

SUBLxx

Amount

9,700

D/C

C

Outgoing check (minus sign)

D

590,300 -

C

1-5 You want to make further changes to the bank statement. Display an overview of the bank statements entered. Select a statement and change its value date from today to yesterday.

1-6 Post your bank statement by generating the sessions and running them in the foreground.

1-7 Check the cash position.

(C) SAP AG

AC805 17

9.16Bank Statement: Manual Entry Solutions Unit: Bank Statement - Manual Entry

1-1 Solution: Posting an Incoming Invoice

→ Accounting → Financial Accounting → Accounts Payable → Document Entry → Invoice - company code ACxx Enter your data. Change the terms of payment under "Payment" to ZB00.

(C) SAP AG

Field Name or Data Type

Values

Vendor

T-T05Axx

Invoice date

7 days ago

Posting date

7 days ago

Amount

500,000 UNI

Input tax

16% - domestic

Calculate tax

Set flag

Payment terms

No discount (ZB00)

G/L account

400020

Amount

500,000 UNI

AC805 18

(VN)

1-2 Solution to Paying This Invoice by Check;

→ Accounting → Financial Accounting → Accounts Payable → Document Entry → Outgoing payment → Post Enter your data.


Values

Document date

6 days ago

Posting date

6 days ago

Bank account

113102

Amount

500,000 UNI

Value date

6 days ago

Vendor

T-T05Axx

Saving the data creates the open item for this vendor.

1-3 Solution for Posting

→ Accounting → Financial Accounting → Accounts Receivable → Document Entry → Invoice Enter your data. Leave the terms of payment under "Payment" unchanged at ZB00.

(C) SAP AG

AC805 19


Values

Customer

T-T05Axx

Invoice date

7 days ago

Posting date

7 days ago

Amount

590,300 UNI

Output tax

16% - domestic

Calculate tax

Set flag

Terms of payment

No discount (ZB00)

G/L account

800200

Amount

590,300 UNI

(AN)

1-4 Solution: Entering Bank Statements

→ Accounting → Treasury → Cash Management → Manual Bank Statement → Enter Enter your data. Do not forget the minus sign for outgoing checks. For the outgoing check, you must also enter the document number; for the incoming transfer, enter the customer matchcode.

(C) SAP AG

AC805 20


Values

Internal bank determination

Do not set flag

Read cash management advices

Set flag

Start variant

1000

Further processing type

1- As batch input

Bank key

200 500 00

Bank account

123456xx

Currency

UNI

Statement number

1

Statement date

Today

Beginning balance

0

Ending balance

100,000

Posting date

Today

Planning type

CA

Bank posting session

BANKxx

Subledger session

SUBLxx

Three bank statement items : :

1-5 Solution: Changing Bank Statements (as task 1-4) Statement overview: position cursor

→ Choose "Transfer", then press Return. Enter your changes.

1-6 Solution: Posting Bank Statements (C) SAP AG

AC805 21

(as task 1-4) Statement overview: Position cursor

→ Post individual statements The system now generates the sessions.. Running the sessions:

→ System → Services → Batch input → Select the sessions → Process the sessions.

1-7 Solution: Checking the Cash Position

→ See previous exercises.

(C) SAP AG

AC805 22

10 Manual Bank Statement: Customizing

Contents  Assignment of statement transactions (user page) to internal transactions (posting rules)  Account determination using posting rules

 SAP AG 1999

(C) SAP AG

AC805 1

10.2 Manual Bank Statement Customizing: Unit Objectives

At the conclusion of this unit, you will be able to:  Make the customizing settings necessary for manually entering bank statements and the entry and update of the related transactions.  Define bank statement transactions for standard postings, and define the relevant posting and account determination rules  Configure account symbols and allocate account numbers

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

10.5 Manual Bank Statement Customizing: Business Scenario

 Having decided to use manual bank statement entry, you will now learn how to use the customizing settings required to regulate postings accordingly.

 SAP AG 1999




(C) SAP AG

AC805 5

10.6 Posting Rules and Transactions

Define Posting Rules P.rule

Text

0001 0002 :

Cash receipt via interim account Outgoing check

Assign Business Transactions Trans.

P.rule

0001 DR :

0001 0006

Acct modif. modif.

IntAlg

Text Cash receipt Check debit

 SAP AG 1999

 

  

The first step is to define posting rules (internal transactions). The posting rules represent posting transactions typical of the bank statement. Assigning a posting rule to a transaction used in the application makes it possible to update the transaction for the bank statement too. You can define the transaction name as you want. You must specify the transaction name in the "Transaction" field in the bank statement detail screen. Account determination is effected using the posting rules. The system uses the internal transaction to determine the information necessary for posting (posting keys, accounts, document type). You can use account modifications to have postings sent to accounts other than the standard account assignment. The interpretation algorithm determines which fields are evaluated for the clearing transaction or document determination.

(C) SAP AG

AC805 6

10.7 Posting Details P.rule

Text

0001 :

Cash receipt via interim account

Posting Posting rule Posting area Debit Credit Doc.type

0001 1 40 50 SA

Posting rule Posting area Debit Credit Doc.type

0001 2 40 50 DZ

BANK CASH REC.

Bank account Cash receipt acct Posting type 1

BANK CASH REC.

Bank account Cash receipt acct Posting type 8

 SAP AG 1999

     

The internal transactions are used to find the posting rules and necessary information (posting keys, accounts, and so on). The system uses the posting area to determine whether it should post the items to the general ledger (1) or subledger (2). The posting type controls the data update. The accounts are set with their account symbols. The account number is found using these symbols. Advantage: No new table entries are required for postings of the same type made to different banks. A posting key or account is still free in posting area 2 (subledger accounting). The data required here for the clearing postings is taken from the check information (drawer, document number, and so on). Bank statement items selected for clearing but not yet cleared can now be posted to an account. This can be an advantage if the customer for the original clearing has been identified and the payment can be posted to the customer ledger for later clearance. In addition, bank clearing accounts can be accessed within the system for the account posting. The same applies to clearing postings in the general ledger.

(C) SAP AG

AC805 7

10.8 Determining Accounts from House Bank Data House bank/ Bank accounts

Bank statement entry CITI Current :

House bank Acct ID :

: CITI : Current

Bank account G/L account :

: :

91005181 113100

Customizing: Account Assignment Application Chart of accts

0001 INT

Bank statement / Check deposit

Acct symbol

Acct modif.

Currency

G/L acct

BANK BANK CASH RECPT 00 01 :

+ + + + +

+ USD + + +

++++++++++ ++++++++19 ++++++++09 ++++++++++ 479000

 SAP AG 1999



Account Determination Rules 1. The account symbol determines the G/L account to which postings are made. 2. The G/L account is determined using the G/L account number assigned to an account ID (full masking). 3. Partially masked entries reference the clearing account that belongs to the G/L account. 4. The system uses the entry in the "Currency" field to send checks in foreign currency to the required foreign currency account. 5. Entries in the account modification are freely definable. They are required by the user exit for company-specific posting transactions. Example: Classification of account activities by person responsible, payments in or out, selection by delivery note.

(C) SAP AG

AC805 8

10.9 Posting Rule and Account Determination BTC

Text

Pstg rule

Pstg area

Doc. type

Posting key

Account

Modification Pstg type

051 067 068

Credit transfer

0001

1

SA

2

DZ

Check credit

0002

1

SA

CHK

Check deposit

0003

1

SA

2

DZ

1

SA

BANK CASH RECEIPT CASH RECEIPT (CUSTOMER) BANK INCOMING CHECK INCOMING CHECK CHECK CLEARING CHECK CLEARING (CUSTOMER) OUTGOING CHECK BANK BANK TRANSFER BANK MISC. BANK

++++++++++ 1 ++++++++09 ++++++++09 8

070

40 50 40 (15) 40

001

Outgoing check

0005

40 50 40 (15) 50

020

Debit transfer

0006

1

SA

GEB

Fees

0009

1

SA

Posting types: 1 = Post G/L account 2 = Debit posting to subledger account 3 = Credit posting to subledger account 4 = Debit clearing to G/L account 5 = Credit clearing to G/L account 7 = Debit clearing to subledger account 8 = Credit clearing to subledger account 9 = Reverse and cancel clearing document

50 40 50

Posting areas: 1 = General ledger 2 = Subledger

 SAP AG 1999



This graphic shows examples of some entries in the customizing table.

(C) SAP AG

AC805 9

++++++++++ 5 ++++++++08 ++++++++08 1 ++++++++09 ++++++++09 8 ++++++++01 4 ++++++++++ ++++++++02 4 ++++++++++ ++++++++05 1 ++++++++++

10.10 Manual Bank Statement Customizing: Unit Summary

 The posting transactions from the bank statement are allocated to internal transactions (posting rules). These control the how posting information is located. They also regulate account determination.

 SAP AG 1999

(C) SAP AG

AC805 10

10.11Manual

Bank Statement - Customizing: Exercises

Unit: Manual Bank Statement: Customizing

At the conclusion of these exercises, you will be able to: • Make all customizing settings up to account determination

You will enter all the customizing settings for a bank statement example.

1-1 Define a key for posting rule xx05 (xx = your group number) in respect of "Check debit GRxx".

1-2 Allocate the above data to an external transaction xx05 "Vendor check deposit gr.xx.

1-3 Define account determination for the new posting rule xx05.  First, create account symbols: xx-BANK

Bank account group xx

xx-OUTCHECK.

Outgoing check xx

SAVE your entries.

(C) SAP AG

AC805 11

Then assign accounts in the INT chart of accounts to the account symbols. Use the facilities for partial and full masking. You can simply overwrite existing masks, thereby creating new ones. xx-BANK xx- OUTCHECK

+ +

+ +

++++++++++ +++++++++1

SAVE your entries.

Now you can define posting specifications for your posting rule xx05 (only necessary for posting area 1 - bank accounting). You do not need to specify a posting key in the debit posting (OUTCHECK). In the credit posting (xx-BANK), specify posting key 50. This is a G/L account document which should clear the balance in the G/L account. 1-4 Now post an incoming invoice in the amount of 22,000: Vendor T-T05Axx; G/L account 400020; Invoice/document date Seven days ago; Terms of payment ZB00; Input tax 16%. 1-5 Pay this invoice by check. Bank account : 11xx01; Posting/Doc./Val .Date Date: Six days ago Make a note of the document number. The vendor cashes the check.

(C) SAP AG

AC805 12

1-6 Enter a manual bank statement for your account GRxx CURRENT. If you have already entered a bank statement for your bank, use the overview button and the tool for having a "New statement" proposed. The bank details, new statement number, statement date, and beginning balance are defaulted automatically. However, you should not have entered any bank statements yet, making this statement number one. Change the start variant to "internal bank determination". Enter the remaining data, such as the new finishing balance, the posting date (today), and, if required, the session name. Enter the transaction you just created as the transaction here. 1-7 Post your bank statement and process the batch session.

1-8 Have the system display vendor item T-T05Axx and G/L item 11xx01. Have the items been cleared?

(C) SAP AG

AC805 13

11 Bank Statement: Electronic Entry

Contents  Technical procedure for electronic bank statement entry  Interpreting the note-to-payee fields  Data entry  Options for postprocessing

 SAP AG 1999

(C) SAP AG

AC805 1

11.2 Bank Statement - Electronic Entry: Unit Objectives

At the conclusion of this unit, you will be able to:  Import bank statement data electronically  Explain the various posting options and the related postprocessing  Handle the transactions for clearing open items

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

11.5 Bank Statement - Electronic Entry: Business Scenario

 You use banking software every morning to access bank statements electronically from one or more of your house banks.  Now you want to familiarize yourself with the options and procedure for importing these statements into SAP Cash Management electronically.  How does the system identify the open items?  How can you postprocess the bank statements?

 SAP AG 1999




(C) SAP AG

AC805 5

11.6 Electronic Bank Statement: Features (1)



Data (such as MultiCash or SWIFT MT940) is imported into a temporary dataset in the SAP System.



Batch input sessions are generated (per bank statement: one session for G/L accounting and one forsubledger forsubledger accounting).



Postings can be made immediately (call transaction).



Bank accounting and subledger accounting can be executed separately or jointly.



Posting rules and account determination can be defined as you want in customizing.



Note to payee fields can be interpreted by document number or reference document number for the clearing transaction (example: standard algorithm).

 SAP AG 1999

Electronic bank statement processing in SAP Cash Management is based on the MultiCash format. Other formats, such as SWIFT MT940, are supported, but you are best advised to use MultiCash.  The system uses the bank data to create two files (STATE.TXT and ITEM.TXT) which are then imported into the SAP system, where more data is added. The system looks for the business transaction codes (BTC) and other information relevant to the posting.  As with other Cash Management objects, you can work with batch input sessions or make postings immediately. The postprocessing activities differ accordingly. 

(C) SAP AG

AC805 6

11.7 Electronic Bank Statement: Features (2)

  

 

Number ranges valid for interpretation can be restricted. Bundling allows you to apportion postings (for example, according to who handles which customer). User Exit for customercustomer-specific interpretation of notenote-toto-payee fields - Generate clearing information - Influence account determination - Distribution of transactions to several sessions per bank statement and posting area Postprocessing for posting proposals which cannot be cleared is possible either directly or in batchbatch-input sessions. Lists: - Bank statements - Posting proposals - Print lineline-items where postings are not possible - Processing statistics

 SAP AG 1999





 



If you want to use alternative currency keys (such as in CSB43 format in Spain), assign a currency class (as well as the transaction type) to the house bank account in customizing for the electronic bank statement. Currency classes are used to form pairs from the alternative currency keys supplied in the bank statement and those used in the system (for example, following the ISO standard). Missing key pairs cause the system to stop processing. Example: SAP currency key: alternative currency key (DEM: 215, FRF : 000) The note-to-payee fields in the electronic bank statement contain various information relevant to open item clearing. If the algorithms we deliver are not sufficient, it is possible to program a user exit tailored to your business. Please note: All changes made in user exits are made at your own risk. As an electronic bank statement is being imported, the system identifies the transactions in it and determines how they are posted. The most important information for this is usually found using the document number or invoice number, which appears in the "note to payee" in the bank statement. You can print lists from the SAP system.

(C) SAP AG

AC805 7

11.8 Electronic Bank Statement - Various Formats Supported SWIFT MT940

EU

MultiCash

EU

Lockbox

USA

BACS

UK

ETEBAC

Bank postings

F

CODA

BE

FIDES

CH

CSB43

E

ZENGINKYO

Cash Position & Liquidity Forecast

JP CZ S

Bank data

Applicationspecific processing

03/15 Banks Subledgers

100 25

Manual Bank Statement Subledgers

Check deposit

 SAP AG 1999

Formats:  The SAP system can read some formats directly.  The SAP system also has some conversion programs, which you can use to convert various formats into MultiCash.  You can also use MultiCash softward from your bank to convert certain formats (such as SWIFT MT940) into MultiCash.  Further processing is as for the check deposit and the manual bank statement.  User exit:  We offer the following enhancement for the electronic bank statement: 

FEB00001, used to analyze each transaction in your bank accounts per clearing information (such as the document number); change the posting rule; influence account determination by means of account modification; distribute postings to different batch input sessions.

(C) SAP AG

AC805 8

11.9 Generating Test Data - RFEBKATX Generate test data X Format Statement file Transaction file

Download to PC M A:STATE.TXT A:STATE.TXT A:ITEM.TXT A:ITEM.TXT

Company code House bank (short key) Account (short key) Statement data Statement date

Invoice date

 Do not display posting screen Creating open items - Customers Creating open items - Clearing accounts

 SAP AG 1999

Program RFEBKATX is designed to help you with the customizing settings needed when you implement the electronic bank statement. It will also give you a feel for the options available in the electronic bank statement.  The electronic bank statement is used, among other things, to automatically assigng incoming and outgoing payments to house bank accounts when they relate to items already posted in the system to customer/vendor/clearing accounts and, where appropriate, the clearing of them.  Experience has shown that two main obstacles arise during implementation, particularly in customizing:  It is very difficult to generate the bank statement fields STATE.TXT and ITEM.TXT. Many implementation errors result from these files being generated incorrectly. It is also difficult to use the actual files from the bank because they are very large.  The open items to be found and cleared using the bank statement must normally be posted manually with the correct clearing information.  You can use this program to create both open items in a company code and the relevant bank statement files for a house bank account in this company code. You can do this directly with the RFEBKA00 import program, thereby testing your settings in customizing and the general function for RFEBKA00. 

(C) SAP AG

AC805 9

11.10 Importing Bank Statement Data Import X Import data Elect. bank statement format Statement file Transaction file X

M A:ZUG.TXT A:ZUG.TXT A:ATZ.TXT A:ATZ.TXT

PC upload

 Post immediately Generate batch input ...

Bank ledger only 1 Session name

CM advices Selection field ... Bundling

02 Planning type

Summariztn

BELNR 18000000 19999999 XBELNR 00000001 39999999 39999999 1

 Print bank statement  Print posting log  SAP AG 1999

The transfer program (for example: MultiCash) uses the bank data to generate two files for further processing, STATE.TXT and ITEM.TXT.  For the input, enter the format, along with the two file names, and stipulate the type of further processing. The system then automatically makes the posting to the bank account, bank clearing account, customer account, and, if required, vendor account, along with the payment clearing. You have two options here:  Immediate posting  Create a batch input session, then run it.  Make your selection for the search by document or reference number. Activate the interpretation algorithm at the same time.  Work with variants. 

(C) SAP AG

AC805 10

11.11 MultiCash Files State.txt 20050000 ;12345600 ;0002;08/30/YY;UNI;52000.00- ;93000.00 ;41000.00; 104000.00- ;SAP Testreport RFEBKATX ; ; ; ; ; ; ; ;5

Item.txt 20050000 ;12345600 ;0002;08/30/YY; ;Invoice number 1800000011 ; ; ; ; ; 1000.00 ; ;0;30.08.JJ; ; ;Invoice date 08/16/YY ; ; ; ; ; ; ; ; ; ; ; ; ; Customer Training AC805 Gr ; Boston ;67292200 ;1234567 ;051; ; ; ; 20050000 ;12345600 ;0002;08/30/YY; ; ;DME deposit ; ; ; ;30000.00 ; ; 0;08/30/YY; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;071; ; ; ; 20050000 ;12345600 ;0002;30.08.JJ; ;Check 0100000010 ; Check debit ; ; ; ;31000,00 ; ;0;08/30/YY; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; 001; ; ; ; 20050000 ;12345600 ;0002;30.08.JJ; ;Check 0100000011 ; Check debit ; ; ; ;32,000 ; ;0;08/30/YY; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; 001; ; ; ; 20050000 ;12345600 ;0002;08/30/YY; ; ;Check deposit ; ; ; ;40,000 ; ; 0;08/30/YY; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;070; ; ; ;

 SAP AG 1999

The MultiCash format is generated using BCS (Banking Communication Standard) software, taking the data from bank statements (usually SWIFT MT940).  This measn that the format is the same for all financial institutions, making checks (using a spreadsheet or word processing program) easy. Two files area created, STATE.TXT and ITEM.TXT. STATE.TXT contains bank statement header information and ITEM.TXT contains the transaction information. Using this format, a number of bank statements can be imported simultaneously, even if they are from different financial institutions.  The BCS software is usually MultiCash software. Many institutions, however, have their own name for the software. 

(C) SAP AG

AC805 11

11.12 Electronic Bank Statement: Printout

Alford Inc. Anytown --------------------------------------------------------------------------------------------------------------------------------------------------------------------------CitiBank Account holder: Joe Smith, Anytown BNo: 66010075 Account number: 179097-756 Statement No.: 00051 Currency: USD Statement date: 09/24/YYYY --------------------------------------------------------------------------------------------------------------------------------------------------------------------------CNo

ValDt

PstgDt

Note to payee

Posting text

BTC

Primanota

Amount

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

00001 09/24 00002 09/24 00003 09/24

09/24 09/24 09/24

00004 09/24 00005 09/24

09/24 09/24

00006 09/24

09/24

Document 1500000285 Your invoice 1710000865 Doc.date 0304YY Check 1500000282 Inv. dated 06/03/YY Inv. no. 17100008111 Cash discount 3 % Inv. dated 06/12/YY

Beginning balance --------------------------------------------SCHECKEINREICHUNG 070 30.000,00 004 3,300.00 CREDIT MEMO 0XX 207,000.00

 SAP AG 1999



You can print and file the bank statement retrospectively.

(C) SAP AG

AC805 12

001 051 051

-

600.00 10,700.00

1,000,000,000.00 ------------------------------------------Total Debit 0,00 Total Credit 0,00 ------------------------------------------Ending balance 1,000,277,700.00

11.13 Electronic Bank Statement: Postprocessing

Company code AC00 House bank 1000 Acct ID CURR ... Statement status 1 Bundle number ... Posting area Posting method

All transactions

2 Subledger accounting A Display all screens

 SAP AG 1999

If you have chosen immediate posting, you must postprocess using the transaction provided. You can see how far transaction posting has progressed by means of the processing status. If both postings and clearing postings have been made, the status will be "Posted in full". The incomplete posting status will appear if only the bank account postings have been made. If no posting has taken place, the status will be "Created".  If open items cannot be cleared using the electronic bank statement, you need to create payment advices. Where postprocessing has not been handled properly, on-account postings are generated. Put another way, the electronic bank statement generates its own payment advices for failed clearing postings (posting type 4-8) in posting area 2.  If the interpretation algorithms identified open items to be cleared, the system determines the business partner from the relevant document, if this has not already been determined using the bank details. If no business partner can be identified, a star ("*") is entered. In this event, the first step in postprocessing is the assignment of the payment advice to the appropriate business partner (use the Process Payment Advice pushbutton). The payment advice cannot be processed further unless a partner is assigned at header level. The first step in postprocessing is to press the Post button. The payment advices must have been processed already, to prevent on-account postings.  On-account postings can only be suppressed if the payment advices is taken out of the posting. To this end, you must set the "Display all screens" mode and delete the payment advice in the account selection. 

(C) SAP AG

AC805 13

11.14 Processing Incomings: Postings on Account  The posting to the G/L account can be made even if no open item can be cleared.  Advantage: The cash position also shows payments that cannot be assigned to an open item.  Example: The electronic bank statement shows a bank transfer from a customer. However, no clearing takes place because the amounts are different.  Up to Release 4.5: No clearing, so no posting From  Release 4.6: Posting "Bank to outgoing check" made: the accounts then appear correctly in the cash position.  “Bank statement postprocessing" as before  Up to Release 4.5: Posting and clearing  From Release 4.6: Clearing only

 SAP AG 1999



Bank statement items selected for clearing but not yet cleared can now be posted to an account. This can be an advantage if the customer for the original clearing has been identified and the payment can be posted to the customer ledger for later clearance. In addition, bank clearing accounts can be accessed within the system for the account posting.

(C) SAP AG

AC805 14

11.15 Important Criteria

Generate / process the session with bank account postings first (performance).

Transactions cannot be posted twice (status management).

Once a transaction is in a session, it is considered to be posted.

 SAP AG 1999

(C) SAP AG

AC805 15

11.16 Bank Statement - Electronic Entry: Unit Summary

 The electronic bank statement generates the postings for bank accounts and subledger accounts using batch input or directly.  Customers are identified by interpreting the note to payee or the details of the sending bank.

 SAP AG 1999

(C) SAP AG

AC805 16

11.17Electronic

Bank Statement: Exercises

Unit: Electronic Bank Statement Topic: Import Data, Postprocess Bank Statement


Import bank statement data electronically

•

Explain the various posting options and the related postprocessing

•

Handle the transactions for clearing open items

You use banking software every morning to access bank statements electronically from one or more of your house banks. Now you want to familiarize yourself with the options and procedure for importing these statements into SAP Cash Management electronically.

1-1 Use program RFEBKATX to generate the test data and the files STATExx.TXT and ITEMxx.TXT. You can reach this program in transaction SE38 or by choosing System -> Services -> Reporting. Do not run a download to your PC, but send the files to the application server. Call the files STATExx.TXT and ITEMxx.TXT. Use the accounts with house bank ID 1000 and account ID 1000 as your bank clearing accounts. Choose today as the statement date. Enter the date from 10 days ago as the invoice date. You can display the posting screens if you want. Create one or more open items in your customer account T-T05Axx and create open items in your clearing accounts too. Run the program.

(C) SAP AG

AC805 17

1-2 Check the log for program RFEBKATX. Have the subledger posting(s) and G/L account posting(s) been made? Have the bank statement fields been generated? Does statement information exist? 1-3 Import the files. Choose immediate posting and confine your document numbers to the range 1800000000 to 1809999999. Now print the bank statement, posting log, and statistics. Run the program. 1-4 Check the posting log, the processing statistics, and the bank statement. 1-5 Now you have to check whether all the postings have been made or whether any postprocessing is required. Do this in G/L accounting first. All the postings should have been made successfully. 1-6 Now go to subledger account and postprocess the posting as required. Choose your bank statement. If a red X appears, postprocessing is required. Select the item that requires postprocessing. You now see all the information you need for postprocessing. You can see from the payment advice that the system has used the document number to identify the open item. Clearing must, therefore, have failed because of an amount variance. Now post the document. You notice that the customer has paid without deducting discount, although he would have been entitled to it. Deduct the amount of the discount and continue posting. From the green checkmark and the document number, you can now see that the posting and, with it, open item clearing were successful.

(C) SAP AG

AC805 18

11.18Solutions Unit: Electronic Bank Statement: Topic: Import Data, Postprocess Bank Statement

1-1 Solution: Generating Test Data and the Files STATExx.TXT and ITEMxx.TXT.

 System  Services  Reporting  Program "RFEBKATX"


Values

Format

M - MultiCash

Statement file

StateXX.txt

Line item file

ITEMxx.TXT

Company code

ACxx

House bank (short key)

1000

Account (short key)

1000

Statement date

Today

Invoice date

-10 days

Posting mode

Set flag

Postings go to customer…

T-T05Axx

First amount

Example: 1000

... Create open items in clearing accounts

Set flag

... Run the program. The system generates postings and bank statement files.

(C) SAP AG

AC805 19

1-2 Solution: check on log Once the program has run, the system displays an evaluation of what the program has generated. 1-3 Soluation to import of bank statement files.

 Accounting  Treasury  Cash Management  Incomings  Electronic bank statement  Import Field Name or Data Type

Values

Import data

Set flag

Format

M - MultiCash

Statement file

StateXX.txt

Line item file

ITEMxx.TXT

Workstation upload

Do not set flag

Post immediately

Set flag

BELNR number range

1800000000 - 1809999999

Print bank statement

Set flag

Print posting log

Set flag

Print statistics

Set flag

Run the program. The files are imported and immediately updated.

1-4 Solution: Check on Posting Log, Processing Statistics, and Bank Statement Once the program has run, the system displays an evaluation of what the program has generated. (C) SAP AG

AC805 20

1-5 Solution: G/L Account Postprocessing

 Accounting  Treasury  Cash Management  Incomings  Electronic bank statement  Postprocess Field Name or Data Type

Values

Application

Electronic and manual bank statement

Statement status

All line items

Posting area

G/L accounting

Posting mode

Display incorrect screens

Press the Overview button This brings up the "Bank Statement Overview" screen which displays the bank statements per company code and per bank. Double click your bank to view the amounts and bank statement status. If a green checkmark is displayed, all postings were successful. If there is no checkmark, postprocessing is required. However, in this exercise, a green checkmark should be displayed for your data. Double click your statement to see the individual postings, the amounts involved, and the document numbers.

1-6 Solution: Subledger Account Postprocessing

 Accounting  Treasury  Cash Management  Incomings  Electronic bank statement  Postprocess

(C) SAP AG

AC805 21


Values

Application

Electronic and manual bank statement

Statement status

All line items

Posting area

Subledger accounting

Posting mode

Display incorrect screens

Press the Overview button This brings up the "Bank Statement Overview" screen which displays the bank statements per company code and per bank. Double click your bank to view the amounts and bank statement status. If a green checkmark is displayed, all postings were successful. If there is no checkmark, postprocessing is required. In your case, a red X should be displayed for your data. Double click your statement to see the posting, the amount involved, and the information that this item has still to be posted. Select the item that requires postprocessing. You now see all the information you need for postprocessing. You can see from the payment advice that the system has used the document number to identify the open item. Clearing must, therefore, have failed because of an amount variance. Now post the document. You notice that the customer has paid without deducting discount, although he would have been entitled to it. Deduct the amount of the discount and continue posting. From the green checkmark and the document number, you can now see that the posting and, with it, open item clearing were successful.

(C) SAP AG

AC805 22

12 Electronic Bank Statement: Customizing

Contents  External transactions (BTC) and internal transactions (posting rules), along with posting processes  Interpretation of the note to payee

 SAP AG 1999

(C) SAP AG

AC805 1

12.2 Electronic Bank Statement - Customizing: Unit Objectives

At the conclusion of this unit, you will be able to:  See the connection between external transactions (business transaction codes - BTC) and internal transactions (posting and account determination rules), and explain the related posting processes  Explain how the note to payee is interpreted, and what the options are for clearing open items

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

12.5 Electronic Bank Statement - Customizing: Business Scenario

 What system settings must be entered so that you can use the electronic bank statement in SAP R/3 Cash Management?  How can you combine a number of banks who all use the same business transaction codes (BTC)?  How do you assign the various options for interpreting the note to payee to the individual transactions?

 SAP AG 1999




(C) SAP AG

AC805 5

12.6 Transactions Allocate

Banks

Bank key

Bank acct

100 200 30 100 200 30 300 500 00 622 512 50 ...

548333 888333 6097612 +

Assign business transactions Ext.trans.

+/-

Int.trans

001 051 Unallocated Unallocated ...

+ + -

0005 0001 0011 0010



Internal Transactions

Trans.type

Pst rule

Text

0001 0002 ...

Credit memo Debit memo

MT940 MT940 MT940 MT940

 Int alg. 1

Posting



Posting rule :

0001



Posting rule Acct asst

 SAP AG 1999

   

 

You use customizing to ensure that all business transactions communicated to you by your bank using the electronic bank statement are posted correctly. You allocate transaction types to combine banks that have identical external transaction codes. You define posting rules. The posting rules represent posting transactions typical of the bank statement. You then assign the business transactions (BTC) to these posting rules, dependent on transaction types. It is this assignement that makes it possible to record data. However, if the bank supplies an unknown external transaction code, the import program stops and an error message is displayed. Now you can use the term "UNALLOCATED" as an external transaction. There is then no need to run the import again. The posting should be made to a separate interim account, which the accountant must postprocess. In addition, you should enter the new external transaction code in customizing, in case it comes up again. Account determination is effected using the posting rules. The system uses the internal transaction to determine the information necessary for posting (posting keys, accounts, document type). You can use account modifications to have postings sent to accounts other than the standard account assignment.

(C) SAP AG

AC805 6

12.7 Account Determination

Statement

Customizing Assign business transactions

:

TrnsTyp

ExtTrans

MT940

051

0001

MT940

Bank trsfr

0001

BTC ...

:

051

Posting text

:

Bank transfer

  

...

Pstg rule

:

:

 SAP AG 1999

     

The internal transactions are used to find the posting rules and necessary information (posting keys, accounts, and so on). The system uses the posting area to determine whether it should post the items to the general ledger (1) or subledger (2). The posting type controls the data update. The posting type determines the posting rules (example: G/L posting, subledger posting). The accounts are set with their account symbols. The account number is found using these symbols. Advantage: No new table entries are required for postings of the same type made to different banks. A posting key or the account remains free for clearing postings. The data required here for the clearing postings is taken from the check information (drawer, document number, and so on). Bank statement items selected for clearing but not yet cleared can now be posted to an account. This can be an advantage if the customer for the original clearing has been identified and the payment can be posted to the customer ledger for later clearance. In addition, bank clearing accounts can be accessed within the system for the account posting.

(C) SAP AG

AC805 7

12.8 Interpretation Algorithm

 The interpretation algorithm determines how the system interprets the information in the note-to-payee lines of the bank statement, so that it can clear open items automatically.  Algorithms can identify and process various information (such as the document number) for each payment.  Example: 

Algorithm 001 interprets the values in the note-to-payee line as document numbers or reference document numbers.

 SAP AG 1999

During the electronic bank statement import, the system identifies the transactions uses the settings you have entered in earlier steps to determine how each transaction must be posted. The system finds the most important information for the clearing process (for example, customer open items are cleared when cash is received) by means of the document number or reference document number in the note-to-payee line in the bank statement.  Sometimes, the information in the note-to-payee field is incomplete - for example, the first characters of the document number may be missing. The interpretation algorithm cannot do anything in such cases. It cannot find the relevant document numbers in the system and the amount cannot be posted. You must then postprocess the transactions manually.  You can increase the success rate of the document number search by defining models for document numbers. The system searches using these "search strings" before the interpretation algorithm comes into play. 

(C) SAP AG

AC805 8

12.9 Electronic Bank Statement - Customizing: Unit Summary

 The business transaction code determines the posting procedure and account determination in bank accounting.  Interpretation of the note to payee determines the following in subledger accounting: a) Account determination b) Document determination  Account determination (subledger) can also be made by interpreting the details of the sending bank.

 SAP AG 1999

(C) SAP AG

AC805 9

13 Extended Bank Processing: Checking Programs

Contents  Reconcile statement postings with manual memo records  Compare statement value dates with planned value dates  Determine the distribution time float with vendors

 SAP AG 1999

(C) SAP AG

AC805 1

13.2 Extended Bank Processing: Checking Programs Unit Objectives

At the conclusion of this unit, you will be able to:  Handle the various monitoring tools in SAP R/3 Cash Management so that the data is managed correctly in the system  Explain how the cashing time of checks to vendors is determined, and how you transfer them to the vendor master record

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

13.5 Extended Bank Processing: Checking Programs Business Scenario

 To ensure that payment flows are not duplicated in the system, you want to compare the statement postings daily with the payment advices.  In addition, you want to monitor the value dates set by the bank.  By determining the maturity period of vendor checks, you can maintain the payment program and the vendor master record, so that you can then use them for planning in respect of upcoming transactions.

 SAP AG 1999




(C) SAP AG

AC805 5

13.6 Comparing Payment Advices with the Bank Statement or Account

Postings

Advices

Comparison

 SAP AG 1999



Individual records which are no longer valid can be archived with the help of the comparison report. The payment advice comparison selects advices from the selected planning period and compares them with the bank postings. If you work with the electronic bank statement and manual individual records, you must run the payment advice comparison. • Compare with Account This section shows the manual and automatic comparison or individual records with account postings. • Compare with Bank Statement This section shows the manual and automatic comparison or individual records with bank data store information, and the selection of archived records.

Individual records cleared by bank postings can be archived, manually or automatically. Archived advices are no longer active - that is, they no longer appear in the cash position. This prevents the same item appearing twice in your planning.  In the manual comparison, postings and advices are listed in ascending order, by amount. Individual records now selected can now be archived by means of function keys. 

(C) SAP AG

AC805 6

13.7 Comparing Value Dates

Bank 2) 01/17

Check Clearing 1) 01/16

2) 01/17

Diff. 1 day

1) Check deposit, value date 01/16 2) Bank statement, value date 01/17

 SAP AG 1999



You use the value date comparison to compare the planned/agreed value date (for example, from the check deposit or preliminary posting) with the value date posted by the bank in the bank statement. The program searches for the balance sheet account postings relating to all the cleared items in a bank clearing account. If there are differences, the program lists both postings. If there is more than one clearing item for a posting, the program takes the first one it finds.



If you want to see all the variances relating to a bank account, you should create a variant containing all the relevant bank clearing accounts in the G/L account selection.

(C) SAP AG

AC805 7

13.8 Cashed Checks Analysis: G/L Account / Vendor FI Accounting Payment run (SAPF110) Update (manual)

SAPF110 Days till value date

Vendor Check cashing time Update (batch)

Outgoing Outgoing checks checks

Statement Pstg dt.

Pstg Pstg dt. dt.

Clrg Clrg dt. dt.

 

Clrg dte OI

RFSRUE RFSRUE 00 00

RFSRUE 10 Determines: Check cashing time per vendor

Analysis Analysis per: per: -- Bank Bank -- Domestic/foreign Domestic/foreign check check -- Amount Amount

 SAP AG 1999



You can determine the average cashing time for your checks for each outgoing check account and, using this account, for each vendor. A program is available to this end:



The program determines the following data:  Average cashing time for checks deposited  Average cashing time for checks still open  Number and total amount for all checks currently outstanding



The average cashing time is always calculated weighted by amount. If you select more than one outgoing check acount, the average cashing time across all banks is also determined. To compare the cashing time for differentamounts, you can have the system sort the checks by amount. If you want to derive the cash flow date relevant for the cash position on the basis of the checking times calculated, you must set the days until the value date in the payment program. This number is added to the posting date. The outgoing funds appear in the cash position as of the value date resulting from this calculation.



The progarm also uses the outgoing check accounts to calculate the average different between the check deposit date and posting date, for each vendor. You also have the option of creating a batch input session with the values calculated for each vendor. If these values differ from the master data entry, the check cashing time field in the master record is updated accordingly.

(C) SAP AG

AC805 8

13.9 Extended Bank Processing: Checking Programs Unit Summary

 The payment advice comparison program archives payment advices that have been replaced by postings.  Planned value dates are analyzed using clearing accounts.  The specified check cashing times (vendor checks) are used to determine the value dates in vendor payment runs.

 SAP AG 1999

(C) SAP AG

AC805 9

13.10Extended

Bank Processing - Checking Programs:

Exercises Unit: Extended Bank Processing: Checking Programs

At the conclusion of these exercises, you will be able to: • Compare payment advices • Verify check cashing times

To ensure that payment flows are not duplicated in the system, carry out a payment advice comparison regularly after the bank statement has been posted. You can use the check cashing time monitor to adapt the vendor master. This information can be used in later transactions to improve the accuracy of cash management. 1-1 After the bank statement has been posted, the relevant payment advices must be archived. Create more than one payment advice if required. Start the payment advice comparison in your company code for your bank accounts and pay attention to the constraints on planning or posting dates. Manually archive any payment advices no longer required.

1-2 Check the period outstanding for checks on your bank account and then for your vendor TT05Axx. Update the appropriate field in the vendor master data for accounting payment transactions. You can then calculate the value dates on check payments in automatic payment, by processing the batch input session generated.

(C) SAP AG

AC805 10

13.11Extended Bank Processing: Solutions Unit: Extended Bank Processing: Checking Programs

1-1 Solution: Comparing Payment Advices

→ Accounting → Treasury → Cash Management → Check → Compare Payment Advices → With Account Enter your data and execute the program. Field Name or Data Type

Values

Chart of accounts:

INT

G/L accounts

113100 - 119999

Company code

ACxx

"Open items" as of key date

Today

Posting date

From two days ago to today

Advice planning date

From two days ago to today

1-2 Solution: Check Cashing Times

→ Accounting → Treasury → Cash Management → Check → Returned vendor checks → G/L Account Enter your data and execute the program.

(C) SAP AG

AC805 11


Values

Chart of accounts:

INT

G/L account

113101

Company code

ACxx

"Open items" as of key date

Today

Vendor

T-T05Axx

Master data maintenance

Set flag

If you select master data maintenance, the system generates a batch input session. If the flag is not set, the checking time analysis should be regarded as a test run.

→ System → Services → Batch Input Sessions → Select session and run it in the foreground. The field in the vendor master data is filled again.

(C) SAP AG

AC805 12

14 Cash Concentration

Contents  Concentration proposals  Concentration correspondence  Posting procedures  Payment program F111

 SAP AG 1999

(C) SAP AG

AC805 1

14.2 Cash Concentration: Unit Objectives

At the conclusion of this unit, you will be able to:  Create and process concentration proposals  Print and send concentration correspondence  Handle the posting procedures used in cash concentration  Use payment program F111

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

14.5 Cash Concentration: Business Scenario

 At the end of each morning, you want to combine your various bank account balances in one target account, thereby obtaining a clear overview of your company's liquidity.  Having informed the banks by telephone, you use the system to print your correspondence forms (revised as necessary) so that you can send them to the banks too.  You then need to make an advance concentration proposal posting, so that you can use the bank statement the next day to make the postings to the current accounts.

 SAP AG 1999




(C) SAP AG

AC805 5

14.6 Cash Concentration: Overview

Features  Default per specified criteria  Interactive manual changes  Generate transfers  Generate correspondence  CrossCross-company code possible Status Bank 1 Bank 2 Bank 3 Bank 4

Before 1200 100 400 -350 1350

After 5 5 1337 3 1350

 SAP AG 1999



Cash concentration involves moving the balances from various bank accounts to one target account, keeping defined minimum balances in the source accounts. The system creates a concentration proposal, based on the grouping. The proposal contains the balance for the end of the day, and the planning result -that as, the likely account transfers. You can correct the concentration proposal at any stage in the process. The result is printed and takes the form of payment orders to the banks. Payment advices are also created. They are necessary for the new bank balance at value date.



The grouping contains only those costs that are to be included in cash concentration. You can define different groupings in cases where the concentration procedure is different.



You have the option of concentrating balances for a number of company codes at the same time. You do this by means of a worklist, which combines a number of company codes.



Cash concentration can be started as a report program.

(C) SAP AG

AC805 6

14.7 Cash Concentration: Program

Co.code : Planned date : Grouping : Tgt account : Target co.code: co.code:

AC01 08/04/YY BANK-ACT CIGIRO AC00 Planning type :CO :

Rounding

Concentration proposal

Change ...........

Create payment advices

Payment orders

 SAP AG 1999

Procedure for running the report program:  Enter the company code or, if you are concentrating cash for more than one company code, the worklist.  In the Planned to field , enter the planning date up to which you want to concentrate balances.  Enter a grouping term in the Grouping field, thereby selecting particular accounts for concentration. Example: BANK-ACT.  Enter the cash management name for the account where the amounts are to be concentrated. Enter the target company code too.  If required, use the Minimum Balance field to stipulate the minimum balance an account must have before it is selected for cash concentration.  In the Planning Type field, enter a planning type assigned to cash concentration. 

The plannable amount is the total of the cash management end balances, less any defined minimum balances applicable. This need not be the case for the target account because the target account must not have a negative balance. You can process the amounts.

(C) SAP AG

AC805 7

14.8 Cash Concentration: Posting Processes Proposal: (Tgt acct 113300)

113100 113300 Outcome:

Before

After

10,000 0

0 10,000

Clrg Acct (T018c) 113105 113305

2 payment advices

Postings: 113100 2a) 10,000 113300 2b) 10,000

113105 2a) 10,000

1) 10,000

113305 1) 10,000

2b) 10,000

 SAP AG 1999



Once you have processed the concentration proposal, you can create two payment advices for each payment order. One advice is for the sender account and one is for the receiver.



Confirm creation of the advices in the additional window. The system tells you that advices have been created, and you return to the initial screen.



With the posting program, you can post payment advices created during cash concentration to the relevant accounts. The program creates a batch input session for the postings and archives the payment advices.



The prerequisite for the posting is that an account for posting must be entered in the customizing table (payment methods and minimum balances).



You can simulate the postings first. The simulation does not create a batch input session for the postings, nor does it archive the payment advices. It does, however, output the list.



Statements for the account in question come the next day and clear the advance postings in the relevant clearing accounts.

(C) SAP AG

AC805 8

14.9 Cash Concentration and Payment Program

 You can use the concentration paymentadvices to generate payment reques, which are then regulated using the relevant payment program (F111).  Procedure: 

Carry out cash concentration



Generate payment requests from paymentadvices



Regulate payment requests

 SAP AG 1999



Payment requests are documents used to create payment media. They are usually generated automatically when transactions due are posted. They are then regulated (individually or together) using F111, the payment program for payment requests.

(C) SAP AG

AC805 9

14.10 Payment Program Parameters Payment transactions: parameters Payment Object

Additional Log

Dynamic Selections

Date Executed

07/19/YYYY

Posting date

07/19/YYYY

Identification

1423

Next payment run on

07/20/YYYY

Payment Control Company code

0001

Interim Accounts

E

To

1000

Constraints Source

TR-LO TR-CM-BT

To

Vendor Account

To

Customer Account

To

G/L Account

To

Additional Constraints Documents entered to Documents to period

07/19/YYYY /

 SAP AG 1999



Field selection control enables you to regulate which input parameter fields are shown or hidden. In customizing for bank accounting, you can use the global settings to stipulate which of the following fields should appear and be ready for input when you enter payment parameters: - Accounts payable - Accounts receivable - G/L accounts - Date entered - Source



You can use the source indicator to determine for which application payments are to be generated.

(C) SAP AG

AC805 10

14.11 Source Indicators

 The new Source indicator is used to stipulate the application for which payments are to be generated.  The following can be source indicators:TR-CM-BT, TR-TM, TRLO  In the case of payment requests from different sources: 

Payment requests can be allocated



Control effected in customizing for bank accounting



Payment program uses only the characteristics of the indicator where the "Grouping" flag is set.

 SAP AG 1999



The Source Indicator field is new. You use it to stipulate the application for which you want to generate payments and how payments are to be processed. We deliver source indicators for the following applications where payments are created:  TR-CM-BT (Bank account transfers from Cash Management)  TR-TM (Transactions from the Treasury Management areas: Money Market, Foreign Exchange, Securities, Derivatives)  TR-LO (Transactions from Treasury Loans)

(C) SAP AG

AC805 11

14.12 More New Features in the Payment Program  Editing in the payment proposal: 

Block payment



Change payment method



Change house banks

 Reversing payments: 

Reverse clearing and cancel payment document



Reverse payment request clearing



Cancel original transaction

 SAP AG 1999

It is now possible to process payment proposals for payment requests. You can block payments and change payment methods and house banks.  The retroactive calculation of payment due dates is effected using the time that elapses between the payment run and the value date at the bank. The calculation takes account of the public holiday calendar. Payments not due this time are postponed until the next payment run. To use the retroactivate due date calculation, you must specify the difference (in days) between the payment run and the bank due date.  You can now reverse a payment completely. You can use transaction F8BW to reverse payment request clearing. The procedure, including cancelation of the original transaction, comprises the following steps: 1. Reverse clearing and cancel payment document 2. Reverse payment request clearing 3. Cancel original transaction 

(C) SAP AG

AC805 12

14.13 Cash Concentration: Unit Summary

 The concentration proposal is created automatically. The system obtains the determining factors from table specifications (customizing) and the grouping.  Correspondence is prepared using the proposal.  The concentration postings also result from the proposal. They are required for electronic statement transfer.

 SAP AG 1999

(C) SAP AG

AC805 13

15 Cash Concentration: Customizing

Contents  Concentration requirements as settings in tables  Concentration examples  Automatic correspondence

 SAP AG 1999

(C) SAP AG

AC805 1

15.2 Cash Concentration - Customizing: Unit Objectives

At the conclusion of this unit, you will be able to:  Configure concentration in customizing  Recognize correspondence settings

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

15.5 Cash Concentration - Customizing: Business Scenario

 When cash is concentrated, minimum balances should continue to be held in the accounts.You enter these in customizing.  You also have to define the clearing account for the concentration proposal posting.  Do you need to make interim postings to an interim account to conceal the postings?

 SAP AG 1999




(C) SAP AG

AC805 5

15.6 Cash Concentration - Specifications Interim Accounts CC

Account

AC01 AC01 AC01

113100 113200 113300

Details

Payment account CC AC01 Account 113300 Minimum balance 5,000 Planning minimum 5,000 Clearing account 113305

 SAP AG 1999



To be able to use cash concentration, you must first enter some customizing settings.



You must enter a clearing account, to which postings are made during cash concentration.



You can concentrate amounts moving between banks by means of an interim account. The amounts do not then flow directly to the target account, but to the interim account. They are then transferred from there to the target account. This means that nobody can use the payment advice and accompanying payment order to trace the account to which the amounts are finally posted.



You also need to configure the minimum balances. By changing in the minimum balances as you carry out cash concentration, you also have the option of changing the closing balances in your accounts. A prerequisite for this is that minimum balances are maintained for the accounts.

(C) SAP AG

AC805 6

15.7 Concentration - Configuration Examples

Ex.

CONACT CONBK INTACT

INTBK

TGACT TGBK

1.

BANKA + 500

AC01

BANKA

AC01

BANKZ 500

AC01

CNCN-ACT/CNACT/CN-BK= INTACT/BK.

2.

BANKA + 500

AC01

BANKA - 500

AC02

BANKZ 0

AC00

(INTACT) INTBK ¹ TGACT/BK

3.

BANKA

AC01

BANKB

a)

+ 500

b)

BANKB + 300

AC01

BANKZ AC01

- 200 + 500 _________ + 300,BANKB

AC01

TABLE 018C

INTACT ¹ TGACT

300

INTBK = TGBK

 SAP AG 1999

  

Example 1: Concentration within a company code Example 2: Concentration for a group Example 3: Concentration within a company code, using an interim account

(C) SAP AG

AC805 7

15.8 Cash Concentration - Correspondence

CC

Name

AC01 :

SAP AG

Program RFFDIS50

Form Name F_FDIS_BC_AVIS

Tools Word processing Form

 SAP AG 1999



The system automatically generates confirmations for the payment orders issued. To this end, you must create the appropriate form and assign it to the program.



The payment recipient can be printed on the form. This is particularly important in the case of payment advices covering more than one company code.



Confirmations can be generated for the bank after you have confirmed that the payment advices have been created.

(C) SAP AG

AC805 8

15.9 Confirmation: Address / Account No. Customizing Bank Master

House bank

House bank : 1000 Bank account key: Current

CITI :

BNKA

House Banks Ctry US

Bank key 100 200 30

Address

 SAP AG 1999



The house bank and account key in the bank account master records to determine the bank key, bank account number, and the accompanying address data.

(C) SAP AG

AC805 9

15.10 Field Selection Control in the Payment Program

 Show and hide fields when entering payment parameters 

Vendor accounts



Customer accounts



G/L accounts



Date entered



Source

 SAP AG 1999



In customizing for bank accounting, you can use the global settings to stipulate which of the following fields should appear and be ready for input when you enter payment parameters: - Vendor accounts - Customer accounts - G/L accounts - Date entered - Source If you want no restrictions and want to pay all items which are due, do not select any of these fields.

(C) SAP AG

AC805 10

15.11 Customizing Source Symbols Display View "Source Control" Overview

SourceControl PldAmounts Source Description TR-CM-BT Bankaccountcarryovers TR-LO LoanManagement TR-TM

AccountDetmtnGrouping

CollectivePosting

Treasury Management:

 Customizing settings for each source symbol: 

Include planned amounts (yes/no)



Account determination of application or payment program (to determine the bank clearing account)



Use of the settings for this indicator (yes/no) using the "Grouping" flag

 SAP AG 1999

Use the customizing settings for the source indicator to control the following in payment transaction processing:  Whether the payment program should check the amounts planned. If you set this indicator, the program does not check the amounts planned for payment requests.  Whether the account determination in the application or that in the payment program should be used to determine the bank clearing account for payments. If you do not set this indicator, the account determination function in the program is used to determine the bank clearing account. The result of the application account determination is ignored.  Whether the characteristics already defined for a source should be used when payment requests with different sources are being cleared. If you set this indicator, the payment program uses the characteristics for this sources when clearing payment requests with different sources.  The origins whose payment requests are allocated against each other must be assigned to each other. You do this in customizing for bank accounting. 

(C) SAP AG

AC805 11

15.12 Cash Concentration - Customizing: Unit Summary

 Table specifications make cash concentration practically automatic - for example, within company codes or across a whole corporate group.  The payment advice notes the system creates from cash concentration provide the necessary data for correspondence with banks and for planned postings from bank statements.

 SAP AG 1999

(C) SAP AG

AC805 12

15.13Cash Concentration Exercises Unit: Cash Concentration

At the conclusion of these exercises, you will be able to: • Create a bank clearing account for cash concentration and complete the payment method table in customizing • Create a cash concentration proposal • Print the cash concentration proposal • Post the cash concentration proposal You have decided to concentrate the daily account balances in your various bank accounts in a target account. You will now enter the necessary system settings and carry out cash concentration. Then print out the cash concentration proposal to send it to the banks whose accounts you want to concentrate. Then post the proposal by way of the bank clearing accounts, and compare them with the next day's bank statement.

1-1 Add your new bank account (11xx00) to the payment method table in customizing. Do not concentrate cash by way of an interim account. Enter minimum balances and clearing account 11xx05. Postings are made to this account when the payment requests generated in cash concentration are converted into FI documents. If you have not yet created account 11xx05, do so now. 1-2 Once all the cash management transactions have been processed, you must decide what it is to be done with the bank balances. You decide to transfer the account balances to account CICURRENT (113200). The transfer is to be in round thousands only (grouping BANK-ACT, advice type CL). Remember: you must enter the cash management account name, not the G/L account number.

1-3 Create corresponding confirmations to the banks (simulate these on your screen).

1-4 Then post the concentration memos for your company code, paying attention to the accounts posted to (+++++5). Process the batch session. (C) SAP AG

AC805 13

1-5 Assign accounts 11xx00 and 11xx05 to the "Concentration" grouping. Display the cash position (concentration grouping). The concentration postings are on level B5.

(C) SAP AG

AC805 14

15.14Cash Concentration: Solutions Unit: Cash Concentration

1-1 Solution on Completing Payment Table Customizing: Customizing ... → Cash Management → Business Transactions → Cash Concentration → Define payment method and minimum balance Copy an entry or enter your data by choosing "New entries". Field Name or Data Type

Values

Company code

ACxx

Bank account

11xx00

Minimum amounts

Your option

Clearing account

11xx05

You create the bank clearing in the FI application component. 1-2 Solution: cash concentration.

→ Rechnungswesen → Treasury → Cash Management → Planning → Cash concentration → Create Enter your selections (including the grouping, target account, target company code, and payment advice details).

(C) SAP AG

AC805 15


Values

Company code

ACxx

Grouping

BANK-ACT

Currency

UNI

Minimum balance

Your option

Target account

CITICURRENT

Target company code

ACxx

Planning type

CL

Minimum amount

Your option

1-3 Solution: Creating Confirmation to the Banks.  Accounting  Treasury  Cash Management  Planning  Cash Concentration  Print Confirmations

1-4 Solution: Posting Concentration Payment Advices in Your Company Code

→ Accounting → Treasury → Cash Management → Planning → Cash Concentration → Post (test / live run) The batch input session is created.

→ System → Services → Batch Input → Select the sessions (C) SAP AG

AC805 16

→ Process the sessions.

1-5 Solution: Display in Cash Position.

 See previous solutions.

(C) SAP AG

AC805 17

16 Liquidity Forecast

Contents  Projecting collections and disbursements from FI, SD, MM, and TR  Individual planning and planned items  Customer payment history  Grouping by planning groups

 SAP AG 1999

(C) SAP AG

AC805 1

16.2 Liquidity Forecast: Unit Objectives

At the conclusion of this unit, you will be able to:  Explain the features and integration aspects of medium-term planning  Recognize the significance of planning groups  Configure subledger accounts

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

16.5 Liquidity Forecast: Business Scenario

 Now that you have a comprehensive overview of how bank and bank clearing accounts develop and how to make the necessary system settings, you now want to know how to obtain a medium-term view of the subledger accounts.

 SAP AG 1999




(C) SAP AG

AC805 5

16.6 Characteristics of the Liquidity Forecast

Liquidity Forecast  Projecting collections and disbursements from FI, SD, MM, and TR  Individual planning and planned items  Automatic maintenance (reversal, document change)  Customer payment history  Planning groups  Additional information (blocked items, special transactions)  Currency exposure  Variable breakdown of planned items (days, weeks, months)  SAP AG 1999



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 you can use to obtain relevant information on forecast payment flows. This information appears as planned items in the liquidity forecast.



The information is based on payments in and out from/to customers and vendors, per the open items. As planning for incoming and outgoing payments covers a larger timeframe, the probability of the payments occurring on the day given is less than in the cash position.



The following are examples of sources of planning information for the liquidity forecast:  Receivables and commitments as expected incoming payments  Planned wage and salary payments



As with the cash position, you just groupings to set up the liquidity forecast structure. The grouping term is used to combine particular levels and planning groups for display purposes.

(C) SAP AG

AC805 6

16.7 Integration: Liquidity Forecast

Planning Analyses FI


Open item accounting

CM

Cash Management

Liquidity forecast

Payment history

SD

Sales Orders

 SAP AG 1999

(C) SAP AG

AC805 7

MM

Purchasing

Purchase order

16.8 Requirements (1): Planning Groups (E2)

Bank collection (E1)

France (E4) Net amount payer (E3)

(E5)

FI = Posting/transactio ns FC = Bills of exchange XA = Block reason 'A'

Groups: Groups: -- Customers Customers with with the the same same payment payment history history -- Customers Customers of of particular particular interest interest Levels: Levels: -- Balances Balances specified specified by by level level

 Integrate database, including customers, vendors, and planned items  Forecast payments in and out for a timeframe of 124 weeks  Support for optimizing financial borrowings and investments Liquidity monitoring  SAP AG 1999

  

Like vendors, customers are divided into planning groups You define the criteria used. Levels provide information about the type of account transaction.

(C) SAP AG

AC805 8

16.9 Requirements (2): Master Record

Acct no. Company code :

T-T05A00 AC01 Planning group E2 Domestic

Input options A1 ...

K-

E2 ...

Domestic

 SAP AG 1999



You have to enter a defined planning group in the master record in order for the system to transfer data between the customer/vendor accounts and the liquidity forecast.

(C) SAP AG

AC805 9

16.10 Payment History - Planning Date Acct no. Company code

T-T05A00 AC01 Rec pmnt hist : X

X : Planning date =

S1 +/+/- payment history If customer usually takes discount Net +/+/- payment history If customer usually pays net net

'_' : Planning date =

Disc1Disc1-DueDate

 SAP AG 1999

The system takes account of the customer payment history when determining the planning date if you select the "Rec pmnt hist." field in the customer master record.  The last three periods in which payments have been made are taken into account (short term payment history). The calculation is weighted by amount.  You can trace the payment history as part of account analysis. 

(C) SAP AG

AC805 10

16.11 Integration: Payment Block

FI posting Payment block A in master record XA

Vendor /Customer (No automatic change)

Payment block A/R in item XR

X + blkg ind. ind.

Planning level in the document  SAP AG 1999

In this menu option, you can define the assignment to the blocked levels for the levels in the liquidity forecast. If you then make a posting with payment blocked, the system uses the blocked level instead of the standard level for the planning group in question.  The payment block on the amounts displayed in the liquidity forecast is then clearly identifiable. 

(C) SAP AG

AC805 11

16.12 Integration: Special Transactions

FI posting F0

Master record verification Special G/L level Transaction type

FF/FW

Validation

Planning level in the document  SAP AG 1999

   

Line items resulting from special transactions are transferred to a special level. It is easier to monitor scheduled special G/L transactions in Cash Management than in Accounting. This makes the reconciliation account irrelevant. Use levels that begin with "F" as these are FI postings. It is a good idea to use the special G/L indicator as the second letter: Example: FF for down payment requests.

(C) SAP AG

AC805 12

16.13 Liquidity Forecast: Unit Summary

 The liquidity forecast is used to monitor incoming and outgoing payments. All documents posted in subledger accounting are aggregated online.  Payment history and document changes are also taken into account online.  The cash position and liquidity forecast reflect the total liquidity of a company.

 SAP AG 1999

(C) SAP AG

AC805 13

16.14Liquidity

Forecast: Exercises

Unit: Liquidity Forecast

At the conclusion of these exercises, you will be able to: • Enter outgoing and incoming invoices so that you can display them in the liquidity forecast • Ensure that the customer payment history is accurately recorded You want to use the liquidity forecast to obtain an overview of mediumterm liquidity. Both the bank accounts and subledger accounts should be included. You want to reproduce outgoing and incoming invoices in the liquidity forecast. In addition, you want to record the customer payment history to take account of the effects in the liquidity forecast in the subsequent transactions.

1-1 Post the following outgoing invoice (document date: today): - Customer T-T05Axx, amount 10,000. Output tax AN, terms of payment: ZB01 - Offset posting: posting key 50, account 800200, tax '*'. Post the following incoming invoice (document date: today): - Vendor T-T05Axx, amount 10,000 Input tax VN. - Offset posting: posting key 40, account 400020, tax '*'.

1-2 Check your entries by displaying medium-term planning – liquidity forecast (subledger grouping or overall grouping).

(C) SAP AG

AC805 14

1-3 Use the account analysis to view the customer accounts T-T05Axx and T-T05Bxx, the line item display, then use the "Goto" menu to access payment history analysis. If you have not posted anything to customer T-T05Bxx, no line item display appears for this customer. Similarly, no payment history analysis is possible for this account. Now change the master data for customer T-T05Bxx, by allocating a planning group to it. Then activate payment history recording. Post the following outgoing invoice (document date: today): - Customer T-T05Bxx, amount 50,000 Output tax AN, terms of payment: ZB01 - Offset posting: posting key 50, account 800200, tax '*'. Now use the account analysis again to view the line item display for customer account T-T05Bxx. The payment history is still empty because no payments have been received. Look at the liquidity forecast (increment in days, overall grouping). The invoice is planned for 14 days from now. The customer pays. Post the incoming payment with posting, document, and value dates 20 days from now (bank account 113102, amount 49,000 - customer T.T05Bxx). The payment history now contains information on customer T-T05Bxx. If you now post another outgoing invoice (document date: today), what planning date appears for it?

(C) SAP AG

AC805 15

16.15Liquidity Forecast: Solutions Unit: Liquidity Forecast

1-1 Solution: Posting Invoices

→ Accounting → Financial Accounting → Accounts Receivable/Payable → Document Entry → Invoice Enter your data.

1-2 Solution: Checking Entries in the Liquidity Forecast.

→ Accounting → Treasury → Cash Management → Status → Liquidity Forecast Enter your selections. Note that a payment history has already been recorded at your customer T-T05Axx.

(C) SAP AG

AC805 16

1-3 Solution: Payment History Analysis Account analysis:

→ Accounting → Financial Accounting → Accounts Receivable → Account → Analysis Enter your data and access the payment history (in the Goto menu). A payment history has already been recorded for your customer T-T05Axx, but not for T-T05Bxx yet. Change master data:

→ Accounting → Financial Accounting → Accounts Receivable → Change Master Data Enter your data (planning group E2, activate payment history recording). Outgoing invoice:

→ Accounting → Financial Accounting → Accounts Receivable → Document Entry → Invoice Enter your data. Account analysis:

→ Accounting → Financial Accounting → Accounts Receivable → Account → Analysis Enter your data and access the payment history (using the "Goto" menu). Liquidity forecast: (C) SAP AG

AC805 17

→ Accounting → Treasury → Cash Management → Information System → Reports on Cash Management - Liquidity Analyses → Liquidity Forecast

Enter your selection (increment in days).

Incoming payment:

→ Accounting → Financial Accounting → Accounts Receivable → Document Entry → Incoming payment Note the later date determined using the payment history.

(C) SAP AG

AC805 18

17 Liquidity Forecast Customizing: Unit Objectives

At the conclusion of this unit, you will be able to:  Configure field selection control for subledger accounts  Configure and access the display options for noted items  Configure screen control for document entry  Ensure integration of special general ledger transactions  Ensure integration of data from MM/SD and Treasury  Correct liquidity surpluses or deficits by means of money market deals

 SAP AG 1999

(C) SAP AG

AC805 1

17.2 Liquidity Forecast: Customizing

Contents  Field selection control  Display types  Screen control  (Blocking) Levels  Integrating special transactions  Integrating data from Logistics  Integrating data from Treasury

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

17.5 Liquidity Forecast Customizing: Business Scenario

 Before activating the liquidity forecast, you must make a number of customizing settings.  How are locked items and special general ledger transactions to be displayed in the liquidity forecast?  How is data from Logistics and Treasury displayed in the liquidity forecast/cash position?

 SAP AG 1999




(C) SAP AG

AC805 5

17.6 Master Data: Subledger Accounts

Customer / Vendor Controls

Field selection Activities

Account group Field selection Company code

Change customer / vendor

 SAP AG 1999



You can control the field status on particular screens directly in the Cash Management IMG. You can do this at different levels: - For all customers or vendors of an account group or a company code - For all customers or vendors that are created or changed in accounting (sales, centrally).

(C) SAP AG

AC805 6

17.7 Percentage Distribution

Cash position Liquidity forecast .. . Display type : .. .

C/D Level AU AU UA NI NI NI NI NI

+/+/- sign + + + -

Days

Percentage

0 1 1 0 1 2 1 2

50 30 20 40 20 10 20 10

 SAP AG 1999

When you select the cumulative and distributed display as well as the display distributed by inflows and outflows, the system will distribute memo records and summary records for each level according to the specifications that you can define.  Items are distributed before or after the determined value date using the +/- signs, days, and percentages that you specify. 

(C) SAP AG

AC805 7

17.8 Planning Data: Screen Control

Plg group

Level

A1 E1 :

Bal. Bal.

F1 F1

X X

Short text

Description

K-Inland CitiIncg

K-Inland Citi income

Posting Customer Co.code AC01

: : :

Planning group E1

Extras

Additional data : Planning date: 04.MM.YY Planning level: F1

 SAP AG 1999

Planning groups differentiate customers and vendors according to particular characteristics (customer in France), behavior (takes cash discount) or risks (credit rating). They are user-definable and are entered in the "Planning group" field in the customer or vendor master record.  If you select the "Screen control" option (SCn), the "Planning date" and "Planning level" fields are ready for input when documents are entered or changed. You can overwrite the values the system automatically defaults for these fields. 

(C) SAP AG

AC805 8

17.9 Blocked Documents

Level

Blockg Ind.

F1

Blocked Level . . . Description XX

Released for payment

F1

A

XA

Payment blocked

F1 :

R

XR

Invoice verification

 SAP AG 1999

 

You can allocate blocked levels or block indicators to the standard levels. The system then assigns the amount to the blocked level when the posting is made with a payment block. If the document is unblocked, the amount is transferred to the standard level.

(C) SAP AG

AC805 9

17.10 Integration: Special General Ledger (SGL) SGL Levels Special G/L Acct type D D :

SGL ind. ind. F W

SGL ind. ind. DP req. req. BE rec. rec.

Description . . Down payment request Bill of exchange receivable

Select Special GL indicator Recon.account Recon.account 140,000 :

W SGL acct

Planning level

125,000

FW

Planning levels Level Source Short text FW :

PSK

Long text FI bill of exc. exc.

FI bill of exc. exc.

 SAP AG 1999



Special G/L postings can be displayed and monitored in a special level in the liquidity forecast. Two levels are already defined in the standard system: - Down payment request (FF)



- Bill of exchange receivable (FW) Even if a bill of exchange is used (discounting), it remains in the planning level until the commitment is deleted. Note the incoming payment in the bank clearing account in the cash position. The discounted amount of the bill of exchange is displayed in this account until the commitment is deleted.

(C) SAP AG

AC805 10

17.11 Integrating Orders and Purchase Orders

MM

SD

Purc.order Purc.order

Order EP

Table RWCA

EP

FDSR

Bllg doc. Discount

FDIS active: X

Tools Production startup MM update SD update

: X : X

Customizing

MFD

Planning level Source

 SAP AG 1999



Procedure 1.

Maintain source indicators

2.

Maintain planning levels (M1, M2, M3, S2)

3.

Maintain logistics levels (M1 and so on)

4.

Switch on SD integration

5.

Switch on MM integration.

(C) SAP AG

AC805 11

17.12 Integrating Orders and Purchase Orders

Subledger accounts Levels Levels

Source

M1 S1

Source indicators ...

MAT VER

Source

Cash pos. pos.

MAT VER

Level Logistics Int

Short ID

002 101

Purc.order Purc.order Order

Level M1 S1

 SAP AG 1999

  

Purchase orders (MM) and sales orders (SD) are displayed in special levels within planning. You can freely define these levels. They require a special source symbol. The internal code you specify integrates orders and purchase orders into Cash Management Agency business from Logistics (vendor invoices, invoice lists, settlement requests) can also be recorded in the liquidity forecast.

(C) SAP AG

AC805 12

17.13 Integration with Other SAP Modules

Market information

Trading

Planning decision

Cash Position G/L accounts

TRTR-TM

Customer/ vendor

Sales orders

FI

Treasury

FI

MM/SD

Financials

 SAP AG 1999

(C) SAP AG

Liquidity Forecast

AC805 13

Logistics

17.14 Selection of Financial Instruments Product Types Investment/Borrowing Instruments

Money market 





Fixed-term deposits Deposit at notice Commercial paper

Hedging Instruments

Securities  



 

 

Stocks Subscription rights Investment certificates Bonds Convertible bonds Warrant bonds Warrants

Loans 



 

Mortgage loans Mortgage loans Policy loans Other loans

Forex 





Forex spot deals Forward exchange deals Foreign exchange swaps

Derivatives   





Cap / floor FRA Swaps - Interest - Interest currency OTC options Currency - Interest - Securities Swaption, IRG Futures traded on the stock market

 SAP AG 1999

Short-term money market or foreign currency deals are one way of dealing with over liquidity shortfalls or surpluses. For the medium to long-term, investments and borrowings are represented by security and loan transactions..  Derivatives, on the other hand, are a means of hedging interest and currency risks. 

(C) SAP AG

AC805 14

17.15 Treasury Management: Functions

 Comprehensive management of financial transactions and balances 

Support for trading and processing functions



Functions to track, check, and release transactions



Data transfer to Financial Accounting (including interest accruals and valuations)

 Flexible control of company-specific transaction and balance management  Financial transaction assigned to portfolios or managed in securities accounts  Flexible reporting and portfolio analysis  Datafeed interface  SAP AG 1999

(C) SAP AG

AC805 15

17.16 Transaction and Balance Management Process

Release

Trading Enter orders / contracts Exercise / expire  Terminations  Rollovers  Dealing slips

Processing Settlement Interest rate adjustment  Compensation  Referencing  Confirmation letters  Securities transfers  Capital measures

Accounting Postings Payment trans  Cancel  Accrual  Valuation













User authorization Limit management

 SAP AG 1999

(C) SAP AG

AC805 16

17.17 Trading: Create Fixed-Term Deposit Fixed term

Edit

Management

Create Fixed-Term Deposit: Basic Data Goto Extras System

Payment

Cash flow

Other flows

Company code Product type Trans.type

AC00 SAP AG Model co. 51A Fixed term deposit 100 Investment

Partner

CITNY

Investments Flow type Amount

1100 1000000

Interest structure Percentage Frequency Wrkg dys due dt. Wrkg days calc. For rollover Start incl. Conclusion Contract date Contact person

5 1

Help

Payment details

Transaction Activity ActyCat

\INTERN\ 1 Contract

Citibank New York Principal increase UNI -

At end of term No shift No shift Payment End inclusive

07/17/YYYY / 10:48:23

Term Start Finish

Calc. meth All

0 +30

2 Days/Months

Trader Trader Reference Reference

 SAP AG 1999



The update to Cash Management distinguishes between two cases:  Alternative 1 (liquidity forecast): If no payment details have been maintained in the transactions - that is, the bank accounts are not known -, the cash flow for a bank account or bank clearing account cannot be displayed. However, the amount must appear in Cash Management somehow, so the amount is displayed re subledger accounts. The system then draws on the planning group specified in the master record for the business partner. 

(C) SAP AG

Alternative 2 (cash position): If payment details are specified in the transaction - that is, the bank accounts are known -, the cash flow appears in TR-CM on the level assigned to the relevant bank account/bank clearing account.

AC805 17

17.18 Postings Using Bank Clearing Accounts Interaction of TR-TM and TR-CM

Fixed-term deposit

Using transaction at fixed deposit level

Posting transactions to clearing account

Switch to clearing accounts

Clearing entry using bank statement

Switch to bank account level

 SAP AG 1999

The graphic illustrates how processing should ideally work, showing how Treasury Management and Cash Management usually work together and how the Financial Accounting posting is made.  Payments are usually triggered by the business partner (bank) and further processed in Cash Management by means of the electronic bank statement. 

(C) SAP AG

AC805 18

17.19 Transfer to Financial Accounting: Logical Process Assign planning levels 0001

Model company

51A

Fixed-term deposit

TB

Bank time deposits

10

Contract

Cash Management: Level Display Banks Lv

Description

10/03 10/03 10/04. 10/05 10/05 Future Future 10/02 10/03 10/02.

TB ...

Time deposits

150.000 xxx,xxx xxx,xxx xxx,xxx xxx,xxx

B5 ...

...

...

Clearing

...

CITI Banks Balance

...

...

...

...

150.000 xxx,xxx xxx,xxx xxx,xxx xxx,xxx

...

...

...

...

...

150.000 xxx,xxx xxx,xxx xxx,xxx xxx,xxx xxx,xxx xxx,xxx xxx,xxx xxx,xxx xxx,xxx

 SAP AG 1999

Every activity in a business transaction is displayed automatically in Cash Management. The exception is orders, which are not included. At your option, you can display and analyze each activity on a separate level.  Cash flows resulting from transactions become visible in Cash Management immediately, whether or not they have already been posted. You can then use them in planning.  Use customizing to maintain the planning levels for G/L and/or subledger accounts where the relevant product types and transactions are to be displayed.  Example: Closed fixed-term deposit: Level FT - fixed term deposit 

Posted forex transaction:

Level B5 - Bank clearing account

On receipt of bank statement:

Level F0 - Bank account

(C) SAP AG

AC805 19

17.20 Liquidity Forecast Customizing: Unit Summary

 Subledger accounting is integrated with Cash Management when you specify planning groups in the master records of subledger accounts.  During posting, you can change the planning date that the system automatically specifies.  Orders and purchase orders are integrated online.  Transactions from Treasury can be integrated also.

 SAP AG 1999

(C) SAP AG

AC805 20

18 Data Transfer and Reorganization

Contents  Data transfer  Data leveling  Reorganization

 SAP AG 1999

(C) SAP AG

AC805 1

18.2 Data Transfer and Reorganization: Unit Objectives

At the conclusion of this unit, you will be able to:  Activate Cash Management  Transfer data from old systems or feeder systems  Distinguish between the various reorganization transactions

 SAP AG 1999

(C) SAP AG

AC805 2



(C) SAP AG

AC805 3



 SAP AG 1999

(C) SAP AG

AC805 4

18.5 Data Transfer and Reorganization: Business Scenario

 You have now made all the system settings and want to reproduce financial accounting and logistics (MM/SD) transactions in Cash Management. What settings must you make and how is the data transfer carried out?  You want to reorganize the database from time to time. This means deleting old or expired data and using memo records to create summary records. How can you start the reorganization run?

 SAP AG 1999




(C) SAP AG

AC805 5

18.6 Implementation Support

FDFD Cash Management active in company code Activate Cash Management in a company code

Customer/vendor data Enters appropriate cash management data in vendor and customer master records

Data Setup/Correct Data/Data Reconciliation Schedule various data setup programs for immediate or later processing  SAP AG 1999

  





This function makes it easier to implement Cash Management and use it productively. The following activities are now quicker and easier to implement: The most import steps in activating Cash Management in a company code now appear in just one view. Activating Cash Management for each company code now involves selecting a single switch. The system stores the relevant data in the customer/vendor master records. This is done automatically, according to selection criteria and priorities you define yourself. You do not need to leave this screen to enter the necessary settings. To ensure that cash management groups are entered in all the master records, you need to specify at least one profile (with the lowest possible priority) that matches a vendor/customer if no other profile does. You use the FDFD initial screen to access individual programs that set up the cash management figures and schedule them for background processing. This means you do not need detailed knowledge of the setup programs in SAP components. Note that each setup program begins by deleting all Cash Management data. If there is any any manual planning data, the system asks you about this separately, because such data does not need to be changed or deleted. The system also offers support for cleaning up data errors and reorganizing cash management data in master records.

(C) SAP AG

AC805 6

18.7 Transferring Data from Accounts With/Without Open Items

Not open items (sales)

LC SKC1A

FC SKC1B

Open item (documents)

BSIS

BSIK

RFFUEB00

RFFDKU00

FDSB

FDSR

Cash position

BSID

Liquidity forecast

 SAP AG 1999



Data for Cash Management should be set up per batch input (performance). - You can simulate the data transfer online. When doing this, make as many selections as possible. - You can transfer data from customer or vendor accounts without making any specifications (only batch).

- The system proposes propose the minimum selections (fiscal year, reporting period, value date) for transferring accounts (resident) that are not managed on an open item basis. These minimum selections are required for summarizing the account balances, and can be overwritten.  When you migrate from to 4.5B from an earlier release, you must completely reconstruct cash management because the update logic is different. In the case of the G/L account, the G/L account currency is not always adopted. Now, either the document currency (for G/L accounts managed on an open item basis) or the G/L account currency (for other G/L accounts) is used. Use the Data Setup function in transaction FDFD to delete the data and reconstruct it.  You do not need to change or delete memo records entered manually. The Data Setup function in transaction FDFD displays a confirmation prompt, asking whether the data records should be irretrievably deleted. Answer "No". However, all other cash management data must be reconstructed. Otherwise, the values in the system will be incorrect.

(C) SAP AG

AC805 7

18.8 Data Reconciliation

Line Line items items Planning Planning Summary Summaryrecords records

FI

FDSB SD

FDSR

MM Same total ?  SAP AG 1999

The system includes a data reconciliation function that can be scheduled from transaction FDFD as batch job. This program compares the totals records from tables FDSR and FDSB with the corresponding memo records from the applications or from the FI accounting documents. If the cash management and forecast has been reorganized, you must specify the summarization data specified in the last reorganization rune (program RFFDIS00).  If the reconciliation does not find any errors, there is no system output. However, where differences between the totals records and the memo records are found, the totals records are highlighted in the display and followed by a list of the relevant memo records. The output from this program can help minimize any data inconsistencies and the need for data reconstruction.  If the data in cash management is not consistent with the actual data, you can use the Correct Data function in transaction FDFD to correct the data, obviating the need for a complete data reconstruction. Depending on what caused the error, you may be able to restrict the reconstruction to certain areas. If a complete reconstruction is necessary, however, use the Data Setup function in transaction FDFD to effect it. 

(C) SAP AG

AC805 8

18.9 Reorganization

Reorganization FDES  Memo records/ archived memo records

FDSB

FDSR

 Summary records  Customer and Bank and clearing accounts

 Active summarized memo records

vendor summary records  Active

summarized plan items

 SAP AG 1999

Tables in Cash Management must be reorganized on a regular basis to increase memory and improve access times.  The reorganization program:  Deletes expired summary records  Ignores blocked records  Summarizes summary records at the summarization date (if the value date is earlier than the summarization date)  Deletes memo records (if the expiration date of memo the record is before the expiration date specified for the reorganization run)  Deletes archived memo records after the retention period has run out  Lists all summary records and memo records (if you select this option) 

(C) SAP AG

AC805 9

18.10 Data Transfer and Reorganization: Unit Summary

 Before data is transferred, Cash Management must be activated in the respective company code.  Data from accounts managed on an open item basis and data from accounts that are not managed on an open item basis is transferred separately.  Datasets from FI, SD, MM, and Cash Management can be compared with planning data by means of the appropriate programs.

 SAP AG 1999

(C) SAP AG

AC805 10

AC805-CashManagement

Recommend Documents