801_BPP_EN_DE

7/27/2019 801_BPP_EN_DE

1/105

EHP4 for SAP ERP6.0

December 2010

English

In-House Cash (801)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

7/27/2019 801_BPP_EN_DE

2/105

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 theexpress 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 componentsof other software vendors.

Microsoft, Windows, Excel, Outlook,and PowerPointare 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, SystemStorage, 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 ofAdobe 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 MultiWinare trademarks orregistered 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 inventedand implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjectsExplorer, and other SAP products and services mentioned herein as well as their respective logos aretrademarks 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 astheir 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

7/27/2019 801_BPP_EN_DE

3/105


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field

names, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

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

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

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

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

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

Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.


7/27/2019 801_BPP_EN_DE

4/105


Contents

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

2 Prerequisites............................................................................................................................... 62.1 Master Data and Organizational Data..................................................................................6

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

4.3 Process Steps External Outgoing Payments by Check...................................................504.4 Process Steps Incoming Payments and Cash Pooling....................................................63

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

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

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

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


7/27/2019 801_BPP_EN_DE

5/105


In-House-Cash

1 Purpose

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

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

External payments: subsidiary received a billing document from the vendor. The subsidiary pays

the invoice to headquarter and headquarter creates a payment medium for this payment to thehouse bank.

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

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


7/27/2019 801_BPP_EN_DE

6/105


2 PrerequisitesThere must be at least two SAP clients or SAP systems. One SAP client or system is the central

reporting unit (headquarters), which collects and summarizes information. In the other clientsthere collects transactions form Supplier payments.

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

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

Master Data Value Selection Comment

Bank Accounts IHC-

This can be checkedusing transaction codeF9K2

- Headquarters

2.2 Transactional DataThe following IDocs are created in this process:

PAYEXT (Create payments)

FINSTA (Create bank statements)

2.3 Preliminary Steps

2.3.1 Posting a Customer Invoice in Accounting

Use

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

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

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


7/27/2019 801_BPP_EN_DE

7/105


Prerequisite

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

Procedure

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP System SAP Business All-in-One Subsidiary System

SAP menu Accounting Controlling Internal Orders Master DataSpecial Functions Order Create

Transaction code KO01

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

Business role SAP_NBPR_CONTROLLER-M (Enterprise Controller)

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

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

Field Name Description User Action andValues

Comment

Order Type Internalorders

e.g. select

Order empty

3. Choose Enter

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


Comment

Controlling Area e.g. select

5. Choose Enter

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


Comment

Description

enter

Company Code e.g. select

Object Class e.g. select

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

Field Name Description User Action and Comment


7/27/2019 801_BPP_EN_DE

8/105


Values

System Status Choose

After choose the Systemstatus is: REL and

User status is: PLIM

Currency e.g. select

8. Choose Save

Result

The message Order was created with number xxxxxx appears. Note this number fortransaction FB70 Enter Customer Invoice-.




SAP menu Accounting Financial Accounting Accounts ReceivableDocument Entry Invoice

Transaction code FB70


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

Business role menu Accounts Receivable Posting Invoice Enter OutgoingInvoices

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

To change the company code in the transaction, choose Edit Change Company

Code. Then choose Continue.

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

enter the following data.


Comment

Customer Customer issubsidiary_1

e.g. SUBSI_1

For example entercustomer which has beencreated with process stepCreating a CustomerMaster Record

Choose the customer forinternal deliveries.

In our case: subsidiary_2delivers to subsidiary_1.So we record in


7/27/2019 801_BPP_EN_DE

9/105


subsidiary_2 a customerinvoice for subsidiary_1.

enter

Invoice Date

e.g.

For Example Todays date

enter

Reference enter

Amount enter

Currency enter

Calculate Tax mark

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

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


Comment

Bline Date BaselineDate for DueDateCalculation

e.g.

Check date

enter

Payt terms e.g. select

Pmt Method empty

12. Enter the following data for the line item:


Comment

G/L acct enter

D/C Debit/Credit select

Amount inDocument Currency

Enter the gross amount.The system calculates the

output tax automatically.

enter

Tax Code For example A1 (19% taxon sales/purchases)

select

Order e.g. Enter the order number noted from transactionKO01

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


7/27/2019 801_BPP_EN_DE

10/105


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

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

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

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

Result

The customer invoice is posted and the G/L account and customer transaction figures areupdated.




