26
EHP3 for SAP ERP 6.0 June 2009 English Cash Management (160) Building Block Configuration Guide

Liquidity & Cash

Embed Size (px)

DESCRIPTION

liquid

Citation preview

Page 1: Liquidity & Cash

EHP3 for SAP ERP 6.0

June 2009

English

Cash Management (160)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf

Building Block Configuration Guide

Page 2: Liquidity & Cash

Germany

Page 3: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Copyright© Copyright 2009 SAP AG. All rights reserved.

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

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

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

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

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

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

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

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

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

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

Content

© SAP AG Page 3 of 21

Page 4: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

1 Purpose................................................................................................................................ 42 Preparation.......................................................................................................................... 42.1 Prerequisites......................................................................................................................... 43 Configuration........................................................................................................................ 4

3.1 Basic Settings................................................................................................................43.1.1 Default Value Date................................................................................................43.1.2 Planning Levels.....................................................................................................5

3.2 Groupings for Cash Position and Liquidity Forecast......................................................73.2.1 Define Cash Management Account Name............................................................93.2.2 Define Groupings and Maintain Headers..............................................................93.2.3 Maintain Structure...............................................................................................103.2.4 Define Levels in payment requests.....................................................................11

3.3 Manual Planning..........................................................................................................113.3.1 Define Number Ranges: Cash Management (Payment Advices)........................11

3.4 Production Startup.......................................................................................................123.4.1 Prepare Production Startup and Data Setup.......................................................12

3.5 Cash Concentration.....................................................................................................133.5.1 Define Intermediate Account, Clearing Accounts, and Amounts.........................133.5.2 Define Payment Methods for Payment Requests................................................15

3.6 Payment Run...............................................................................................................153.6.1 Define Clearing Accts for Receiving Bank for Acct. Transfer..............................153.6.2 Define Global Settings........................................................................................163.6.3 Enter Origin Indicators........................................................................................173.6.4 Define Account Determination.............................................................................18

4 Creating/Changing Master Data.........................................................................................194.1 Master Data: Planning Levels in G/L Accounts............................................................19

© SAP AG Page 4 of 21

Page 5: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Cash Management: Configuration Guide1 PurposeThis configuration guide provides the information you need to set up the configuration of this building block manually.If you do not want to configure manually and prefer an automated installation process using the SAP Best Practices Installation Assistant and other tools, refer to the SAP Best Practices Quick Guide.

2 Preparation

2.1 PrerequisitesBefore you start installing this scenario, you must install prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for SAP Best Practices Baseline Package .

Before you begin installing building block 160 Cash Management, ensure that all the required settings have been made. This applies in particular to the basic settings for the company code and the accounts in the chart of accounts being used, PUCC.

3 Configuration3.1 Basic Settings

3.1.1 Default Value Date

UseIn this step, you specify whether the system is to propose the current date as the default value date when you enter line items. You make this setting for the company codes in which you wish to implement Cash Management.

PrerequisitesThe company codes have been created in which the functions for cash management and forecast are activated.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Basic Settings Define Value Date Default

Menu IMG SAP Financial Supply Chain Management Gestión de caja y liquidezGestión de cajaParametrizaciones básicas Definir propuesta de fecha valor

Transaction Code SPRO

© SAP AG Page 5 of 21

Page 6: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

2. On the Change View “Company Code: Default Value Date”: Overview screen, make the following entries:

Field Name Description User Actions and Values

Note

CoCd Company Code 1000 Select this line

Propose Value Date

<space>

3. Save your entries.

ResultThe current date is not proposed as the default value date.

3.1.2 Planning Levels

UseIn this step, you specify the G/L-account and sub ledger-account relevant planning levels and assign the planning level to the cash position or liquidity forecast by using the source symbol.Typical financial transactions in Cash Management are displayed using planning levels, which explain the opening and closing balances.

Cash Management can also be used in conjunction with preliminary logistical processes from Materials Management or Sales and Distribution. This enables the liquidity planning activities that affect liquidity to be displayed before the activity is posted with the vendor invoice to FI (when the purchase requisition or order is submitted, for example). For that planning levels are to be defined separately for logistics area.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Master Data G/L Accounts Define Planning Levels

Menú IMG SAP Financial Supply Chain Management Gestión de caja y liquidezGestión de caja Datos MaestrosCuentas de mayor Definir niveles de tesorería

