IHC

EHP4 for SAP ERP 6.0

December 2010

English

In-House Cash (801)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices In-House Cash (801): BPD

Copyright

© 2010 SAP AG. All rights reserved.

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

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

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

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

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

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

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

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

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

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

© SAP AG Page 2 of 105


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

1 Purpose.................................................................................................................................. 5

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

2.1 Master Data and Organizational Data.............................................................................6

2.2 Transactional Data..........................................................................................................6

2.3 Preliminary Steps............................................................................................................6

2.4 Roles............................................................................................................................. 18

3 Process Overview Tables.....................................................................................................19

3.1 Internal Payments.........................................................................................................19

3.2 External Outgoing Payments.........................................................................................20

3.3 External Outgoing Payments by Check.........................................................................21

3.4 Incoming Payments and Cash Pooling..........................................................................22

3.5 External Payments with Foreign Currency to another Clearing Center.........................23

3.6 Internal Returns.............................................................................................................24

3.7 External Returns............................................................................................................25

3.8 End-of Day Processing..................................................................................................26

4 Process Steps......................................................................................................................27

4.1 Process Steps – Internal Payments..............................................................................27

4.2 Process Steps – External Outgoing Payments..............................................................37

4.3 Process Steps – External Outgoing Payments by Check..............................................50

4.4 Process Steps – Incoming Payments and Cash Pooling...............................................63

4.5 Process Steps – External payments with foreign currency to a other clearing center. . .71

4.6 Process Steps – Internal Returns..................................................................................82

4.7 Process Steps – External Returns.................................................................................89

4.8 End-of-Day Processing...............................................................................................100



In-House-Cash

1 Purpose Collaboration within corporate groups is a model used when integrating the business management software solution used at a corporate group headquarters with the systems used by its subsidiaries. Such a situation – wherein a company may need to employ different business systems in different places throughout its organization – can occur for various business reasons. At the same time, in order to help enable the organization to function as a whole, the company must find a way to integrate the relevant business processes across these different systems. The provision of collaboration scenarios is an efficient way to achieve this goal.

This scenario describes how to set up the internal payments, external payments, incoming payments, cash pooling and separate clearing center for foreign currency of In-House Cash (IHC) within corporate groups and subsidiaries. Automated intra-group payments between headquarters (in-house cash center) and subsidiaries are made.

External payments: subsidiary received a billing document from the vendor. The subsidiary pays the invoice to headquarter and headquarter creates a payment medium for this payment to the house bank.

The in-house cash center is like a virtual bank at which your subsidiaries keep checking accounts. The headquarters (in-house cash center) is responsible for all payments between subsidiaries and subsidiaries with vendors. When there is an open item (creditor) in one subsidiary from other subsidiary or vendor, the payment run creates a payment medium for headquarters and the headquarters creates bank statements for the subsidiaries. This allows subsidiaries to assign bank statements to open items.

Payment for goods received or any other reason (including treasury payments) between subsidiaries can be executed from the In-House Bank (IHB) account that the paying subsidiaries hold with the IHB. The IHB credits the payment amount to the IHB account of the receiving subsidiary.



2 PrerequisitesThere must be at least two SAP clients or SAP systems. One SAP client or system is the central reporting unit (headquarters), which collects and summarizes information. In the other clients there collects transactions form Supplier payments.

2.1 Master Data and Organizational DataEssential master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for G/L-Accounts (Banks), vendors with their assigned payments.

You have entered the master data required to go through the procedures of this scenario. Ensure that the following scenario-specific master data exists before you start this scenario:

Master Data Value Selection Comment

Bank Accounts – IHC- <Subsidiaries Inhouse Bank account number>

This can be checked using transaction code F9K2

- Headquarters –

2.2 Transactional DataThe following IDocs are created in this process:

PAYEXT (Create payments)

FINSTA (Create bank statements)

2.3 Preliminary Steps

2.3.1 Posting a Customer Invoice in Accounting

UseCustomer invoices are posted in accounting. Accounting documents are created. When there are internal payments between subsidiaries, post this e.g. in subsidiary_2 (send delivery/billing document to subsidiary_1). We need this document later for clearing and credit note posting (bank statement from In-House Cash Center).

The vendor invoice for the other subsidiary (subsidiary_1) in this step should have the same amount than the customer invoice posted in this step and should reference the customer invoice.

Customer master data should exist (see process step Creating a Customer Master Record or Creating a One-Time Account).



PrerequisiteThere is installed a second subsidiary (separate client) and a customer master data (SUBSI_1) is created in this subsidiary. Record this invoice in this subsidiary/client.

Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP System SAP Business All-in-One Subsidiary System

SAP menu Accounting Controlling Internal Orders Master Data Special Functions Order Create

Transaction code KO01

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role SAP_NBPR_CONTROLLER-M (Enterprise Controller)

Business role menu Overhead Cost Controlling Master Data Internal Orders Create Internal Orders

2. On the Create Internal Order screen, enter following data.

Field Name Description User Action and Values

Comment

Order Type Internal orders

e.g. <0500> select

Order empty

3. Choose Enter

4. On the Set Controlling Area screen, enter following data.


Comment

Controlling Area e.g. <1000> select

5. Choose Enter

6. On the Create Internal Order: Master data screen, enter following data – tab: Assignments -.


Comment

Description <Internal Order for Revenue>

enter

Company Code e.g. <1000> select

Object Class e.g. <PROFT> select

7. On the Create Internal Order: Master data screen, enter following data – tab: Control data -.

Field Name Description User Action and Comment



Values

System Status <Release> Choose

After choose the System status is: REL and

User status is: PLIM

Currency e.g. <EUR> select

8. Choose Save

ResultThe message “Order was created with number ‘xxxxxx’ appears. Note this number for transaction FB70 –Enter Customer Invoice-.




SAP menu Accounting Financial Accounting Accounts Receivable Document Entry Invoice

Transaction code FB70


Business role Accounts Receivable Accountant –FI Only (SAP_NBPR_AR_FI_ONLY-S)

Business role menu Accounts Receivable Posting Invoice Enter Outgoing Invoices

When you call up the transaction for the first time, a dialog box appears for you to enter the company code. Enter company code.

To change the company code in the transaction, choose Edit Change Company Code. Then choose Continue.

10. On the Basic Data tab page on the Enter Customer Invoice: Company Code 1000 screen, enter the following data.


Comment

Customer Customer is subsidiary_1

<customer number>

e.g. SUBSI_1

For example enter customer which has been created with process step Creating a Customer Master Record

Choose the customer for internal deliveries.

In our case: subsidiary_2 delivers to subsidiary_1. So we record in



subsidiary_2 a customer invoice for subsidiary_1.

enter

Invoice Date <date>

e.g. <15.04.2010>

For Example Today’s date

enter

Reference <any reference> enter

Amount <11.900> enter

Currency <EUR> enter

Calculate Tax mark

Based on the previously posted down payment the system reacts with a message about the existing amount of down payments. Confirm this message with Continue (Enter).

11. On the Payment tab page on the Enter Customer Invoice: Company Code 1000 screen, enter the following data.


Comment

Bline Date Baseline Date for Due Date Calculation

<for example Today’s date>

e.g. <15.04.2010>

Check date

enter

Payt terms e.g. <0001> select

Pmt Method empty

12. Enter the following data for the line item:


Comment

G/L acct <500000> enter

D/C Debit/Credit <Credit> select

Amount in Document Currency

<11.900>Enter the gross amount. The system calculates the output tax automatically.

enter

Tax Code <A1> For example A1 (19% tax on sales/purchases)

select

Order e.g. <500000> Enter the order number noted from transaction KO01

If profit centers exist they should also be entered in field Profit Center. In this case scroll to the right to fill in the field.



13. To check the document before it is posted, choose Simulate (F9).This enables you to display the document, including the tax on sales/purchases to be posted, and to correct it if necessary.

14. Choose Post (Ctrl+S). The system may prompt you with an Information dialog box that a down payment exists. Confirm the Information dialog box by choosing Enter.

In the lower area of the screen, the system generates the message: Document 18000000xx was posted in company code 1000, where xx is the sequential document number posted by the system.

15. Make a note of the invoice document number for later use in “Post Vendor Invoice”.

ResultThe customer invoice is posted and the G/L account and customer transaction figures are updated.