SAP menu Accounting Financial Accounting Accounts ReceivableDocument Entry Invoice

Transaction code FB70


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

Business role menu Accounts Receivable Posting Invoice Enter Outgoing

Invoices

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

To change the company code in the transaction, choose Edit Change Company

Code. Then choose Continue.

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


Comment

Customer External Customerin subsidiary_1

e.g.

The customer we need forexternal incomingpayments

enter

Invoice Date

e.g.

For example todays date

enter

Reference enter

Amount enter Currency enter


7/27/2019 801_BPP_EN_DE

11/105


Calculate Tax mark

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

(Enter).

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


Comment

Bline Date BaselineDate for DueDateCalculation

e.g.

Check date

enter

Payt terms e.g. select

Pmt Method empty

19. Enter the following data for the line item:


Comment

G/L acct enter

D/C Debit/Credit select

Amount inDocument Currency

Enter the gross amount.

The system calculates theoutput tax automatically.

enter

Tax Code For example A1 (19% taxon sales/purchases)

select

Order e.g. Enter the order number noted from transactionKO01

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

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

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

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

the system.


7/27/2019 801_BPP_EN_DE

12/105


Result

The customer invoice is posted and the G/L account and customer transaction figures areupdated.

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

Use

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

We need 2 vendor invoices:

1. For internal payments. E.g.: delivery from subsidiary_2 to subsidiary_1. Create a

vendor invoice in subsidiary_1. Vendor is subsidiary_2.

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

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

Procedure




SAP ECC Menu AccountingFinancial AccountingAccounts Payable

Document EntryInvoice

Transaction Code FB60


Business role Accounts Payable Accountant (SAP_NBPR_AP_CLERK-S)

Business role menu Accounts Payable PostingInvoices Enter Vendor Invoice

w/o PO Reference

2. On the Enter Vendor Invoice screen, make the following entries:

Field name Description User action and values Comment

Vendor Subsi_2 is vendor insubsidiary_1 andcreated a customerinvoice for subsi_1 insubsidiary_2

e.g.: for internal deliveries =e.g.

Refer Master Data

enter

Invoice Date e.g. enter

Reference (*) Enter the documentnumber from thePosting a Customer


7/27/2019 801_BPP_EN_DE

13/105


Invoice in Accounting

Customer invoicecreated insubsidiary_2 withcustomer subsi_1.

- only when internalpayments

Amount enter

Currency enter

Calculate tax mark

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

select

Text

enter

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

4. Enter following data:


G/L Account enter

D/C select

Amount in

DocumentCurrency

Gross amount;

enter

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

select

Cost Center e.g. Select a valid costcenter

5. Choose Post (Ctrl + S).

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

Procedure






7/27/2019 801_BPP_EN_DE

14/105






Business role menu Accounts Payable Posting Invoices Enter Vendor Invoice

w/o PO Reference



Vendor Vendor insubsidiary_1

e.g.: for external deliveriese.g.

Refer Master Data

enter


Reference enter

Amount enter

Currency enter

Calculate tax mark


select

Text

enter




Pmt Method External Payment Select

If field Pmt Methodempty, we use thepayment method frommaster data (vendor).

G/L Account enter

D/C select

Amount inDocumentCurrency

Gross amount;

enter


select



7/27/2019 801_BPP_EN_DE

15/105



Result

The invoice for external payments has been posted. For further processing, make a note of thedocument number.

Use

Enter a vendor invoice with foreign currency for payment to a other clearing center in theheadquarters

Procedure









Business role menu Accounts Payable Posting Invoices Enter Vendor Invoice

w/o PO Reference



Vendor Vendor insubsidiary_1 withforeign currency. Foradditional clearingcenter.

e.g.: for external deliveriese.g

Refer Master Data

enter


Reference enter

Amount enter

Currency enter

Calculate tax mark

Tax Code No tax procedure

select

Text

enter


7/27/2019 801_BPP_EN_DE

16/105





Pmt Method External Payment Select

If field Pmt Methodempty, we use thepayment method frommaster data (vendor).

G/L Account enter

D/C select


Gross amount;

enter

Tax Code No tax procedure

select



Result

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

2.3.3 Post Vendor Invoice external payment by check

To run through this scenario, the open items for payables must be available in the subsidiarysystem.

Use

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

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

Procedure







7/27/2019 801_BPP_EN_DE

17/105





Business role menu Accounts Payable Posting Invoices Enter Vendor Invoicew/o PO Reference



