160 BB Config Guide EN MX

EHP4 for SAP ERP 6.0September 2010English

Cash Management (160)Building Block Configuration Guide

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Cash Management (160): Configuration Guide

Copyright

© 2010 SAP AG. All rights reserved.

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

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

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

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

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

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

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

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

© SAP AG of 44


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

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

© SAP AG of 44


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.Cross-references to other documentation.

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

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

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

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

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

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

© SAP AG of 44


Content1 Purpose.........................................................52 Preparation.....................................................52.1 Prerequisites.................................................5

3 Configuration...................................................53.1 Basic Settings..............................................53.1.1 Default Value Date........................................53.1.2 Define Source Symbols.....................................63.1.3 Planning Groups...........................................73.1.4 Planning Levels...........................................9

3.2 Groupings for Cash Position and Liquidity Forecast.........113.2.1 Define Cash Management Account Name......................133.2.2 Define Groupings and Maintain Headers....................153.2.3 Maintain Structure.......................................163.2.4 Define Levels in Payment Requests........................20

3.3 Manual Planning............................................213.3.1 Define Number Ranges: Cash Management (Payment Advices)..223.3.2 Planning Types...........................................22

3.4 Production Startup.........................................233.4.1 Prepare Production Startup and Data Setup................25

3.5 Cash Concentration.........................................253.5.1 Define Intermediate Account, Clearing Accounts, and Amounts

263.5.2 Define Payment Methods for Payment Requests..............27

3.6 Payment Run................................................273.6.1 Define Clearing Accounts for Receiving Bank for Account Transfer.......................................................273.6.2 Define Global Settings...................................283.6.3 Enter Origin Indicators..................................293.6.4 Define Account Determination.............................30

3.7 Creating/Changing Master Data..............................313.7.1 Master Data: Planning Levels in G/L Accounts.............31

© SAP AG of 44


Cash Management: Configuration Guide

1 PurposeThis configuration guide provides the information you need to set up the configuration of this building block manually.If you 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 building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_DE.xls; the placeholder [xx] depends on the SAP Best Practices version you use, e.g. BL refers to the SAP Best Practices Baseline Package: Prerequisites_Matrix_BL_EN_DE.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\BBLibrary\Documentation\.Before you begin installing building block 160 Cash Management, ensurethat 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, YIKR.

3 Configuration

3.1 Basic Settings3.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. Youmake this setting for the company codes in which you wish to implement Cash Management.

Prerequisites

© SAP AG of 44


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

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

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

Transaction Code SPRO

© SAP AG of 44


2. On the Change View “Company Code: Default Value Date”: Overview screen, make the following entries:Field Name Description User Actions and

ValuesComment

CoCd Company Code 1000 Select this linePropose Value Date

<space>

3. Save your entries.

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

3.1.2 Define Source Symbols

UseIn this step, you define source symbols and assign them to either theliquidity forecast or the cash position. The source symbol groups the planning levels according to the sourcesthat provide them with data.

Prerequisite Source Symbols are already created with standard SAP ERP. The following list provides all source symbols which are reused in SAP Best Practices without any change.

Source Cash Pos. Description Short TextBNK X Bank Accounting Bank acctgMMF Materials Management MMPSK Subledger Accounting Sub. AcctgREM Real Estate Management RealEstateSDF Sales and Distribution Sales


IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Basic Settings Define Source Symbols

© SAP AG of 44



2. On the Change View “Source Symbols for Cash Management”: Overview screen,make the following entries:

Source Symbol

Allocation forCash Position

Description Short Text

No further entries required.

3. Save your entries if additional source symbols are added.

3.1.3 Planning Groups

UseIn this step, you define planning groups for customers and vendors. Aplanning group represents particular characteristics, behaviors, or risks of a customer or vendor group. It enables you to break down incoming and outgoing payments according to the probability of the cash inflow or outflow, the amount, and the type of business relationship.

PrerequisitesYou assign customers and vendors to a planning group by making an entry in the master record.


IMG Menu Financial Supply Chain Management Cash and Liquidity Management Cash Management Master Data Subledger Accounts Define Planning Groups


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

Group(Plan.grp)

Level

ScreenControl(SCn)

DaCo Short Text Description

A1 F1 X Domestic Domestic payments (A/P)

A2 F1 Foreign Foreign payments (A/P)