SAP menu Accounting Financial Accounting Accounts Receivable Document Entry Invoice

Transaction code FB70


Business role Accounts Receivable Accountant –FI Only (SAP_NBPR_AR_FI_ONLY-S)

Business role menu Accounts Receivable Posting Invoice Enter Outgoing Invoices

When you call up the transaction for the first time, a dialog box appears for you to enter the company code. Enter company code.

To change the company code in the transaction, choose Edit Change Company Code. Then choose Continue.

17. On the Basic Data tab page on the Enter Customer Invoice: Company Code 1000 screen, enter the following data.


Comment

Customer External Customer in subsidiary_1

<customer number>

e.g. <SUB_CUSTOM>

The customer we need for external incoming payments

enter

Invoice Date <date>

e.g. <15.04.2010>

For example today’s date

enter


Amount <1,10> enter




Calculate Tax mark

Based on the previously posted down payment the system reacts with a message about the existing amount of down payments. Confirm this message with Continue (Enter).

18. On the Payment tab page on the Enter Customer Invoice: Company Code 1000 screen, enter the following data.


Comment

Bline Date Baseline Date for Due Date Calculation

<for example Today’s date>

e.g. <15.04.2010>

Check date

enter

Payt terms e.g. <0001> select

Pmt Method empty

19. Enter the following data for the line item:


Comment

G/L acct <500000> enter

D/C Debit/Credit <Credit> select


<1,10>Enter the gross amount. The system calculates the output tax automatically.

enter

Tax Code <A1> For example A1 (19% tax on sales/purchases)

select

Order e.g. <500000> Enter the order number noted from transaction KO01

If profit centers exist they should also be entered in field Profit Center. In this case scroll to the right to fill in the field.

20. To check the document before it is posted, choose Simulate (F9).This enables you to display the document, including the tax on sales/purchases to be posted, and to correct it if necessary.

21. Choose Post (Ctrl+S). The system may prompt you with an Information dialog box that a down payment exists. Confirm the Information dialog box by choosing Enter.

In the lower area of the screen, the system generates the message: Document 18000000xx was posted in company code 1000, where xx is the sequential document number posted by the system.



ResultThe customer invoice is posted and the G/L account and customer transaction figures are updated.

2.3.2 Post Vendor InvoiceTo run through this scenario, the open items for payables must be available in the subsidiary system.

UseYou receive the invoice from the vendor/subsidiary and post it in the system. Vendor Invoices for material are posted in materials module, Refer document for this. You can also post invoices in FI for other than materials like expenses for example as explained below.

We need 2 vendor invoices:

1. For internal payments. E.g.: delivery from subsidiary_2 to subsidiary_1. Create a vendor invoice in subsidiary_1. Vendor is subsidiary_2.

2. For external payments. E.g.: delivery from external vendor to subsidiary_1. Create a vendor invoice in subsidiary_1.

Many vendor invoices are posted with logistics. These invoices need to be posted for material with purchasing.

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



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, make the following entries:

Field name Description User action and values Comment

Vendor Subsi_2 is vendor in subsidiary_1 and created a customer invoice for subsi_1 in subsidiary_2

e.g.: for internal deliveries = e.g. <SUBSI_2>

Refer Master Data

enter

Invoice Date e.g. <today’s date> enter

Reference (*) Enter the document number from the “Posting a Customer



Invoice in Accounting”

Customer invoice created in subsidiary_2 with customer subsi_1.

- only when internal payments



Calculate tax mark

Tax Code <V1> domestic input tax; for example, V1 = 19% for Germany

select

Text <Internal Delivery/Payment>

enter

3. On the Enter Vendor Invoice screen, choose payment.

4. Enter following data:


G/L Account <680000> enter

D/C <Debit> select


<11.900> Gross amount;

enter

Tax Code <V1> domestic input tax; for example, V1 = 19% (Germany)

select

Cost Center e.g. <1801> Select a valid cost center

5. Choose Post (Ctrl + S).

ResultThe invoice for internal payments has been posted. For further processing, make a note of the document number.













Vendor Vendor in subsidiary_1 e.g.: for external deliveries e.g. <SUB_VENDOR>

Refer Master Data

enter





Calculate tax mark


select

Text <External Delivery / Payment>

enter




Pmt Method External Payment <4> Select

If field Pmt Method empty, we use the payment method from master data (vendor).


D/C <S Debit> select



enter


select





ResultThe invoice for external payments has been posted. For further processing, make a note of the document number.

UseEnter a vendor invoice with foreign currency for payment to a other clearing center in the headquarters











Vendor Vendor in subsidiary_1 with foreign currency. For additional clearing center.

e.g.: for external deliveries e.g <FW_VENDOR>

Refer Master Data

enter




Currency <JPY> enter

Calculate tax mark

Tax Code <V0> No tax procedure

select

Text <Payment with foreign currency – clearing center>

enter






Pmt Method External Payment <4> Select

If field Pmt Method empty, we use the payment method from master data (vendor).


D/C <S Debit> select



enter

Tax Code <V0> No tax procedure

select



ResultThe invoice for external payments –foreign currency- has been posted. For further processing, make a note of the document number.

2.3.3 Post Vendor Invoice – external payment by check To run through this scenario, the open items for payables must be available in the subsidiary system.

UseYou receive the invoice from the vendor and post it in the system. Vendor Invoices for material are posted in materials module, Refer document for this. You can also post invoices in FI for other than materials like expenses for example as explained below.

Many vendor invoices are posted with logistics. These invoices need to be posted for material with purchasing.













Vendor Vendor in subsidiary_1 e.g.: for external deliveries e.g. <SUB_VENDOR>

Refer Master Data

enter

Invoice Date <date>

e.g. <today’s date>

for example, today’s date

enter

Reference empty Enter the document number from the “Posting a Customer Invoice in Accounting”

- only when internal payments



Calculate tax mark


select

Text <External Delivery / Payment by Check>

enter

3. On the Enter Vendor Invoice screen, choose Payment:

4. Enter the following data:


Pmt Method Payment method for checks

<7> select


D/C <Debit> select



enter


select





ResultThe invoice has been posted. For further processing, make a note of the document number

2.4 Roles

UseThe following roles must already have been installed in order to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user, or users, testing this scenario. You only need these roles if you are using the NWBC interface within the SAP Business All-in-One system. You do not need these roles if you are using the standard SAP GUI. You do not need these roles in your headquarters’ system.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario in the subsidiary system:

Business Role Technical Name Process Step Payable Accountant SAP_NBPR_AP_CLERK-S Posting vendor data

Receivable Account-FI Only SAP_NBPR_AR_FI_ONLY-S Posting Customer data

Bank Accountant SAP_NBPR_BANKACC-S Processing bank data

Treasurer SAP_NBPR_TREASURER-S Payments to house bank

Enterprise Controller SAP_NBPR_CONTROLLER-M

Internal Orders

Treasurer BNI SAP_NBPR_TREASURER-BNI-S

Payments



3 Process Overview TablesThe following process steps follow a schedule of activities related to payment transactions and provide a daily review of the corporate cash position and liquidity forecast.

3.1 Internal Payments

Process Step Business Condition

Business Role

Transaction Code Expected Results

Subsidiary

Automatic Payment Transaction

Prerequisite: open items

Accountant Payables

F110 Data Medium is created and sent to other system – Headquarters-

IDoc: PAYEXT

Headquarters

Post Payment Orders

IHC0 Post Payment Order from Subsidiary

Headquarters

Check account statements

F9K3

-optional-

Account statements exist

Headquarters

Create Bank Statement

Payment Order is posted

F9N7 IDoc – FINSTA –

Bank Statements for each Subsidiary

Sent “Bank Statements” to Subsidiary

Subsidiary

Post Bank Statement

IDoc – FINSTA - available

Accountant Bank

FEBP

Select Bank Statements

Post Bank Statements

Clearing Account – Debit/Credit IHC

Attention: This is a task for each subsidiary (Payee and payer).

Subsidiary

Post process Bank Statement

When Transaction FEBP has been completed

FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: Are there any errors.




3.2 External Outgoing Payments


Business Role


Subsidiary



Accountant Payables

F110 Data medium is created and sent to other system – Headquarters-

IDoc: PAYEXT

Headquarters

Post Payment Orders


Output:

IDoc: PAYEXT – created

A “Payment Request” is created.

