EHP4 for SAP ERP 6.

0 December 2010 English

In-House Cash (801)
Business Process Documentation

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

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

SAP Best Practices

In-House Cash (801): BPD

Icons
Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice

Typographic Conventions
Type Style Example text Description 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 EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as ENTER key.
F2)

Example text

EXAMPLE TEXT

or the

Example text <Example text>

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG

Page 3 of 105

.............................................7 Process Steps – External Returns.............................. 6 2.................................................50 4..................................3 Preliminary Steps.......8 End-of Day Processing.................................................7 External Returns.......................................................6 2. 19 3... 20 3..................................................................... 100 © SAP AG Page 4 of 105 .8 End-of-Day Processing..........................................................................82 4....................4 Incoming Payments and Cash Pooling........................................................................3 External Outgoing Payments by Check.................................................................................................................5 Process Steps – External payments with foreign currency to a other clearing center..............................................................23 3.................2 Transactional Data...................................................37 4................................................1 Process Steps – Internal Payments.SAP Best Practices In-House Cash (801): BPD Contents 1 Purpose ..............................................................................................3 Process Steps – External Outgoing Payments by Check.............................................................................................4 Roles......................................... 6 2.........................71 4....................1 Master Data and Organizational Data........................................................................................................................... 27 4..............................................................................................................21 3..........2 Process Steps – External Outgoing Payments....................................4 Process Steps – Incoming Payments and Cash Pooling...........................................................................................................5 External Payments with Foreign Currency to another Clearing Center ..................................................63 4...................................................................................................................................22 3................................. 18 3 Process Overview Tables.............................6 Internal Returns.................................... 24 3................. 5 2 Prerequisites.......................................................................1 Internal Payments................................................ 26 4 Process Steps....6 Process Steps – Internal Returns.................. 19 3........................................................89 4.......................................................................................................................................... 25 3...........................................................27 4...... 6 2.................................2 External Outgoing Payments..........

external payments. The provision of collaboration scenarios is an efficient way to achieve this goal.SAP Best Practices In-House Cash (801): BPD 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. cash pooling and separate clearing center for foreign currency of In-House Cash (IHC) within corporate groups and subsidiaries. the company must find a way to integrate the relevant business processes across these different systems. 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. 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. incoming payments. 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. At the same time. © SAP AG Page 5 of 105 . Automated intra-group payments between headquarters (in-house cash center) and subsidiaries are made. The IHB credits the payment amount to the IHB account of the receiving subsidiary. When there is an open item (creditor) in one subsidiary from other subsidiary or vendor. in order to help enable the organization to function as a whole. External payments: subsidiary received a billing document from the vendor. The headquarters (in-house cash center) is responsible for all payments between subsidiaries and subsidiaries with vendors. 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. This scenario describes how to set up the internal payments.

g.SAP Best Practices In-House Cash (801): BPD 2 Prerequisites There must be at least two SAP clients or SAP systems. for example. in subsidiary_2 (send delivery/billing document to subsidiary_1). One SAP client or system is the central reporting unit (headquarters). 2. master data for G/L-Accounts (Banks). When there are internal payments between subsidiaries. Ensure that the following scenario-specific master data exists before you start this scenario: Master Data Value Selection Comment This can be checked using transaction code F9K2 Headquarters – Bank Accounts – IHC.2 Transactional Data The following IDocs are created in this process: • • PAYEXT (Create payments) FINSTA (Create bank statements) 2.<Subsidiaries Inhouse Bank account number> 2. 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. We need this document later for clearing and credit note posting (bank statement from In-House Cash Center). such as the data that reflects the organizational structure of your company and master data that suits its operational focus. Accounting documents are created. Posting a Customer Invoice in Accounting © SAP AG Page 6 of 105 . which collects and summarizes information. In the other clients there collects transactions form Supplier payments.1 Master Data and Organizational Data Essential master and organizational data was created in your ERP system in the implementation phase. post this e.3 Preliminary Steps 2. vendors with their assigned payments. You have entered the master data required to go through the procedures of this scenario.1 Use Customer invoices are posted in accounting.3. Customer master data should exist (see process step Creating a Customer Master Record or Creating a One-Time Account).

On the Create Internal Order screen. On the Create Internal Order: Master data screen. enter following data – tab: Control data -.g. Field Name Order Type Order 3. Choose Enter 6. Field Name Description User Action and Comment © SAP AG Page 7 of 105 . <1000> e. <1000> Comment select Description Internal orders User Action and Values e. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP menu Transaction code SAP Business All-in-One Subsidiary System Accounting  Controlling  Internal Orders  Master Data Special Functions Order  Create KO01 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_CONTROLLER-M (Enterprise Controller) Overhead Cost Controlling  Master Data  Internal Orders  Create Internal Orders 2. Procedure 1. enter following data.SAP Best Practices In-House Cash (801): BPD Prerequisite There is installed a second subsidiary (separate client) and a customer master data (SUBSI_1) is created in this subsidiary. On the Set Controlling Area screen. Record this invoice in this subsidiary/client. <0500> empty Comment select 7. On the Create Internal Order: Master data screen. <PROFT> Comment enter select select Description User Action and Values e. Choose Enter 4. Field Name Controlling Area 5. enter following data – tab: Assignments -.g. Field Name Description Company Code Object Class Description User Action and Values <Internal Order for Revenue> e.g. enter following data.g.

<EUR> select Result The message “Order was created with number ‘xxxxxx’ appears. a dialog box appears for you to enter the company code. SUBSI_1 Comment For example enter customer which has been created with process step Creating a Customer Master Record Choose the customer for internal deliveries. enter the following data.g. In our case: subsidiary_2 delivers to subsidiary_1. choose Edit → Change Company Code. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP menu Transaction code SAP Business All-in-One Subsidiary System Accounting  Financial Accounting  Accounts Receivable  Document Entry  Invoice FB70 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Receivable Accountant –FI Only (SAP_NBPR_AR_FI_ONLY-S) Accounts Receivable  Posting  Invoice  Enter Outgoing Invoices When you call up the transaction for the first time.g. Enter company code. 9. On the Basic Data tab page on the Enter Customer Invoice: Company Code 1000 screen. 10. Then choose Continue. Field Name Customer Description Customer is subsidiary_1 User Action and Values <customer number> e. So we record in © SAP AG Page 8 of 105 . To change the company code in the transaction.SAP Best Practices Values System Status <Release> In-House Cash (801): BPD Choose After choose the System status is: REL and User status is: PLIM Currency 8. Choose Save e. Note this number for transaction FB70 –Enter Customer Invoice-.

g. The system calculates the output tax automatically.2010> <any reference> <11. <0001> empty select Comment Check date enter Payt terms Pmt Method 12. On the Payment tab page on the Enter Customer Invoice: Company Code 1000 screen. enter the following data. <15. Confirm this message with Continue (Enter).900> Enter the gross amount. <500000> Enter the order number noted from transaction KO01 Comment enter select If profit centers exist they should also be entered in field Profit Center. © SAP AG Page 9 of 105 .g.900> <EUR> mark For Example Today’s date enter enter enter enter Based on the previously posted down payment the system reacts with a message about the existing amount of down payments.g. Enter the following data for the line item: Field Name G/L acct D/C Amount in Document Currency Debit/Credit Description User Action and Values <500000> <Credit> <11. 11. In this case scroll to the right to fill in the field. enter Tax Code <A1> For example A1 (19% tax on sales/purchases) select Order e. enter Invoice Date Reference Amount Currency Calculate Tax <date> e.04. Field Name Bline Date Description Baseline Date for Due Date Calculation User Action and Values <for example Today’s date> e.04.2010> e.g.SAP Best Practices In-House Cash (801): BPD subsidiary_2 a customer invoice for subsidiary_1. <15.

15. 16. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP menu Transaction code SAP Business All-in-One Subsidiary System Accounting  Financial Accounting  Accounts Receivable  Document Entry  Invoice FB70 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Receivable Accountant –FI Only (SAP_NBPR_AR_FI_ONLY-S) Accounts Receivable  Posting  Invoice  Enter Outgoing Invoices When you call up the transaction for the first time.g. Then choose Continue. The system may prompt you with an Information dialog box that a down payment exists. a dialog box appears for you to enter the company code. 14. To check the document before it is posted. Choose Post (Ctrl+S). Result The customer invoice is posted and the G/L account and customer transaction figures are updated.SAP Best Practices In-House Cash (801): BPD 13. choose Edit → Change Company Code. including the tax on sales/purchases to be posted. the system generates the message: Document 18000000xx was posted in company code 1000. where xx is the sequential document number posted by the system. 17.10> <EUR> For example today’s date enter enter enter enter © SAP AG Page 10 of 105 .g. On the Basic Data tab page on the Enter Customer Invoice: Company Code 1000 screen. enter the following data. choose Simulate (F9). <15. Make a note of the invoice document number for later use in “Post Vendor Invoice”. In the lower area of the screen. To change the company code in the transaction. Field Name Customer Description External Customer in subsidiary_1 User Action and Values <customer number> e. <SUB_CUSTOM> Comment The customer we need for external incoming payments enter Invoice Date Reference Amount Currency <date> e. This enables you to display the document. and to correct it if necessary. Enter company code.2010> <any reference> <1. Confirm the Information dialog box by choosing Enter.04.

Confirm the Information dialog box by choosing Enter. In the lower area of the screen. To check the document before it is posted. 21. Enter the following data for the line item: Field Name G/L acct D/C Amount in Document Currency Debit/Credit Description User Action and Values <500000> <Credit> <1.g.g. Choose Post (Ctrl+S).04. This enables you to display the document. <0001> empty select Comment Check date enter Payt terms Pmt Method 19.SAP Best Practices Calculate Tax mark In-House Cash (801): BPD Based on the previously posted down payment the system reacts with a message about the existing amount of down payments. <500000> Enter the order number noted from transaction KO01 Comment enter select If profit centers exist they should also be entered in field Profit Center. enter Tax Code <A1> For example A1 (19% tax on sales/purchases) select Order e. choose Simulate (F9). the system generates the message: Document 18000000xx was posted in company code 1000. Field Name Bline Date Description Baseline Date for Due Date Calculation User Action and Values <for example Today’s date> e. enter the following data. The system may prompt you with an Information dialog box that a down payment exists. In this case scroll to the right to fill in the field. 18. 20.2010> e. including the tax on sales/purchases to be posted. The system calculates the output tax automatically.10> Enter the gross amount. where xx is the sequential document number posted by the system. Confirm this message with Continue (Enter). and to correct it if necessary. <15.g. © SAP AG Page 11 of 105 . On the Payment tab page on the Enter Customer Invoice: Company Code 1000 screen.

: for internal deliveries = e.g.g. Refer document for this.g. <today’s date> (*) enter Enter the document number from the “Posting a Customer © SAP AG Page 12 of 105 .SAP Best Practices In-House Cash (801): BPD Result The customer invoice is posted and the G/L account and customer transaction figures are updated.: delivery from subsidiary_2 to subsidiary_1. the open items for payables must be available in the subsidiary system. For external payments. Vendor is subsidiary_2. 2. Create a vendor invoice in subsidiary_1. 2. E. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → Document Entry → Invoice FB60 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable → Posting → Invoices → Enter Vendor Invoice w/o PO Reference 2. For internal payments. Create a vendor invoice in subsidiary_1.g. You can also post invoices in FI for other than materials like expenses for example as explained below. On the Enter Vendor Invoice screen.g. Use You receive the invoice from the vendor/subsidiary and post it in the system. make the following entries: Field name Vendor Description Subsi_2 is vendor in subsidiary_1 and created a customer invoice for subsi_1 in subsidiary_2 User action and values e. E. <SUBSI_2> Comment Refer Master Data enter Invoice Date Reference e. Procedure 1.: delivery from external vendor to subsidiary_1. These invoices need to be posted for material with purchasing. Vendor Invoices for material are posted in materials module.2 Post Vendor Invoice To run through this scenario.3. We need 2 vendor invoices: 1. Many vendor invoices are posted with logistics.

Enter following data: Field name G/L Account D/C Amount in Document Currency Tax Code Description User action and values <680000> <Debit> <11. V1 = 19% for Germany select enter Text <Internal Delivery/Payment> 3. For further processing.g. V1 = 19% (Germany) select Cost Center e. for example.900> <EUR> mark <V1> enter enter domestic input tax. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → © SAP AG Page 13 of 105 . Result The invoice for internal payments has been posted.SAP Best Practices In-House Cash (801): BPD Invoice in Accounting” Customer invoice created in subsidiary_2 with customer subsi_1. <1801> Select a valid cost center 5. On the Enter Vendor Invoice screen. make a note of the document number. choose payment. enter <V1> domestic input tax.only when internal payments Amount Currency Calculate tax Tax Code <11. 4. . Choose Post (Ctrl + S). for example. Procedure 1.900> Comment enter select Gross amount.