A3 F1 V-affil Vendor-affiliated

© SAP AG of 44


Group(Plan.grp)

Level

ScreenControl(SCn)

DaCo Short Text Description

companies

A4 F1 Major ven Major vendors

A5 F1 HR Personnel costs

A6 F1 Taxes Taxes

E1 F1 Receipts Customer receipts (A/R)

E2 F1 Domestic Domestic customers

E3 F1 X Foreign Foreign customers

E4 F1 X C-affil Customer-affiliated companies

E5 F1 X High risk High risk customer

E6 F1 X Major Major customers

E7 F1 Rent (A/R) Rent received

E8 F1 Redemption Loan redemption (A/R)


© SAP AG of 44


3.1.4 Planning Levels

UseIn this step, you specify the G/L-account and subledger-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 usingplanning 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.

PrerequisitePlanning levels are already created with standard SAP ERP. The following list provides all planning levels which are reused in SAP Best Practices without any change.

Level Source Short Text Planning Level long textAB BNK Advice, c. Payment advice (confirmed)AG PSK Agcy bus. Agency businessAU BNK Advice, uc Payment advice (unconfirmed)B1 BNK Out. check Outgoing checksB2 BNK Dom trans Outgoing transfer, domesticB3 BNK For. trans Outgoing transfer, foreignB4 BNK Bank coll. Bank collectionB5 BNK Int posts Other interim postingsB6 BNK Liability Own-accepted liabilitiesB7 BNK Cl. bill Cl. acct for bill paymentB8 BNK Inc checks Incoming checksB9 BNK Cash rec Customer cash receiptCB BNK Comm.paper Commercial paper - bankCL BNK Concentrn Cash concentrationCP PSK Comm.paper Commmercial paper - subledger© SAP AG of 44


DB BNK TR Forex Bank foreign exchangeDE BNK Loans Loan revenueDI PSK Planned General planningDP PSK TR Forex Subledger forexF0 BNK FI Banks Posting to bank accountF1 PSK FI C/V Posting of purchasing & salesFF PSK FI DP req Down payment requestFK PSK FI DP req Advance pymts (offsettg entry)FR PSK FRA FRA PersonnelFW PSK FI bill FI bill of exchangeIB BNK Int. Deriv Interest Derivatives BankIP PSK Int. Deriv Interest Derivatives PeopleKB BNK Dep.at not Deposit at noticeKP PSK Dep.at not Deposits at notice - subledgerLB BNK Loans Bank loansLP PSK Loans Personal loansM1 MMF Purch.Req. Purchase requisitionM2 MMF Pur. Order Purchase orderM3 MMF SchedAgree Scheduling agreementME BNK Rents Rent receivedMP PSK Noted itms Planning - Noted itemsOB BNK TR Bk Crcy TR currency option, bankOP PSK TR SL Crcy TR currency option, subledgerRE PSK RealEstate Real EstateRL REM Rent Res. Rent ResultRR REM Rents rcvb Rents ReceivableS1 SDF Order Sales OrdersTA BNK Investment Deposit/loan mgmt: investTB BNK Deps/loans Time deposits: banksTD BNK F-T Dep. Fixed-term deposit managementTK BNK Borrowing Deposit/loan mgmt: borrowTP PSK Deps/loans Time deposits: subledgerWB BNK Securities Bank securitiesWP BNK Sec rev Security revenueXA PSK Block ID A Blocked for payment

© SAP AG of 44


XR PSK Block ID R Invoice verificationXX PSK Block ID X Block indicator XZB BNK All fields All fields of bank recordsZP PSK All fields All fields, subledger records


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


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

Level SC(+/- Sign Control)

Source Short Text Planning Level Long Text

YP BNK Paym.Req. Payment Request


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 temporalproximity 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

© SAP AG of 44


particular bank and/or subledger accounts in the cash position or theliquidity 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 suitthe 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 subledger accounts, the following bank subaccountsare 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 Accounts

The 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 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 EUR. The incoming paymentis posted in the bank statement as follows: 10,000 from bank

© SAP AG of 44


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-DB2. YBANK-DRGrouping 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 subledger accounts (F+)

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

3.2.1 Define Cash Management Account Name

Use

© SAP AG of 44


In 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 accountsand the company code. In the case of a genuine bank account, you haveto define a bank ID and an account ID, as well as have 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


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

