Business Process Proceduressapidp/... · Web viewSAP AG Dietmar-Hopp-Allee 16 69190 Walldorf...

EHP7 for SAP ERP 6.0

February 2014

English

Cash Management (160)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Cash Management (160): BPD

Copyright

© 2014 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

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

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE Page 6 of 8

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

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

Cross-references to other documentation.

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

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

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

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

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

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



Contents

Cash Management........................................................................................................................ 5

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

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

2 Prerequisites.......................................................................................................................... 6

2.1 Master Data..................................................................................................................... 6

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

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

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

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

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

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

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

3 Process Overview Table.......................................................................................................13

4 Process Steps......................................................................................................................15

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

4.2 Archiving the Memo Record..........................................................................................16

4.3 Bank Statement.............................................................................................................17

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

4.3.2 Entering a Manual Bank Statement........................................................................18

4.3.3 Display an Account Statement in Bank Statement Overview (optional).................23

4.3.4 Post processing an Account Statement..................................................................24

4.4 Cash Concentration.......................................................................................................26

4.4.1 Creating a Concentration Proposal........................................................................27

4.4.2 Generation of Payment Requests..........................................................................28

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

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

5 Appendix.............................................................................................................................. 35

5.1 Reversal of Process Steps............................................................................................35

5.2 Used Forms...................................................................................................................35



Cash Management

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

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

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

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

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

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

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

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

This document provides an overview how to use the SAP ERP Cash Management functionality. The scope item includes the following sequence:

Posting of a vendor invoice in local and foreign currency

Posting of a customer invoice in local currency (from a sales order)

Posting of planning items and memo records

Execution of the report showing cash position and the liquidity forecast. All posted documents are displayed on the value date basis.

After posting the manual bank statement, the flow between the planning levels is demonstrated

Due to the actual postings of the bank statement, the memo records are archived automatically (by using a special report).

The function of cash concentration illustrate how to identify the relevant amounts and transfer them from one account to another.

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

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



2 Prerequisites

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

Master Data

Value Selection Comment

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

For master data creation, see Central Master Data (152) scope item

IBAN and payment method "6" are mandatory in customer master data in case of use of EURO SEPA Direct Debit payment method.

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

For master data creation, see Central Master Data (152) scope item

IBAN and payment method "5" are mandatory in vendor master data in case of use of EURO SEPA Credit Transfer payment method.

G/L Accounts

* 280000-281015

Cash Management Planning Level must be assigned to all bank G/L accounts which should be included in the Cash Position Overview

© SAP SE of 8


2.2 Roles

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

PrerequisitesThe business roles have been assigned to the users who perform the process steps described in this document.

Business Role Technical Name Process Step

Employee (Professional User)

SAP_NBPR_EMPLOYEE_S Assignment of this role is necessary for basic functionality.

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

Archiving the Memo Record

Execute Cash Concentration

Display Financial Overview / Cash Position & Liquidity Forecast

Bank Accountant SAP_NBPR_BANKACC_S Import Bank Statement (Electronic Bank Statement)

Entering a Manual Bank Statement

Post process Bank Statement

Accounts Payable Accountant

SAP_NBPR_AP_CLERK_S Create demo data: Posting a Vendor Invoice (in domestic currency)

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

IT Administrator (Professional User)

SAP_NBPR_IT_ADMIN_S Create demo data: Simulate Bank Statement and Open Customer Item for Electronic Bank Statement Processing

Process Bank Statement

SAP_FI_BL_BANK_STATEMENT_EXT Item for Electronic Bank Statement Processing (Bank Statement Monitor)



2.3 Creating Demo Data2.3.1 Posting a Customer Invoice (in Domestic Currency)

UseThe following example describes how to enter a customer invoice.

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

Procedure

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

ExampleField name Description User action and values Comment

Material F126

Customer 100000

Amount in LC 20.000

Currency EUR

Reference DR00001



2.3.2 Posting a Vendor Invoice (in Domestic Currency)

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

PurposeThe company receives a vendor invoice to be paid. The invoice must be posted.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Accounting → Financial Accounting → Accounts Payable → Document Entry → Invoice

Transaction code

FB60



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

Business role Accounts Payable Accountant

(SAP_NBPR_AP_CLERK_S)

Business role menu