861> <EUR> mark <V1> domestic input tax. for example.SAP Best Practices Document Entry → Invoice Transaction Code FB60 In-House Cash (801): BPD Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable→ Posting → Invoices → Enter Vendor Invoice w/o PO Reference 3. On the Enter Vendor Invoice screen.g. <SUB_VENDOR> e.g.861> enter select Gross amount. we use the payment method from master data (vendor). enter <V1> domestic input tax. On the Enter Vendor Invoice screen. G/L Account D/C Amount in Document Currency Tax Code <680000> <S Debit> <1.g. <1801> Select a valid cost center © SAP AG Page 14 of 105 . Enter following data: Field name Pmt Method Description External Payment User action and values <4> Comment Select If field Pmt Method empty. <today’s date> <any reference> <1. V1 = 19% for Germany select Text <External Delivery / Payment> enter Comment Refer Master Data enter enter enter enter enter 4. 5. choose payment. V1 = 19% (Germany) select Cost Center e.g. make the following entries: Field name Vendor Invoice Date Reference Amount Currency Calculate tax Tax Code Description Vendor in subsidiary_1 User action and values e. for example.: for external deliveries e.

In-House Cash (801): BPD Result The invoice for external payments has been posted.g. Use Enter a vendor invoice with foreign currency for payment to a other clearing center in the headquarters Procedure 1. <today’s date> <any reference> <1. make the following entries: Field name Vendor Description Vendor in subsidiary_1 with foreign currency. Choose Post (Ctrl + S). User action and values e. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → Document Entry → Invoice FB60 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable→ Posting → Invoices → Enter Vendor Invoice w/o PO Reference 7.g <FW_VENDOR> Comment Refer Master Data enter Invoice Date Reference Amount Currency Calculate tax Tax Code Text e.g. For additional clearing center.866> <JPY> mark <V0> <Payment with foreign currency – clearing center> enter enter enter enter No tax procedure select enter © SAP AG Page 15 of 105 .: for external deliveries e. For further processing. On the Enter Vendor Invoice screen.SAP Best Practices 6. make a note of the document number.

3 Post Vendor Invoice – external payment by check To run through this scenario. G/L Account D/C Amount in Document Currency Tax Code Cost Center <680000> <S Debit> <1. For further processing. Choose Post (Ctrl + S). Vendor Invoices for material are posted in materials module.3. You can also post invoices in FI for other than materials like expenses for example as explained below. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → Document Entry → Invoice © SAP AG Page 16 of 105 . we use the payment method from master data (vendor). Use You receive the invoice from the vendor and post it in the system. <1801> No tax procedure select Select a valid cost center 10. Result The invoice for external payments –foreign currency. 9.g.866> enter select Gross amount. 2. choose payment. Procedure 1. These invoices need to be posted for material with purchasing.SAP Best Practices 8. make a note of the document number.has been posted. On the Enter Vendor Invoice screen. Enter following data: Field name Pmt Method Description External Payment In-House Cash (801): BPD User action and values <4> Comment Select If field Pmt Method empty. enter <V0> e. Many vendor invoices are posted with logistics. Refer document for this. the open items for payables must be available in the subsidiary system.

SAP Best Practices Transaction Code FB60 In-House Cash (801): BPD Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable → Posting → Invoices → Enter Vendor Invoice w/o PO Reference 2. today’s date enter Enter the document number from the “Posting a Customer Invoice in Accounting” . On the Enter Vendor Invoice screen. <SUB_VENDOR> <date> e.only when internal payments Amount Currency Calculate tax Tax Code <1.862> Comment select enter select Gross amount.: for external deliveries e. for example. <today’s date> Reference empty Comment Refer Master Data enter for example. V1 = 19% for Germany select Text <External Delivery / Payment by Check> enter enter enter 3. On the Enter Vendor Invoice screen. make the following entries: Field name Vendor Invoice Date Description Vendor in subsidiary_1 User action and values e. choose Payment: 4. V1 = 19% (Germany) select © SAP AG Page 17 of 105 . Enter the following data: Field name Pmt Method G/L Account D/C Amount in Document Currency Tax Code Description Payment method for checks User action and values <7> <680000> <Debit> <1. enter <V1> domestic input tax.g.862> <EUR> mark <V1> domestic input tax.g.g. for example.

g. or users. The roles in this Business Process Documentation must be assigned to the user. Prerequisites The business roles have been assigned to the user who is testing this scenario in the subsidiary system: Business Role Payable Accountant Technical Name SAP_NBPR_AP_CLERK-S Process Step Posting vendor data Posting Customer data Processing bank data Payments to house bank Internal Orders Payments Receivable Account-FI Only SAP_NBPR_AR_FI_ONLY-S Bank Accountant Treasurer Enterprise Controller Treasurer BNI SAP_NBPR_BANKACC-S SAP_NBPR_TREASURER-S SAP_NBPR_CONTROLLERM SAP_NBPR_TREASURERBNI-S © SAP AG Page 18 of 105 . Choose Post (Ctrl + S). make a note of the document number 2. You do not need these roles if you are using the standard SAP GUI. You only need these roles if you are using the NWBC interface within the SAP Business All-in-One system. For further processing. You do not need these roles in your headquarters’ system.4 Use Roles The following roles must already have been installed in order to test this scenario in the SAP NetWeaver Business Client (NWBC).SAP Best Practices Field name Cost Center Description In-House Cash (801): BPD User action and values e. <1801> Comment Select a valid cost center 5. testing this scenario. Result The invoice has been posted.

SAP Best Practices In-House Cash (801): BPD 3 Process Overview Tables The 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. Subsidiary Post process Bank Statement When Transaction FEBP has been completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: Are there any errors. © SAP AG Page 19 of 105 .1 Internal Payments Process Step Subsidiary Automatic Payment Transaction Business Condition Prerequisite: open items Business Role Accountant Payables Transaction Code F110 Expected Results Data Medium is created and sent to other system – HeadquartersIDoc: PAYEXT Headquarters Post Payment Orders IHC0 Post Payment Order from Subsidiary Headquarters Check account statements Headquarters Create Bank Statement Payment Order is posted F9K3 -optionalF9N7 Account statements exist 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). Attention: This is a task for each subsidiary (Payee and payer). 3.

Check with transaction F8BT that payment request is created.SAP Best Practices In-House Cash (801): BPD 3.2 External Outgoing Payments Process Step Subsidiary Automatic Payment Transaction Business Condition Prerequisite: open items Business Role Accountant Payables Transaction Code F110 Expected Results Data medium is created and sent to other system – HeadquartersIDoc: PAYEXT Headquarters Post Payment Orders IHC0 Post Payment Order from Subsidiary Output: IDoc: PAYEXT – created A “Payment Request” is created. Headquarters Check account statements Headquarters Create Bank Statement Payment Order is posted F9K3 -optionalF9N7 Account statements exist IDoc – FINSTA – Bank Statements for Subsidiary Sent “Bank Statements” to Subsidiary Headquarter Automatic Payment Transaction for Payment Requests Headquarter Check data medium Subsidiary Post Bank Statement Subsidiary Post process Bank Statement IDoc – FINSTA available Accountant Bank F111 Data Medium for House Bank created FDTA -optionalFEBP Select Bank Statements Data Medium should exist Post Bank Statements Clearing Account – Debit/Credit IHC When Transaction FEBP completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: Are there any errors © SAP AG Page 20 of 105 .

3 External Outgoing Payments by Check Process Step Subsidiary Automatic Payment Transaction Business Condition Prerequisite: open items Business Role Accountant Payables Transaction Code F110 Expected Results Data medium is created and sent to other system – HeadquartersIDoc: PAYEXT Headquarters Post Payment Orders IHC0 Post Payment Order from Subsidiary Output: IDoc: PAYEXT – created A “Payment Request” is created.SAP Best Practices In-House Cash (801): BPD 3. Check with transaction F8BT that payment request is created. Headquarters Check account statements Headquarters Create Bank Statement Payment Order is posted F9K3 -optionalF9N7 Exist account statements IDoc – FINSTA – Bank Statements for Subsidiary Sent “Bank Statements” to Subsidiary Headquarter Automatic Payment Transaction for Payment Requests Headquarter Subsidiary Post Bank Statement Prüfen ob Check erstellt ist IDoc – FINSTA available Accountant Bank F111 Outgoing check created FEBP Select Bank Statements Post Bank Statements Clearing Account – Debit/Credit IHC Subsidiary Post process Bank Statement When Transaction FEBP completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: There are any errors © SAP AG Page 21 of 105 .

SAP Best Practices Process Step Business Condition Business Role In-House Cash (801): BPD Transaction Code Expected Results 3.4 Incoming Payments and Cash Pooling Process Step Headquarters Automatic Payment Transaction Business Condition Prerequisite: open items in Subsidiary Business Role Transaction Code FF_5 Expected Results Process data medium from House Bank Data Format : MT940 Headquarters Post Payment Orders IHC0 Post Payment Order from House Bank Headquarters Check account statements Headquarters Create Bank Statement Payment Order is posted F9K3 -optionalF9N7 Exist account statements IDoc – FINSTA – Bank Statements for Subsidiary Sent “Bank Statements” to Subsidiary Subsidiary Post Bank Statement IDoc – FINSTA available Accountant Bank FEBP Select Bank Statements Post Bank Statements Subsidiary Post process Bank Statement When Transaction FEBP completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: There are any errors © SAP AG Page 22 of 105 .

SAP Best Practices In-House Cash (801): BPD 3. 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).5 External Payments with Foreign Currency to another Clearing Center Process Step Subsidiary Automatic Payment Transaction Business Condition Prerequisite: open items Business Role Accountant Payables Transaction Code F110 Expected Results Data Medium is created and sent to other system – HeadquartersIDoc: PAYEXT Headquarters Post Payment Orders IHC0 Post Payment Order from Subsidiary Headquarters Check account statements Headquarters Create Bank Statement Payment Order is posted F9K3 -optionalF9N7 Account statements exist IDoc – FINSTA – Sent “Bank Statements” to Subsidiary Bank statements for Headquarters created Headquarters Post Bank Statement IDoc – FINSTA available Accountant Bank FEBP Select Bank Statements Post Bank Statements Headquarters Post process Bank Statement When Transaction FEBP has been completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: Are there any errors. Subsidiary Post process Bank Statement When Transaction FEBP has been completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: Are there any © SAP AG Page 23 of 105 .

Attention: This is a task for each subsidiary (Payee and payer).SAP Best Practices Process Step Business Condition Business Role In-House Cash (801): BPD Transaction Code Expected Results errors. Subsidiary Post process Bank Statement When Transaction FEBP has been completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: Are there are any errors.6 Internal Returns Process Step Headquarters Reverse Payment Orders Business Condition Business Role Transaction Code IHC0 Expected Results Reversed Payment Order from Subsidiary Headquarters Check account statements Headquarters Create Bank Statement Payment Order is posted F9K3 -optional- Account statements exist Posting Text: Canceled 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). 3. Attention: This is a task for each subsidiary (Payee © SAP AG Page 24 of 105 .

Payment request is cleared Clearing document number from transaction F8BT FB08 Business Condition Business Role Transaction Code F8BT Expected Results Cleared payment request: clearing document number is available Reversed clearing document from payment request Payment request is cleared F8BW Reversed payment order from subsidiary Exist account statements Posting Text: Canceled 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). Attention: This is a task for each subsidiary (Payee © SAP AG Page 25 of 105 .SAP Best Practices Process Step Business Condition Business Role In-House Cash (801): BPD Transaction Code Expected Results and payer). 3.7 External Returns Process Step Headquarters Display Payment Requests Headquarters Reverse Document Headquarters Reverse Clearing of Payment Request Headquarters Reverse Payment Order Headquarters Check account statements Headquarters Create Bank Statement Payment Order is posted F9K3 -optionalIHC0 When F111 is done. Subsidiary Post process Bank Statement When Transaction FEBP completed FEBA_BANK_STATEMENT -optional- Edit Bank statement Check: Are there any errors.

SAP Best Practices Process Step Business Condition Business Role

In-House Cash (801): BPD Transaction Code Expected Results
and payer).

3.8 End-of Day Processing
Process Step
Headquarters End-of-Day Processing

Business Condition

Business Role

Transaction Code
F9N11

Expected Results
Transfer transaction data from IHC to FI. All transactions are posted in the Financial Accounting. Status of Report should be “ Completed”

Headquarters Status Overview of Reports in End of Day Processing Headquarters Spool Requests

F9N10

Check Own Spool Requests

Headquarters Status message types

F961

Check message types