Check with transaction F8BT that payment request is created.

Headquarters


F9K3

-optional-


Headquarters




Bank Statements for Subsidiary


Headquarter

Automatic Payment Transaction for Payment Requests

F111 Data Medium for House Bank - created

Headquarter

Check data medium

FDTA

-optional-

Data Medium should exist

Subsidiary

Post Bank Statement


Accountant Bank

FEBP




Subsidiary


When Transaction FEBP completed

FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: Are there any errors



3.3 External Outgoing Payments by Check


Business Role


Subsidiary



Accountant Payables

F110 Data medium is created and sent to other system – Headquarters-

IDoc: PAYEXT

Headquarters

Post Payment Orders


Output:

IDoc: PAYEXT – created

A “Payment Request” is created.

Check with transaction F8BT that payment request is created.

Headquarters


F9K3

-optional-

Exist account statements

Headquarters






Headquarter

Automatic Payment Transaction for Payment Requests

F111 Outgoing check created

Headquarter Prüfen ob Check erstellt ist

Subsidiary

Post Bank Statement


Accountant Bank

FEBP




Subsidiary



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: There are any errors




Business Role


3.4 Incoming Payments and Cash Pooling


Business Role


Headquarters


Prerequisite: open items in Subsidiary

FF_5 Process data medium from House Bank

Data Format : MT940

Headquarters

Post Payment Orders

IHC0 Post Payment Order from House Bank

Headquarters


F9K3

-optional-


Headquarters






Subsidiary

Post Bank Statement


Accountant Bank

FEBP



Subsidiary



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: There are any errors



3.5 External Payments with Foreign Currency to another Clearing Center


Business Role


Subsidiary



Accountant Payables

F110 Data Medium is created and sent to other system – Headquarters-

IDoc: PAYEXT

Headquarters

Post Payment Orders


Headquarters


F9K3

-optional-


Headquarters





Bank statements for Headquarters created

Headquarters

Post Bank Statement


Accountant Bank

FEBP



Headquarters



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement


Subsidiary

Post Bank Statement


Accountant Bank

FEBP





Subsidiary



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement





Business Role



3.6 Internal Returns


Business Role


Headquarters

Reverse Payment Orders

IHC0 Reversed Payment Order from Subsidiary

Headquarters


F9K3

-optional-


Posting Text: Canceled

Headquarters






Subsidiary

Post Bank Statement


Accountant Bank

FEBP





Subsidiary



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: Are there are any errors.




3.7 External Returns


Business Role


Headquarters

Display Payment Requests

When F111 is done, Payment request is cleared

F8BT Cleared payment request: clearing document number is available

Headquarters

Reverse Document

Clearing document number from transaction F8BT

FB08 Reversed clearing document from payment request

Headquarters

Reverse Clearing of Payment Request

F8BW Payment request is cleared

Headquarters

Reverse Payment Order

IHC0 Reversed payment order from subsidiary

Headquarters


F9K3

-optional-


Posting Text: Canceled

Headquarters






Subsidiary

Post Bank Statement


Accountant Bank

FEBP





Subsidiary



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement





3.8 End-of Day Processing

Process Step Business Condition Business Role

Transaction Code

Expected Results

Headquarters

End-of-Day Processing

F9N11 Transfer transaction data from IHC to FI. All transactions are posted in the Financial Accounting.

Headquarters

Status Overview of Reports in End of Day Processing

F9N10 Status of Report should be “ Completed”

Headquarters Check Own Spool Requests

Spool Requests

Headquarters

Status message types

F961 Check message types



4 Process Steps

You can refer to the process overview table above for a first glance on the basic functionality.

The following process steps follow a schedule of activities related to payment transactions and provide a daily review of the corporate cash position.

The business process described in this document is not specific to any particular country. However, some of the data that appears within the document is specific to Germany, because the examples are taken from the SAP Best Practices Baseline package for Germany. In cases where this country-specific data appears, you must replace the data valid for Germany by data valid for your country.

4.1 Process Steps – Internal Payments

4.1.1 Creation of Payment Media Using Classical Payment Medium Program

UseThe purpose of this activity is to create internal payments between the subsidiaries.

Prerequisites There are open Items in the subsidiary for internal payments.




SAP ECC Menu Accounting Financial Accounting Accounts Payable Periodic Processing Payments

Transaction Code F110



Business role menu Accounts Payable Posting Payments Automatic Payment



2. On the Automatic payment transactions: Status screen, make the following entries:


Run Date e.g. <today’s day>

e.g. <26.03.2010>

enter

Identification freely define the identification

e.g. <IP_01> enter

3. Choose Parameter.

4. On the Automatic payment transactions: Parameter screen, make the following entries:


Posting Date e.g. <today’s day>

e.g. <26.03.2010>

enter

Docs Entered Up To

e.g. <today’s day>

e.g. <26.03.2010>

enter

Company Code

e.g. <1000> enter

Pymt Meths Payment Methods <3 IHB-Transfer internal>

select

Next p/date Posting Date of the next Payment Date

e.g. <30.03.2010> the day of the next posting date you want to run the payments

enter

Vendor e.g.: <SUBSI_2> Only you want certain Vendor(s)

Enter

Otherwise: ‘*’

to e.g. <SUBSI_2> Vendor, if you select an interval

Enter

Otherwise: empty

5. Choose Additional Log and make the following entries:

Field name Description User action and values

Comment

Due date check mark

Payment method selection in all cases

mark

Pmnt method selection if not successful

empty

Line items of the payment documents

mark

Vendors (from/to) <Vendors>

e.g. <SUBSI_2>

Enter

optional



6. Choose Printout/data medium and make following entries:


Program RFFOEDI1 Payment media program RFFOEDI1

select

Variant <Internal> Standard internal

The variant has been created in configuration guide.

select

7. Choose Save (Ctrl+S).

8. Choose Status.

9. Choose Proposal (Shift+F1).

10. On the Schedule Proposal screen, make the following entries:


Start immediately mark

11. Choose Schedule (Enter). The message Proposal run has been scheduled appears.

12. Choose – for more than one time - Status (Shift+F2) to update the status

13. As soon as the proposal has been created, this will be shown on the screen Automatic payment transactions: Status.

14. To maintain or display the payment proposal, choose Edit Proposal (Shift+F4) or Display Proposal (Shift+F9) and confirm the following screen (selection of accounting clerks) by pressing Continue (Shift+F1).

15. Choose Back (F3).

16. Choose Schedule Payment run (F7). Confirm the dialog box.

17. On the Schedule Payment screen, make the following entries:


Start immediately

mark

Create Payment Medium

mark

18. Choose Schedule (Enter). The message Payment run has been scheduled appears.

19. Choose Status (Shift+F2) more than once to update the status.

As soon as the payment run has been finished, this will be shown on the Status screen. The number of generated and completed posting orders is displayed.

20. Choose payment log, Payments. Check the selection of your document



21. In addition you can create the payment list and the exception list. To do so, choose Edit Payments Payment List or Edit Payments Exception List. Choose Continue (Enter) to execute the list.

ResultThe invoices have been paid taking a cash discount into account and posted to the bank clearing accounts. The IDoc generated has been sent to the In-House Cash Center, which will execute payment.

4.1.2 Post Payment Orders

UseThe purpose of this activity is to post the payment order from the subsidiary.

Procedure

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

SAP System SAP Headquarters’ System

SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Account Management IHC Payment Orders Payment Order Browser

Transaction Code IHC0


Business role Treasurer (SAP_NBPR_TREASURER_BNI-S)

Business role menu Cash Management Cash Management Planning Payment Order Browser

2. On the Browser for IHC Payment Orders screen, make the following entries:


Bank Area <IHB> select

Year e.g. <2010> enter current year

3. On the Browser for IHC Payment Order screen, choose Select IHC Payment Orders.

In the Selected Payment Orders, select the line(s):

- Description of Status: Flagged for Posting

- Transaction Type: INTPAY

Note the “Payer Account Number” and “Recipient Account Number” for the steps: Display Bank Accounts and Create Bank Statement.

The Recipient Bank Number is: ‘88888888’



4. Choose the Payment Order tab page.

5. Choose Post.

Note the “Payment Order” for step – Internal Returns- transaction IHC0.

ResultThe system issues one of the following messages:

Payment order IHB/0000000069/2010 is being checked (the number of the selected Payment Order is displayed)