3. On the Change View “Cash Management: Account Names”: 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

DB-EUR-BNK 280000 1133698 DEUBA EUR account

DB-EUR-CHI 280008 DEUBA incoming checks

DB-EUR-CHO 280001 DEUBA outgoing checks

DB-EUR-DEB 280004 DEUBA bank collection

DB-EUR-DIS 280007 DEUBA BoE contingent liability

DB-EUR-INC 280009 DEUBA cust. incoming payment

DB-EUR-OTH 280005 DEUBA other interim posting

DB-EUR-PRM 280006 DEUBA promissory BoE liability

DB-EUR-TRD 280002 DEUBA bank transfer domestic

© SAP AG of 44


CM Acct G/L Acct Bank Account

CMF Description

DB-EUR-TRF 280003 DEUBA bank transfer foreign

DB-USD-BNK 280050 5689500 DEUBA USD account

DB-USD-CHI 280058 DEUBA incoming checks

DB-USD-CHO 280051 DEUBA outgoing checks

DB-USD-DEB 280054 DEUBA bank collection

DB-USD-DIS 280057 DEUBA BoE contingent liability

DB-USD-INC 280059 DEUBA cust. incoming payment

DB-USD-OTH 280055 DEUBA other interim posting

DB-USD-PRM 280056 DEUBA promissory BoE liability

DB-USD-TRD 280052 DEUBA bank transfer domestic

DB-USD-TRF 280053 DEUBA bank transfer foreign

DR-EUR-BNK 281000 2580061 DREBA EUR account

DR-EUR-CHI 281008 DREBA incoming checks

DR-EUR-CHO 281001 DREBA outgoing checks

DR-EUR-DEB 281004 DREBA bank collection

DR-EUR-DIS 281007 DREBA BoE contingent liability

DR-EUR-INC 281009 DREBA cust. incoming payment

DR-EUR-OTH 281005 DREBA other interim posting

DR-EUR-PRM 281006 DREBA promissory BoE liability

DR-EUR-TRD 281002 DREBA bank transfer domestic

DR-EUR-TRF 281003 DREBA bank transfer foreign


© SAP AG of 44


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 Define Groupings and Maintain Headers


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

3. On the New Entries: Overview of Added Entries” screen, make the following entries:Field Name Description User Actions and

ValuesComment

Grouping YTOTAL

Heading Total Display - bank accounts and subledger accounts

Line Heading Total

Field Name Description User Actions and Values

Comment

Grouping YCUST-VEND

Heading Customers/Vendors and clearing accounts

Line Heading Subledger Accts


Comment

Grouping YBANKSHeading Bank Accounts -

including bank cl. accounts

Line Heading Bank Accounts

© SAP AG of 44



Comment

Grouping YBANKS-STHeading Status of all

available bank accounts

Line Heading Bank Accounts


Comment

Grouping YBANK-DBHeading Bank Accounts –

Deutsche BankLine Heading Deutsche Bank


Comment

Grouping YBANK-DR

Heading Bank Accounts - Dresdner Bank

Line Heading Dresdner Bank


Comment

Grouping YCASHCONCHeading Cash ConcentrationLine Heading Cash Concentrtn


Comment

Grouping YALLHeading Total Display -

subledger accountsLine Heading Subledger Accts


© SAP AG of 44


3.2.3 Maintain Structure


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


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

YTOTAL E ++ **

YTOTAL G ++ PERSONS

YTOTAL G ++++++++++

BANKS

Grouping

Ty. Selection CoCd ChAc Exclude

Sum. term Summ.Acct

SCOCD

YCUST-VEND

E ++ **

YCUST-VEND

E FK X

YCUST-VEND

G 0000280007

YIKR WECHSELDIS

YCUST-VEND

G 0000280009

YIKR VKGELDEING

YCUST-VEND

G 0000280057

YIKR WECHSELDIS

YCUST-VEND

G 0000280059

YIKR VKGELDEING

YCUST-VEND

G 0000281007

YIKR WECHSELDIS

YCUST-VEND

G 0000281009

YIKR VKGELDEING

YCUST-VEND

G A+ AUSGABEN

© SAP AG of 44


Grouping

Ty. Selection CoCd ChAc Exclude

Sum. term Summ.Acct

SCOCD

YCUST-VEND

G E+ EINNAHMEN



SCOCD