© SAP AG

Page 26 of 105

SAP Best Practices

In-House Cash (801): BPD

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 Use
The purpose of this activity is to create internal payments between the subsidiaries.

Creation of Payment Media Using Classical Payment Medium Program

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

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → Periodic Processing → Payments F110

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable → Posting → Payments → Automatic Payment

© SAP AG

Page 27 of 105

SAP Best Practices

In-House Cash (801): BPD

2. On the Automatic payment transactions: Status screen, make the following entries: Field name Run Date Identification
freely define the identification

Description

User action and values e.g. <today’s day> e.g. <26.03.2010> e.g. <IP_01>

Comment enter enter

3. Choose Parameter. 4. On the Automatic payment transactions: Parameter screen, make the following entries: Field name Posting Date Docs Entered Up To Company Code Pymt Meths Next p/date Payment Methods Posting Date of the next Payment Date Description User action and values e.g. <today’s day> e.g. <26.03.2010> e.g. <today’s day> e.g. <26.03.2010> e.g. <1000> <3 IHB-Transfer internal> e.g. <30.03.2010> enter select 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 Due date check Payment method selection in all cases Pmnt method selection if not successful Line items of the payment documents Vendors (from/to) Description User action and values mark mark empty mark <Vendors> e.g. <SUBSI_2> Enter optional Comment enter Comment enter

© SAP AG

Page 28 of 105

On the Schedule Payment screen. Check the selection of your document © SAP AG Page 29 of 105 . Choose payment log. choose Edit Proposal (Shift+F4) or Display Proposal (Shift+F9) and confirm the following screen (selection of accounting clerks) by pressing Continue (Shift+F1).SAP Best Practices In-House Cash (801): BPD 6. 12. Choose Save (Ctrl+S). The number of generated and completed posting orders is displayed. this will be shown on the Status screen. Choose Proposal (Shift+F1). 20. select 7. To maintain or display the payment proposal. Choose – for more than one time . 8. Confirm the dialog box. As soon as the payment run has been finished. As soon as the proposal has been created. 14. this will be shown on the screen Automatic payment transactions: Status. 19. 17. Choose Status. Choose Schedule (Enter). 16. 10. On the Schedule Proposal screen. 15. make the following entries: Field name Start immediately Description User action and values mark Comment 11. The message Proposal run has been scheduled appears.Status (Shift+F2) to update the status 13. Choose Status (Shift+F2) more than once to update the status. Choose Schedule Payment run (F7). Payments. 9. Choose Schedule (Enter). Choose Back (F3). Choose Printout/data medium and make following entries: Field name Program Description User action and values RFFOEDI1 Comment Payment media program RFFOEDI1 select Variant <Internal> Standard internal The variant has been created in configuration guide. make the following entries: Field name Start immediately Create Payment Medium Description User action and values mark mark Comment 18. The message Payment run has been scheduled appears.

2 Use Post Payment Orders The purpose of this activity is to post the payment order from the subsidiary. Choose Continue (Enter) to execute the list. The Recipient Bank Number is: ‘88888888’ © SAP AG Page 30 of 105 .Transaction Type: INTPAY Note the “Payer Account Number” and “Recipient Account Number” for the steps: Display Bank Accounts and Create Bank Statement. <2010> Comment select enter current year 3. select the line(s): .1. which will execute payment. To do so.Description of Status: Flagged for Posting . Result The invoices have been paid taking a cash discount into account and posted to the bank clearing accounts.SAP Best Practices In-House Cash (801): BPD 21. In the Selected Payment Orders. Access the transaction choosing one of the following navigation options SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account Management → IHC Payment Orders → Payment Order Browser IHC0 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Payment Order Browser 2. The IDoc generated has been sent to the In-House Cash Center. On the Browser for IHC Payment Order screen. make the following entries: Field name Bank Area Year Description User action and values <IHB> e. choose Edit → Payments → Payment List or Edit → Payments → Exception List. choose Select IHC Payment Orders. 4. On the Browser for IHC Payment Orders screen.g. In addition you can create the payment list and the exception list. Procedure 1.

Subsidiary_1 and Subsidiary_2. Result The 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. for subsidiary_1 <1101004901> and subsidiary_2 Comment select Enter “Payer Account Number” used for “Post Payment Order” + Internal Payments “Recipient Account Number” © SAP AG Page 31 of 105 .1. Procedure 1.g. Choose Post. Access the transaction choosing one of the following navigation options Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account → Display F9K3 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Account 2. There should be account statements for both companies.SAP Best Practices 4. Payment order IHB/0000000069/2010 has been finally posted . Choose the Payment Order tab page. The selected payment orders have been posted in the In-House Cash Center. 5. On the Bank Accounts Display: Initial screen.transaction IHC0. 4. make the following entries: Field name Bank Area Account number Description User action and values <IHB> <Bank Account Number> e.3 Use Display Bank Accounts (optional) The purpose of this activity is to check the posted accounts. In-House Cash (801): BPD Note the “Payment Order” for step – Internal Returns.

1. When there are internal payments. Account Number from the Vendor and Post Date for transaction F9N7. 4. Subsidary_2. so you must execute this step for Subsidary_1 and Subsidary_2.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values <1102004901> Comment From Transaction IHC0 (before). Choose Current Bank Statement. 4. Result The selected account statements are displayed with the following values: Bank Key (88888888). make the following entries: Field name Bank Area Account Number Description User action and values <IHB> <bank account number> Comment select enter © SAP AG Page 32 of 105 . you must execute this step at least twice.4 Use Create Bank Statement The purpose of this activity is to create bank statements for subsidiaries.g. Access the transaction choosing one of the following navigation options Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Bank Statement → New Run → Single Run F9N7 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Bank Statement . Procedure 1. When in subsidiary_1 there are open Bank Statements for e.Single Account 2. 5. On the Create One Single bank Statement on Request screen. For all internal payments. Prerequisites The subsidiaries have made internal payments to the headquarters. Amount. There will be created Bank Statement for both subsidiaries. 3. perform this transaction for the “Payer Account” and for the “Recipient Account”. Choose Enter. Choose the Account Statements tab page.

payee and payer. Procedure 1. Statement Without Turnovers With Address 3.5 Use Post Bank Statement The purpose of this activity is to post the bank statement that was created in headquarters for subsidiaries. for subsidiary_1 <1101004901> and subsidiary_2 <1102004901> Comment Statement Date <Date> Post Day from “Post Payment Order” You can see it with transaction F9K3 – too. The system displays a screen with the address. Result The banks statements for subsidiaries have been created and an IDoc is sent to the subsidiaries system.g. an FAS IDoc is created” appears.1. bank account. Choose Enter. empty mark The message “For account ‘999999999’. bank area IHB. this indicator must not be set. For this case. amount and posting date. Choose Execute (F8). Selection date must be before or on the current posting date Simulation Run Standard Output empty empty If this indicator is set. Access the transaction choosing one of the following navigation options: © SAP AG Page 33 of 105 . the bank statement is output in standard form. This is a task for each subsidiary. 4.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values e. 4.

: <IHEUR> 5. make the following entries: Field name Post immed.g. On the Update Bank Statement screen. Assign Value Date Account Description User action and values mark mark Comment House Bank Account ID e.2010> Comment Enter date.03.g. Or you can select in detail and the Bank Statement will only processed for these choice: Field name Statement Date Description User action and values <date> e. where the Bank Statements created in Headquarter (WithTransaction F9K3 you can see the Posting Date in HQ) select Select The Company Code appears too Currency e. <01. all not processed bank statements will processed 3. in the area Output Control. On the Update Bank Statement screen.SAP Best Practices Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code In-House Cash (801): BPD SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post Electronic Bank Statement 2. make the following entries: © SAP AG Page 34 of 105 .: <IHB> e.g. On the Update Bank Statement screen. <EUR> Only Bank Statements with currency EUR enter 4. in the area Bank Statements.g. in the area Posting Params. make the following entries: Field name *all Description When all fields empty – processed all open bank statements User action and values Comment When there is no selection (choice).

Access the transaction choosing one of the following navigation options: © SAP AG Page 35 of 105 . Choose Back (F3) There appears a message “Processing Completed” Posting in subsidiary_1 (payee) account 479901(debit) – account 479900(credit). Subsidiary_1: IND – and subsidiary_2: INC + Account 479900 is the bank account against headquarters. Procedure 1. mark mark Result The bank statements are posted in the subsidiary.6 Use Post process Bank Statement (optional) The purpose of this activity is to edit bank statements that contain errors. 4. payee and payer. Posting in subsidiary_2 (recipient) account 479900(debit) – account 479901(credit). Choose Execute.1.SAP Best Practices Field name Execute as background Job Print Bank Statements Print Posting Log Description In-House Cash (801): BPD User action and values empty Comment The job is working on the screen List of the Bank Statements Posted Bank Statements in the subsidiary mark mark Print Statistics Separate List 6. The transactional code is IND – : outgoing internal payments and INC + : incoming internal payments. There appears a message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’. This is a task for each subsidiary. In this case: subsidiary_1 has a liability against headquarters and subsidiary has a credit against headquarters.

4. Select the errors that are red. Choose Save. On the Edit Bank Statement screen: open IHB -> open IHEUR . make the following entries: Field name House Bank Account ID 3. © SAP AG Page 36 of 105 . 6. 5.SAP Best Practices Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code In-House Cash (801): BPD SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Postprocessing Bank Statement 2. 7. Description User action and values <IHB> <IHEUR> Comment select select Result The errors have been corrected in the subsidiary system. On the Selection of Bank Statements by Banks and Account Nos. Choose Execute. Change the error and post again.

On the Automatic payment transactions: Parameter screen. make the following entries: Field name Run Date Identification Freely define the identification Description User action and values e. <26. <26. Creation of Payment Media Using Classical Payment Medium Program Prerequisites There are open items in the subsidiary for external payments.g.2010> e.g.03. <today’s date> e.2010> e.g. <26. On the Automatic payment transactions: Status screen. <EP_01> enter Comment enter 3.SAP Best Practices In-House Cash (801): BPD 4.g. 4. <today’s date> e. <today’s date> e.03.2. Procedure 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → Periodic Processing → Payments F110 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable → Posting → Payments → Automatic Payment 2. Choose Parameter.g.2 Process Steps – External Outgoing Payments 4.2010> <1000> <4 IHB-Transfer enter select enter Comment enter © SAP AG Page 37 of 105 .g.1 Use The purpose of this activity is to create external payments in the subsidiary for the headquarters.g.03. External payments are defined in the vendor’s master data view Payment Transactions Accounting and the field Payment method. make the following entries: Field name Posting Date Docs Entered Up To Company Code Pymt Meths Payment Methods Description User action and values e.

<sub_vendor> to e.2010> the day of the next posting date you want to run Only you want certain vendor Enter Otherwise: ‘’*’ enter Vendor e. Choose Additional Log and make the following entries: Field name Due date check Payment method selection in all cases Pmnt method selection if not successful Line items of the payment documents Vendors (from/to) Description User action and values mark mark empty mark <Vendors> e. Choose Save (Ctrl+S).<30. Choose Status. Enter optional Comment © SAP AG Page 38 of 105 . <sub_vendor> Vendor.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values external> Comment Next p/date Posting Date of the next Payment e. Make the following entries: Field name Program Variant Description User action and values RFFOEDI1 <Internal> Comment Payment media program RFFOEDI1 Standard internal Use the variant created in the configuration guide for this building block (step Create Variant for Payment Run F110). select 8. Choose Printout/data medium.g.03. 7.g. if you select an interval Enter Otherwise: empty 5.g.g. <sub_vendor> 6. 9.

© SAP AG Page 39 of 105 . To find out the DME reference numbers. The number of generated and completed posting orders is displayed. The message Payment run has been scheduled appears. Make a note of the reference number (Data Medium tab page) for the domestic payment (YB_F110_D_UEBERW). Choose Schedule Payment Run (F7). choose Edit → Payments → Payment List or Edit → Payments → Exception List. You will need these later for the manual account statement. On the Schedule Proposal screen. As soon as the proposal has been created. 17. 13. Make a note of the DME reference numbers (YB_F110_D_UEBERW). Choose Schedule (Enter). Check the selection of your document 23. On the Schedule Payment screen. Choose payment log Payments. 21. As soon as the payment run has been finished. In addition you can create the payment list and the exception list. 22. 16. The message Proposal run has been scheduled appears. choose Edit Proposal (Shift+F4) or Display Proposal (Shift+F9) and confirm the following screen (selection of accounting clerks) by pressing Continue (Shift+F1). Confirm the dialog box. Choose Back (F3). The IDoc generated has been sent to the In-House Cash Center. this will be shown on the screen Automatic payment transactions: Status. Choose Schedule (Enter). make the following entries: Field name Start immediately Description User action and values mark Comment 12.Status (Shift+F2) to update the status 14. Choose – for more than one time . 18. this will be shown on the Schedule Payment screen. you can display its attributes. Choose Continue (Enter) to execute the list.SAP Best Practices 10. 20. make the following entries: Field name Start immediately Create Payment Medium Description User action and values mark mark Comment 19. Choose Status (Shift+F2) more than once to update the status. Choose Proposal (Shift+F1). To maintain or display the payment proposal. Result The invoice has been paid taking a cash discount into account and posted to the bank clearing accounts. By double-clicking the data medium. 15. To do so. In-House Cash (801): BPD 11. which will execute payment. go to DME Administration by choosing Environment → Payment Medium → DME Administration.