No error was found.

Payment order IHB/0000000069/2010 has been finally posted.

The selected payment orders have been posted in the In-House Cash Center.

4.1.3 Display Bank Accounts (optional)

UseThe purpose of this activity is to check the posted accounts.

There should be account statements for both companies. Subsidiary_1 and Subsidiary_2.

Procedure



SAP System SAP Headquarters’’ System

SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Account Display

Transaction Code F9K3



Business role menu Cash Management Cash Management Reporting Display Account

2. On the Bank Accounts Display: Initial screen, make the following entries:



Account number <Bank Account Number>

e.g. for subsidiary_1 <1101004901> and subsidiary_2 <1102004901>

Enter “Payer Account Number” used for “Post Payment Order”

+ Internal Payments “Recipient Account Number”




From Transaction IHC0 (before).

3. Choose Enter.

4. Choose the Account Statements tab page.

5. Choose Current Bank Statement.

ResultThe selected account statements are displayed with the following values: Bank Key (88888888), Amount, Account Number from the Vendor and Post Date for transaction F9N7.

4.1.4 Create Bank Statement

UseThe purpose of this activity is to create bank statements for subsidiaries. When there are internal payments, perform this transaction for the “Payer Account” and for the “Recipient Account”. There will be created Bank Statement for both subsidiaries. When in subsidiary_1 there are open Bank Statements for e.g. Subsidary_2, so you must execute this step for Subsidary_1 and Subsidary_2. For all internal payments, you must execute this step at least twice.

PrerequisitesThe subsidiaries have made internal payments to the headquarters.

Procedure




SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Periodic Processing Bank Statement New Run Single Run

Transaction Code F9N7



Business role menu Cash Management Cash Management Planning Bank Statement - Single Account

2. On the Create One Single bank Statement on Request screen, make the following entries:



Account Number <bank account number>

enter



Field name Description User action and values Commente.g. for subsidiary_1 <1101004901>

and subsidiary_2 <1102004901>

Statement Date <Date> Post Day from “Post Payment Order”

You can see it with transaction F9K3 – too.

Selection date must be before or on the current posting date

Simulation Run empty

Standard Output empty If this indicator is set, the bank statement is output in standard form.

For this case, this indicator must not be set.

Statement Without Turnovers

empty

With Address mark

3. Choose Execute (F8).

The message “For account ‘999999999’, bank area IHB, an FAS IDoc is created” appears.

4. Choose Enter.

ResultThe banks statements for subsidiaries have been created and an IDoc is sent to the subsidiaries system. The system displays a screen with the address, bank account, amount and posting date.

4.1.5 Post Bank Statement

UseThe purpose of this activity is to post the bank statement that was created in headquarters for subsidiaries.

This is a task for each subsidiary, payee and payer.

Procedure






SAP ECC Menu Accounting Financial Accounting Banks Incomings Bank Statement Post

Transaction code FEBP


Business role SAP_NBPR_BANKACC_S (Bank Accountant)

Business role menu Bank Accounting Incomings Post Electronic Bank Statement

2. On the Update Bank Statement screen, in the area Bank Statements, make the following entries:


*all When all fields empty – processed all open bank statements

When there is no selection (choice), all not processed bank statements will processed

3. Or you can select in detail and the Bank Statement will only processed for these choice:


Statement Date <date>

e.g. <01.03.2010>Enter date, where the Bank Statements created in Headquarter (WithTransaction F9K3 you can see the Posting Date in HQ)

House Bank e.g.: <IHB> select

Account ID e.g.: <IHEUR> Select

The Company Code appears too

Currency e.g. <EUR> Only Bank Statements with currency EUR

enter

4. On the Update Bank Statement screen, in the area Posting Params, make the following entries:


Post immed. mark

Assign Value Date Account

mark

5. On the Update Bank Statement screen, in the area Output Control, make the following entries:




Execute as background Job

empty The job is working on the screen

Print Bank Statements

mark List of the Bank Statements

Print Posting Log mark Posted Bank Statements in the subsidiary

Print Statistics mark

Separate List mark

6. Choose Execute.

ResultThe bank statements are posted in the subsidiary.

There appears a message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’.

Choose Back (F3)

There appears a message “Processing Completed”

Posting in subsidiary_1 (payee) account 479901(debit) – account 479900(credit).

Posting in subsidiary_2 (recipient) account 479900(debit) – account 479901(credit).

The transactional code is IND – : outgoing internal payments and INC + : incoming internal payments.

Subsidiary_1: IND – and subsidiary_2: INC +

Account 479900 is the bank account against headquarters. In this case: subsidiary_1 has a liability against headquarters and subsidiary has a credit against headquarters.

4.1.6 Post process Bank Statement (optional)

UseThe purpose of this activity is to edit bank statements that contain errors.







SAP ECC Menu Accounting Financial Accounting Banks Incomings Bank Statement Reprocess

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, make the following entries:


House Bank <IHB> select

Account ID <IHEUR> select

3. Choose Execute.

4. On the Edit Bank Statement screen: open IHB -> open IHEUR.

5. Select the errors that are red.

6. Change the error and post again.

7. Choose Save.

ResultThe errors have been corrected in the subsidiary system.



4.2 Process Steps – External Outgoing Payments


UseThe purpose of this activity is to create external payments in the subsidiary for the headquarters.

External payments are defined in the vendor’s master data view Payment Transactions Accounting and the field Payment method.

Prerequisites There are open items in the subsidiary for external payments.











Run Date e.g. <today’s date>

e.g. <26.03.2010>

enter

Identification Freely define the identification

e.g. <EP_01> enter




Posting Date e.g. <today’s date>

e.g. <26.03.2010>

enter

Docs Entered Up To

e.g. <today’s date>

e.g. <26.03.2010>

enter

Company Code

<1000> enter

Pymt Meths Payment Methods <4 IHB-Transfer select



Field name Description User action and values Commentexternal>

Next p/date Posting Date of the next Payment

e.g.<30.03.2010> the day of the next posting date you want to run

Vendor e.g. <sub_vendor> Only you want certain vendor

Enter

Otherwise: ‘’*’ enter

to e.g. <sub_vendor> Vendor, if you select an interval

Enter

Otherwise: empty



Comment

Due date check mark


mark


empty


mark


e.g. <sub_vendor>

Enter

optional

6. Choose Printout/data medium.

7. Make the following entries:




Use the variant created in the configuration guide for this building block (step Create Variant for Payment Run F110).

select


9. Choose Status.












17. Choose Schedule Payment Run (F7). Confirm the dialog box.



Start immediately

mark


mark



As soon as the payment run has been finished, this will be shown on the Schedule Payment screen. The number of generated and completed posting orders is displayed.

21. Make a note of the DME reference numbers (YB_F110_D_UEBERW). You will need these later for the manual account statement.

To find out the DME reference numbers, go to DME Administration by choosing Environment Payment Medium DME Administration. By double-clicking the data medium, you can display its attributes. Make a note of the reference number (Data Medium tab page) for the domestic payment (YB_F110_D_UEBERW).

22. Choose payment log Payments. Check the selection of your document


ResultThe invoice has been paid taking a cash discount into account and posted to the bank clearing accounts. The IDoc generated has been sent to the In-House Cash Center, which will execute payment.





Procedure








On the Browser for IHC Payment Orders screen, make the following entries:







- Transaction Type: EXTPAY

Note the “Payer Account Number” for the steps: Display Bank Accounts and Create Bank Statement.

The Recipient Bank Number is <> ‘88888888’


3. Choose Post.

Note the “Payment Order” for step – Internal Returns- transaction IHC0.




Payment order IHB/0000000069/2009 is being checked (the number of the selected payment order is displayed)

No error was found.





Procedure













e.g. for subsidiary_1 <1101004901>


From transaction IHC0 (before)

3. Choose Enter.

4. Select the Account Statements tab page.




6. On this screen, you can check the open bank statement from this bank account. You see the external bank accounts with the open amount. When the next step – Create Bank Statement – for this account is done, there will be no “Current Bk Statement” for this account.




UseThe purpose of this activity is to create bank statements for subsidiaries. When in subsidiary_1 there are open bank statements for external payments, you must execute this step for subsidary_1.


Procedure









2. On the Create One Single Bank Statement on Request screen, make the following entries:





Enter payer account number