Vendor Vendor insubsidiary_1

e.g.: for external deliveriese.g.

Refer Master Data

enter

Invoice Date

e.g.

for example, todaysdate

enter

Reference empty Enter the documentnumber from thePosting a CustomerInvoice in Accounting

- only when internalpayments

Amount enter

Currency enter

Calculate tax mark


select

Text

enter

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

4. Enter the following data:


Pmt Method Payment method forchecks

select

G/L Account enter

D/C select


Gross amount;

enter


select


7/27/2019 801_BPP_EN_DE

18/105





Result

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

2.4 RolesUse

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

Prerequisites

The business roles have been assigned to the user who is testing this scenario in the subsidiarysystem:

Business Role Technical Name Process Step

Payable Accountant SAP_NBPR_AP_CLERK-S Posting vendor data

Receivable Account-FI Only SAP_NBPR_AR_FI_ONLY-S Posting Customer data

Bank Accountant SAP_NBPR_BANKACC-S Processing bank data

Treasurer SAP_NBPR_TREASURER-S Payments to house bank

Enterprise Controller SAP_NBPR_CONTROLLER-M

Internal Orders

Treasurer BNI SAP_NBPR_TREASURER-BNI-S

Payments


7/27/2019 801_BPP_EN_DE

19/105


3 Process Overview TablesThe following process steps follow a schedule of activities related to payment transactions and

provide a daily review of the corporate cash position and liquidity forecast.

3.1 Internal Payments

Process Step BusinessCondition

BusinessRole

Transaction Code Expected Results

Subsidiary

Automatic PaymentTransaction

Prerequisite: openitems

AccountantPayables

F110 Data Medium iscreated and sent toother system Headquarters-

IDoc: PAYEXT

Headquarters

Post PaymentOrders

IHC0 Post Payment Order from Subsidiary

Headquarters

Check accountstatements

F9K3

-optional-

Account statementsexist

Headquarters

Create BankStatement

Payment Order isposted F9N7 IDoc FINSTA

Bank Statements foreach Subsidiary

Sent BankStatements toSubsidiary

Subsidiary

Post BankStatement

IDoc FINSTA -available

AccountantBank

FEBP

Select Bank Statements

Post BankStatements

Clearing Account

Debit/Credit IHC

Attention: This is atask for eachsubsidiary (Payeeand payer).

Subsidiary

Post process BankStatement

When TransactionFEBP has beencompleted

FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: Are there anyerrors.

Attention: This is atask for eachsubsidiary (Payee

and payer).


7/27/2019 801_BPP_EN_DE

20/105


3.2 External Outgoing Payments


BusinessRole


Subsidiary



AccountantPayables

F110 Data medium iscreated and sent toother system Headquarters-

IDoc: PAYEXT

Headquarters

Post PaymentOrders


Output:

IDoc: PAYEXT created

A Payment Requestis created.

Check withtransaction F8BT thatpayment request iscreated.

Headquarters


F9K3

-optional-


Headquarters


Payment Order isposted

F9N7 IDoc FINSTA

Bank Statements forSubsidiary


Headquarter

Automatic PaymentTransaction forPayment Requests

F111 Data Medium for House Bank -created

Headquarter

Check data medium

FDTA

-optional-

Data Medium shouldexist

Subsidiary

Post BankStatement


AccountantBank

FEBP


Post BankStatements

Clearing Account Debit/Credit IHC

Subsidiary


When TransactionFEBP completed

FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: Are there anyerrors


7/27/2019 801_BPP_EN_DE

21/105


3.3 External Outgoing Payments by Check


BusinessRole


Subsidiary



AccountantPayables

F110 Data medium iscreated and sent toother system Headquarters-

IDoc: PAYEXT

Headquarters

Post PaymentOrders


Output:

IDoc: PAYEXT created

A Payment Requestis created.

Check withtransaction F8BT thatpayment request iscreated.

Headquarters

Check account

statements

F9K3

-optional-

Exist accountstatements

Headquarters



F9N7 IDoc FINSTA



Headquarter

Automatic PaymentTransaction for

Payment Requests

F111 Outgoing checkcreated

Headquarter Prfen ob Checkerstellt ist

Subsidiary

Post BankStatement


AccountantBank

FEBP


Post BankStatements


Subsidiary

Post process Bank

Statement


FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: There are

any errors


7/27/2019 801_BPP_EN_DE