transaction IHC0.2 Use Post Payment Orders The purpose of this activity is to post the payment order from the subsidiary. choose Select IHC Payment Orders. Access the transaction choosing one of the following navigation options: SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account Management → IHC Payment Orders → Payment Order Browser IHC0 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Payment Order Browser On the Browser for IHC Payment Orders screen. Choose Post.Description of Status: Flagged for Posting . On the Browser for IHC Payment Order screen.2.g. The Recipient Bank Number is <> ‘88888888’ 2. select the line(s): . 3. In the Selected Payment Orders.Transaction Type: EXTPAY Note the “Payer Account Number” for the steps: Display Bank Accounts and Create Bank Statement. Procedure 1.SAP Best Practices In-House Cash (801): BPD 4. <2010> Comment select enter current year 1. Choose the Payment Order tab page. Note the “Payment Order” for step – Internal Returns. make the following entries: Field name Bank Area Year Description User action and values <IHB> e. © SAP AG Page 40 of 105 .

SAP Best Practices In-House Cash (801): BPD Result The system issues one of the following messages: • • • Payment order IHB/0000000069/2009 is being checked (the number of the selected payment order is displayed) No error was found. Payment order IHB/0000000069/2009 has been finally posted . 5. 4. make the following entries: Field name Bank Area Account number Description User action and values <IHB> <Bank Account Number> e.2. Choose Enter. 4. On the Bank Accounts Display: Initial screen.g. The selected payment orders have been posted in the In-House Cash Center. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account → Display F9K3 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Account 2. Choose Current Bank Statement. Select the Account Statements tab page. Comment select Enter “Payer Account Number” used for “Post Payment Order” From transaction IHC0 (before) © SAP AG Page 41 of 105 . Procedure 1. for subsidiary_1 <1101004901> 3.3 Use Display Bank Accounts (optional) The purpose of this activity is to check the posted accounts.

You see the external bank accounts with the open amount. Amount. you must execute this step for subsidary_1.2.Single Account 2. Procedure 1.g. Account Number from the Vendor and Post Date for transaction F9N7. When the next step – Create Bank Statement – for this account is done. make the following entries: Field name Bank Area Account Number Description User action and values <IHB> <bank account number> e.4 Use Create Bank Statement The purpose of this activity is to create bank statements for subsidiaries. When in subsidiary_1 there are open bank statements for external payments. On the Create One Single Bank Statement on Request screen. Prerequisites The subsidiaries have made internal payments to the headquarters. 4.SAP Best Practices In-House Cash (801): BPD 6. 7. for subsidiary_1 <1101004901> Statement Date <Date> Post Day from “Post Payment Order” Comment select Enter payer account number © SAP AG Page 42 of 105 . Result The selected account statements are displayed with the following values: Bank Key (88888888). Choose Back (F3). On this screen. there will be no “Current Bk Statement” for this account. you can check the open bank statement from this bank account. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Bank Statement → New Run → Single Run F9N7 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Bank Statement .

an FAS IDoc is created” appears.5 Use Automatic Payment Transaction for Payment Requests The purpose of this activity is to create a payment medium for the house bank. 4. the payments are not based on open items (FI documents) but on payment requests. Statement Without Turnovers With Address 3. Prerequisites There are open payment requests. empty select The message “For account ‘999999999’. Procedure 1. Selection date must be before or on the current posting date Simulation Run Standard Output empty empty If this indicator is set. amount.2. the bank statement is output in standard form. Choose Execute. You can use this payment program to make payments to vendors or between G/L accounts. bank area IHB. Result The 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. 4. Choose Enter. For this case. Unlike the standard payment program. bank account. and posting date. this indicator must not be set. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) © SAP AG Page 43 of 105 .SAP Best Practices Field name Description In-House Cash (801): BPD User action and values Comment You can also display it with transaction F9K3.

g. Choose Parameter. On the Automatic payment transactions: Status screen. <today day> e.g. On the Automatic payment transactions: Parameter screen.g.03.g.g. Should be the latest number. make the following entries: Field name Run Date Identification Freely define the identification Description User action and values e. You will need this later for the reversal. Make the following entries: Field name Key number Description User action and values <> e. <1000> <Y> select Bank Transfer (Outgoing) select Comment enter © SAP AG Page 44 of 105 . <PR_01> Comment enter enter 3. <30.03. Choose Dynamic selections.SAP Best Practices SAP System SAP ECC Menu Transaction Code SAP Headquarters’ System In-House Cash (801): BPD Accounting → Financial Accounting → Banks → Outgoing → Automatic Payment → Payment Requests F111 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER-S) Cash Management → Cash Management → Planning → Automatic Payment of PRequest 2. 6.: <42> Comment Key number payment request from: Use transaction F8BT to display all open payment requests. make the following entries: Field name Posting Date Next p/date Next Posting Date for the next payment run Description User action and values e. <today’s date> e. 4.2010> e.2010> the day of the next posting date you want to run enter Company code Payment methods 5. Make a note of the payment request number. <26.g.

g. Choose Continue. Make the following entries: Field name Payment method selection in all cases Line items of the payment documents Due date check 10. 18. Choose Status (Shift+F2) more than once to update the status. make the following entries: Field name Report Program Variant 13. © SAP AG Page 45 of 105 . 8. <1000> e. Choose Save (Ctrl+S). Choose Additional Log. 14. 15. Choose Payment medium. Description <> e. make the following entries: Field name Start immediately Create Payment Medium Description User action and values mark empty Comment Description User action and values „RFFOEDI1“ “EXTERNAL” select Comment 17. 14. On the Automatic Payment Transactions: Print Programs screen.:: <42> e.g. Choose Save (Ctrl+S). On the Schedule Proposal screen. Choose Enter. Choose Continue 13.g. There appears a pop_up with the message “Log created for all accounts” 12. <DISB> In-House Cash (801): BPD Key number payment request till: select select User action and values mark Comment mark empty 11. Choose Save. 9. Choose Proposal 16. The message Proposal is running appears.SAP Best Practices To House Bank Account ID 7.

2. this will be shown on screen and the message Payment run has been carried out appears 24. User action and values mark mark Comment 22. The FI document that was created contains two line items.SAP Best Practices In-House Cash (801): BPD As soon as the proposal run has been finished. The generated payment medium files can now be sent to the bank. 23. Procedure © SAP AG Page 46 of 105 .6 Use Check Output Data Medium – optional - The purpose of this activity is to check whether the payment medium is created. Result The payment document and the payment medium have been created. The message Payment run is running appears. Prerequisites Job Automatic Payment Transaction for Payment Requests is done. this will be shown on screen and the message Payment proposal has been created appears. For additional information regarding the payment. Choose payment log Payments to display the executed payments. Choose Enter. which has an account number that ends with the digit 0. which will execute payment. As soon as the payment run has been finished. 26. make the following entries: 22. The other line item has been posted to the clearing account IHC external payments. If there are no errors. 19. On the Schedule Payment screen. Check the selection of your document. 4. For additional information regarding the payment. see F111-menu: System -> Own Spool Requests -> Payment summary ->Display contents (F6). Choose proposal log Proposal. One line item has been posted to the account for outgoing transfers (bank subaccounts ending with character 2 – bank clearing accounts). see F111-menu: Edit –>Payments – > Payment List – Choose Enter. 25. choose Back 21. Choose Status (Shift+F2) more than once to update the status. Schedule payment run by choosing Field name Start immediately Create Payment Medium Description Pmnt run. 20.

To external) Data medium w/out acct stmt Data medium with acct stmt 3. Date created should be “today’s day’.g. For all countries Description User action and values Empty for example. Choose Execute (F8). <today’s date> empty empty select empty select enter enter empty select 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. make the following entries: Field name Reference number Paying company code Bank country Run Date Identification Format Pymt. runs Proposal runs Data medium (not yet transferred externally) Data medium (transmit.SAP Best Practices In-House Cash (801): BPD 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Accounting → Banks → Outgoing → Automatic Payment → Environment → Payment Medium → DME Administration FDTA Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Bank Data → TemSe/REGUT Data Administration 2. On the Automatic payment transactions: Status screen. © SAP AG Page 47 of 105 . <1000> enter Comment “*” e.

On the Update Bank Statement screen.g. all unprocessed bank statements will be processed.2010> Comment Enter date bank statements created in headquarters. in the area Bank Statements. make the following entries: Field name *all Description When all fields empty – processed all open bank statements User action and values Comment When there is no selection. 3. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post Electronic Bank Statement 2. Procedure 1.2.: <IHEUR> Select © SAP AG Page 48 of 105 .7 Use Post Bank Statement The purpose of this activity is to post the bank statement that was created in headquarters for subsidiaries.g. <01.03.: <IHB> Select The company code appears too Account ID e. Or you can select in detail and the bank statement will only be processed for this selection: Field name Statement Date Description User action and values <date> e. With transaction F9K3 you can see the posting date in HQ) enter House Bank e.g.SAP Best Practices In-House Cash (801): BPD 4.

On the Update Bank Statement screen. 4.account 479900 (IHB-account). On the Update Bank Statement screen. Subsidiary_1 has a liability against headquarters. mark mark Result The bank statements are posted in the subsidiary. Choose Execute.g.8 Use © SAP AG Post process Bank Statement (optional) Page 49 of 105 .: <EUR> Only bank statements with currency EUR enter 4.SAP Best Practices In-House Cash (801): BPD The company code appears too Currency e. Choose Back (F3) The message “Processing Completed” appears. . Posting in subsidiary_1 (payee): account 479903 (clearing account / debit) . There appears a message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’”. in the area Output Control. make the following entries: Field name Post immed Assign Value Date Account Description User action and values mark mark Comment 5. make the following entries: Field name Execute as background Job Print Bank Statements Print Posting Log Description User action and values empty mark mark Comment The job is working on the screen List of the bank statements Posted bank statements in the subsidiary Print Statistics Separate List 6. in the area Posting Parms. Transactional code is: 020 -.2.

On the Edit Bank Statement screen: open IHB -> open IHEUR . 7. 5. On the Selection of Bank Statements by Banks and Account Nos. Select the errors that are red.SAP Best Practices In-House Cash (801): BPD The purpose of this activity is to edit bank statements that contain errors. make the following entries: Field name House Bank Account ID 3. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Postprocessing Bank Statement 2. 4. Choose Execute. Choose Save. Description User action and values <IHB> <IHEUR> Comment select select Result The errors have been corrected in the subsidiary system. 4. Procedure 1. 6.3 Process Steps – External Outgoing Payments by Check © SAP AG Page 50 of 105 . Change the error and post again.

Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → Periodic Processing → Payments F110 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable → Posting → Payments → Automatic Payment 2.SAP Best Practices In-House Cash (801): BPD 4.g.g. On the Automatic payment transactions: Parameter screen.1 Use Creation of Payment Media Using Classical Payment Medium Program The purpose of this activity is to create external payments by check in the subsidiary for the headquarters.g.g. <today’s day> e. <29.g. On the Automatic payment transactions: Status screen.g.03.2010> e. <1000> <7 IHB-Check enter enter select Comment enter © SAP AG Page 51 of 105 .3.03. 4.2010> e. make the following entries: Field name Posting Date Docs Entered Up To Company Code Pymt Meths Payment Methods Description User action and values e. <29. <today’s day> e. Choose Parameter. <PS_01> enter Comment enter 3. make the following entries: Field name Run Date Identification Freely define the identification Description User action and values e. Procedure 1. <29. External payments are defined in the vendor’s master data view Payment Transactions Accounting and the field Payment method.2010> e. Prerequisites There are open items in the subsidiary for external payments with payment method: check.g.03.