You can also display it with transaction F9K3.






empty

With Address select

3. Choose Execute.


4. Choose Enter.

ResultThe banks statements for subsidiaries have been created and an IDoc is sent to the subsidiary’s system. The system displays a screen with the address, bank account, amount, and posting date.

4.2.5 Automatic Payment Transaction for Payment Requests

UseThe purpose of this activity is to create a payment medium for the house bank.

You can use this payment program to make payments to 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.

Prerequisites There are open payment requests.

Procedure






SAP ECC Menu Accounting Financial Accounting Banks Outgoing Automatic Payment Payment Requests



Business role Treasurer (SAP_NBPR_TREASURER-S)

Business role menu

Cash Management Cash Management Planning Automatic Payment of PRequest



Run Date e.g. <today day> enter


e.g. <PR_01> enter




Posting Date e.g. <today’s date>

e.g. <26.03.2010>

enter

Next p/date Next Posting Date for the next payment run

e.g. <30.03.2010> the day of the next posting date you want to run

enter

Company code

<1000> select

Payment methods

<Y> Bank Transfer (Outgoing)

select

5. Choose Dynamic selections.



Key number <>

e.g.: <42>

Key number payment request from:

Use transaction F8BT to display all open payment requests. Should be the latest number.

Make a note of the payment request number. You will need this later for the reversal.



To <>

e.g.:: <42>

Key number payment request till:

House Bank e.g. <1000> select

Account ID e.g. <DISB> select


8. Choose Additional Log.




mark


mark

Due date check

empty

10. Choose Continue.

11. There appears a pop_up with the message “Log created for all accounts”

12. Choose Continue

13. Choose Payment medium.

14. On the Automatic Payment Transactions: Print Programs screen, make the following entries:


Report Program

„RFFOEDI1“

Variant “EXTERNAL” select


14. Choose Save.

15. Choose Proposal



Start immediately

mark


empty

17. Choose Enter. The message Proposal is running appears.




As soon as the proposal run has been finished, this will be shown on screen and the message Payment proposal has been created appears.

19. Choose proposal log Proposal. Check the selection of your document.

20. If there are no errors, choose Back

21. Schedule payment run by choosing Pmnt run.



Start immediately

mark


mark

22. Choose Enter. The message Payment run is running appears.


As soon as the payment run has been finished, this will be shown on screen and the message Payment run has been carried out appears

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

25. For additional information regarding the payment, see F111-menu: Edit –>Payments – > Payment List – Choose Enter.

26. For additional information regarding the payment, see F111-menu: System -> Own Spool Requests -> Payment summary ->Display contents (F6).

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 transfers (bank subaccounts ending with character 2 – bank clearing accounts).

The other line item has been posted to the clearing account IHC external payments, which has an account number that ends with the digit 0.

The generated payment medium files can now be sent to the bank, which will execute payment.

4.2.6 Check Output Data Medium – optional -

UseThe purpose of this activity is to check whether the payment medium is created.

Prerequisites Job Automatic Payment Transaction for Payment Requests is done.

Procedure






SAP ECC Menu Accounting Financial Accounting Banks Outgoing Automatic Payment Environment Payment Medium DME Administration

Transaction Code FDTA



Business role menu Cash Management Cash Management Bank Data TemSe/REGUT Data Administration



Reference number

Empty

Paying company code

for example, <1000> enter

Bank country For all countries “*” enter

Run Date e.g. <today’s date> enter

Identification empty

Format empty

Pymt. runs select

Proposal runs

empty

Data medium (not yet transferred externally)

select

Data medium (transmit. To external)

empty

Data medium w/out acct stmt

select

Data medium with acct stmt

select


Result

There should be a line with the same Identification (added by the letter ‘R’) you used for the payment run with transaction F111. Date created should be “today’s day’.





Procedure












When there is no selection, all unprocessed bank statements will be processed.

3. Or you can select in detail and the bank statement will only be processed for this selection:



e.g. <01.03.2010>Enter date bank statements created in headquarters. With transaction F9K3 you can see the posting date in HQ)

enter

House Bank e.g.: <IHB> Select

The company code appears too


The company code



appears too

Currency e.g.: <EUR> Only bank statements with currency EUR

enter

4. On the Update Bank Statement screen, in the area Posting Parms, make the following entries:


Post immed mark


mark

5. On the Update Bank Statement screen, in the area Output Control , make the following entries:





mark List of the bank statements

Print Posting Log mark Posted bank statements in the subsidiary


Separate List mark

6. Choose Execute. .


There appears a message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’”.

Choose Back (F3)

The message “Processing Completed” appears.

Posting in subsidiary_1 (payee): account 479903 (clearing account / debit) - account 479900 (IHB-account). Subsidiary_1 has a liability against headquarters.

Transactional code is: 020 -.


Use



The purpose of this activity is to edit bank statements that contain errors.













3. Choose Execute.




7. Choose Save.


4.3 Process Steps – External Outgoing Payments by Check




UseThe purpose of this activity is to create external payments by check in the subsidiary for the headquarters.

External payments are defined in the vendor’s master data view Payment Transactions Accounting and the field Payment method.

Prerequisites There are open items in the subsidiary for external payments with payment method: check.












e.g. <29.03.2010>

enter


e.g. <PS_01> enter





e.g. <29.03.2010>

enter

Docs Entered Up To

e.g. <29.03.2010> enter

Company Code

e.g. <1000> enter

Pymt Meths Payment Methods <7 IHB-Check external>

select




Next p/date Posting date of the next Payment Run

e.g. <10.04.2010> enter

Vendor e.g. <sub_vendor> enter

to e.g. <sub_vendor> Vendor, if you select an interval

Enter

Otherwise: empty



Comment

Due date check mark


mark


empty


mark


e.g. <sub_vendor>

Enter

optional

6. Choose Printout/data medium.


Field name

Description User action and values Comment



Use the variant created in the configuration guide for this building block (step Create Variant for Payment Run F110).

select

8. Choose Save Parameters (Ctrl+S).

9. Choose Status.












17. Choose Schedule Payment Run (F7). Confirm the dialog box.



Start immediately

mark


mark



As soon as the payment run has been finished, this will be shown on the Schedule Payment screen. The number of generated and completed posting orders is displayed.

21. Make a note of the DME reference numbers (YB_F110_D_UEBERW). You will need these later for the manual account statement.

To find out the DME reference numbers, go to DME Administration by choosing Environment Payment Medium DME Administration. By double-clicking the data medium, you can display its attributes. Make a note of the reference number (Data Medium tab page) for the domestic payment (YB_F110_D_UEBERW).

22. Choose payment log Payments. Check the selection of your document


ResultThe invoice has been paid taking a cash discount into account and posted to the bank clearing accounts. The generated DME files can now be sent to the bank, which will execute payment.





Procedure








6. On the Browser for IHC Payment Order screen, choose “Select IHC Payment Orders”.



- Transaction Type: CHECK



8. Choose Post.



No error was found.







Procedure















enter

3. Choose Enter.

4. Select the Account Statements tab page.


6. On this screen, you can check the open bank statement from this bank account. There should be bank accounts –Check Debit- with the open amount -. When the next step – Create Bank Statement – for this account is done, there will be no “Current Bk Statement” for this account.


ResultThe selected account statements are displayed with the following values: Bank Key, Amount, Posting date and Value date.




UseThe purpose of this activity is to create bank statements for subsidiaries. When in subsidiary_1 there are open bank statements for external payments, you must execute this step for subsidiary_1.


Procedure









2. On the Create One Single Bank Statement on Request screen, make the following entries:





Enter payer account number

enter


You can also display it with transaction F9K3.


enter


Standard Output empty If this indicator is set, the bank statement is output in standard




form.



empty

With Address select

3. Choose Execute.


4. Choose Enter.

ResultThe banks statements for subsidiary have been created and an IDoc is sent to the subsidiary system. The system displays a screen with the address, bank account, amount, and posting date.

4.3.5 Automatic Payment Transaction for Payment Requests

UseThe purpose of this activity is to create a payment medium for the house bank.

You can use this payment program to make payments to 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.

Prerequisites There are open payment requests.

Procedure




SAP ECC Menu Accounting Financial Accounting Banks Outgoing Automatic Payment Payment Requests



Business role Treasurer (SAP_NBPR_TREASURER-S)

Business role menu