22/105



BusinessRole


3.4 Incoming Payments and Cash Pooling


BusinessRole


Headquarters


Prerequisite: openitems in Subsidiary

FF_5 Process datamedium from HouseBank

Data Format :MT940

Headquarters

Post PaymentOrders

IHC0 Post Payment Order from House Bank

Headquarters


F9K3

-optional-

Exist accountstatements

Headquarters



F9N7 IDoc FINSTA



Subsidiary

Post BankStatement


AccountantBank

FEBP


Post BankStatements

Subsidiary



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: There areany errors


7/27/2019 801_BPP_EN_DE

23/105


3.5 External Payments with Foreign Currency toanother Clearing Center


BusinessRole


Subsidiary



AccountantPayables

F110 Data Medium iscreated and sent toother system Headquarters-

IDoc: PAYEXT

Headquarters

Post PaymentOrders


Headquarters


F9K3

-optional-


Headquarters



F9N7 IDoc FINSTA


Bank statements forHeadquarterscreated

Headquarters

Post BankStatement


AccountantBank

FEBP


Post BankStatements

Headquarters


When TransactionFEBP has beencompleted

FEBA_BANK_STATEMENT

-optional-

Edit Bank statement


Subsidiary

Post BankStatement


AccountantBank

FEBP


Post BankStatements



Subsidiary


When Transaction

FEBP has beencompleted

FEBA_BANK_STATEMENT

-optional-

Edit Bank statement

Check: Are there any


7/27/2019 801_BPP_EN_DE

24/105



BusinessRole


errors.

Attention: This is atask for each

subsidiary (Payeeand payer).

3.6 Internal Returns

Process Step Business

Condition

Business

Role

Transaction Code Expected

Results

Headquarters

Reverse PaymentOrders

IHC0 Reversed PaymentOrder fromSubsidiary

Headquarters


F9K3

-optional-

Accountstatements exist

Posting Text:Canceled

Headquarters



F9N7 IDoc FINSTA

Bank Statementsfor eachSubsidiary


Subsidiary

Post Bank

Statement


AccountantBank

FEBP


Post BankStatements



Subsidiary

Post processBank Statement

WhenTransactionFEBP has beencompleted

FEBA_BANK_STATEMENT

-optional-

Edit Bankstatement

Check: Are thereare any errors.



7/27/2019 801_BPP_EN_DE

25/105



BusinessRole

Transaction Code ExpectedResults

and payer).

3.7 External Returns


BusinessRole


Headquarters

Display PaymentRequests

When F111 isdone, Paymentrequest is cleared

F8BT Cleared paymentrequest: clearingdocument number isavailable

Headquarters

Reverse Document

Clearing documentnumber fromtransaction F8BT

FB08 Reversed clearingdocument frompayment request

Headquarters

Reverse Clearing ofPayment Request

F8BW Payment request iscleared

Headquarters

Reverse PaymentOrder

IHC0 Reversed paymentorder from subsidiary

Headquarters


F9K3

-optional-

Exist account

statements

Posting Text:Canceled

Headquarters



F9N7 IDoc FINSTA

Bank Statements foreach Subsidiary


Subsidiary

Post BankStatement

IDoc FINSTA -

available

Accountant

Bank

FEBP


Post Bank

Statements



Subsidiary



FEBA_BANK_STATEMENT

-optional-

Edit Bank statement




7/27/2019 801_BPP_EN_DE

26/105



BusinessRole


and payer).

3.8 End-of Day Processing

Process Step Business Condition BusinessRole

TransactionCode

Expected Results

Headquarters

End-of-Day Processing

F9N11 Transfer transaction datafrom IHC to FI. Alltransactions are postedin the FinancialAccounting.

Headquarters

Status Overview ofReports in End of DayProcessing

F9N10 Status of Report shouldbe Completed

Headquarters Check OwnSpool Requests

Spool Requests

Headquarters

Status message types

F961 Check message types


7/27/2019 801_BPP_EN_DE

27/105


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 andprovide a daily review of the corporate cash position.

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

4.1 Process Steps Internal Payments

4.1.1 Creation of Payment Media Using Classical PaymentMedium Program

Use

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

Prerequisites

There are open Items in the subsidiary for internal payments.

Procedure





Periodic Processing Payments

Transaction Code F110



Business role menu Accounts Payable Posting Payments Automatic Payment


7/27/2019 801_BPP_EN_DE