Transaction Code SPRO

2. On the Change View “Planning levels”: Overview screen, make the following entries:

Planning Levels for G/L Accounts

Level SC(+/- sign control)

Source Short text Planning level long text

AB BNK Advice, c. Payment Advice (Confirmed)

© SAP AG Page 6 of 21

Page 7: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Level SC(+/- sign control)

Source Short text Planning level long text

AU BNK Advice, uc Payment Advice (Unconfirmed)

B1 BNK Out. Check Outgoing Checks

B2 BNK Dom trans Outgoing Transfer, Domestic

B3 BNK Oth.Debits Other Debits

B4 BNK Oth.Credit Other Credits

B5 BNK Out.Transf Outgoing transfer, domestic

B6 BNK Liability Own-Accepted Liabilities

B7 BNK Cl. Bill Cl. Acct for Bill Payment

B8 BNK Inc checks Incoming Checks

B9 BNK Cash rec Customer Cash Receipt

CB BNK Comm.paper Commercial Paper - Bank

CL BNK Concentrn Cash Concentration

DB BNK TR Forex Bank Foreign Exchange

DE BNK Loans Loan Revenue

F0 BNK FI Banks Posting to Bank Account

IB BNK Int. Deriv Interest Derivatives Bank

KB BNK Dep.at not Deposit at Notice

LB BNK Loans Bank Loans

M1 MMF Purch.Req. Purchase Requisition

M2 MMF Pur. Order Purchase Order

M3 MMF SchedAgree Scheduling Agreement

ME BNK Rents Rent Receipts

OB BNK TR Bk Crcy TR Currency Option, Bank

RL REM Rent Res. Rent Result

RR REM Rents rcvb Rents Receivable

S1 SDF Order Sales Orders

TA BNK Investment Deposit/Loan Mgmt: Invest.

TB BNK Deps/loans Time Deposits: Banks

TD BNK F-T Dep. Fixed-Term Deposit Management

TK BNK Borrowing Deposit/Loan Mgmt: Borrow

WB BNK Securities Bank Securities

WP BNK Sec rev Security Revenue

YP BNK Paym.Req. Payment Request

ZB BNK All fields All Fields of Bank Records© SAP AG Page 7 of 21

Page 8: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

3. Save your entries.

3.2 Groupings for Cash Position and Liquidity Forecast

UseThe cash position gives you an overview of daily cash inflow and outflow. As the bank accounts are grouped according to their temporal proximity to the date of the cash flow, you can plan short-term liquidity.You can use the liquidity forecast to identify the medium-term cash inflows and outflows generated by the posted debit-side and credit-side invoices.

In the next steps, you make settings that affect the way the cash position is displayed.You define the groups and specify the main headings and line headings. You also define the grouping structures that group together particular bank and/or sub ledger accounts in the cash position or the liquidity forecast display.

The bank account groupings contain the G/L account numbers of the bank accounts. These settings are dependent on the company’s house banks and must therefore be adjusted to suit the company.

The following groupings are defined:Total DisplayThe YTOTAL grouping includes ALL G/L- and vendor/customer accounts.

Customer/Vendor and Clearing AccountsThe YCUST-VEND grouping includes all customer and vendor accounts. This grouping provides an overview of all incoming and outgoing payments.In addition to the sub ledger accounts, the following bank subaccounts are included in the analysis:

Bill of Exchange Contingent Liabilities (WECHSELDIS) Customer Incoming Payments (VKGELDEING)

The YCUST-VEND grouping selects all levels except the level FK - Advance Payments (Offsetting Entry).

Bank AccountsThe YBANKS-STAT grouping includes all the house banks’ main bank accounts (local currency and foreign currency). This grouping provides an overview of the actual bank account balances.Bank subaccounts are not considered in the grouping.

Available Bank AccountsThe YBANKS grouping displays the house bank accounts. It provides an overview of the bank account balances, in which all the accounts for one bank are grouped together under one

© SAP AG Page 8 of 21

Page 9: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

summarization term. So this grouping includes all relevant accounts for identifying the cash positions.Main and subaccounts are considered. The following accounts are not considered:

++++07 Bill of Exchange Contingent Liabilities ++++09 Customer Incoming Payments ++++13 Fixed Term Deposits