<sub_vendor> e. Choose Status. <10. <sub_vendor> 6.g. Enter optional Comment 9. Make the following entries: Field name Program Variant Description User action and values RFFOEDI1 <Internal> Comment Payment media program RFFOEDI1 Standard internal Use the variant created in the configuration guide for this building block (step Create Variant for Payment Run F110). Choose Printout/data medium.g. © SAP AG Page 52 of 105 .04.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values external> Comment Next p/date Vendor to Posting date of the next Payment Run e. <sub_vendor> enter enter Vendor. 7. select 8.g. Choose Save Parameters (Ctrl+S). if you select an interval Enter Otherwise: empty 5.g. Choose Additional Log and make the following entries: Field name Due date check Payment method selection in all cases Pmnt method selection if not successful Line items of the payment documents Vendors (from/to) Description User action and values mark mark empty mark <Vendors> e.2010> e.

As soon as the proposal has been created. On the Schedule Payment screen. you can display its attributes. Choose Schedule (Enter). make the following entries: Field name Start immediately Create Payment Medium Description User action and values mark mark Comment 19. 18. To do so. 22. By double-clicking the data medium. Choose Back (F3). Make a note of the DME reference numbers (YB_F110_D_UEBERW). 21.Status (Shift+F2) to update the status 14. The number of generated and completed posting orders is displayed. As soon as the payment run has been finished. 16. 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). Choose payment log Payments. Make a note of the reference number (Data Medium tab page) for the domestic payment (YB_F110_D_UEBERW). Choose – for more than one time . Confirm the dialog box.SAP Best Practices 10. Choose Proposal (Shift+F1). On the Schedule Proposal screen. Result The invoice has been paid taking a cash discount into account and posted to the bank clearing accounts. Check the selection of your document 23. In-House Cash (801): BPD 11. The generated DME files can now be sent to the bank. You will need these later for the manual account statement. In addition you can create the payment list and the exception list. choose Edit → Payments → Payment List or Edit → Payments → Exception List. © SAP AG Page 53 of 105 . Choose Schedule Payment Run (F7). make the following entries: Field name Start immediately Description User action and values mark Comment 12. The message Proposal run has been scheduled appears. To find out the DME reference numbers. 15. which will execute payment. 20. Choose Schedule (Enter). 17. go to DME Administration by choosing Environment → Payment Medium → DME Administration. The message Payment run has been scheduled appears. 13. Choose Continue (Enter) to execute the list. this will be shown on the Schedule Payment screen. Choose Status (Shift+F2) more than once to update the status. this will be shown on the screen Automatic payment transactions: Status.

Choose Post.Description of Status: Flagged for Posting . 8. Choose the Payment Order tab page. 7. select the line(s): . © SAP AG Page 54 of 105 . Procedure 1. In the Selected Payment Orders.3. Access the transaction choosing one of the following navigation options: SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account Management → IHC Payment Orders → Payment Order Browser IHC0 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Payment Order Browser 6.Transaction Type: CHECK Note the “Payer Account Number” for the steps: Display Bank Accounts and Create Bank Statement. Result The system issues one of the following messages: • • • Payment order IHB/0000000069/2009 is being checked (the number of the selected Payment Order is displayed) No error was found. choose “Select IHC Payment Orders”.SAP Best Practices In-House Cash (801): BPD 4.2 Use Post Payment Orders The purpose of this activity is to post the payment order from the subsidiary. The selected payment orders have been posted in the In-House Cash Center. On the Browser for IHC Payment Order screen. Payment order IHB/0000000069/2009 has been finally posted .

make the following entries: Field name Bank Area Account number Description User action and values <IHB> <Bank Account Number> e.SAP Best Practices In-House Cash (801): BPD 4.3 Use Display Bank Accounts (optional) The purpose of this activity is to check the posted accounts. Amount. Choose Current Bank Statement. 7. On this screen. When the next step – Create Bank Statement – for this account is done. there will be no “Current Bk Statement” for this account. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account → Display F9K3 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Account 2. Posting date and Value date. for subsidiary_2 <1102004901> 3.with the open amount -. There should be bank accounts –Check Debit.g.3. Comment select Enter “Payer Account Number” used for “Post Payment Order” enter Result The selected account statements are displayed with the following values: Bank Key. Choose Back (F3). you can check the open bank statement from this bank account. On the Bank Accounts Display: Initial screen. 4. 5. © SAP AG Page 55 of 105 . Choose Enter. Procedure 1. Select the Account Statements tab page. 6.

make the following entries: Field name Bank Area Account Number Description User action and values <IHB> <bank account number> e.g. for subsidiary_1 <1101004901> Statement Date <Date> Comment select Enter payer account number enter Post Day from “Post Payment Order” You can also display it with transaction F9K3.SAP Best Practices In-House Cash (801): BPD 4.4 Use Create Bank Statement The purpose of this activity is to create bank statements for subsidiaries. the bank statement is © SAP AG Page 56 of 105 . you must execute this step for subsidiary_1. When in subsidiary_1 there are open bank statements for external payments. Prerequisites The subsidiaries have made internal payments to the headquarters.Single Account 2. Procedure 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Bank Statement → New Run → Single Run F9N7 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Bank Statement .3. On the Create One Single Bank Statement on Request screen. Selection date must be before or on the current posting date enter Simulation Run Standard Output empty empty If this indicator is set.

3. and posting date. Choose Enter.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values Comment output in standard form. 4.5 Use Automatic Payment Transaction for Payment Requests The purpose of this activity is to create a payment medium for the house bank. the payments are not based on open items (FI documents) but on payment requests. Prerequisites There are open payment requests. Statement Without Turnovers With Address 3. bank account. Choose Execute. 4. bank area IHB. Result The banks statements for subsidiary have been created and an IDoc is sent to the subsidiary system. Procedure 1. For this case. Unlike the standard payment program. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’ System Accounting → Financial Accounting → Banks → Outgoing → Automatic Payment → Payment Requests F111 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role Treasurer (SAP_NBPR_TREASURER-S) Cash Management → Cash Management → Planning → © SAP AG Page 57 of 105 . amount. You can use this payment program to make payments to vendors or between G/L accounts. empty select The message “For account ‘999999999’. this indicator must not be set. an FAS IDoc is created” appears. The system displays a screen with the address.

g. make the following entries: Field name Posting Date Next p/date Company code Payment methods 5. 8.04. Choose Additional Log. <today’s day> e. Choose Parameter. <42> Comment Key number payment request from: Use transaction F8BT to display all open payment requests. 6. On the Automatic payment transactions: Status screen. <DISB> Key number payment request till: select select select Posting date of the next payment run Description User action and values e.g. <today’s day> e. <10. <1000> <S> enter select Outgoing check select Comment enter © SAP AG Page 58 of 105 .g. 4.2010> e.03. Choose Save Parameters (Ctrl+S). <42> House Bank Account ID 7. Make the following entries: Field name Payment method Description User action and values mark Comment for example. <PS_01> enter Comment enter 3. make the following entries: Field name Run Date Identification freely define the identification Description User action and values e.g.2010> e.g.2010> e. On the Automatic payment transactions: Parameter screen. <1000> for example. select To <> e.g.03. <29.g.SAP Best Practices menu In-House Cash (801): BPD Automatic Payment of Request 2.g. 9.g. Choose Dynamic selections. Should be the latest number. Make the following entries: Field name Key number Description User action and values <> e. <29.

this will be shown on screen and the message Payment proposal has been created appears. Choose Save Parameters (Ctrl+S). <today’s day> e. Choose proposal log Proposal. On the Schedule Proposal screen. There appears a pop_up with the message “Log created for all accounts” 12. make the following entries: Field name Report Program Variant 15.g. Choose Payment medium.03. The message Proposal is running appears. Choose Save. If there are no errors.SAP Best Practices selection in all cases Line items of the payment documents Due date check 10. 17. Choose Continue 13. mark In-House Cash (801): BPD empty 11. 14. 22. 16. Choose Proposal 18. <29. Choose Status (Shift+F2) more than once to update the status. Choose Continue. 20.g. On the Automatic Payment Transactions: Print Programs screen. make the following entries: Field name Start Date Start immediately Create Payment Medium Description User action and values e. As soon as the proposal run has been finished. schedule payment run by choosing © SAP AG Page 59 of 105 . Pmnt run. Check the selection of your document.2010> mark empty Comment enter Description User action and values „RFFOD__S“ “CHECK_IHB” select Comment 19. 21. Choose Enter.

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. <29.SAP Best Practices In-House Cash (801): BPD 23. As soon as the payment run has been finished.g. Result The generated payment document can now be sent to the vendor/recipient. see F111-menu: System -> Own Spool Requests -> Payment summary. 29.3.g. On the Schedule Payment screen. make the following entries: Field name Start Date Start immediately Create Payment Medium Description User action and values e. The message Payment run is running appears.03. 25. Choose Enter.6 Use Post Bank Statement The purpose of this activity is to post the bank statement that was created in headquarters for subsidiaries. For additional information regarding the payment. 28. see F111-menu: System -> Own Spool Requests -> Scheck. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role SAP_NBPR_BANKACC_S (Bank Accountant) © SAP AG Page 60 of 105 . For additional information regarding the payment. see F111-menu: Edit –>Payments – > Payment List.2010> mark mark Comment enter 24. Procedure 1. For document check. 27. 4. <today’s day> e. Choose Status (Shift+F2) more than once to update the status.

On the Update Bank Statement screen. where the Bank Statements created in Headquarter (With Transaction F9K3 you can see the Posting Date in HQ) Select The company code appears too Account ID e.g. On the Update Bank Statement screen.SAP Best Practices Business role menu In-House Cash (801): BPD Bank Accounting → Incomings → Post Electronic Bank Statement 2. make the following entries: Field name Post immed Assign Value Date Account Description User action and values select select Comment House Bank e.: <EUR> Only bank statements with currency EUR enter 4. make the following entries: Field name Execute as background Job Print Bank Statements Print Posting Log Description User action and values empty select select Comment The job is working on the screen List of the bank statements Posted bank statements in the © SAP AG Page 61 of 105 .: <IHEUR> Select The company code appears too Currency e.g. in the area Bank Statements. 3. <29.03. all unprocessed bank statements will be processed. Or you can select in detail and the bank statement will only be processed for this selection: Field name Statement Date Description User action and values <date> e.: <IHB> 5.2010> Comment Enter date. make the following entries: Field name *all Description When all fields empty – processed all open bank statements User action and values Comment When there is no selection. On the Update Bank Statement screen. in the area Posting Parms.g.g. in the area Output Control.

Subsidiary_1 has a liability against headquarters. make the following entries: Field name House Bank Description User action and values <IHB> Comment select © SAP AG Page 62 of 105 . The bank statements are posted in the subsidiary. Choose Execute. Posting in subsidiary_1: account 479903 (clearing account – debit) .account 479900 (IHBaccount –credit). On the Selection of Bank Statements by Banks and Account No .7 Use Post process Bank Statement (optional) The purpose of this activity is to edit bank statements that contain errors. Procedure 1.3.SAP Best Practices In-House Cash (801): BPD subsidiary Print Statistics Separate List 6. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Postprocessing Bank Statement 2. Transactional code is: CKD -. 4. select select Result . Choose Back (F3) There appears a message “Processing Completed”. There appears a message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’.

7. 6. <IHEUR> In-House Cash (801): BPD select 4.SAP Best Practices Account ID 3. Access the transaction choosing one of the following navigation options SAP System SAP ECC Menu Transaction Code SAP Headquarters’ System Accounting → Financial Accounting → Banks → Incomings → Bank Statements → Import FF_5 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC-S (Bank Accountant) Bank Accounting → Incomings → Import Electronic Bank Statement © SAP AG Page 63 of 105 . cash pooling.4. Prerequisites There are open items at the subsidiary from a customer. The bank medium contains incoming payments – payments from customers. 5. 4. and balancing bank accounts from subsidiaries and the house bank at the headquarters.4 Process Steps – Incoming Payments and Cash Pooling Use The purpose of this activity is to process the bank medium from the house bank. Choose Execute. Procedure 1. Choose Save. Select the errors that are red.1 Use Import Bank Statements The purpose of this activity is to post the payment medium from the house bank. Result The errors have been corrected in the subsidiary system. 4. Change the error and post again. On the Edit Bank Statement screen: open IHB -> open IHEUR .

SAP Best Practices In-House Cash (801): BPD 2. make the following entries: Field name Import Data Elect. On the Browser for IHC Payment Orders screen. Bank statement format Statement file Line item file Post Immediately Only bank postings Generate batch input Do not post Assign value date Cash management BELNR number interval to XBLNR number interval to Bundling Items per Bundle Execute as background job Print bank statement Print posting log Print statistics Separate list The file from the house bank empty mark empty empty empty mark All fields are empty <0000000000> enter Description User action and values mark <SWIFT MT940 with field 86 structure> select Comment Choose <9999999999>’ empty enter <ZZZZZZZZZZZZZZZZ> empty empty empty enter mark mark mark mark © SAP AG Page 64 of 105 .