28/105


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


Run Date e.g.

e.g.

enter

Identification freely define theidentification

e.g. enter

3. Choose Parameter.

4. On theAutomatic payment transactions: Parameterscreen, make the following entries:


Posting Date e.g.

e.g.

enter

Docs EnteredUp To

e.g.

e.g.

enter

CompanyCode

e.g. enter

Pymt Meths Payment Methods

select

Next p/date Posting Date of thenext Payment Date

e.g. the day of the nextposting date you wantto run the payments

enter

Vendor e.g.: Only you want certain

Vendor(s)Enter

Otherwise: *

to e.g. Vendor, if you selectan interval

Enter

Otherwise: empty

5. Choose Additional Log and make the following entries:

Field name Description User action andvalues

Comment

Due date check mark

Payment methodselection in all cases

mark

Pmnt method selection ifnot successful

empty

Line items of the paymentdocuments

mark

Vendors (from/to)

e.g.

Enter

optional


7/27/2019 801_BPP_EN_DE

29/105


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


Program RFFOEDI1 Payment mediaprogram RFFOEDI1

select

Variant Standard internal

The variant has beencreated inconfiguration guide.

select

7. Choose Save (Ctrl+S).

8. Choose Status.

9. Choose Proposal (Shift+F1).

10. On the Schedule Proposalscreen, make the following entries:


Start immediately mark

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

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

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

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

15. Choose Back (F3).

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

17. On the Schedule Paymentscreen, make the following entries:


Start

immediately

mark

CreatePaymentMedium

mark

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

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

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

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


7/27/2019 801_BPP_EN_DE

30/105


21. In addition you can create thepayment listand the exception list. To do so, choose Edit

Payments Payment ListorEditPayments Exception List.Choose Continue (Enter)

to execute the list.

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

4.1.2 Post Payment Orders

Use

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

Procedure

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

SAP System SAP Headquarters System

SAP ECC Menu AccountingFinancial Supply Chain ManagementIn-

House CashAccount ManagementIHC Payment

Orders Payment Order Browser

Transaction Code IHC0


Business role Treasurer (SAP_NBPR_TREASURER_BNI-S)

Business role menu Cash Management Cash Management Planning Payment

Order Browser

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


Bank Area select

Year e.g. enter current year

3. On the Browser for IHC Payment Orderscreen, choose SelectIHC Payment Orders.

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

- Description of Status: Flagged for Posting

- Transaction Type: INTPAY

Note the Payer Account Number and Recipient Account Number for the steps: DisplayBank Accounts and Create Bank Statement.

The Recipient Bank Number is: 88888888


7/27/2019 801_BPP_EN_DE

31/105


4. Choose the Payment Ordertab page.

5. Choose Post.

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

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.

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

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

4.1.3 Display Bank Accounts (optional)

Use

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

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

Procedure

1. Access the transaction choosing one of the following navigation optionsOption 1: SAP Graphical User Interface (SAP GUI)



House CashAccountDisplay

Transaction Code F9K3



Business role menu Cash Management Cash Management Reporting Display

Account

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


Bank Area select

Account number

e.g. forsubsidiary_1

andsubsidiary_2

Enter Payer AccountNumber used forPost Payment Order

+ Internal Payments

Recipient AccountNumber


7/27/2019 801_BPP_EN_DE

32/105



From TransactionIHC0 (before).

3. Choose Enter.

4. Choose theAccount Statements tab page.

5. Choose Current Bank Statement.

Result

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

4.1.4 Create Bank Statement

Use

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

Prerequisites

The subsidiaries have made internal payments to the headquarters.

Procedure

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




House Cash Periodic ProcessingBank Statement

New RunSingle Run

Transaction Code F9N7



Business role menu Cash Management Cash Management Planning Bank

Statement - Single Account

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


Bank Area select

Account Number

enter


7/27/2019 801_BPP_EN_DE

33/105




and subsidiary_2

Statement Date Post Day from PostPayment Order

You can see it withtransaction F9K3 too.

Selection date mustbe before or on thecurrent posting date

Simulation Run empty

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

For this case, thisindicator must not beset.

StatementWithoutTurnovers

empty

With Address mark

3. Choose Execute (F8).The message For account 999999999, bank area IHB, an FAS IDoc is createdappears.

4. Choose Enter.

Result

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

4.1.5 Post Bank Statement

Use

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

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

Procedure