YBANKS E ++ **

YBANKS G 0000280000

YIKR DEUBA

YBANKS G 0000280001

YIKR DEUBA

YBANKS G 0000280002

YIKR DEUBA

YBANKS G 0000280003

YIKR DEUBA

YBANKS G 0000280004

YIKR DEUBA

YBANKS G 0000280005

YIKR DEUBA

YBANKS G 0000280006

YIKR DEUBA

YBANKS G 0000280007

YIKR DEUBA

YBANKS G 0000280008

YIKR DEUBA

YBANKS G 0000280009

YIKR DEUBA

YBANKS G 0000280010

YIKR DEUBA

YBANKS G 0000280011

YIKR DEUBA

YBANKS G 0000280012

YIKR DEUBA

YBANKS G 0000280013

YIKR DEUBA

YBANKS G 0000280014

YIKR DEUBA

YBANKS G 000028001 YIKR DEUBA

© SAP AG of 44




SCOCD

5

YBANKS G 0000280050

YIKR DEUBA

YBANKS G 0000280051

YIKR DEUBA

YBANKS G 0000280052

YIKR DEUBA

YBANKS G 0000280053

YIKR DEUBA

YBANKS G 0000280054

YIKR DEUBA

YBANKS G 0000280055

YIKR DEUBA

YBANKS G 0000280056

YIKR DEUBA

YBANKS G 0000280057

YIKR DEUBA

YBANKS G 0000280058

YIKR DEUBA

YBANKS G 0000280059

YIKR DEUBA

YBANKS G 0000281000

YIKR DREBA

YBANKS G 0000281001

YIKR DREBA

YBANKS G 0000281002

YIKR DREBA

YBANKS G 0000281003

YIKR DREBA

YBANKS G 0000281004

YIKR DREBA

YBANKS G 0000281005

YIKR DREBA

YBANKS G 0000281006

YIKR DREBA

YBANKS G 0000281007

YIKR DREBA

© SAP AG of 44




SCOCD

YBANKS G 0000281008

YIKR DREBA

YBANKS G 0000281009

YIKR DREBA

YBANKS G 0000281010

YIKR DREBA

YBANKS G 0000281011

YIKR DREBA

YBANKS G 0000281012

YIKR DREBA

YBANKS G 0000281013

YIKR DREBA

YBANKS G 0000281014

YIKR DREBA

YBANKS G 0000281015

YIKR DREBA


Sum. Term

Summ. Acct

SCOCD

YBANKS-ST E ++ **

YBANKS-ST G 0000280000

YIKR DEUBA


YIKR DEUBA


YIKR DREBA


Sum.Term

Summ. Acct

SCOCD

YBANK-DB E ++ **

YBANK-DB G 00002800++

YIKR

YBANK-DB G 0000280007

YIKR X

YBANK-DB G 0000280009

YIKR X

YBANK-DB G 000028001 YIKR X

© SAP AG of 44



Sum.Term

Summ. Acct

SCOCD

3

YBANK-DB G 0000280057

YIKR X

YBANK-DB G 0000280059

YIKR X


Sum.Term

Summ. Acct

SCOCD

YBANK-DR E ++ **

YBANK-DR G 00002810++

YIKR

YBANK-DR G 0000281007

YIKR X

YBANK-DR G 0000281009

YIKR X

YBANK-DR G 0000281013

YIKR X

Grouping T Selection CoCd ChAc Sum. Term Summ. Acct

SCOCD

YCASHCONC E AB **

YCASHCONC E B+ **

YCASHCONC E CL **

YCASHCONC E F+ **

YCASHCONC G 0000280000

YIKR DEUBA


YIKR DEUBA 0000280000









© SAP AG of 44


Grouping T Selection CoCd ChAc Sum. Term Summ. Acct

SCOCD






YIKR DREBA


YIKR DREBA 0000281000













Grouping T Selection

CoCd ChAc Exclude

Sum. Term

Summ.Acct

SCOCD

YALL E ++ **YALL G A1 DomesticYALL G A2 ForeignYALL G A3 V-affilYALL G A4 Major

venYALL G A5 HRYALL G A6 TaxesYALL G E1 ReceiptsYALL G E2 DomesticYALL G E3 ForeignYALL G E4 C-affil

© SAP AG of 44


Grouping T Selection

CoCd ChAc Exclude

Sum. Term