Accounts Payable → Posting → Invoices → Enter Vendor Invoice w/o PO Reference



2. On the Enter Vendor invoice screen, choose the Basic data tab.

3. Enter the following data.

Field name Description User action and values Comment

Company code 1000

Vendor <any domestic vendor>

Invoice date Current date

Posting date Current date

Amount 3.000

Currency EUR

Calculate Tax Select

Tax Code V1

GL Account <G/L account number> 680000

Cost center <cost center number> 1101

Amount *



4. Choose the Payment tab.

5. Enter the following data:

Field name Description User action and values

Comment

Payment method

5 5 represents a SEPA credit transfer (payment)

Pmnt Terms

0001 If a cash discount is to be deducted for this payment, consider this when you enter the bank statement.



6. Save your entries.

2.3.3 Posting a Vendor Invoice (in Foreign Currency)

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

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



SAP ECC menu Accounting → Financial Accounting → Accounts Payable → Document Entry → Invoice

Transaction code

FB60




Business role Accounts Payable Accountant

(SAP_NBPR_AP_CLERK_S)

Business role menu

Accounts Payable → Posting → Invoices → Enter Vendor Invoice w/o PO Reference



2. On the Enter Vendor invoice screen, choose the Basic data tab.

3. Make the following entries:


Company code 1000

Vendor <any foreign vendor>

Invoice date Current date


Amount 10.000

Currency USD

Calculate Tax Select

Tax Code V1

GL Account <G/L account number> 680000

Cost center <cost center number> 1101

Amount *



4. Choose the Payment tab.


Field name

Description User action and values

Comment

Payment method

L L is a transfer payment (cross-border)

Pmnt Terms

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


2.3.4 Clearing of Vendor Invoices by the F110-Payment Run

Procedure

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


Run date Current date

Identification Any Identification of the payment run

for example your initials + sequential number (XX01)


Documents entered up to

Current date

Customer items due by

Current date + 1 month Enter date in future

Company code 1000

Payment method

5L SEPA credit transfer (payment) method 5 and transfer payment (cross-border) L

Next p/date Date of next Payment run execution

Current date + 1 month Enter date in future

Vendor vendor used in previous steps

Enter vendors of previous steps



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

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

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

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

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

Example:

G/L account: 280000

Substitute account: 280019



SAP ECC menu System → Services → Reporting

Transaction code SA38




Business role IT Administrator (Professional User)

(SAP_NBPR_IT_ADMIN_S)

Business role menu

IT Administration → Administration → ABAP Workbench → ABAP Reporting



2. On the ABAP: Program Execution screen, enter the following data:


Program RFEBKATX

3. Choose Execute.

4. Enter the following data on the next screen:


Download to PC Tick box

Statement file statement.txt

Line item file lineitem.txt

Company Code 1000

House Bank (ID) DB

Account ID GIRO

Statement Date Today

Invoice Date Today minus 2 days

Posting method Display all posting screens

Customers to be posted to Enter customer of previous steps

Number of open items 1

First Amount ‘any’

All other values can remain unchanged.

5. Choose Execute.

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

7. On the Enter Customer invoice: Add customer item screen, enter the following data (item 1/Invoice 01):


Customer <Customer entered in previous screen>

Company Code 1000

Amount ‘higher amount than first amount’

8. Choose Enter.

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

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


G/L account Substitute account for example 280019

Company Code 1000

Amount ‘*’

Value Date for example <current date>

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



3 Process Overview TableProcess step

External process reference

Business condition

Business role

Transaction code Expected results

Posting of a Planning Memo Record for Recurring Payments

A memo record provides forecast information

Treasurer FF63 Memo record posted

Archiving the memo record

After the Memo record expires it should be archived

Treasurer FF6B

Import Bank Statement (Electronic Bank Statement)

Bank accountant

FF_5 Bank Statement posted

Entering a Manual Bank Statement

Bank accountant

FF67 Clearing the customer invoice and the clearing account

Display an Account Statement in Bank Statement Overview (optional)

Account statements entered or posted

Process Bank Statement

N/A Display of account statements only offered for SAP NetWeaver Business Client via Business Role

Postprocess Bank Statement

Bank accountant

FEBA_BANK_STATEMENT Residual Item settled

Cash concentration

Concentrate all your account balances in one target account

Treasurer FF73

FF.D

F111