7/27/2019 801_BPP_EN_DE

34/105




SAP ECC Menu AccountingFinancial AccountingBanksIncomings

Bank StatementPost

Transaction code FEBP


Business role SAP_NBPR_BANKACC_S (Bank Accountant)

Business role menu Bank AccountingIncomingsPost Electronic Bank

Statement

2. On the Update Bank Statementscreen, in the area Bank Statements, make the followingentries:


*all When all fieldsempty processed allopen bankstatements

When there is noselection (choice), allnot processed bankstatements willprocessed

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


Statement Date

e.g.

Enter date, where theBank Statementscreated inHeadquarter(WithTransactionF9K3 you can see thePosting Date in HQ)

House Bank e.g.: select

Account ID e.g.: Select

The Company Codeappears too

Currency e.g. Only BankStatements with

currency EURenter

4. On the Update Bank Statementscreen, in the area Posting Params, make the followingentries:


Post immed. mark

Assign ValueDate Account

mark

5. On the Update Bank Statementscreen, in the area Output Control, make the followingentries:


7/27/2019 801_BPP_EN_DE

35/105



Execute asbackground Job

empty The job is working onthe screen

Print BankStatements

mark List of the BankStatements

Print Posting Log mark Posted BankStatements in thesubsidiary

Print Statistics mark

Separate List mark

6. Choose Execute.

ResultThe bank statements are posted in the subsidiary.

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

Choose Back (F3)

There appears a message Processing Completed

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

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

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

Subsidiary_1: IND and subsidiary_2: INC +

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

4.1.6 Post process Bank Statement (optional)

Use

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

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

Procedure



7/27/2019 801_BPP_EN_DE

36/105





Bank StatementReprocess

Transaction code FEBA_BANK_STATEMENT



Business role menu Bank AccountingIncomingsPostprocessing Bank

Statement

2. On the Selection of Bank Statements by Banks and Account Nos, make the following entries:Field name Description User action and values Comment

House Bank select

Account ID select

3. Choose Execute.

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

5. Select the errors that are red.

6. Change the error and post again.

7. Choose Save.

Result

The errors have been corrected in the subsidiary system.


7/27/2019 801_BPP_EN_DE

37/105


4.2 Process Steps External Outgoing Payments

4.2.1 Creation of Payment Media Using Classical Payment

Medium Program

Use

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

External payments are defined in the vendors master data view Payment TransactionsAccountingand the field Payment method.

Prerequisites

There are open items in the subsidiary for external payments.

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











Run Date e.g.

e.g.

enter

Identification Freely define theidentification

e.g. enter




Posting Date e.g.

e.g.

enter

Docs EnteredUp To

e.g.

e.g.

enter

Company

Code

enter


7/27/2019 801_BPP_EN_DE

38/105



external>

Next p/date Posting Date of thenext Payment

e.g. the day of the nextposting date you wantto run

Vendor e.g. Only you want certainvendor

Enter

Otherwise: * enter


Enter

Otherwise: empty



Comment

Due date check mark


mark


empty

Line items of the payment

documents

mark

Vendors (from/to)

e.g.

Enter

optional

6. Choose Printout/data medium.

7. Make the following entries:


Program RFFOEDI1 Payment media

program RFFOEDI1


Use the variantcreated in theconfiguration guide forthis building block(step Create Variantfor Payment RunF110).

select


9. Choose Status.


7/27/2019 801_BPP_EN_DE

39/105











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



Startimmediately

mark

CreatePaymentMedium

mark


20. Choose Status (Shift+F2) more than once to update the status.As soon as the payment run has been finished, this will be shown on the Schedule Paymentscreen. The number of generated and completed posting orders is displayed.

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

To find out the DME reference numbers, go to DME Administration by choosing Environment

Payment MediumDME Administration. By double-clicking the data medium, you can

display its attributes. Make a note of the reference number(Data Medium tab page) for thedomestic payment (YB_F110_D_UEBERW).

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




Result

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


7/27/2019 801_BPP_EN_DE

40/105



Use


Procedure










Order Browser

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


Bank Area select

Year e.g. enter current year




- Transaction Type: EXTPAY

Note the Payer Account Number for the steps: Display Bank Accounts and Create BankStatement.

The Recipient Bank Number is 88888888

2. Choose the Payment Ordertab page.

3. Choose Post.

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


7/27/2019 801_BPP_EN_DE

41/105


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.

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