A customer pays a sum of 10,000.00 COP. The incoming payment is posted in the bank statement as follows: 10,000 from bank account to “Customer Incoming Payments” subaccount. If you then summarize the balances from the bank account and bank subaccount, the incoming payment is not displayed in the status analysis.

Groupings per house bankThere is an individual grouping for each house bank, which provides an overview of the balances of all the bank accounts that are kept for the particular house bank. Accounts do not have to be summarized per bank in this case, which means that the system generates a row for each account in the status analysis.The following groupings are set up:1. YBANK-CO2. YBANK-CI

Grouping for Cash ConcentrationA separate YCASHCONC grouping for cash concentration comprises all the main bank accounts that are managed in a local currency and that are to be included in the cash concentration process. In addition to the bank accounts, the bank subaccounts managed as treasury clearing accounts are also relevant for cash concentration. The bank subaccount balances are cumulated with the bank account balances in cash concentration.Cash concentration does not take place between bank accounts with different currencies.The following levels are selected during the cash concentration process: Confirmed payment advices (AB) Payment advices that are created when the concentration proposal is created (CL) Interim postings; in particular interim postings to the TR clearing account that are generated in

cash concentration (B5) Postings to bank accounts as well as incoming and outgoing payments to sub ledger accounts

(F+)

PrerequisitesThe chart of accounts 0010 has been set up with the relevant bank and bank subaccounts. Other prerequisites are listed for the individual activities.

© SAP AG Page 9 of 21

Page 10: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

3.2.1 Define Cash Management Account Name

UseIn this step, you assign a mnemonic name as the cash management account name to each bank account and bank clearing account. This mnemonic name is used with all functions and reports in Cash Management instead of the account number.The name is unique within a company code.

PrerequisitesMake sure that the bank accounts are defined in the chart of accounts and the company code. In the case of a genuine bank account, you have to define a bank ID and an account ID, as well as defined the external bank account number.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Structuring Define Cash Management Account Name

Menú IMG SAP Financial Supply Chain Management Gestión de caja y liquidezGestión de caja EstructuraciónDefinir código nemotécnico de cuenta

Transaction Code SPRO

2. In the Determine Work Area: Entry dialog box, enter Company Code 1000 and choose Continue (Enter).

3. On the Change View “Cash Management: Groupings and Their Headers”: Overview screen, choose New Entries.

4. On the New Entries: Overview of Added Entries” screen, make the following entries:

CM acct G/L acct Bank Account CMF Description

BNK1ACCT1 113000 00000000001 Concentration Account - Banamex

BNK2ACCT1 113020 00000000001 Controlled Disbursement Acct - BankBoston

BNK3ACCT1 113030 Payment Account - Santander

5. Save your entries.

3.2.2 Define Groupings and Maintain Headers

UseIn the next steps, you make settings that affect the way the cash position is displayed.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Structuring Groupings

© SAP AG Page 10 of 21

Page 11: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Define Groupings and Maintain Headers

Menú IMG SAP Financial Supply Chain Management Gestión de caja y liquidezGestión de caja Estructuración Clasificaciones Definir clasificaciones y actualizar títulos

Transaction Code SPRO

2. On the Change View “Cash Management: Groupings and Their Headers”: Overview screen, choose New Entries.

3. On the New Entries: Overview of Added Entries” screen, make the following entries:

Field Name Description User Actions and Values Note

Grouping YBANKS

Heading Bank Accounts - including bank cl. accounts

Line Heading Bank Accounts

4. Save your entries.

3.2.3 Maintain Structure

Use1. Access the next activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Structuring Groupings Maintain Structure

Menú IMG SAP Financial Supply Chain Management Gestión de caja y liquidezGestión de caja Estructuración Clasificaciones Actualizar estructura

Transaction Code SPRO

2. On the Change View “Cash Management: Grouping Structure”: Overview screen, choose New Entries (F5).

3. On the New Entries: Overview of Added Entries” screen, make the following entries:

Grouping T Selection CoCd

ChAc Exclude

Sum. Term Summ. Acct SCOCD

YBANKS E ++ **

YBANKS G 000011300+ 0010 BANCO01

YBANKS G 000011302+ 0010 BANCO02

YBANKS G 000011303+ 0010 BANCO03

© SAP AG Page 11 of 21

Page 12: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

4. Save your entries.

3.2.4 Define Levels in payment requests

Use5. Access the next activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Structuring Define levels in payment requests