Create a concentration proposal.

Generation of payment requests.

Execution of F111 – payment program.



Process step

External process reference

Business condition

Business role

Transaction code Expected results

Financial overview / Cash Position & Liquidity Forecast

Cash Position and Forecast

Treasurer FF7A or FF7B Financial Status updated



4 Process Steps

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

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

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

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

A special planning type YB is provided to show credit limits on house bank account level. This planning type can be selected with grouping YCREDIT. YB is excluded in all other groups.

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


SAP ECC menu

Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Incomings → Memo Record → Create

Transaction code FF63


Business role Treasurer

(SAP_NBPR_TREASURER_S)

Business role menu

Cash Management → Cash Management → Planning → Create Planning Memo Record

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


Company code 1000

Planning Type any planning type <DI>

3. Choose Enter.



Planning Day any date < current day>




Planning Group any planning group < A6>

Amount any amount < 15.000

Currency any currency < EUR>

Assignment any text < Recurring tax>

5. Choose Enter.

6. Choose Copy.


Field name Description User action and values

Comment

Number any number

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

Increment in days/weeks/months

any number

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

for example, 1 in the field for the month

Set to previous Friday/working day instead of skipping

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

8. Choose Enter.


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

4.2 Archiving the Memo Record

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

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

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

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



PrerequisitesThe bank statement is processed.



SAP ECC menu

Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Planning → Memo Record → Change Using List

Transaction code FF6B




Business role menu

Cash Management → Cash Management → Planning → Change Memo Record



Company code 1000

Cash Position select

Liquidity forecast select

3. Choose Execute (F8).

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

4.3 Bank Statement4.3.1 Importing Bank Statement (Electronic Bank Statement)



SAP ECC menu Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Import

Transaction code FF_5


Business role Bank Accountant

(SAP_NBPR_BANKACC_S)

Business role Bank Accounting → Incomings → Import Electronic Bank



menu Statement



Import data Selected

Statement file statement.txt

Line item file lineitem.txt

All other values should remain unchanged.


4.3.2 Entering a Manual Bank Statement

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

PrerequisitesThere is an open customer invoice in the system.

The following transactions are available for bank statement processing:

Transaction Text Details

001+ Cash receipt via interim account

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

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

Posting:

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

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

Posting:

Debit: ‘Check Out’ (Interim Account)

Credit: ‘Bank’

004- Domestic transfer Outgoing Domestic bank transfer in local currency

005- Foreign transfer Outgoing Foreign bank transfer in any currency

006- Other disbursements

Outgoings which do not fit to the other transactions.

007+ Other receipts Incomings which do not fit to the other transactions.

008- Cash payment Any cash outgoing payment

009+ Cash receipt Any cash incoming payment

010+ Collection/direct The cash receipt of the automatic debit was



Transaction Text Details

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

011- Returns collection/direct debit

Automatic debit returned by the customer

012- Bank fee Bank fee

013+ Interest received Interest received for credit on bank account

014- Interest paid Interest paid for debit on bank account

016- Vendor direct debit The vendor executed an automatic debit. The bank account is debited and the open vendor item is settled.



SAP ECC menu

Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Incomings → Manual Bank Statement → Enter





Business role menu Bank Accounting → Incomings → Manual Account Statement

2. When you access the transaction for the first time, the Specifications dialog box displays for you to enter the following data:

Field name DescriptionUser action and values

Comment

Internal Bank Determination

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

Import Advices select

Start Variant YB01

Processing Type

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

Transfer Value select



Field name DescriptionUser action and values

Comment

Date

You can also display this dialog box by choosing Settings Specifications. Check that the correct data is entered.

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


Company Code

1000

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

for example, DB

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

for example, GIRO

Statement Number

Bank statement number

Last bank statement number for the selected house bank/account + 1

(see following note for more information)

For example 1

Statement Date

Date of bank statement

<Today’s date>

Opening Balance

Opening balance

Opening balance = Closing Balance of the previous bank statement

(see following note for more information)

For example 0

Closing Balance

Closing balance

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

for example, 0 + 2000 – 3000 – 4000 = - 5000

The amounts indicated correspond to the following example.