4.2.3 Display Bank Accounts (optional)

Use

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

Procedure





House CashAccountDisplay

Transaction Code F9K3



Business role menu Cash Management Cash Management Reporting Display

Account

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


Bank Area select

Account number


Enter Payer AccountNumber used forPost Payment Order

From transactionIHC0 (before)

3. Choose Enter.

4. Select theAccount Statements tab page.

5. Choose Current Bank Statement.


7/27/2019 801_BPP_EN_DE

42/105


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

7. Choose Back(F3).

Result

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

4.2.4 Create Bank Statement

Use

The purpose of this activity is to create bank statements for subsidiaries. When in subsidiary_1there are open bank statements for external payments, you must execute this step forsubsidary_1.

Prerequisites

The subsidiaries have made internal payments to the headquarters.

Procedure





House Cash Periodic ProcessingBank Statement

New RunSingle Run

Transaction Code F9N7



Business role menu Cash Management Cash Management Planning Bank

Statement - Single Account

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


Bank Area select

Account Number


Enter payer accountnumber

Statement Date Post Day from PostPayment Order


7/27/2019 801_BPP_EN_DE

43/105



You can also displayit with transactionF9K3.

Selection date must

be before or on thecurrent posting date

Simulation Run empty

Standard Output empty If this indicator is set,the bank statement isoutput in standardform.

For this case, thisindicator must not beset.

StatementWithoutTurnovers

empty

With Address select

3. Choose Execute.

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 subsidiaryssystem. The system displays a screen with the address, bank account, amount, and postingdate.

4.2.5 Automatic Payment Transaction for PaymentRequests

Use

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

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

Prerequisites

There are open payment requests.

Procedure




7/27/2019 801_BPP_EN_DE

44/105



SAP ECC Menu AccountingFinancial AccountingBanksOutgoing

Automatic PaymentPayment Requests



Business role Treasurer (SAP_NBPR_TREASURER-S)

Business rolemenu

Cash Management Cash Management Planning

Automatic Payment of PRequest



Run Date e.g. enter


e.g. enter




Posting Date e.g.

e.g.

enter

Next p/date Next Posting Date for

the next payment run

e.g. the day of the next

posting date you wantto run

enter

Companycode

select

Paymentmethods

Bank Transfer (Outgoing)

select

5. Choose Dynamic selections.



Key number

e.g.:

Key number paymentrequest from:

Use transaction F8BTto display all openpayment requests.Should be the latestnumber.

Make a note of thepayment requestnumber. You will need

this later for thereversal.


7/27/2019 801_BPP_EN_DE

45/105


To

e.g.::

Key number paymentrequest till:

House Bank e.g. select

Account ID e.g. select


8. ChooseAdditional Log.



Paymentmethodselection inall cases

mark

Line items ofthe paymentdocuments

mark

Due datecheck

empty

10. Choose Continue.

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

12. Choose Continue

13. Choose Payment medium.

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


ReportProgram

RFFOEDI1

Variant EXTERNAL select


14. Choose Save.

15. Choose Proposal



Startimmediately

mark

CreatePaymentMedium

empty

17. Choose Enter. The message Proposal is runningappears.



7/27/2019 801_BPP_EN_DE

46/105


As soon as the proposal run has been finished, this will be shown on screen and themessage Payment proposal has been createdappears.

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

20. If there are no errors, choose Back

21. Schedule payment run by choosing Pmnt run.



Startimmediately

mark

CreatePaymentMedium

mark

22. Choose Enter. The message Payment run is runningappears.


As soon as the payment run has been finished, this will be shown on screen and themessage Payment run has been carried outappears

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

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

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

Result

The payment document and the payment medium have been created. The FI document that wascreated contains two line items. One line item has been posted to the account for outgoingtransfers (bank subaccounts ending with character2 bank clearing accounts).

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

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

4.2.6 Check Output Data Medium optional -

Use

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

Prerequisites

Job Automatic Payment Transaction for Payment Requests is done.

Procedure


7/27/2019 801_BPP_EN_DE

47/105





SAP ECC Menu AccountingFinancial AccountingBanksOutgoing

Automatic Payment Environment Payment Medium DMEAdministration

Transaction Code FDTA



Business role menu Cash Management Cash Management Bank Data

TemSe/REGUT Data Administration



Referencenumber

Empty

Payingcompanycode

for example, enter

Bank country For all countries * enter

Run Date e.g. enter