The Recipient Bank Number is: ‘88888888’ © SAP AG Page 65 of 105 .g. A posting log has been created with posting accounts and with the external transaction for cash pooling: 833.4. select the line(s): .SAP Best Practices 3. choose Select IHC Payment Orders. Procedure 4.Transaction Type: INCCRE/INCDEB (incoming payments) and CPOOLD/CPOOLC (cash pooling). make the following entries: Field name Bank Area Year Description User action and values <IHB> e. 4. Note the “Recipient Account Number” for the steps: Display Bank Accounts and Create Bank Statement. On the Browser for IHC Payment Orders screen.Description of Status: Flagged for Posting . On the Browser for IHC Payment Order screen. Access the transaction choosing one of the following navigation options SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account Management → IHC Payment Orders → Payment Order Browser IHC0 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Payment Order Browser 5. In the Selected Payment Orders. and for incoming payments: 051 / 071. They are posted against bank accounts. Choose Execute (F8) In-House Cash (801): BPD Result Following message appears: document ‘999999999’ was posted in company code ‘xxxx’. clearing accounts and accounts for cash pooling. <2010> Comment select enter current year 6. Account statements are posted at the Headquarters.2 Use Post Payment Orders The purpose of this activity is to post the payment order from the subsidiary.

© SAP AG Page 66 of 105 . 9. Choose the Payment Order tab page.g. The selected payment orders have been posted in the In-House Cash Center. Choose Post.3 Use Display Bank Accounts (optional) The purpose of this activity is to check the posted accounts. Access the transaction choosing one of the following navigation options Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account → Display F9K3 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Account 7. Comment select “Recipient Account Number” From Transaction IHC0 (before). for subsidiary_1 <1101004901> 8. Procedure 6.SAP Best Practices 7. Choose Enter. On the Bank Accounts Display: Initial screen. In-House Cash (801): BPD Result The 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. Choose the Account Statements tab page. Payment order IHB/0000000069/2010 has been finally posted . make the following entries: Field name Bank Area Account number Description User action and values <IHB> <Bank Account Number> e. 4.4. 8.

Procedure 1. Account Number from the Vendor and Post Date for transaction F9N7.4 Use Create Bank Statement The purpose of this activity is to create bank statements for subsidiaries. Access the transaction choosing one of the following navigation options Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Bank Statement → New Run → Single Run F9N7 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Bank Statement . Prerequisites There are bank statements from the house bank exist. 4.Single Account 2. Selection date must Comment select enter © SAP AG Page 67 of 105 . On the Create One Single bank Statement on Request screen.SAP Best Practices 10. make the following entries: Field name Bank Area Account Number Description User action and values <IHB> <bank account number> e. In-House Cash (801): BPD Result The selected account statements are displayed with the following values: Bank Key (88888888). Choose Current Bank Statement.4.g. Amount. for subsidiary_1 <1101004901> Statement Date <Date> Post Day from “Post Payment Order” You can see it with transaction F9K3 – too.

SAP Best Practices Field name Description

In-House Cash (801): BPD User action and values Comment be before or on the current posting date

Simulation Run Standard Output

empty 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 With Address 3. Choose Execute (F8).

empty

mark

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

Result
The 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.4.5 Use

Post Bank Statement

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

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post Electronic Bank Statement

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

© SAP AG

Page 68 of 105

SAP Best Practices Field name *all Description When all fields empty – processed all open bank statements

In-House Cash (801): BPD User action and values Comment 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: Field name Statement Date Description User action and values <date> e.g. <01.03.2010> Comment Enter date, where the Bank Statements created in Headquarter (WithTransaction F9K3 you can see the Posting Date in HQ) select 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: Field name Post immed. Assign Value Date Account Description User action and values mark mark Comment

House Bank Account ID

e.g.: <IHB> e.g.: <IHEUR>

5. On the Update Bank Statement screen, in the area Output Control, make the following entries: Field name Execute as background Job Print Bank Statements Print Posting Log Description User action and values empty Comment The job is working on the screen List of the Bank Statements Posted Bank Statements in the subsidiary

mark mark

Print Statistics Separate List 6. Choose Execute.

mark mark

© SAP AG

Page 69 of 105

SAP Best Practices

In-House Cash (801): BPD

Result
The 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” 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.

4.4.6 Use

Post process Bank Statement (optional)

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

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

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Postprocessing Bank Statement

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

© SAP AG

Page 70 of 105