Entering the opening balance causes a check, if the amount matches with previously entered account statements. To determine the ending balance of the last account statement, which might have been entered during previous tests, choose Overview (F8) and - on the following screen – select the line belonging to the bank, to which you want to add another account statement. From the following screen, you can pick the values of the last account statement and the account statement number, which is posted. In this way, the statement number, statement date, and beginning balance are filled automatically.

4. Choose Enter.



Transaction * Process code for cash receipts

for example, 001+

Value Date value date Value date of credit transaction

for example, Today’s date

Amount amount Transaction amount

for example, 20.000

Bank Ref. reference from customer invoice

Enter reference from customer invoice

for example, DR00001

Customer * Customer number

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

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


Transaction * Process code for domestic transfer

for example, 004-

Value Date value date Value date of debit transaction


Amount any amount Transaction amount

for example, 3.000-

Bank Ref. reference from customer invoice

The reference entered here has to be in line with the reference number in the




invoice document header,

for example, DR00002

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

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


Transaction * Process code for bank transfer (debit memo)

for example, 006-




for example, 4000-

Bank Ref. Bank reference

The reference entered here has to be in line with the reference number in the invoice document header.

6. Choose Save and then Post.

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

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

Bank Subaccount / Bank Account

A different step is necessary for clearing the open item against the correct expense account. This is not part of the further scope item.

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

Field name Description User action

and values Comment

Company Code

1000

House Bank

House bank ID

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

for example, DB

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



Field name Description User action

and values Comment

for example, USD

Statement Number

Bank statement number

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

Statement Date

Date of bank statement


Opening Balance

Opening balance

Opening balance = Ending balance of previous statement

for example, 0

Closing Balance

Closing balance

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

for example, 0 - 10000 = -10000

8. Choose Enter.



Transaction * Process code for foreign transfer

for example, 005-




for example, 10000-

10. Choose Save and then Post.

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

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

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

4.3.3 Display an Account Statement in Bank Statement Overview (optional)



UseOnce you posted a manual account statement, you are now able to display this account statement. This is possible on an optional basis in NetWeaver Business Client.

PrerequisitesThe manual account statement has been posted.



SAP ECC menu N/A

Transaction code N/A


Business role Process Bank Statement

(SAP_FI_BL_BANK_STATEMENT_EXT)

Business role menu

Process Bank Statement → Bank Statement → Bank Statement Overview

2. On the Bank Statement Overview screen, you can find under Imported bank statements those statements, which you have already posted.

A green light next to the statement item indicates that the postings have been processed without errors.

A red light next to the statement item indicates that the account statement items could not be posted. You have to reprocess these items.

To do so, you need to select a bank statement in the list of the Imported Bank Statements and navigate to the bank statement processing. This functionality will be described in the next chapter.

3. On the Bank Statement Overview screen, choose under your Imported Bank Statements the bank statement that must be processed and then the button Process Bank Statement.

4.3.4 Post processing an Account Statement

UseAfter the posting of a manual bank statement, it is not absolutely necessary, but possible, that you have to post process an electronic bank statement due to certain cases in which not all statement items could be cleared by the system automatically. This is particularly important if the customer has not paid the total amount, or has quoted the wrong reference. In this particular case, no clearing posting is carried out and, consequently, reprocessing is necessary.

The activities described under Additional Optional Activities can be executed in the system within this Business Process Document only under certain conditions (for example, underpayment or wrong payment reference).



PrerequisitesThe manual account statement is posted.

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


SAP ECC menu Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Postprocess

Transaction code

FEBA_BANK_STATEMENT




Business role menu Bank Accounting → Incomings → Postprocessing Bank Statement

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


Company Code

1000

House Bank House bank for which bank statement is being processed

For example, DB

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

For example, GIRO


4. On the Edit Bank Statement screen, all the statement numbers are displayed (tree display).

A green light next to the statement item indicates that the postings have been processed without errors. Double-click an item to display further information, such as the reference, partner bank, business partner, value date, external transaction, note to payee, and so on.

A red light next to the statement item indicates that the account statement items could not be posted. You have to reprocess these items.

The following steps need only to be done by red light in the upper left area of the screen either in the bank ledger or sub ledger accounting.

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

6. In the case that the transaction amount indicated for the account statement position does not correspond to an open item of a customer in the Assigned field, you can search for open items on tab Assignment that is available on the lower screen area by choosing Read More Items. You may use the data shown in the Note to Payee area as selection criteria such as the customer number, the document number, the posting date, the amount, the reference etc. Choose Start Search in order select the open items according to your selection.