Summ.Acct

SCOCD

YALL G E5 High risk

YALL G E6 MajorYALL G E7 Rent

(A/R)YALL G E8 Redempti

on


3.2.4 Define Levels in Payment Requests

UseIn this step you define separate Cash Management planning levels for payment requests.If the Cash Management update writes the flows to a bank account, youmust define a separate planning level for payment requests. Otherwise, the payment requests are displayed at the same level as the bank statement postings when you call up the cash position.This setting is optional if the Cash Management update writes the flows to a bank clearing account.


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

Transaction Code spro

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

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

Level Cty PM PR Level

F0 YP

4. Save your entry.

© SAP AG of 44


3.3 Manual PlanningUseManual planning involves manually creating payment advices or planneditems. 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.

© SAP AG of 44


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.


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

Transaction Code OT20

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

3. Choose Change Intervals.

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

5. In the Insert Interval dialog box make the following entries:Field Name Short Text User Actions and

ValuesComment

No Number range number

01

From number Number Range Number

0900000000

To number 0999999999Ext. Internal (‘ ’)

or External (‘X’) Number Range Flag

<space>

6. Choose Insert (Enter).

7. Choose Save.8. Confirm the dialogue box Transport number range intervals with Continue

(Enter).

© SAP AG of 44


3.3.2 Planning Types

UseDifferent planning types are used to make a distinction between payment advices and planned items.

PrerequisitesThe number range and the planning level are defined.Planning types are already created with standard SAP ERP. The following list provides all planning types which are reused in SAP Best Practices without any change.Plg.Type Plg.level Archcat. Auto expir. Number mg Planning Type TextAB AB A 01 Confirmed advicesAU AU A 01 Unconfirmed advicesCL CL A X 01 Cash concentrationDE DE A 01 Loan revenueDI DI A 01 General planningME ME A 01 Rent receivedMP MP A 01 Noted itemsTA TA A 01 Funds depositedTD TD A 01 Fixed-term depositsTK TK A 01 Funds borrowedWP WP A 01 Security revenueZB ZB A 01 All bank fieldsZP ZP A 01 All subledger fields


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


© SAP AG of 44


2. On the Change View “Planning Types”: Overview screen, make the followingentries:

Plg Type

Plg level

Arch.cat.

Auto Expir

Number Rng

Planning Type Text

No further entries required

3. Save your entries if additional planning types are added.

3.4 Production StartupUseMost 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.

© SAP AG of 44


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.


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


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

ValuesComment

Cash Management Activated

X


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 ConcentrationUseYou 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 housebanks. This ensures that each house bank account has enough liquidityeach 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.

© SAP AG of 44


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.

PrerequisitesOther prerequisites are listed for the individual steps


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

Transaction Code SPRO2. On the Change View “Concentration: Interim Account and Amount Stipulations”

screen, make the following entries and save:Field Name Description User Actions and

ValuesComment

Company Code 1000Account Account 280000Company Code Intermediate

account: Company Code

<space> The company code of the bank account

Account Intermediate account: account

<space>

Planned Balance 1000Deficit Tolerance

Planning Minimum 1000Minimum Amount 1000Minimum Balance 1000Excess Tolerance 1000

© SAP AG of 44



Comment

Company Code 1000Account Account 281000Company Code Intermediate

account: Company Code

<space> The company code of the bank account

Account Intermediate account: account

<space>

Planned Balance 1000Deficit Tolerance

Planning Minimum 1000 Minimum Amount

Minimum Balance 1000Excess Tolerance 1000

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 caseof cross country transfers.Since the current scenario is focusing on domestic transfers (paymentmethod U will only be used) this is not relevant and won’t be set up.


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


© SAP AG of 44


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 DB GIRO U

1000 DRE GIRO U


3.6 Payment Run3.6.1 Define Clearing Accounts for Receiving Bank

for Account Transfer

UseIn this activity you define the offsetting accounts for the receivingbank accounts for bank account transfers (payments between house bankaccounts) 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 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.


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


© SAP AG of 44


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:

CoCd House bk Country

Pmt Method Currency

Account ID

Clrg acct

1000 DB DE U EUR GIRO 280005

1000 DRE DE U EUR GIRO 281005


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.


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


© SAP AG of 44


2. On the Change View “Global Settings: Payment Program for Payment Requests": D screen, make the following entries:Field Name Description User Actions and