Cash Management Cash Management Planning Automatic Payment of Request






e.g. <29.03.2010>

enter

Identification freely define the identification

e.g. <PS_01> enter





e.g. <29.03.2010>

enter

Next p/date Posting date of the next payment run

e.g. <10.04.2010> enter

Company code

e.g. <1000> select

Payment methods

<S> Outgoing check

select

5. Choose Dynamic selections.



Key number <>

e.g. <42>

Key number payment request from:

Use transaction F8BT to display all open payment requests. Should be the latest number.

select

To <>

e.g. <42>

Key number payment request till:

select

House Bank for example, <1000> select

Account ID for example, <DISB> select


8. Choose Additional Log.




mark




mark

Due date check

empty

10. Choose Continue.

11. There appears a pop_up with the message “Log created for all accounts”

12. Choose Continue

13. Choose Payment medium.

14. On the Automatic Payment Transactions: Print Programs screen, make the following entries:


Report Program

„RFFOD__S“

Variant “CHECK_IHB” select


16. Choose Save.

17. Choose Proposal



Start Date e.g. <today’s day>

e.g. <29.03.2010>

enter

Start immediately

mark


empty

19. Choose Enter. The message Proposal is running appears.


As soon as the proposal run has been finished, this will be shown on screen and the message Payment proposal has been created appears.

21. Choose proposal log Proposal. Check the selection of your document.

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





Start Date e.g. <today’s day>

e.g. <29.03.2010>

enter

Start immediately

mark


mark

24. Choose Enter. The message Payment run is running appears.


As soon as the payment run has been finished, this will be shown on screen and the message Payment run has been carried out appears

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

27. For additional information regarding the payment, see F111-menu: Edit –>Payments – > Payment List.

28. For additional information regarding the payment, see F111-menu: System -> Own Spool Requests -> Payment summary.

29. For document check, see F111-menu: System -> Own Spool Requests -> Scheck.

ResultThe generated payment document can now be sent to the vendor/recipient.



Procedure








Business role menu Bank Accounting Incomings Post Electronic Bank



Statement




When there is no selection, all unprocessed bank statements will be processed.

3. Or you can select in detail and the bank statement will only be processed for this selection:



e.g. <29.03.2010>Enter date, where the Bank Statements created in Headquarter (With Transaction F9K3 you can see the Posting Date in HQ)

House Bank e.g.: <IHB> Select




Currency e.g.: <EUR> Only bank statements with currency EUR

enter

4. On the Update Bank Statement screen, in the area Posting Parms, make the following entries:


Post immed select


select

5. On the Update Bank Statement screen, in the area Output Control , make the following entries:





select List of the bank statements

Print Posting Log select Posted bank statements in the subsidiary



Print Statistics select

Separate List select

6. Choose Execute.

Result.

The bank statements are posted in the subsidiary.


Choose Back (F3)

There appears a message “Processing Completed”.

Posting in subsidiary_1: account 479903 (clearing account – debit) - account 479900 (IHB-account –credit). Subsidiary_1 has a liability against headquarters.

Transactional code is: CKD -.











2. On the Selection of Bank Statements by Banks and Account No, make the following entries:






3. Choose Execute.




7. Choose Save.


4.4 Process Steps – Incoming Payments and Cash Pooling

UseThe purpose of this activity is to process the bank medium from the house bank. The bank medium contains incoming payments – payments from customers, cash pooling, and balancing bank accounts from subsidiaries and the house bank at the headquarters.

Prerequisites There are open items at the subsidiary from a customer.

4.4.1 Import Bank Statements

UseThe purpose of this activity is to post the payment medium from the house bank.

Procedure



SAP ECC Menu Accounting Financial Accounting Banks Incomings Bank Statements Import

Transaction Code FF_5


Business role SAP_NBPR_BANKACC-S (Bank Accountant)

Business role menu Bank Accounting Incomings Import Electronic Bank Statement





Import Data mark

Elect. Bank statement format

<SWIFT MT940 with field 86 structure>

select

Statement file The file from the house bank

Choose

Line item file empty

Post Immediately

mark

Only bank postings

empty

Generate batch input

empty

Do not post empty

Assign value date

mark

Cash management

All fields are empty

BELNR number interval

<0000000000> enter

to <9999999999>’ enter

XBLNR number interval

empty

to <ZZZZZZZZZZZZZZZZ> enter

Bundling empty

Items per Bundle

empty

Execute as background job

empty

Print bank statement

mark

Print posting log

mark

Print statistics

mark

Separate list mark

3. Choose Execute (F8)



ResultFollowing message appears: document ‘999999999’ was posted in company code ‘xxxx’.

Account statements are posted at the Headquarters. They are posted against bank accounts, clearing accounts and accounts for cash pooling. A posting log has been created with posting accounts and with the external transaction for cash pooling: 833, and for incoming payments: 051 / 071.



Procedure















- Transaction Type: INCCRE/INCDEB (incoming payments) and CPOOLD/CPOOLC (cash pooling).

Note the “Recipient Account Number” for the steps: Display Bank Accounts and Create Bank Statement.

The Recipient Bank Number is: ‘88888888’




8. Choose Post.



No error was found.





Procedure














“Recipient Account Number”


8. Choose Enter.







UseThe purpose of this activity is to create bank statements for subsidiaries.

PrerequisitesThere are bank statements from the house bank exist.

Procedure














enter











empty

With Address mark



4. Choose Enter.




Procedure











*all When all fields When there is no



empty – processed all open bank statements

selection (choice), all not processed bank statements will processed









enter



Post immed. mark


mark









Separate List mark

6. Choose Execute.

Result



The bank statements are posted in the subsidiary.


Choose Back (F3)

There appears a message “Processing Completed”

Attention: accounts are not balanced automatically

The posting for incoming payments: account 479900 (IHB-account) - 479902 (account ext. incoming payments) – Transaction code: EXC +.

Transaction EXD -: inverse posting.

Reducing the liability or increasing receivables against headquarters.