7. If the open items can be identified with your selection criteria and the assigned amount corresponds to the transaction amount of the bank statement, the system displays a green



light in the middle section, the amount in the Open field is 0 and the option Posting possible displays.

8. Post the document and make a note of the document number.

ResultThe posting in the Subledger are carried out. Two green lights in the upper screen section are being displayed. The account statement was successfully post processed.

Additional optional activities

UseThe following examples describe possible post processing scope item that, however, are not necessarily reflected in the flow of this Business Process Document.

Procedure1. On the Edit Bank Statement Item screen, select the statement number with a double-click

you want to post (statement with the red light).

2. In the Assigned field in the middle section of the screen, the system displays the bank statement amount to be cleared. When you pick the relevant document numbers the Assigned field shows the total amount.

3. In terms of an underpayment, check in the middle section of the screen, if the amount for Assigned differs from the Transaction Amount. A red light is displayed next to Open and posting is impossible.

4. On the Edit Bank Statement Item screen double-click the Assigned field in the lower area of the screen.

5. In the Remainder field in the lower area of the screen you can see the difference between Transaction Amount and Assigned.

6. Next to the Remainder field on the right side named Difference Posting Type; choose whether the remainder is a residual item or a partial payment.

7. Check if the assigned amount in the lower area of the screen is automatically corrected equal to the transaction amount, so that you get a green light next to the field Open and the bank statement can be posted.

8. Choose Post (Crtl+S).

9. In terms of another bank statement with wrong reference, stay on the same screen and start again with step 1.

10. In the field for the note to payee in the middle section of the screen two invoices are mentioned but only one bank statement line item is displayed due to an incorrect invoice number in the note to payee. Reasons could be, for example, additional signs like -, ~ or +, missing single digits, additional check digits, or transposed digits.

11. Edit and correct the wrong invoice number in the note to payee to correct it.

12. Choose Scan.

13. Check, if the missing bank statement line item is now displayed in the middle section of the screen and the light next to Open has turned to green.

14. The bank statement can now be posted, click on Post.

ResultThe items are posted which could not be cleared automatically



4.4 Cash Concentration

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

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

4.4.1 Creating a Concentration Proposal

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

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

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



SAP ECC menu

Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Planning → Cash Concentration → Create





Business role menu

Cash Management → Cash Management → Planning → Cash Concentration

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


Company Code

1000

Planned Date

any date for example, Today’s date

Grouping YCASHCONC Selection of accounts for the cash concentration




Account Currency

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

Minimum Balance

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

for example, 1000

Target Account Name

any main bank account assigned to grouping YCASHCONC

Cash Management account name of target account

for example, DB-EUR-BNK

Target Company Code

1000

Value Date any date for example, Today’s date

Expiration Date

any date for example, Today’s date

Planning Type

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

Minimum Amount

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

for example, 1000

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

4. Choose Process Payment Advices.On the Edit Payment Advice for Cash Concentration screen, you can change the amounts available for planning as required.

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

6. Confirm with Yes.The system displays the message Payment advices generated. You can display the newly created payment advices in the cash position to analyze the cash concentration result.

7. To exit the transaction, choose Back.

ResultYou make internal preparations for clearing the bank accounts by executing a concentration proposal and generating the corresponding payment advices.

The next step is to generate payment requests from the payment advices that were created by the cash concentration proposal. The payment requests are regulated by the payment program F111. The DME file is created with the regular reports for DME-file creation.



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

4.4.2 Generation of Payment Requests

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

PrerequisitesPayment advices have been created by the cash concentration proposal.



SAP ECC menu

Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Planning → Generate Payment Request → From Payment Advice Notes

Transaction code FF.D




Business role menu

Cash Management → Cash Management → Planning → Generate payt req. from advices

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


Company Code

1000

Planning Type

CL

Test Run Remove the flag once you have done a simulation run

Payment method

5 Payment method for SEPA credit transfer (payment).

3. Choose Execute.

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



4.4.3 Clearing the Payment Requests by the F111-Payment Run

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

PrerequisitesThe payment requests have been created within the previous step.



SAP ECC menu

Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Planning → Payment Program → Payment Requests

Transaction code

F111




Business role menu