ValuesComment

Origin Indicator: Selection byOrigin Indicator

Vendor accounts Indicator: Selection byVendor Account

Customer accounts X Indicator: Selection byCustomer Account

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

Created on Indicator: Selection byDate of Entry

ALE active ALE DistributionActive


3.6.3 Enter Origin Indicators

UseIn this activity, you enter the settings for the origin indicator. Indoing so, you specify (per origin), for payment transactions based onpayment requests, whether: 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

© SAP AG of 44

sapevent:DOCU_LINK%5CDS:GLOS.3528EA82E8AA5570E10000009B38F983

sapevent:DOCU_LINK%5CDS:GLOS.36FA607340794C15E10000009B38F9B7


This table is cross client. Be cautious with changes. The following settings are delivered by standard SAP ERP. SAP Best Practices does not change these settings. Please check the entries for completeness.

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 one of the following navigation options:IMG Menu Financial Accounting (New) Bank Accounting Business

Transactions Payment Transactions Payment Handling Enter Origin Indicators


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


Comment

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 exchangerate differences


© SAP AG of 44


3.6.4 Define Account Determination

UseIn this activity you can define the bank sub-accounts to be posted toin 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 aremade 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 useof 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.


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


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 SubacctDB U GIRO 280002

© SAP AG of 44


DRE U GIRO 281002

3.7 Creating/Changing Master Data

3.7.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 settingsrequired for cash management. The assignments have already been carried out in the External Financial Accounting (102) building block. If building block 102 is already activated in your client, you do not need to execute the following steps.


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

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:

G/L Account No. Name of Account Planning Level

280000 Deutsche Bank (Domestic) F0280001 Deutsche Bank (Checks Payable) B1280002 Deutsche Bank (Bank Transfer Domestic) B2280003 Deutsche Bank (Bank Transfer Foreign) B3280004 Deutsche Bank (Autom. Debit) B4280005 Deutsche Bank (Other Interim Postings) B5

© SAP AG of 44


280006 Deutsche Bank (Promiss BoE Liabil.) B6280007 Deutsche Bank (BoE Contingent Liabil.) B7280008 Deutsche Bank (Checks Received) B8280009 Deutsche Bank (Cust. Incoming Paymnt) B9280011 Deutsche Bank (Current BoE Payable) B7280012 Deutsche Bank (BoE Collection) B7280013 Deutsche Bank (Fixed-Term Deposits) B9280014 Deutsche Bank (Cash Disbursement) B5280015 Deutsche Bank (Cash Receipt) B5280050 Deutsche Bank - USD Account F0280051 Deutsche Bank - USD (Checks Payable) B1

280052Deutsche Bank - USD (Bank Transfer Domestic) B2

280053Deutsche Bank - USD (Bank Transfer Foreign) B3

280054 Deutsche Bank - USD (Autom. Debit) B4

280055Deutsche Bank - USD (Other Interim Postings) B5

280056Deutsche Bank - USD (Promiss. BoE Liabil.) B6

280057Deutsche Bank - USD (BoE Contingent Liabil.) B7

280058 Deutsche Bank - USD (Checks Received) B8

280059Deutsche Bank - USD (Cust. Incoming Paymnt) B9

281000 Dresdner Bank (Domestic) F0281001 Dresdner Bank (Checks Payable) B1281002 Dresdner Bank (Bank Transfer Domestic) B2281003 Dresdner Bank (Bank Transfer Foreign) B3281004 Dresdner Bank (Autom. Debit) B4281005 Dresdner Bank (Other Interim Postings) B5281006 Dresdner Bank (Promiss. BoE Liabil.) B6281007 Dresdner Bank (BoE Contingent Liabil.) B7281008 Dresdner Bank (Checks Received) B8281009 Dresdner Bank (Cust. Incoming Paymnt) B9281011 Dresdner Bank (Current BoE Payable) B7

© SAP AG of 44


281012 Dresdner Bank (BoE Collection) B7281013 Dresdner Bank (Fixed-Term Deposits) B9281014 Dresdner Bank (Cash Disbursement) B5281015 Dresdner Bank (Cash Receipt) B5288000 Cash Account F0289100 Cash Freight F0

© SAP AG of 44

160 BB Config Guide EN MX

Documents

Transcript of 160 BB Config Guide EN MX