Menú IMG SAP Financial Supply Chain Management Gestión de caja y liquidezGestión de caja EstructuraciónDefinir niveles en solicitudes de pago

Transaction Code SPRO

6. On the Change View “Payment Request Levels”: Overview screen, choose New Entries (F5).

7. On the New Entries: Overview of Added Entries” screen, make the following entries:

Planning Level

Country Key Planning level

Payment Method

F0 MX YP

8. Save your entries.

3.3 Manual Planning

UseManual planning involves manually creating payment advices or planned items. Different planning types are defined in order to make a distinction between payment advices and planned items. A separate number range is also required.

PrerequisitesOther prerequisites are listed for the individual activities.

3.3.1 Define Number Ranges: Cash Management (Payment Advices)

UseA separate number range is required for posting plan line items.

PrerequisitesThe company code has to be created.

Procedure1. Access the activity using the following navigation option:

© SAP AG Page 12 of 21

Page 13: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Structuring Manual Planning Define Number Ranges

Menú IMG SAP Financial Supply Chain ManagementGestión de caja y liquidezGestión de cajaEstructuraciónTesorería manualDefinir rangos de números

Transaction Code OT20

2. On the Cash Management and Forecast Number Ranges screen enter 1000 in the Company Code field.

3. Choose the Change Intervals pushbutton.

4. On the Maintain Number Range Intervals screen choose the Insert interval button.

5. In the Insert Interval dialog box make the following entries:

Field name Short Text User actions and values Note

No Number range number

01

From number Number Range Number

0000000001

To number 0999999999

Ext. Internal (‘ ’) or External (‘X’) Number Range Flag

<space>

6. Choose Insert (Enter).7. Choose Save.8. Confirm the dialog box Transport number range intervals with Continue (Enter).

3.4 Production Startup

UseMost of the Cash Management settings apply to all company codes. In practice, however, it may often be the case that Cash Management is only to be used for certain company codes. To run Cash Management with a minimum of resources and to prevent legacy data when Cash Management is later used, you can activate Cash Management for specific company codes.

PrerequisitesCash Management must have been configured accordingly.

3.4.1 Prepare Production Startup and Data Setup

UseThis function enables you to post transactions to Cash Management once you have completed the configuration process.

© SAP AG Page 13 of 21

Page 14: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Accounting (New) Financial Accounting Global Settings (New) Global Parameters for Company Code Enter Global Parameters

Menú IMG Gestión financiera(nuevo) Parametrizaciones básicas de gestión financiera(nuevo) Parámetros globales para la sociedadVerificar y completar parámetros globales

Transaction Code SPRO

2. On the Change View “Company Code Global Data”: Overview screen, select company code 1000 and choose “Details” (F2).

3. On the Change View “Company Code Global Data”: Details screen, make the following entries:

Field name Description User actions and values Note

Cash Management Activated

X

4. Save your entries.

ResultCash Management is activated when you carry out this step. Cash Management-relevant data is now updated when any transactions are carried out and is available for evaluation.

3.5 Cash Concentration

UseYou can use cash concentration to clear liquidity gaps or deficits that arise in day-to-day payments as a result of incoming payments from customers or outgoing payments to vendors across different house banks. This ensures that each house bank account has enough liquidity each day and that any liquidity gaps are collected at a house bank, which enables you to optimize the use of liquidity.In the following steps, you make the cash concentration settings.

PrerequisitesThe basic settings and the cash position or liquidity forecast settings have been made.

3.5.1 Define Intermediate Account, Clearing Accounts, and Amounts

UseIn this step, you specify for each bank account the conditions that have to be met when you carry out the cash concentration process.

© SAP AG Page 14 of 21

Page 15: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

PrerequisitesOther prerequisites are listed for the individual steps

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Business Transactions Cash Concentration Define Intermediate Account, Clearing Accounts, and Amounts

Menú IMG SAP Financial Supply Chain ManagementGestión de caja y liquidezGestión de cajaOperaciones contablesClearing de cuentasEspecificar cuenta de vía de pago, cuentas de compensación e importes

Transaction Code SPRO

2. On the Change View “Concentration: Interim Account and Amount Stipulations” screen, make the following entries and save:

Field name Description User actions and values Note

Company Code 1000

Account Account 113000

Company Code Intermediate account: Company Code

<space> The company code of the bank account

Account Intermediate account: account