The transaction code for cash pooling (debit) is CPD -. Posting: account 479905 (cash pool - 479900 (account headquarters). Subsidiary has a liability against headquarters.

Transaction CPC +: inverse posting.


















3. Choose Execute.




7. Choose Save.


4.5 Process Steps – External payments with foreign currency to a other clearing center


UseThe purpose of this activity is to create payments to another clearing center. This enables you to save costs (for example, the handling charge) when your payments for foreign currency in the same country take place. For example, a payment in currency JPY to a house bank in Japan.

We have defined the procedure between the subsidiary and the headquarters, and the headquarters to the clearing center. There is no customizing in clearing center Japan (JP01, so we cannot send and receive IDoc’s to and from clearing center Japan (JP01).

Prerequisites There are open Items in the subsidiary with foreign currency.














e.g. <26.03.2010>

Enter


e.g. <CC_01> Enter





e.g. <26.03.2010>

Enter

Docs Entered Up To

e.g. <today’s day>

e.g. <26.03.2010>

Enter

Company Code

e.g. <1000> Enter

Pymt Meths Payment Methods <4 IHB-Transfer external>

Select

Next p/date Posting Date of the next Payment Date

e.g. <30.03.2010> The day of the next posting date you want to run the payments

Enter

Vendor e.g.: <FW_VENDOR> Only you want certain Vendor(s)

Enter

Otherwise: ‘*’

to e.g. <FW_VENDOR> Vendor, if you select an interval

Enter

Otherwise: Empty



Comment

Due date check Mark


Mark


Empty

Line items of the payment Mark



documents


For example, <FW_VENDOR>

Enter

Optional

6. Choose Printout/data medium and make following entries:



select


The variant has been created in configuration guide.

Select


8. Choose Status.




Start immediately Mark


12. Choose – for more than one occurrence - Status (Shift+F2) to update the status

13. As soon as the proposal has been created, it will be shown on the Automatic payment transactions: Status screen.



16. Choose Schedule Payment run (F7). Confirm the dialog box.



Start immediately

Mark


Mark





As soon as the payment run has been finished, it will be shown on the Status screen. The number of generated and completed posting orders is displayed.

20. Choose payment log, Payments. Check the selection of your document

21. In addition you can create the Payment List and the Exception List. To do so, choose Edit Payments Payment List or Edit Payments Exception List. Choose Continue (Enter) to execute the list.

ResultThe invoices have been paid while taking a cash discount into account and have been posted to the bank clearing accounts. The IDoc generated has been sent to the In-House Cash Center, which will execute payment.



Procedure















- Transaction Type: EXTPAY

- Transaction Currency: <> ‘EUR’




The Recipient Bank Number should be <>: ‘88888888’


5. Choose Post.



No error was found.



There are two IDoc’s (PAYEXT) have been created. One outbound IDoc –Partner: LS //Local with status 3 –green light-.

The second IDoc inbound for Partner: LS//XXXXXXXxxx with Status 51 –red light- , because there is no customizing for a bank in the clearing center JP01.



.

Procedure
















and

for clearing center:

<1101008101>



3. Choose Enter.



ResultThe selected account statements are displayed with the following values: Bank Key <> (88888888), Amount, Account Number from the Vendor and Post Date for transaction F9N7.


UseThe purpose of this activity is to create bank statements for subsidiaries and for headquarters in order to post for the clearing center.

PrerequisitesThe subsidiaries have made external payments to the headquarters in foreign currency.

Procedure














Account Number For subsidiary and clearing center

<bank account number>

e.g. <1101004901>

and

e.g. <1101008101>

enter





Standard Output empty If this indicator is set, the bank statement is generated in standard form.



empty

With Address mark


The message “For account ‘999999999’, bank area ‘IHB’, an FAS IDoc is created” appears.

4. Choose Enter.

ResultThe bank statements for subsidiaries and the clearing center have been created and an IDoc sent to the subsidiaries’ systems. The system displays a screen with the address, bank account, amount and posting date. There are two IDoc’s created.

One outbound FINSTA IDoc with partner GP//SUB_JAPAN port LOCAL.

One inbound FINSTA IDoc with partner B//0088888888 port SAPBHQ.


UseThe purpose of this activity is to post the bank statement that was created at the headquarters for the clearing center.



Procedure









7. On the Update Bank Statement screen, in the Bank Statements area, make the following entries:




House Bank e.g.: <JPY> select

8. On the Update Bank Statement screen, in the Posting Params area, make the following entries:


Post immed. mark


mark

9. On the Update Bank Statement screen, in the Output Control area, make the following entries:






Print Posting Log mark Posted Bank Statements




Separate List mark

10. Choose Execute.

ResultThe bank statements are posted in the headquarters.

The message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’ appears.

Choose Back (F3)


The transaction code is 051 and the posting: clearing account 289009 – account clearing center 289000.

.











2. On the Selection of Bank Statements by Banks and Account Nos screen, make the following entries:


Company code <1000> select

House Bank <JPY> select

3. Choose Execute.

4. On the Edit Bank Statement screen: open JPY -> open JPY01.

5. Select the errors that are marked in red.

6. Correct the errors and post again.

7. Choose Save.



ResultThe errors have been corrected in the headquarters system.



Procedure









2. On the Update Bank Statement screen, in the Bank Statements area, make the following entries:




3. Alternatively you can make your selections in detail and the Bank Statement will only be processed for those choices:



e.g. <01.03.2010>Enter date, where the Bank Statements created in Headquarter (With Transaction F9K3 you can see the Posting Date in HQ)







enter

4. On the Update Bank Statement screen, in the Posting Params area, make the following entries:


Post immed. mark


mark

5. On the Update Bank Statement screen, in the Output Control area, make the following entries:








Separate List mark

6. Choose Execute.


The message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’ appears.

Choose Back (F3)


Posting in subsidiary: account 479903 (clearing account – debit) - account 479900 (IHB account – credit). Subsidiary has a liability against the headquarters. The transactional code is 020.













2. On the Selection of Bank Statements by Banks and Account Nos screen, make the following entries:




3. Choose Execute.

4. On the Edit Bank Statement screen, open IHB then open IHEUR.

5. Select the errors that are marked in red.

6. Correct the errors and post again.

7. Choose Save.


4.6 Process Steps – Internal Returns

4.6.1 Reverse Payment Orders

UseThe purpose of this activity is to cancel the payment order from the subsidiary. When there is a wrong payment from the subsidiary, with the function reverse is it possible to cancel the payment. Subsidiary_1 –payer- receives the payment back with the sign plus and subsidiary –receiver of the payment- receives the payment back with the sign minus.

Procedure









Business role menu

Cash Management Cash Management Planning Payment Order Browser




Year e.g.< 2010> enter current year

3. On the Browser for IHC Payment Order screen, select “Select “IHC Payment Orders”.

Select the notated “Payment Order” from transaction IHC0 –Internal Payments-, select the line(s):

- Description of Status:” Finally Posted”

- Transaction Type: “INTPAY”

Note the “Payer Account Number” for the next step, Display Bank Accounts:

For Internal Payments note the “Recipient Account Number”. There is Recipient Bank Number = ‘88888888’


5. Choose Reverse

6. There appears a pop-up with the question: Do you want to reverse all payment orders?

- Confirm with: Yes



No error was found.



No outbound IDoc existsI

Payment order IHB/0000000001/2010 has been reversed.

The Description of Status is: Reversed



UseThe purpose of this activity is to check the posted accounts for each subsidiary.

Procedure








Business role menu

Cash Management Cash Management Reporting Display Account








3. Choose Enter.



Result



The selected account statements are displayed with the following values: Bank Key, Amount, Account Number from the Vendor and Post Date for transaction F9N7. The Posting Text is “Canceled: IHC Item”


UseThe purpose of this activity is to create bank statements for subsidiaries. When there are internal payments, perform this transaction for the “Payer Account” and for the “Recipient Account”. There will be created Bank Statement for both subsidiaries. When in subsidiary_1 there are open Bank Statements for e.g. Subsidary_2, so you must execute this step for Subsidary_1 and Subsidary_2. For all internal payments, you must execute this step at least twice.


Procedure








Business role menu

Cash Management Cash Management Planning Bank Statement - Single Account






enter











empty

With Address mark

3. Choose Execute.

The message For account ‘999999999’, bank area IHB, an FAS IDoc is created appears.

4. Choose Enter.





Procedure

















Statement Date <date> Enter date, where the Bank Statements created in Headquarter




Currency e.g.<EUR> Only Bank Statements with currency EUR



Post immed. mark


mark









Separate List mark



6. Choose Execute.

7. The system issues the message Processing Complete.

ResultThe bank statements are posted in the subsidiary. The posting document should be e.g. in subsidiary_1: “account IHB” –debit- to “account IHB reversal” – credit-. Transactional code is IND +. In subsidiary_2 inverse posting as in subsidiary_1. Transactional code is: INC -

Mind that the FI –posting that result from the bank statement posts the return to a special bank subaccount that allows a monitoring of the returns.











Business role menu Bank Accounting Incomings Post processing Bank Statement







3. Choose Execute.




7. Choose Save.


4.7 Process Steps – External ReturnsThe purpose of this activity is to cancel the payment order from the subsidiary. When there was a wrong external payment to the house bank, with the function reverse is it possible to cancel the payment. Subsidiary_1 –payer- receives the payment back with the sign plus and can change /revise the payment and start the payment again..

4.7.1 Display Payment Request

UseInvestigate the clearing document for returns.

Procedure



SAP ECC Menu Accounting Financial Accounting Outgoings Online Payments Display Payment Request

Transaction Code F8BT

2. Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role


Business role menu

Cash Management Cash Management Reporting Display Payment Requests

3. On the display payment requests screen, enter following entries:


Company Code

e.g. <1000> select

Open empty




Cleared mark

4. On the display payment requests screen, choose Administration Data and enter following entries:


Origin <TR-IHC> select

5. On the display payment requests screen, choose Bank data and enter following entries:


House Bank e.g. <1000> enter

House Bank Account

e.g. Deutsche Bank e.g. <DISB> enter

6. On the display payment requests screen:


Key Number e.g. <46> Use the payment request number noted from transaction F111

7. Choose Execute

ResultOn the detail display you can see the “Clearing Document”-Number. Note the number for transaction FB08 and F8BW as well as the entry date for transaction IHC0 later.

4.7.2 Individual Reversal

UseThe first step for reverse a payment is, to reverse the posted document: Header Data

Procedure





SAP ECC Menu Accounting Financial Accounting General Ledger Document Reverse Individual Reversal




Business role menu

Accounts Payable Posting Document Processing

1. Only SAP NetWeaver Business Client (SAP NWBC):

2. Mark “All Vendor Line Items Cleared”Choose the necessary Search Criteria:


Vendor Account: e.g.: <sub_vendor> enter

Company Code: 1000

2. Only SAP NetWeaver Business Client (SAP NWBC): Choose Apply.

3. Only SAP NetWeaver Business Client (SAP NWBC): Mark the required row (document number) and choose Reverse Document.

4. On the reverse document: header data screen, make the following entries:


Document Number

e.g. <200000001> Enter.

“Clearing Document”-number from transaction F8BT.

Or from Job Log –payment run F111.

Company Code

e.g. <1000> select

Fiscal Year e.g. <2010> enter

Reversal Reason

<01> select

5. Choose Save

ResultThere appears the message: Document ‘9999999999’ was posted in company code 1000



4.7.3 Reset Cleared Items

UseThe second step for reverse a payment is to reverse clearing of a payment request



SAP ECC Menu Accounting Financial Accounting Banks Environment Payment Requests Reset Cleared Items

Transaction Code F8BW



Business role menu

Cash Management Cash Management Planning Reset Cleared Items: Payt Requests

2. On the reverse clearing of payment requests screen, make the following entries:


Company Code

e.g. <1000> enter

Payment document

Document from transaction F8BT

e.g. <200000001> Enter

The same document number like in transaction FB08

Fiscal Year e.g. <2010> enter

Mark for cancelation

empty

3. Choose Execute

ResultThere appears the message: “Cleared payment request items were reset”



4.7.4 Reverse Payment Orders

UseThe purpose of this activity is to reverse the payment order from the subsidiary.

Procedure







Business role menu

Cash Management Cash Management Planning Payment Order Browser





Date Executed

Date from transaction F8BT –entry date

<date> enter

3. On the Browser for IHC Payment Order screen, choose “Select IHC Payment Orders”.


- Payment Order: noted transaction IHC0 (external outgoing payments) e.g. 204

- Description of Status:” Finally Posted”

- Transaction Type: “EXTPAY”

- Recipient Bank Number: should be the same from the house bank - return

- Recipient Account Number: should be the same from the house bank - return

Note the “Payer Account Number” for the next step, Display Bank Accounts:


5. Choose Reverse



6. There appears a pop-up with the question: Do you want to reverse all payment orders?

- Confirm with: Yes



No error was found

Outbound IDoc 9999999999999999 is used for partner Type FI.

Payment order ‘99’ in system ‘XXX’ was reserved (date dd.mm.yyyy / reason 01)

Payment order IHB/0000000001/2010 has been reversed.

The Description of Status is: Reversed




Procedure

1. Access the transaction using one of the following navigation option:







Business role menu

Cash Management Cash Management Reporting Display Account








Field name Description User action and values Commente.g. for subsidiary_1 <1101004901>


3. Choose Enter.



ResultThe selected account statements are displayed with the following values: Bank Key, Amount, Account Number from the Vendor and Post Date for transaction F9N7. The Posting Text is “Canceled: Bank transfer”.



Procedure








Business role menu

Cash Management Cash Management Planning Bank Statement - Single Account




Account Number <bank account enter



Field name Description User action and values Commentnumber>

e.g. <1101004901>

Statement Date <Date>

e.g.<12.04.2010>Post Day from “Post Payment Order”







empty

With Address mark

3. Choose Execute.


4. Choose Enter.

5. Choose Back (F3)





Procedure













Statement Date

Statement Number

House Bank

Account ID

Currency

When all fields empty – processed all open bank statements




Statement Date <date> Enter date, where the Bank Statements created in Headquarter. Current Posting Date – look transaction F9B2







Post immed. mark

Assign Value mark



Date Account




Empty The job is working on the screen





Separate List mark

6. Choose Execute.

7. The system issues the message Processing Complete.

ResultThe bank statements are posted in the subsidiary. The posting document should be:” account IHB” –debit- to “account IHB reversal” – credit-. Transactional code is 020 +.

Mind that the FI –posting that result from the bank statement posts the return to a special bank subaccount that allows a monitoring of the returns.


















3. Choose Execute.




7. Choose Save.




4.8 End-of-Day Processing

UseIn the In-House Cash Center there are all bank postings from the subsidiaries. These transactions are necessary in the Financial Accounting for reconciliation.

If you start at the first time with the End-of-Day Processing, check the “Current Posting Date” from Transaction F9B1 with the date from transaction F9N11. The date from F9N11 parameters should be the same. If the date is not the same, there won’t be transfers from IHC -> FI.




SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Periodic Processing Posting Date Payment Transaction

Transaction Code F9B1



Business role menu

Cash Management Cash Management Reporting BCA: Posting cut-off paym. transact.

2. Enter following data;

Field Name Description User action and Values

Comment


Current Posting Date

The field is protect

3. Choose Execute (Enter)

If Date is not the same as the date from transaction F9N11, enter the following data:



Field Name Description User action and Values

Comment

New Posting Date

Date from transaction F9N11

<date> enter

Normally – daily process – it should be the same and always the current date.

4. Choose Save

5. Procedure for check/change Current Posting Date in F9N11 (Date must be equal like transaction F9B1):




SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Periodic Processing End-of-Day Processing Start




Business role menu

Cash Management Cash Management Reporting Start End-of-Day Processing

7. Procedure for check/change Current Posting Date in F9N11:


Processing Chain <STD> select


9. Mark line and choose Maintain Variants F5.

10. The Date e.g. Balances c/f on (from Cash Concentration) – should be the same like “Current Posting Date” from transaction F9B1. The date in the transaction F9B11 has the default value “current date”. Therefore generally no changes necessary.

11. Check all lines.

Furthermore, ensure that no Simulation run is marked in the parameters of transaction F9N11.

PrerequisitesThe subsidiaries have made payments to the headquarters.

Procedure






SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Periodic Processing End-of-Day Processing Start




Business role menu

Cash Management Cash Management Reporting Start End-of-Day Processing

2. On the Start Sequence of Reports in End-of-Day Processing screen, make the following entries:


Processing Chain <STD> select

3. Choose Execute.

There could be appear a message “Parameters were not changed Start Anyway”.

Please confirm “Yes”.

ResultAll bank postings from IHC are posted in the Financial Accounting.

4.8.1 End-of-Day Processing – Control Check 1 (optional)

UseThe purpose of this activity is to make a control check of an End-of-Day processing.

PrerequisitesThe job with transaction F9N11 is started or finished.

Procedure






SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Periodic Processing End-of-Day Processing Overview




Business role menu

Cash Management Cash Management Reporting Overview End of Day Processing

2. On the Status Overview of Reports in End of Day Processing screen, make the following entries:


Start Date from <Date from run F9N11> enter

Start Date to Could be empty

3. Choose Execute.

ResultAll jobs should have the message Completed without Error(s).


UseThe purpose of this activity is to make an additional control check of an End-of-Day processing.

PrerequisitesThe job with transaction F9N11 is finished.

Procedure




SAP Graphical User Interface (SAP GUI)


SAP ECC Menu Accessible from the menu bar in any screen

Transaction Code No transaction code necessary



Business role menu

Accessible from the menu bar in any screen

Choose More…

2. Choose System.

3. Choose Own Spool Requests.

4. Choose List1s from Time today e.g. Lists LOCAL RFBKGL01_ xxx.

ResultPostings from IHC FI. You can see all transfers from the accounts - IHC to FI.

The list included: Recon. Key, Post date, Currency, Value Date and the posted amount.

Last line should have the message: Transfer finished w/o error.


UseThe purpose of this activity is to make an additional control check of an End-of-Day processing.

PrerequisitesThe job with transaction F9N11 is finished.

Procedure




SAP ECC Menu Accounting Financial Supply Chain Management In-House Cash Periodic Processing Applications Logs Transfer FI






Business role menu

Cash Management Cash Management Reporting Application Log FI Transfer

2. On the Status Overview of Reports in End of Day Processing screen, make the following entries:


Object <FIBA> select

Subobject <BAGLTRANS> select

From(Date/Time) <Today’s date> enter

To(Date/Time) <Today’s date> enter

All Logs mark

Format Completely from Database

mark

4. Choose Execute.

ResultColumn “Message Type” should be green.

When the column “Message Types” is red, open the messages. You can see the reason for the error.


Documents

IHC