Identification empty

Format emptyPymt. runs select

Proposalruns

empty

Data medium(not yettransferredexternally)

select

Data medium(transmit. Toexternal)

empty

Data mediumw/out acctstmt

select

Data mediumwith acct stmt

select

3. Choose Execute (F8).

Result

There should be a line with the same Identification (added by the letter R) you used for thepayment run with transaction F111. Date created should be todays day.


7/27/2019 801_BPP_EN_DE

48/105


4.2.7 Post Bank Statement

Use

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

Procedure





Bank StatementPost

Transaction code FEBP



Business role menu Bank AccountingIncomingsPost Electronic Bank

Statement

2. On the Update Bank Statementscreen, in the area Bank Statements, make the followingentries:


*all When all fieldsempty processed allopen bankstatements

When there is noselection, allunprocessed bankstatements will beprocessed.

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


Statement Date

e.g.

Enter date bankstatements created inheadquarters. Withtransaction F9K3 youcan see the postingdate in HQ)

enter

House Bank e.g.: Select

The company codeappears too

Account ID e.g.: Select


7/27/2019 801_BPP_EN_DE

49/105


The company codeappears too

Currency e.g.: Only bank statementswith currency EUR

enter

4. On the Update Bank Statementscreen, in the area Posting Parms, make the followingentries:


Post immed mark

Assign ValueDate Account

mark

5. On the Update Bank Statementscreen, in the area Output Control, make the followingentries:


Execute asbackground Job

empty The job is working onthe screen

Print BankStatements

mark List of the bankstatements

Print Posting Log mark Posted bankstatements in thesubsidiary

Print Statistics mark

Separate List mark

6. Choose Execute. .

Result

The bank statements are posted in the subsidiary.

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

Choose Back (F3)

The message Processing Completed appears.

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

Transactional code is: 020 -.

4.2.8 Post process Bank Statement (optional)

Use


7/27/2019 801_BPP_EN_DE

50/105


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

Procedure





Bank StatementReprocess

Transaction code FEBA_BANK_STATEMENT



Business role menu Bank AccountingIncomingsPostprocessing Bank

Statement

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


House Bank select

Account ID select

3. Choose Execute.

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

5. Select the errors that are red.

6. Change the error and post again.

7. Choose Save.

Result

The errors have been corrected in the subsidiary system.

4.3 Process Steps External Outgoing Payments byCheck


7/27/2019 801_BPP_EN_DE

51/105


4.3.1 Creation of Payment Media Using Classical PaymentMedium Program

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

External payments are defined in the vendors master data view Payment TransactionsAccountingand the field Payment method.

Prerequisites

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

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











Run Date e.g.

e.g.

enter


e.g. enter




Posting Date e.g.

e.g.

enter

Docs EnteredUp To

e.g. enter

Company

Code

e.g. enter


7/27/2019 801_BPP_EN_DE

52/105



external>

Next p/date Posting date of thenext Payment Run

e.g. enter

Vendor e.g. enter


Enter

Otherwise: empty



Comment

Due date check mark


mark


empty

Line items of the paymentdocuments

mark

Vendors (from/to)

e.g.

Enter

optional

6. Choose Printout/data medium.


Fieldname

Description User action and values Comment

Program RFFOEDI1 Payment mediaprogram RFFOEDI1


Use the variant

created in theconfiguration guide forthis building block(step Create Variantfor Payment RunF110).

select

8. Choose Save Parameters (Ctrl+S).

9. Choose Status.


7/27/2019 801_BPP_EN_DE

53/105











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



Startimmediately

mark

CreatePaymentMedium

mark


20. Choose Status (Shift+F2) more than once to update the status.As soon as the payment run has been finished, this will be shown on the Schedule Paymentscreen. The number of generated and completed posting orders is displayed.

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

To find out the DME reference numbers, go to DME Administration by choosing Environment

Payment MediumDME Administration. By double-clicking the data medium, you can

display its attributes. Make a note of the reference number(Data Medium tab page) for thedomestic payment (YB_F110_D_UEBERW).

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




Result

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


7/27/2019 801_BPP_EN_DE

54/105



Use


Procedure










Order Browser




- Transaction Type: CHECK

Note the Payer Account Number for the steps: Display Bank Accounts and Create BankStatement.

7. Choose the Payment Ordert

801_BPP_EN_DE

Documents

Transcript of 801_BPP_EN_DE