<space>

Planned Balance 1000.00

Deficit Tolerance 0.00

Planning Minimum 1000.00

Minimum Balance 1000.00

Excess Tolerance 1000.00

Field name Description User actions and values Note

Company Code 1000

Account Account 113020

Company Code Intermediate account: Company Code

<space> The company code of the bank account

Account Intermediate account: account

<space>

Planned Balance 1000.00

Deficit Tolerance 0.00

Planning Minimum 1000.00

© SAP AG Page 15 of 21

Page 16: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Field name Description User actions and values Note

Minimum Amount 1000.00

Excess Tolerance 1000.00

3.5.2 Define Payment Methods for Payment Requests

UseHere you can specify the payment methods for creating payment requests. The currency field is optional. If no currency is entered, the entry is valid for all currencies.This customizing is relevant if several payment methods will be used because of one cash concentration run. This will be necessary in case of cross country transfers.Since the current scenario is focusing on domestic transfers (payment method T/C will only be used) this is not relevant and won’t be set up.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Business Transactions Cash Concentration Define Payment Methods for Payment Requests

Menú IMG SAP Financial Supply Chain ManagementGestión de caja y liquidezGestión de cajaOperaciones contablesClearing de cuentasEspecificar vías de pago para órdenes de pago

Transaction Code SPRO

2. On the Change View “Cash Transfer: Payment Method Determination Payment Reque” screen, choose New Entries (F5).

3. On the New Entries: Overview of Added Entries screen, make the following entries:

Pay. BA

House Bk

Acct. ID Rec. BA House Bk

Currency IP Pmt Method

1000 BAN01 CTA01 MXN T

1000 BAN02 CTA01 MXN T

4. Save your entries.

3.6 Payment Run3.6.1 Define Clearing Accts for Receiving Bank for Acct.

Transfer

UseIn this activity you define the offsetting accounts for the receiving bank accounts for bank account transfers (payments between house bank accounts) which should be posted to when payment is made.The entries are necessary when payment requests are created for cash management payment advice notes that result from cash concentration, for example. The offsetting accounts for the © SAP AG Page 16 of 21

Page 17: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

paying house bank are determined by the payment program specifications and the payment methods used. The offsetting accounts for the receiving house bank cannot be determined from these specifications, however, but can be defined in this section.

PrerequisitesThe Customizing for the payment run F110 delivered by building block 102 has to be uploaded.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Accounting (New) → Bank Accounting → Business Transactions → Payment Transactions → Payment Request → Define Clearing Accts for Receiving Bank for Acct. Transfer

Menú IMG Gestión financiera (nuevo) →Contabilidad bancaria→ Operaciones contable → Pagos→Orden de pago → Definir cuentas de compensación p.banco receptor en transf.cta

Transaction Code SPRO

2. On the Change View “Acct Transfer: Determine Receiving Bank's Clearing Account" screen, choose New Entries (F5).

3. On the New Entries: Overview of Added Entries screen, make the following entries:

4. Save your entries.

3.6.2 Define Global Settings

UseIn this activity you define the account types for which payments should be made for the payment program for payment requests.You can configure the payment program to settle payment requests for customers, vendors and bank accounts (G/L accounts).You also specify whether the payment data should be distributed to other systems using ALE. It only makes sense to do so if the general ledger accounting is in a central system and if the payment transactions are to be carried out in the central system.Due to the problem documented in note 507601, the default settings will be enlarged with the interval for customers and vendors.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Accounting (New) → Bank Accounting → Business Transactions → Payment Transactions → Payment Handling → Define Global Settings

Menú IMG Gestión financiera (nuevo) →Contabilidad bancaria→

© SAP AG Page 17 of 21

CoCd House bk

Country Pmt Method

Currency Account ID

Clrg acct

1000 BAN01 MX T MXN CTA01 0000113000

1000 BAN02 MX T MXN CTA01 0000113020

Page 18: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Operaciones contable → Pagos→Gestión de pago → Definir parametrizaciones globales

Transaction Code SPRO

2. On the Change View “Global Settings: Payment Program for Payment Requests": D screen, make the following entries:

Field name Description User actions and values Note

Origin Indicator: Selection by Origin Indicator

Vendor accounts Indicator: Selection by Vendor Account

Customer accounts

X Indicator: Selection by Customer Account

G/L accounts X Indicator: Selection by G/L Account