Cash Management → Cash Management → Planning → Automatic Payment of PRequest



Run date any date for example, current date

Identification any identification for example, your initials

3. Choose Parameters.

Field name Description

User action and values

Comment

Posting date

any date for example, current date

Next payment run on

any date in future

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

for example, current date + 1 month

Company code

1000



Payment method

5 SEPA credit transfer (payment)

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

4. Choose Additional Log.


Payment method selection in all cases

select

Line items of the payment documents

select

Due date check select

5. Choose Continue (Enter) and confirm with a second Continue (Enter) the information dialog box.


7. Choose the Status tab.

8. Choose Proposal.

9. Select Start immediately and Create payment medium and choose Enter.

10. By choosing Status, you can see the status of the payment proposal. The payment proposal is generated when the system displays message Payment proposal has been created.

11. Choose proposal log, Proposal. Check the selection of your document.

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

13. Select Start immediately and Create payment medium, and choose Enter.

14. Choose payment log Payments to display the executed payments.

ResultThe payment document and the payment medium have been created.

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

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

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

4.5 Financial Overview / Cash Position & Liquidity Forecast

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



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

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

The following groupings are defined:

Grouping Purpose

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

YTOTAL includes all bank accounts and vendor/customer accounts

YCUST-VEND

includes all customer and vendor accountsprovides an overview of all incoming and outgoing payments

YBANKS-ST includes all the house banks’ main bank accountsprovides an overview of the actual bank account balances

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

YBANK-DB includes all house bank accounts and subaccounts with Deutsche Bank

YBANK-DR includes all house bank accounts and subaccounts with Dresdner Bank

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

YCREDIT Includes all credit memo postings with planning type YB on level of banks’ main bank accounts



SAP ECC menu

Accounting → Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Information System → Reports for Cash Management → Liquidity Analyses → Cash Position

Transaction code FF7A




Business role menu

Cash Management → Cash Management → Reporting → Cash Position

2. On the Cash Management and Forecast: CURRENCY OVERVIEW screen, make the following entries:


Company Code

1000




Cash Position

select Analysis of the bank accounts

Liquidity Forecast

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

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

Display as of

any date for example, today’s date

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

3. Choose Execute.

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

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

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

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

ResultOpen Invoices and memo recordsAll open vendor invoices are visible within the A* planning group.

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

The memo records are visible under the corresponding planning group.

Bank AccountsThe bank accounts are visible under planning level F0.

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

Bank account Description Cash Management account

280000 DB – EUR account DB-EUR_BNK

280050 DB – USD account DB-USD-BNK

281000 DRE – EUR account DR-EUR-BNK

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

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



Bank account

Description Cash Management account

280002 DB bank transfer domestic (EUR account) DB-EUR-TRD

280003 DB bank transfer foreign (EUR account) DB-EUR-TRF

280052 DB bank transfer domestic (USD account) DB-USD-TRD

280053 DB bank transfer foreign (USD account) DB-USD-TRF

281002 DRE bank transfer domestic (EUR account)

DR-EUR-TRD

281003 DRE bank transfer foreign (EUR account) DR-EUR-TRD

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

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

Bank account

Description Cash Management account

280004 DB automatic debit (EUR account) DB-EUR-DEB

280009 DB customer incoming payment (EUR account)

DB-EUR-INC

280054 DB automatic debit (USD account) DB-USD-DEB

280059 DB customer incoming payment (USD account)

DB-USD-INC

281004 DRE automatic debit (EUR account) DR-EUR-DEB

281009 DRE customer incoming payment (EUR account)

DR-EUR-INC



5 Appendix

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

Archiving the Memo Record

Transaction code (SAP GUI)

FF6B

Reversal: Reactivate archived Memo Records


FF6B



Business role menu

Cash Management Cash Management Planning Change Memo Record

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

Creating a Concentration Proposal


FF73

Reversal: Archiving the Memo Record


FF6B



Business role menu

Cash Management Cash Management Planning Change Memo Record

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

(compare step 4.4).

5.2 Used FormsNot relevant


Business Process Proceduressapidp/... · Web viewSAP AG Dietmar-Hopp-Allee 16 69190 Walldorf...

Documents

Transcript of Business Process Proceduressapidp/... · Web viewSAP AG Dietmar-Hopp-Allee 16 69190 Walldorf...