SAP Best Practices Field name House Bank Account ID 3. Choose Save. Creation of Payment Media Using Classical Payment Medium Program Prerequisites There are open Items in the subsidiary with foreign currency. Procedure 1. and the headquarters to the clearing center. Description In-House Cash (801): BPD User action and values <IHB> <IHEUR> Comment select select 4. the handling charge) when your payments for foreign currency in the same country take place.5. There is no customizing in clearing center Japan (JP01. a payment in currency JPY to a house bank in Japan. On the Edit Bank Statement screen: open IHB -> open IHEUR . 4. We have defined the procedure between the subsidiary and the headquarters. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Accounts Payable → Periodic Processing → Payments F110 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role © SAP AG Page 71 of 105 . For example. Select the errors that are red. 6.5 Process Steps – External payments with foreign currency to a other clearing center 4.1 Use The purpose of this activity is to create payments to another clearing center. This enables you to save costs (for example. Result The errors have been corrected in the subsidiary system. 5. so we cannot send and receive IDoc’s to and from clearing center Japan (JP01). Choose Execute. Change the error and post again. 7.

<CC_01> Comment Enter Enter 3. On the Automatic payment transactions: Status screen.g. <26. make the following entries: Field name Run Date Identification Freely define the identification Description User action and values e. On the Automatic payment transactions: Parameter screen.2010> e.g.g. <1000> <4 IHB-Transfer external> e.03. <26. <today’s day> e.2010> e. if you select an interval Enter Otherwise: Empty 5. make the following entries: Field name Posting Date Docs Entered Up To Company Code Pymt Meths Next p/date Payment Methods Posting Date of the next Payment Date Description User action and values e.g.g. Choose Additional Log and make the following entries: Field name Due date check Payment method selection in all cases Pmnt method selection if not successful Line items of the payment Description User action and values Mark Mark Empty Mark Comment Enter Comment Enter © SAP AG Page 72 of 105 .g. <FW_VENDOR> Vendor.03.: <FW_VENDOR> Only you want certain Vendor(s) Enter Otherwise: ‘*’ to e.2010> Enter Select The day of the next posting date you want to run the payments Enter Vendor e. <today’s day> e.SAP Best Practices Business role Business role menu In-House Cash (801): BPD Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable → Posting → Payments → Automatic Payment 2.2010> e. <30.g.g.g. Choose Parameter.g. 4.03. <26.03.g. <today’s day> e.

Choose Schedule Payment run (F7). Choose Schedule (Enter). Choose Save (Ctrl+S). Choose Status. choose Edit Proposal (Shift+F4) or Display Proposal (Shift+F9) and confirm the following screen (selection of accounting clerks) by pressing Continue (Shift+F1). Choose Schedule (Enter). make the following entries: Field name Start immediately Create Payment Medium Description User action and values Mark Mark Comment 18. Confirm the dialog box. Choose Printout/data medium and make following entries: Field name Program Description User action and values RFFOEDI1 Comment Payment media program RFFOEDI1 select Variant <Internal> Standard internal The variant has been created in configuration guide. On the Schedule Payment screen. 19.Status (Shift+F2) to update the status 13. © SAP AG Page 73 of 105 . The message Proposal run has been scheduled appears. 17. make the following entries: Field name Start immediately Description User action and values Mark Comment 11. 9. The message Payment run has been scheduled appears. 15. Choose Proposal (Shift+F1). 14. 16. Choose Status (Shift+F2) more than once to update the status. Select 7. To maintain or display the payment proposal.SAP Best Practices documents Vendors (from/to) In-House Cash (801): BPD <Vendors> For example. Choose – for more than one occurrence . 12. <FW_VENDOR> Enter Optional 6. As soon as the proposal has been created. 10. Choose Back (F3). On the Schedule Proposal screen. 8. it will be shown on the Automatic payment transactions: Status screen.

In addition you can create the Payment List and the Exception List.SAP Best Practices In-House Cash (801): BPD As soon as the payment run has been finished. Result The invoices have been paid while taking a cash discount into account and have been posted to the bank clearing accounts. Choose Continue (Enter) to execute the list.5.g. it will be shown on the Status screen. choose Select IHC Payment Orders. Access the transaction choosing one of the following navigation options SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account Management → IHC Payment Orders → Payment Order Browser IHC0 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Payment Order Browser 2.Description of Status: Flagged for Posting . Procedure 1. To do so. The IDoc generated has been sent to the In-House Cash Center. On the Browser for IHC Payment Orders screen. Choose payment log.2 Use Post Payment Orders The purpose of this activity is to post the payment order from the subsidiary. choose Edit → Payments → Payment List or Edit → Payments → Exception List. <2010> Comment select enter current year 3. The number of generated and completed posting orders is displayed. Payments.Transaction Type: EXTPAY © SAP AG Page 74 of 105 . make the following entries: Field name Bank Area Year Description User action and values <IHB> e. which will execute payment. On the Browser for IHC Payment Order screen. select the line(s): . 4. 20. In the Selected Payment Orders. Check the selection of your document 21.

3 Use Display Bank Accounts (optional) The purpose of this activity is to check the posted accounts. 4. Choose the Payment Order tab page.Transaction Currency: <> ‘EUR’ In-House Cash (801): BPD Note the “Payer Account Number” for the steps: Display Bank Accounts and Create Bank Statement. . The Recipient Bank Number should be <>: ‘88888888’ 4. Payment order IHB/0000000069/2010 has been finally posted .5.SAP Best Practices . Access the transaction choosing one of the following navigation options Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account → Display F9K3 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Account © SAP AG Page 75 of 105 . Procedure 1. because there is no customizing for a bank in the clearing center JP01. There are two IDoc’s (PAYEXT) have been created. The second IDoc inbound for Partner: LS//XXXXXXXxxx with Status 51 –red light. Choose Post. 5. One outbound IDoc –Partner: LS //Local with status 3 –green light-. Result The system issues one of the following messages: • • • Payment order IHB/0000000069/20109 is being checked (the number of the selected Payment Order is displayed) No error was found.. The selected payment orders have been posted in the In-House Cash Center.

SAP Best Practices In-House Cash (801): BPD 2.4 Use Create Bank Statement The purpose of this activity is to create bank statements for subsidiaries and for headquarters in order to post for the clearing center. 4. 5. for subsidiary_1 <1101004901> and for clearing center: <1101008101> 3. Account Number from the Vendor and Post Date for transaction F9N7. Procedure 1. On the Bank Accounts Display: Initial screen. Comment select Enter “Payer Account Number” used for “Post Payment Order” From Transaction IHC0 (before). Amount. Choose Current Bank Statement. Result The selected account statements are displayed with the following values: Bank Key <> (88888888). Choose the Account Statements tab page. Prerequisites The subsidiaries have made external payments to the headquarters in foreign currency.5. 4.Single Account © SAP AG Page 76 of 105 . Choose Enter.g. Access the transaction choosing one of the following navigation options Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Bank Statement → New Run → Single Run F9N7 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Bank Statement . make the following entries: Field name Bank Area Account number Description User action and values <IHB> <Bank Account Number> e.

4. There are two IDoc’s created. make the following entries: Field name Bank Area Account Number For subsidiary and clearing center Description User action and values <IHB> <bank account number> e. The system displays a screen with the address. © SAP AG Page 77 of 105 . On the Create One Single bank Statement on Request screen. One inbound FINSTA IDoc with partner B//0088888888 port SAPBHQ. the bank statement is generated in standard form. For this case. One outbound FINSTA IDoc with partner GP//SUB_JAPAN port LOCAL.g. Choose Execute (F8). an FAS IDoc is created” appears.5 Use Post Bank Statement The purpose of this activity is to post the bank statement that was created at the headquarters for the clearing center. 4. bank account. Statement Without Turnovers With Address 3.g.SAP Best Practices In-House Cash (801): BPD 2. Selection date must be before or on the current posting date Simulation Run Standard Output empty empty If this indicator is set. Result The bank statements for subsidiaries and the clearing center have been created and an IDoc sent to the subsidiaries’ systems. <1101008101> Comment select enter Statement Date <Date> Post Day from “Post Payment Order” You can see it with transaction F9K3 – too. bank area ‘IHB’. empty mark The message “For account ‘999999999’. amount and posting date.5. Choose Enter. this indicator must not be set. <1101004901> and e.

On the Update Bank Statement screen. make the following entries: Field name Statement Date Description User action and values <date> e. make the following entries: Field name Post immed. where the Bank Statements created in Headquarter (WithTransaction F9K3 you can see the Posting Date in HQ) select House Bank e.g. in the Bank Statements area. Assign Value Date Account Description User action and values mark mark Comment 9.03.2010> Comment Enter date. On the Update Bank Statement screen.g. <01.: <JPY> 8. On the Update Bank Statement screen. in the Posting Params area. in the Output Control area. make the following entries: Field name Execute as background Job Print Bank Statements Print Posting Log Print Statistics Description User action and values empty Comment The job is working on the screen List of the Bank Statements Posted Bank Statements mark mark mark © SAP AG Page 78 of 105 . Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Headquarters’ System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post Electronic Bank Statement 7.SAP Best Practices In-House Cash (801): BPD Procedure 1.

Choose Execute. On the Edit Bank Statement screen: open JPY -> open JPY01. Procedure 1. 5. . make the following entries: Field name Company code House Bank 3. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Headquarters’ System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Postprocessing Bank Statement 2. 4.6 Use Post process Bank Statement (optional) The purpose of this activity is to edit bank statements that contain errors. Choose Back (F3) The message “Processing Completed” appears.SAP Best Practices Separate List 10. On the Selection of Bank Statements by Banks and Account Nos screen. 6. 4. mark In-House Cash (801): BPD Result The bank statements are posted in the headquarters. Correct the errors and post again. Choose Save. 7. The message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’ appears. Choose Execute. Description User action and values <1000> <JPY> Comment select select © SAP AG Page 79 of 105 . The transaction code is 051 and the posting: clearing account 289009 – account clearing center 289000.5. Select the errors that are marked in red.

4.: <IHB> e. On the Update Bank Statement screen.7 Use Post Bank Statement The purpose of this activity is to post the bank statement that was created in headquarters for subsidiaries.03. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post Electronic Bank Statement 2.2010> Comment Enter date.: <IHEUR> © SAP AG Page 80 of 105 . make the following entries: Field name *all Description When all fields empty – processed all open bank statements User action and values Comment When there is no selection (choice).g. in the Bank Statements area.5. all not processed bank statements will processed 3. <01. where the Bank Statements created in Headquarter (With Transaction F9K3 you can see the Posting Date in HQ) select Select The Company Code appears too House Bank Account ID e.g.SAP Best Practices In-House Cash (801): BPD Result The errors have been corrected in the headquarters system. Procedure 1. Alternatively you can make your selections in detail and the Bank Statement will only be processed for those choices: Field name Statement Date Description User action and values <date> e.g.

Choose Back (F3) The message “Processing Completed” appears.5. in the Output Control area. The transactional code is 020. make the following entries: Field name Execute as background Job Print Bank Statements Print Posting Log Description User action and values empty Comment The job is working on the screen List of the Bank Statements Posted Bank Statements in the subsidiary mark mark Print Statistics Separate List 6. Procedure 1. mark mark Result The bank statements are posted in the subsidiary. On the Update Bank Statement screen. Subsidiary has a liability against the headquarters. 4. The message “Document ‘xxxxxxxxx’ was posted in company code ‘xxxx’ appears. make the following entries: Field name Post immed. in the Posting Params area. <EUR> In-House Cash (801): BPD Only Bank Statements with currency EUR enter 4.account 479900 (IHB account – credit).SAP Best Practices Currency e. Assign Value Date Account Description User action and values mark mark Comment 5. Choose Execute. On the Update Bank Statement screen. Access the transaction choosing one of the following navigation options: © SAP AG Page 81 of 105 . Posting in subsidiary: account 479903 (clearing account – debit) .g.8 Use Post process Bank Statement (optional) The purpose of this activity is to edit bank statements that contain errors.

On the Selection of Bank Statements by Banks and Account Nos screen.6. with the function reverse is it possible to cancel the payment. On the Edit Bank Statement screen. make the following entries: Field name House Bank Account ID 3. Description User action and values <IHB> <IHEUR> Comment select select Result The errors have been corrected in the subsidiary system. Choose Execute.6 Process Steps – Internal Returns 4.receives the payment back with the sign minus. open IHB then open IHEUR. Access the transaction choosing one of the following navigation options: © SAP AG Page 82 of 105 . 4.SAP Best Practices Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code In-House Cash (801): BPD SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Postprocessing Bank Statement 2. Choose Save. 5. 7. Correct the errors and post again.1 Use The purpose of this activity is to cancel the payment order from the subsidiary. When there is a wrong payment from the subsidiary.receives the payment back with the sign plus and subsidiary – receiver of the payment. Subsidiary_1 –payer. 4. Reverse Payment Orders Procedure 1. 6. Select the errors that are marked in red.

Description of Status:” Finally Posted” . On the Browser for IHC Payment Orders screen.SAP Best Practices SAP System SAP ECC Menu In-House Cash (801): BPD SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account Management → IHC Payment Orders → Payment Order Browser IHC0 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Payment Order Browser 2. © SAP AG Page 83 of 105 .g. 5.Transaction Type: “INTPAY” Note the “Payer Account Number” for the next step.< 2010> Comment select enter current year 3. make the following entries: Field name Bank Area Year Description User action and values <IHB> e.. Choose the Payment Order tab page. On the Browser for IHC Payment Order screen. Display Bank Accounts: For Internal Payments note the “Recipient Account Number”. select “Select “IHC Payment Orders”. Select the notated “Payment Order” from transaction IHC0 –Internal Payments. There appears a pop-up with the question: Do you want to reverse all payment orders? Confirm with: Yes Result The system issues one of the following messages: • • Payment order IHB/0000000001/2010 is being checked (the number of the selected Payment Order is displayed) No error was found. select the line(s): . Choose Reverse 6. There is Recipient Bank Number = ‘88888888’ 4.

for subsidiary_1 <1101004901> and subsidiary_2 <1102004901> 3. On the Bank Accounts Display: Initial screen.g.SAP Best Practices • • No outbound IDoc existsI In-House Cash (801): BPD Payment order IHB/0000000001/2010 has been reversed . Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account → Display F9K3 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Account 2.2 Use Display Bank Accounts (optional) The purpose of this activity is to check the posted accounts for each subsidiary. Choose Enter. Choose the Account Statements tab page. 4. Procedure 1. 4. Choose Current Bank Statement. 5. Comment select Enter “Payer Account Number” used for “Post Payment Order” + Internal Payments “Recipient Account Number” Result © SAP AG Page 84 of 105 .6. The Description of Status is: Reversed The selected payment orders have been posted in the In-House Cash Center. make the following entries: Field name Bank Area Account number Description User action and values <IHB> <Bank Account Number> e.

When there are internal payments. Account Number from the Vendor and Post Date for transaction F9N7. There will be created Bank Statement for both subsidiaries. When in subsidiary_1 there are open Bank Statements for e.g. Subsidary_2. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Bank Statement → New Run → Single Run F9N7 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Bank Statement . Amount. The Posting Text is “Canceled: IHC Item” 4. for subsidiary_1 <1101004901> and subsidiary_2 <1102004901> Statement Date <Date> Post Day from “Post Payment Order” You can see it with transaction F9K3 – Comment select enter © SAP AG Page 85 of 105 .Single Account 2. Procedure 1. you must execute this step at least twice. Prerequisites The subsidiaries have made internal payments to the headquarters. perform this transaction for the “Payer Account” and for the “Recipient Account”. On the Create One Single bank Statement on Request screen. so you must execute this step for Subsidary_1 and Subsidary_2. For all internal payments.6. make the following entries: Field name Bank Area Account Number Description User action and values <IHB> <bank account number> e.SAP Best Practices In-House Cash (801): BPD The selected account statements are displayed with the following values: Bank Key.g.3 Use Create Bank Statement The purpose of this activity is to create bank statements for subsidiaries.

Selection date must be before or on the current posting date Simulation Run Standard Output empty empty If this indicator is set. payee and payer. This is a task for each subsidiary. this indicator must not be set. Choose Execute. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role © SAP AG Page 86 of 105 . bank area IHB.6. 4. The system displays a screen with the address. bank account. amount and posting date.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values Comment too. 4.4 Use Post Bank Statement The purpose of this activity is to post the bank statement that was created in headquarters for subsidiaries. Result The banks statements for subsidiaries have been created and an IDoc is sent to the subsidiaries system. empty mark The message For account ‘999999999’. the bank statement is output in standard form. Statement Without Turnovers With Address 3. an FAS IDoc is created appears. For this case. Choose Enter. Procedure 1.

On the Update Bank Statement screen.SAP Best Practices Business role Business role menu In-House Cash (801): BPD SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post Electronic Bank Statement 2.: <IHB> e.g. make the following entries: Field name *all Description When all fields empty – processed all open bank statements User action and values Comment When there is no selection (choice).: <IHEUR> 4. make the following entries: Field name Execute as background Job Print Bank Statements Print Posting Log Description User action and values empty Comment The job is working on the screen List of the Bank Statements Posted Bank Statements in the subsidiary mark mark Print Statistics Separate List mark mark © SAP AG Page 87 of 105 . Or you can select in detail and the Bank Statement will only processed for these choice: Field name Statement Date Description User action and values <date> Comment Enter date.g.<EUR> Only Bank Statements with currency EUR House Bank Account ID e. in the area Output Control. On the Update Bank Statement screen. in the area Bank Statements. all not processed bank statements will processed 3. Assign Value Date Account Description User action and values mark mark Comment 5. in the area Posting Params. make the following entries: Field name Post immed. On the Update Bank Statement screen. where the Bank Statements created in Headquarter select Select The Company Code appears too Currency e.g.

to “account IHB reversal” – credit-. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post processing Bank Statement 2. Result The bank statements are posted in the subsidiary. Procedure 1. Transactional code is IND +. The posting document should be e. payee and payer. In subsidiary_2 inverse posting as in subsidiary_1. make the following entries: Field name House Bank Account ID Description User action and values <IHB> <IHEUR> Comment select select © SAP AG Page 88 of 105 . 7. On the Selection of Bank Statements by Banks and Account Nos.6. 4. in subsidiary_1: “account IHB” –debit.g.SAP Best Practices In-House Cash (801): BPD 6. This is a task for each subsidiary. The system issues the message Processing Complete. Choose Execute. 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.5 Use Post process Bank Statement (optional) The purpose of this activity is to edit bank statements that contain errors.

Result The errors have been corrected in the subsidiary system. Choose Execute. When there was a wrong external payment to the house bank. with the function reverse is it possible to cancel the payment.7. On the display payment requests screen.7 Process Steps – External Returns The purpose of this activity is to cancel the payment order from the subsidiary. enter following entries: Field name Company Code Description User action and values e. On the Edit Bank Statement screen: open IHB -> open IHEUR . Select the errors that are red. Access the transaction choosing one of the following navigation options: SAP System SAP ECC Menu Transaction Code SAP Headquarters’ System Accounting → Financial Accounting → Outgoings → Online Payments → Display Payment Request F8BT 2. 4. Choose Save. Change the error and post again.receives the payment back with the sign plus and can change /revise the payment and start the payment again. 6. 4. 7.g. <1000> Comment select © SAP AG Page 89 of 105 . Subsidiary_1 –payer. Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Payment Requests 3. 4. 5..SAP Best Practices In-House Cash (801): BPD 3.1 Use Display Payment Request Investigate the clearing document for returns. Procedure 1.

choose Administration Data and enter following entries: Field name Origin Description User action and values <TR-IHC> Comment select 5.2 Use Individual Reversal The first step for reverse a payment is. 4. choose Bank data and enter following entries: Field name House Bank House Bank Account e. Deutsche Bank Description User action and values e.g. Choose Execute Result On the detail display you can see the “Clearing Document”-Number. On the display payment requests screen. On the display payment requests screen: Field name Key Number Description User action and values e.7. On the display payment requests screen.g. <1000> e.g. <46> Comment Use the payment request number noted from transaction F111 7. <DISB> Comment enter enter 6. Access the transaction choosing one of the following navigation options: © SAP AG Page 90 of 105 .SAP Best Practices Field name Open Cleared Description In-House Cash (801): BPD User action and values empty mark Comment 4. Note the number for transaction FB08 and F8BW as well as the entry date for transaction IHC0 later. to reverse the posted document: Header Data Procedure 1.g.

g.g.: <sub_vendor> 1000 Comment enter 2. On the reverse document: header data screen. Mark “All Vendor Line Items Cleared” Choose the necessary Search Criteria: Field name Vendor Account: Company Code: Description User action and values e. <2010> <01> select enter select Result There appears the message: Document ‘9999999999’ was posted in company code 1000 © SAP AG Page 91 of 105 . Company Code Fiscal Year Reversal Reason 5.SAP Best Practices SAP System SAP ECC Menu Transaction Code In-House Cash (801): BPD SAP Headquarters’ System Accounting → Financial Accounting → General Ledger → Document → Reverse → Individual Reversal FB08 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S) Accounts Payable → Posting → Document Processing 1. Or from Job Log – payment run F111.g. Only SAP NetWeaver Business Client (SAP NWBC): 2. 3.g. Choose Save e. make the following entries: Field name Document Number Description User action and values e. Only SAP NetWeaver Business Client (SAP NWBC): Mark the required row (document number) and choose Reverse Document. <1000> e. Only SAP NetWeaver Business Client (SAP NWBC): Choose Apply. 4. “Clearing Document”number from transaction F8BT. <200000001> Comment Enter.

make the following entries: Field name Company Code Payment document Document from transaction F8BT Description User action and values e. <2010> empty enter Fiscal Year Mark for cancelation 3. <200000001> Comment enter Enter The same document number like in transaction FB08 e.g.7. <1000> e.3 Use Reset Cleared Items The second step for reverse a payment is to reverse clearing of a payment request 1.g.g.SAP Best Practices In-House Cash (801): BPD 4. Access the transaction choosing one of the following navigation options: SAP System SAP ECC Menu Transaction Code SAP Headquarters’ System Accounting → Financial Accounting → Banks → Environment → Payment Requests → Reset Cleared Items F8BW Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Reset Cleared Items: Payt Requests 2. Choose Execute Result There appears the message: “Cleared payment request items were reset” © SAP AG Page 92 of 105 . On the reverse clearing of payment requests screen.

Choose Reverse © SAP AG Page 93 of 105 .return . choose “Select IHC Payment Orders”.g.Transaction Type: “EXTPAY” . On the Browser for IHC Payment Order screen.4 Use Reverse Payment Orders The purpose of this activity is to reverse the payment order from the subsidiary. Choose the Payment Order tab page. Procedure 1. On the Browser for IHC Payment Orders screen.g.7.Payment Order: noted transaction IHC0 (external outgoing payments) e. In the Selected Payment Orders.Description of Status:” Finally Posted” . 5. select the line(s): . 204 .Recipient Account Number: should be the same from the house bank .Recipient Bank Number: should be the same from the house bank . make the following entries: Field name Bank Area Year Date Executed Date from transaction F8BT –entry date Description User action and values <IHB> e. Display Bank Accounts: 4.SAP Best Practices In-House Cash (801): BPD 4. <2010> <date> Comment select enter current year enter 3. Access the transaction choosing one of the following navigation options: SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account Management → IHC Payment Orders → Payment Order Browser IHC0 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Payment Order Browser 2.return Note the “Payer Account Number” for the next step.

There appears a pop-up with the question: Do you want to reverse all payment orders? Confirm with: Yes Result The system issues one of the following messages: • • • • • Payment order IHB/0000000001/2010 is being checked (the number of the selected Payment Order is displayed) No error was found Outbound IDoc 9999999999999999 is used for partner Type FI .SAP Best Practices In-House Cash (801): BPD 6.mm. make the following entries: Field name Bank Area Account number Description User action and values <IHB> <Bank Account Number> Comment select Enter “Payer Account Number” used for © SAP AG Page 94 of 105 . 4.7. Procedure 1.5 Use Display Bank Accounts (optional) The purpose of this activity is to check the posted accounts. Access the transaction using one of the following navigation option: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code SAP Headquarters’’ System Accounting → Financial Supply Chain Management → InHouse Cash → Account → Display F9K3 Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Display Account 2. On the Bank Accounts Display: Initial screen. The Description of Status is: Reversed The selected payment orders have been posted in the In-House Cash Center. Payment order ‘99’ in system ‘XXX’ was reserved (date dd.yyyy / reason 01) Payment order IHB/0000000001/2010 has been reversed .

Amount.g. Procedure 1.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values e.7. Choose Current Bank Statement. Account Number from the Vendor and Post Date for transaction F9N7. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Bank Statement → New Run → Single Run F9N7 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Planning → Bank Statement . On the Create One Single bank Statement on Request screen. make the following entries: Field name Bank Area Description User action and values <IHB> Comment select © SAP AG Page 95 of 105 . for subsidiary_1 <1101004901> Comment “Post Payment Order” + Internal Payments “Recipient Account Number” 3. Choose the Account Statements tab page. 5.6 Create Bank Statement Prerequisites The subsidiaries have made internal payments to the headquarters. 4. 4. The Posting Text is “Canceled: Bank transfer”.Single Account 2. Choose Enter. Result The selected account statements are displayed with the following values: Bank Key.

5.7.2010> Comment Account Number enter Statement Date Post Day from “Post Payment Order” You can see it with transaction F9K3 – too. <1101004901> <Date> e. This is a task for each subsidiary. © SAP AG Page 96 of 105 . Choose Back (F3) Result The banks statements for subsidiaries have been created and an IDoc is sent to the subsidiaries system.7 Use Post Bank Statement The purpose of this activity is to post the bank statement that was created in headquarters for subsidiaries.<12.SAP Best Practices Field name Description In-House Cash (801): BPD User action and values <bank account number> e. 4. Statement Without Turnovers With Address 3. amount and posting date. an FAS IDoc is created” appears. the bank statement is output in standard form. empty mark The message “For account ‘999999999’. this indicator must not be set. payee and payer.04.g. Choose Execute. For this case. bank area IHB. 4.g. The system displays a screen with the address. bank account. Choose Enter. Selection date must be before or on the current posting date Simulation Run Standard Output empty empty If this indicator is set.

where the Bank Statements created in Headquarter.: <IHEUR> 4. all not processed bank statements will processed House Bank Account ID e. Or you can select in detail and the Bank Statement will only processed for these choice: Field name Statement Date Description User action and values <date> Comment Enter date. in the area Posting Params. in the area Bank Statements. <EUR> Only Bank Statements with currency EUR Description When all fields empty – processed all open bank statements User action and values Comment When there is no selection (choice). On the Update Bank Statement screen.g.: <IHB> e.g. Current Posting Date – look transaction F9B2 select Select The Company Code appears too Currency e. make the following entries: Field name Description User action and values Comment © SAP AG Page 97 of 105 .g. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Post FEBP Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Post Electronic Bank Statement 2. On the Update Bank Statement screen.SAP Best Practices In-House Cash (801): BPD Procedure 1. make the following entries: Field name Statement Date Statement Number House Bank Account ID Currency 3.

Transactional code is 020 +. Choose Execute. in the area Output Control. On the Update Bank Statement screen. This is a task for each subsidiary. Procedure 1. 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. make the following entries: Field name Execute as background Job Print Bank Statements Print Posting Log Description User action and values Empty Comment The job is working on the screen List of the Bank Statements Posted Bank Statements in the subsidiary mark mark Print Statistics Separate List 6.SAP Best Practices Post immed. mark mark The system issues the message Processing Complete. 4.to “account IHB reversal” – credit-. Result The bank statements are posted in the subsidiary. payee and payer.8 Use Post process Bank Statement (optional) The purpose of this activity is to edit bank statements that contain errors.7. Assign Value Date Account mark mark In-House Cash (801): BPD 5. 7. Access the transaction choosing one of the following navigation options: © SAP AG Page 98 of 105 . The posting document should be:” account IHB” –debit.

SAP Best Practices Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction code In-House Cash (801): BPD SAP Business All-in-One Subsidiary System Accounting → Financial Accounting → Banks → Incomings → Bank Statement → Reprocess FEBA_BANK_STATEMENT Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_NBPR_BANKACC_S (Bank Accountant) Bank Accounting → Incomings → Postprocessing Bank Statement 2. Change the error and post again. Choose Execute. 7. Select the errors that are red. 5. 6. On the Selection of Bank Statements by Banks and Account Nos. Description User action and values <IHB> <IHEUR> Comment select select Result The errors have been corrected in the subsidiary system. © SAP AG Page 99 of 105 . 4. make the following entries: Field name House Bank Account ID 3. On the Edit Bank Statement screen: open IHB -> open IHEUR . Choose Save.

These transactions are necessary in the Financial Accounting for reconciliation.8 End-of-Day Processing Use In the In-House Cash Center there are all bank postings from the subsidiaries. Field Name Bank Area Current Posting Date 3. enter the following data: Description User action and Values <IHB> Comment select The field is protect © SAP AG Page 100 of 105 . 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. Enter following data. 2.SAP Best Practices In-House Cash (801): BPD 4. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Posting Date → Payment Transaction F9B1 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → BCA: Posting cut-off paym. Choose Execute (Enter) If Date is not the same as the date from transaction F9N11. there won’t be transfers from IHC -> FI. 1. The date from F9N11 parameters should be the same. transact. If the date is not the same.

Description User action and values <STD> Comment select Prerequisites The subsidiaries have made payments to the headquarters. Mark line and choose Maintain Variants F5. ensure that no Simulation run is marked in the parameters of transaction F9N11. The date in the transaction F9B11 has the default value “current date”. Choose Save 5. Procedure for check/change Current Posting Date in F9N11: Field name Processing Chain 8. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → End-of-Day Processing → Start F9N11 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Start End-of-Day Processing 7. Check all lines. 11. Furthermore.SAP Best Practices Field Name New Posting Date Description Date from transaction F9N11 User action and Values <date> In-House Cash (801): BPD Comment enter Normally – daily process – it should be the same and always the current date. © SAP AG Page 101 of 105 . 4. The Date e. Procedure for check/change Current Posting Date in F9N11 (Date must be equal like transaction F9B1): 6. Therefore generally no changes necessary. Balances c/f on (from Cash Concentration) – should be the same like “Current Posting Date” from transaction F9B1. Choose Parameter.g. 9. 10.

Prerequisites The job with transaction F9N11 is started or finished. On the Start Sequence of Reports in End-of-Day Processing screen.1 Use End-of-Day Processing – Control Check 1 (optional) The purpose of this activity is to make a control check of an End-of-Day processing. Access the transaction choosing one of the following navigation options: © SAP AG Page 102 of 105 .8. make the following entries: Field name Processing Chain 3. Please confirm “Yes”.SAP Best Practices In-House Cash (801): BPD Procedure 1. Procedure 1. 4. Choose Execute. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → End-of-Day Processing → Start F9N11 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Start End-of-Day Processing 2. There could be appear a message “Parameters were not changed Start Anyway”. Description User action and values <STD> Comment select Result All bank postings from IHC are posted in the Financial Accounting.

Access the transaction choosing one of the following navigation options: © SAP AG Page 103 of 105 .8. Choose Execute. 4.2 Use End-of-Day Processing – Control Check 2 (optional) The purpose of this activity is to make an additional control check of an End-of-Day processing.SAP Best Practices In-House Cash (801): BPD Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → End-of-Day Processing → Overview F9N10 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Overview End of Day Processing 2. Prerequisites The job with transaction F9N11 is finished. Description User action and values <Date from run F9N11> Comment enter Could be empty Result All jobs should have the message Completed without Error(s). On the Status Overview of Reports in End of Day Processing screen. make the following entries: Field name Start Date from Start Date to 3. Procedure 1.

Value Date and the posted amount. Lists LOCAL RFBKGL01_ xxx.SAP Best Practices SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu Transaction Code In-House Cash (801): BPD SAP Headquarters’ System Accessible from the menu bar in any screen No transaction code necessary Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu Treasurer (SAP_NBPR_TREASURER_BNI-S) Accessible from the menu bar in any screen Choose More… 2. Currency. Prerequisites The job with transaction F9N11 is finished.8. Choose System.g. Last line should have the message: Transfer finished w/o error. 4.IHC to FI. The list included: Recon. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP System SAP ECC Menu SAP Headquarters’ System Accounting → Financial Supply Chain Management → InHouse Cash → Periodic Processing → Applications Logs →Transfer FI F961 Transaction Code Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role © SAP AG Page 104 of 105 . Choose Own Spool Requests. Post date. You can see all transfers from the accounts . Result Postings from IHC → FI. Choose List1s from Time today e. Key. Procedure 1. 3. 4.3 Use End-of-Day Processing – Control Check 3 (optional) The purpose of this activity is to make an additional control check of an End-of-Day processing.

make the following entries: Field name Object Subobject From(Date/Time) To(Date/Time) All Logs Format Completely from Database 4. Choose Execute.SAP Best Practices Business role Business role menu In-House Cash (801): BPD Treasurer (SAP_NBPR_TREASURER_BNI-S) Cash Management → Cash Management → Reporting → Application Log FI Transfer 2. On the Status Overview of Reports in End of Day Processing screen. open the messages. Description User action and values <FIBA> <BAGLTRANS> <Today’s date> <Today’s date> mark mark Comment select select enter enter Result Column “Message Type” should be green. You can see the reason for the error. When the column “Message Types” is red. © SAP AG Page 105 of 105 .

Sign up to vote on this title
UsefulNot useful