Created on Indicator: Selection by Date of Entry

ALE active ALE Distribution Active

3. Save your entries.

3.6.3 Enter Origin Indicators

UseIn this activity, you enter the settings for the origin indicator. In so doing, you specify (per origin) whether, for payment transactions based on payment requests: The payment program should check available amounts The account determination of the application is used, or that of the payment program Existing attributes of an origin are to be used for combining payment requests from different

origins

PrerequisitesThe origins, from which payment requests can be combined, have to be assigned to each other. You do this in Customizing for Bank Accounting in the activity Assign Origin to Combination of Payments.

Procedure1. Access the activity using the following navigation option:

IMG Menu Financial Accounting (New) → Bank Accounting → Business Transactions → Payment Transactions → Payment Handling →

© SAP AG Page 18 of 21

Page 19: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

Enter Origin Indicators

Menú IMG Gestión financiera (nuevo) →Contabilidad bancaria→Operaciones contable → Pagos→Gestión de pago → Parametrizar indicador de origen

Transaction Code SPRO

2. On the Change View: “Origin settings”: Overview screen, make the following entries:

Field name Description User actions and values Note

Origin TR-CM-BT Origin indicator

Available amts X Available amounts not active

Account determ. X Use account from application

Grouping

No exchange rate differences

Do not post any exchange rate differences

3. Save your entries.

3.6.4 Define Account Determination

UseIn this activity you can define the bank sub-accounts to be posted to in the general ledger for payment transactions with bank accounts. The accounts are specified by house bank account, payment method and currency. If a currency is not specified, the account applies to all currencies.This account determination is only used when payment transactions are made between bank accounts. If the bank sub-account is directly specified in the payment request, this entry overrides the account determination.Because the bank sub-account is always specified for transactions in Treasury Management, this table must be maintained mainly for the use of cash management and forecast (bank account transfers, cash concentration).

PrerequisitesThe bank sub-accounts must be created for the company code and be fully maintained.

Tables T042I (configuration of F110 payment programs) and T042Y (configuration of F111 payment programs) must be consistent. The consistency of the entire table is checked; not only at company-code level. See SAP Note 481197.

Procedure1. Access the activity using the following navigation option:

© SAP AG Page 19 of 21

Page 20: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

IMG Menu Financial Accounting (New) → Bank Accounting → Business Transactions → Payment Transactions → Payment Handling → Bank clearing Account Determination → Define Account Determination

Menú IMG Gestión financiera (nuevo) →Contabilidad bancaria→Operaciones contable → Pagos→Gestión de pago → Determinación cuentas: Cuenta bancaria compensación→ Definir determinación de cuentas

Transaction Code SPRO

2. In the Determine Work Area: Entry dialog box, enter 1000 as the Paying company code and choose Continue (Enter).

3. On the Change View “Account determination for G/L Account Payments”: Overview screen, select “New Entries” (F5).

4. On the New Entries: Overview of Added Entries screen, make the following entries, and then choose Save.

House Bk PM Crcy Acct ID Bank subacct

BAN01 T MXN CTA01 0000113000

BAN02 T MXN CTA01 0000113020

4 Creating/Changing Master Data

4.1 Master Data: Planning Levels in G/L Accounts

UseOnly the G/L accounts are used in the Cash Management building block. The planning level is to be assigned to the bank master data accounts.

This step is added to complete the documentation of settings required for cash management. The assignments are already done with the 103 External Financial Accounting building blocks. If the building block 103 is already activated in your client you do not need to execute the following steps.

Procedure1. Access the activity using the following navigation option:

SAP Menu Accounting Financial Accounting General Ledger Master Records G/L Accounts Individual Processing Centrally

Menú SAP FinanzasGestión financieraLibro mayorDatos maestros Cuentas de mayorTratamiento individual Central

Transaction Code FS00

2. On the Edit G/L Account Centrally screen, enter G/L Account (see table below) and company code 1000.

3. Choose Change.4. On the Create/Bank/Interest tab page, add the planning level to the following accounts:

© SAP AG Page 20 of 21

Page 21: Liquidity & Cash

SAP Best Practices Cash Management: Configuration Guide

G/L Account No.Name of Account Planning Level

113000 Concentration Account - Banamex F0

113020 Controlled Disbursement Acct - BankBoston F0

© SAP AG Page 21 of 21