Config in House Cash

8/18/2019 Config in House Cash

http://slidepdf.com/reader/full/config-in-house-cash 1/64

SAP In-House Cash:Configuration Guide

Release mySAP ERP 2004



Configuration Guide SAP In-House Cash (Release mySAP ERP 2004) 22.6.2004

Copyright

© Copyright 2004 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 in this publication is subject to change without noticeand does not represent a commitment on the part of SAP AG in the future.

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

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registeredtrademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of the

IBM Corporation 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 Open Group.

Citrix®, the Citrix Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,MultiWin® and other names of Citrix products mentioned are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 fortechnology invented and implemented by Netscape.

Market Set and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned hereinas well as their respective logos and trademarks or registered trademarks of SAP AG in Germany andin several other countries all over the world. All other products and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informationpurposes only. National product specifications may vary.

Page 2/64




Symbols

Symbol Description

Caution

Example

Note

Recommendation

Syntax

Typographical Conventions

Format Description

Example Text Words or characters quoted from screens.

These include field names, screen titles, pushbutton labels, menunames, menu paths and menu options.

Cross-references to other documentation.

Example Text Emphasized words or phrases in body text, graphic titles and tablestitles.

EXAMPLE TEXT Technical names of system objects.These include report names, program names, transaction codes, tablenames and key concepts of a programming language when they aresurrounded by body text, for example, SELECT and INCLUDE.

Example Text Output on the screen.

This includes file and directory names and their paths, messages,names of variables and parameters, source text, and names ofinstallation, upgrade and database tools.

Example Text Exact user entry.

These are words or characters that you enter in the system exactly asthey appear in the documentation.

<Example Text> Variable user entry.

Angle brackets indicate that you replace these words and characterswith appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Page 3/64




Content

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

1.1 SAP In-House Cash: The Components...................................................................................... 5

1.2

SAP In-House Cash: The Configuration Guide.......................................................................... 5

1.3 SAP Notes.................................................................................................................................. 6

2 General Settings for Creating New Company Codes ..................................................................... 8

3 Integration of Systems.................................................................................................................. 10

3.1 ALE Customizing in the SAP In-House Cash System.............................................................. 10

3.2 ALE Customizing in the Subsidiary Company System............................................................. 21

4 Business Customizing .................................................................................................................. 26

4.1 Customizing Financial Accounting for Subsidiary Companies................................................. 26

4.2

Customizing the In-House Cash Center................................................................................... 31

4.2.1 Basic Settings ........................................................................................................................... 31

4.2.2 Master Data .............................................................................................................................. 37

4.2.3 Account Management............................................................................................................... 38

4.2.4 Periodic Tasks (General Ledger Transfer) ............................................................................... 45

4.2.5 Authorization Management....................................................................................................... 47

4.2.6 Integration in SAP Cash Management ..................................................................................... 49

4.3 Customizing the Group Head Office......................................................................................... 50

4.4 Localization............................................................................................................................... 54

5

Configuring Component-Specific Master Data ............................................................................. 56

5.1 Create Business Partner Roles in SAP In-House Cash ........................................................... 56

5.2 Create Current Account............................................................................................................ 57

6 Ongoing Settings .......................................................................................................................... 58

6.1 Current Settings for Updating the Posting Date for Payment Transactions and Closing......... 58

6.2 Ongoing Settings for Integration with SAP Cash Management ............................................... 59

7 Tips and Tricks.............................................................................................................................. 60

7.1 PAYEXT IDoc is not created .................................................................................................... 60

7.2

FINSTA IDoc is not created...................................................................................................... 60

7.3 Forwarding of payment requests failed .................................................................................... 60

8 Reverse......................................................................................................................................... 62

9 Application Security Guide for SAP In-House Cash ..................................................................... 63

9.1 Introduction............................................................................................................................... 63

9.2 Security Measures for Saving Data.......................................................................................... 63

9.3 Authorizations........................................................................................................................... 64

9.4 Data Protection......................................................................................................................... 64

9.5 ALE........................................................................................................................................... 64

9.6

Encryption................................................................................................................................. 64

Page 4/64




1 Introduction

1.1 SAP In-House Cash: The Components

PurposeThe SAP In-House Cash component is a solution for processing internal and external paymenttransactions within a group or company. It reduces the amount of external bank accounts and cross-border payments required.

Implementation Considerations

The head office financial accounting system used by SAP In-House Cash is based on Release mySAPERP 2004.

Integration

Use of SAP R/3 FI standard payment programs

Use of SAP R/3 FI standard account statement programs

Link to SAP R/3 Cash Management

Scope of Functions

• Automation of payment transactions within the group: Internal payment clearing

• Automation of payment transactions outside the group: Central payments

• Automation of incoming payments: Central cash receipt

• Account management functions

• Currency conversion

Example

For examples of the use of this component, see the white paper for SAP In-House Cash:

• German version: Material number 50 051 076s

• English version: Material number 50 059 428s

You can also access this document in SAPNet under the alias fscm → Media Library.

1.2 SAP In-House Cash: The Configuration Guide

SAP In-House Cash Processes

This configuration guide applies to the following SAP In-House Cash processes in connection with thecorresponding release of the relevant mySAP.com application components.

In-House Cash Processes and mySAP.com Application Components

SAP In-House Cash Process mySAP.com Application Component with Minimum Release

Internal payments SAP ECC 5.00

Central payments SAP ECC 5.00

Central incoming payments SAP ECC 5.00

Page 5/64




Content

This configuration guide contains all of the steps required to implement the SAP In-House Cash processes. The guide explains both the order of the individual configuration activities and their mutualdependencies.

It contains information about the following:

• Integration of systems

• Business Customizing

• Configuring the component-specific master data

• Current settings in production operations

• Tips and tricks

• Reverse

• Application security guide for SAP In-House Cash

For more information about the SAP In-House-Cash processes, see SAPNet under the alias fscm or

SAP Service Marketplace under the Internet address service.sap.com/business maps.

Target Audience

• SAP application consultants – SAP internal. The following prerequisites apply: SAP In-HouseCash training course (FSC120), knowledge of the processes of SAP In-House Cash, andknowledge of BCA.

Documentation

For more information about the documentation and demo scripts available, see SAPNet under thealias fscm . For more information about the IDES demo systems available for SAP In-House Cash,

see SAPNet under the alias ides. This also gives you informtion about settings.

Feedback on Configuration Guide

In order to continually improve the configuration guide, we would appreciate your feedback. If you finderrors in the configuration guide, enter a message for the component SAP In-House Cash, (FIN-FSCM-IHC) in the SAP Service Marketplace under the Internet addressservice.sap.com/messages .

1.3 SAP Notes

Before you start to configure this business scenario, read the following SAP notes. This summarycontains only the most central SAP notes to give you an initial overview.

Central SAP Notes for SAP In-House Cash, Release mySAP ERP 2004

Support Package SAP Note Title of SAP Note

460630 Bank Data Incomplete in PAYEXT IDoc

481197 Inconsistencies in Tables T042Y and T042I

506628 Authorization Groups and Authorization GroupObjects

522747 Partner Company Not Filled in General LedgerTransfer

527431 EUPEXR IDoc Created with Status 63

Page 6/64




537404 Customizing Value Date: Payment Order perIDoc

576679 General Ledger Transfer to G/L AccountsManaged by Company

494777 Customer Enhancement in Electronic Account

Statement

406037 IHC General Ledger Transfer

501068 Bank Statement Subsequent Processing: In-House Cash

To get a comprehensive and up-to-date overview of the SAP notes for a businessscenario and the relevant mySAP.com application components, use the search functionfor notes on the SAP Service Marketplace under the Internet addressservice.sap.com/notes .

Page 7/64






5. Define Days Difference Between Value Date at House Bank and Partner Bank

Menu Path Transaction Code

IMG: Corporate Finance Management → Transaction Manager →

General Settings → Payment Management → Payment Handling → Value Date → Define Diff. in Days Betw. Value Date of House/PartnerBank

F8B4

6. Define Factory Calendar per Currency


IMG: Corporate Finance Management → Transaction Manager →

General Settings → Payment Management → Payment Handling →

Value Date → Define Factory Calendar per Currency

F8BC

7. Deactivate Financial Object Integration


IMG: Corporate Finance Management → Basic Analyzer Settings → Automatic Integration of Financial Objects in Transaction Master Data

→ Other Transactions → BCA Account → Activate/Deactivate FinancialObject Integration

RMIBKKA

Deactivate the Component Active indicator.

Page 9/64




3 Integration of Systems

Purpose

This section contains information about integrating your systems in a mySAP.com system landscape.

This includes, for example:

• Defining and configuring logical systems

• Processing the distribution model in the system in which SAP In-House Cash is installed anddistributing the distribution model in the systems of the subsidiary companies

• Generating and editing partner profiles

• Completing the configuration settings and carrying out additional activities required

Process Flow

Carry out the steps below in the order in which they are listed.

For more information, see the documentation for Application Link Enabling (ALE) and IDoc (transaction WE60).

3.1 ALE Customizing in the SAP In-House Cash System

Use

Here you make the ALE Customizing settings required for the SAP In-House Cash component fromthe view of the system in which SAP In-House Cash and Financial Accounting for the group headoffice are run. Include a person responsible at the customer’s end in the implementation project.

For payment orders from companies affiliated with the in-house cash center, use message typePAYEXT with basic type PEXR2002 and transaction code PEXR as the inbound parameter. For bank

statements from the in-house cash center to affiliated companies, use message type FINSTA withbasic type FINSTA01 and the transaction code FINS as the inbound parameter.

For the payment order from the in-house cash center to the clearing partner or executing system, usemessage type PAYEXT with basic type PEXR2002 and the transaction code PEXC as the inboundparameter. The clearing partner can either be a company code or a different bank area. You can alsohave two clearing partners in the same client. In this case the recipient and sender systems are thesame. Use the RFC destination NONE.

If SAP In-House Cash is in a different system from Financial Accounting of the head office, use thefollowing parameters for transferring the general ledger from the in-house cash center to financialaccounting:

• Outbound parameter in SAP In-House Cash:

Message type FIDCC1 or FIDCC2

Basic type FIDCCP01 or FIDCCP02

Transaction code FID1 or FID2

• Inbound parameters in Financial Accounting for the head office:

Message type FIDCC1 or FIDCC2

Basic type FIDCCP01 or FIDCCP02

Transaction code FID1 or FID2

See also SAP notes 114814 and 555021.

Page 10/64




For external payments, consistent bank master data (table BNKA) may be necessary for the differentaffiliated systems or clients (subsidiaries, SAP In-House Cash system and FI of head office).

You can start an automatic distribution of bank master data. For more information, see the SAP libraryunder Cross-Application Components Business Framework Architecture (CA-BFA) ALEBusiness Process Library (CA-BFA-ABL) Cross-Application Business Processes BankDistribution.

Prerequisites

Basic knowledge of the SAP ALE distribution model.

The In-House Cash business partners have been created.

If SAP In-House Cash and subsidiary companies are in the same system, you can skip steps 4 to 6.

Procedure

All ALE settings are in the IMG under:


IMG: SAP NetWeaver → SAP Web Application Server → IDoc Interface / Application Link Enabling (ALE)

SALE

1. Define Logical System

You have to define the logical systems. You store system names here for the logical systemsfor SAP In-House Cash, the subsidiaries and Financial Accounting of your head office. IfFinancial Accounting of your head office is in the same client as SAP In-House Cash, youshould make an entry here to show that an RFC connection is not used, for example, LOCAL.


IMG: IDoc Interface / Application Link Enabling (ALE)→ Basic Settings

→ Logical Systems → Define Logical System

SALE

Detailed Settings

Field Name Description User Action and Values Note

Log.System Logical system Example: TNFCLNT400

Name Name

2. Assign Logical System to Client

Here you assign a client to the system for SAP In-House Cash. Generally, the customer hasalready made this assignment.



→ Logical Systems → Assign Logical System to Client

SALE

Page 11/64




Detailed Settings

Field Name Description User Action andValues

Note

Client Client Example: 400

City City

Logical system Logical system Logical system that youdefined in 1

Example:

TNFCLNT400

Std currency Standard currency

Changes andtransports for client-specific objects

Changes andtransports for client-specific objects

Indicator Changeswithout automaticrecording

Cross-client objectchanges


Changes to Repositoryand cross-clientCustomizing allowed

Protection: Clientcopier andcomparison tool

Protection regardingclient copy programand comparison tools

Protection level 0: Norestriction

Restrictions Restrictions Indicator that startingCATT processes ispermitted

3. Define Target Systems for RFC Calls

Here you define the subsidiary system as the target system. If Financial Accounting of thehead office is not in the same client as In-House Cash, you must also create an RFC

destination for it. Otherwise you do not need to explicitly create an RFC connection. (In thecase of external payments, the fixed RFC destination NONE can be used for the IDoc port.)


IMG: IDoc Interface / Application Link Enabling (ALE)→ Communication

→ Create RFC Connections

SM59

Choose R/3 connections → Create.

Detailed Settings


RFC Destination RFC destination Example: TNFCLNT401

Connection Type Connection type 3

Description Description

Logon/Security Logon data

Save and click on Test Connection to test the connection.

Here you can define a technical user. This means that the system is still accessible even ifthe personal user is deleted.

Page 12/64




4. Modeling and Implementing Business Processes, Maintain Distribution Model, andDistribute Views

Note: You do not have to maintain and distribute the distribution model if SAP In-House Cash and the subsidiary companies are in the same client. If this is the case, go to step 7.


IMG: IDoc Interface / Application Link Enabling (ALE)→ Modeling and

Implementing Business Processes → Maintain Distribution Model andDistribute Views

BD64

Choose Switch between Display and Edit Mode → Create Model View .

Detailed Settings


Short text Short text

Technical name Technical name Example: IHCStart date Start date

End date End date

Choose Enter , then double click on your model view to check the entry.

Choose Add Message Type.

Here you process the entries for sending bank statements (IDoc FINSTA) from SAP In-House Cash to subsidiary companies.

Detailed Settings


Model view Model view The model view you defined Example: IHC

Sender Sender Logical system of headoffice

Example: TNFCLNT400

Receiver Receiver Logical system of subsidiary Example: TNFCLNT401

Message type Message type FINSTA Bank statement


Here you process entries for sending payment orders (IDoc PAYEXT) and bankcollections (IDoc DIRDEB) from the subsidiary to SAP In-House Cash. For bankcollections you can copy PAYEXT.

Page 13/64




Detailed Settings



Sender Sender Logical system of subsidiary Example: TNFCLNT401

Receiver Receiver Logical system of headoffice

Example: TNFCLNT400

Message type Message type PAYEXT Payment order


Detailed Settings



Sender Sender Logical system of subsidiary Example: TNFCLNT401

Receiver Receiver Logical system of headoffice

Example: TNFCLNT400

Message type Message type DIRDEB Preauthorizedwithdrawal

5. Generate Partner Profiles


IMG: IDoc Interface / Application Link Enabling (ALE)→ Modeling and

Implementing Business Processes → Partner Profiles → GeneratePartner Profiles

BD82

Detailed Settings



Partner system Partner system Logical system of subsidiary Example: TNFCLNT401

Output mode Indicator: Transfer IDocimmediately

Choose Execute to generate the partner profile.

6. Distribute Model View


IMG: IDoc Interface / Application Link Enabling (ALE) → Modeling and

Implementing Business Processes → Maintain Distribution Model andDistribute Views

BD64

Select your model view.

Choose Edit → Model View → Distribute.

Select the subsidiary system as the target system.

Page 14/64




In the subsidiary system, check whether the distribution model has been distributed. Fortechnical purposes, the system generates message type SYNCH in the partner profiles ofpartner type LS in the outgoing direction. Therefore, you do not need to create messagetype SYNCH in the distribution model.

7. Create Transactional RFC Port

Carry out the following activity only if SAP In-House Cash and the subsidiary companies are inthe same client.


SAP Easy Access → Tools → ALE→ ALE Administration → Runtime

Settings→ Port Maintenance

WE21

Choose Create to create a transactional RFC port.

Detailed Settings


Port Port Let the system generate a portname or assign your own portname

Description Description Send IDocs to self

RFC destination RFC destination NONE

Choose Save to create a transactional RFC port.

Carry out the following activity only if SAP In-House Cash and Financial Accounting of thehead office are in the same client.


SAP Easy Access → Tools → ALE → ALE Administration → Runtime

Settings→ Port Maintenance

WE21

Choose Create to create a transactional RFC port.

Detailed Settings


Port Port Let the system generate a port

name or assign your own portname

Description Description Loopback to local system

RFC Destination RFC destination NONE

Choose Save to create a transactional RFC port.

Page 15/64




8. Process Partner Profiles for Business Partners Manually

See SAP note 429133.

For ALE communication, you have to define partners with inbound and outbound parameters.


SAP Easy Access → Tools → ALE → ALE Administration → RuntimeSettings → Partner Profiles

WE20

Select Partner Type BP .

Choose Create.

Detailed Settings


Partner no. Partner number Business partner number

Type US

Agent Agent User ID

Language Language

Choose Outbound Parameters.

Detailed Settings


Message type Message type FINSTA

Receiver port Receiver port The port you generated

Output mode Output mode Indicator: Transfer IDocimmediately

Basic type Basic type FINSTA01

Syntax check Syntax check Select

Choose Inbound Parameter .

Detailed Settings

Field Name DescriptionUser Action and Values

NoteMessage type Message type DIRDEB

Process code Process code PEXN (used to be PEXR) Processing of incomingpayments


Processing byfunction module


Trigger immediately Only in test phase,otherwise Trigger bybackground program

Page 16/64




Detailed Settings


Message type Message type PAYEXT

Process code Process code PEXN Processing of

incoming payments





Copy the settings for message type PAYEXT for preauthorized withdrawal (bank collection) withmessage type DIRDEB.

You have to make entries for each subsidiary company. You can copy the entries as

follows:

Select the partner.

Choose Create Copy .

9. Process Partner Profiles Manually for Logical Systems

Here you process the clearing partners in partner type LS.


SAP Easy Access → Tools → ALE→ ALE Administration → Runtime

Settings→ Port Maintenance → Partner Profiles

WE20

To do this, proceed as described above.

Choose Create.

Detailed Settings


Partner no. Partner number Logical system of Financial Accounting

For example, LOCAL

Partn.Type LS

Agent Agent User ID

Lang. Language


Page 17/64




Detailed Settings


Message type Message type DIRDEB

Message code Message code IHC This field needs to be

filled if FI of headoffice is in the sameclient as IHC becausethe field can be usedto outsort outboundprocessing.

Message function Message function FI See above

Receiver port Receiver port The port you generated Port with destinationNONE if FI of headoffice is in the sameclient, otherwise port

with RFC destinationof FI’s logical system.


Basic type Basic type PEXR2002




Message code Message code IHC This field needs to befilled if FI of headoffice is in the sameclient as IHC becausethe field can be usedto outsort outboundprocessing.


Receiver port Receiver port The port you generated Port with destinationNONE if FI of headoffice is in the sameclient, otherwise port

with RFC destinationof FI’s logical system.




Page 18/64





Message type Message type SYNC

Receiver port Receiver port The port you generated Port with destination

NONE if FI of headoffice is in the sameclient, otherwise portwith RFC destinationof FI’s logical system.


Basic type Basic type SYNCHRON


The following outbound parameter must only be maintained if Financial Accounting of your head officeis not in the same client as your SAP In-House Cash.


Message type Message type FIDCC1 or

FIDCC2

Sending FIdocuments for G/Ltransfer

If SAP In-House Cash and Financial Accounting for thehead office are not in

the same system asBCA, you have to usemessage typeFIDCC1.

Receiver port Receiver port The port you generated Port with RFCdestination of the FI’slogical system


Basic type Basic type FIDCCP01 or

FIDCCP02


Select the logical system of your head office’s Financial Accounting. If the FI is inthe same client as the in-house cash center, this will be the logical system of thein-house cash center. Otherwise, select the logical system that you have definedfor Financial Accounting.

Choose Inbound Parameters

Page 19/64




Detailed Settings


Message type Message type DIRDEB

Message code Message code IHC This field needs to be

filled if FI of head officeis in the same client asIHC because the fieldcan be used to outsortoutbound processing.


Process code Process code PEXC Create paymentrequests


Processing by

function module

Processing by

function module

Trigger immediately Only in test phase,

otherwise Trigger bybackground program

Detailed Settings



Message code Message code IHC This field needs to befilled if FI of head officeis in the same client asIHC because the field

can be used to outsortoutbound processing.


Process code Process code PEXC Create paymentrequests





Copy the settings for message type PAYEXT for preauthorized withdrawal (bank collection) withmessage type DIRDEB.

The following inbound parameter must only be maintained if Financial Accounting of your head officeis not in the same client as your SAP In-House Cash.

Page 20/64





Message type Message type FIDCC1 or

FIDCC2

Sending FI documentsfor G/L transfer

Process code Process code FID1 or

FID2

If SAP In-House Cash and Financial Accounting for the headoffice are not in thesame system as BCA,you have to use processcode FID1.




Trigger immediately Only in test phase,otherwise Trigger bybackground program.

3.2 ALE Customizing in the Subsidiary Company System

Use

Here you make the ALE Customizing settings required for the SAP In-House Cash component fromthe view of the subsidiary company.

For payment orders from companies affiliated with SAP In-House Cash, use message type PAYEXTwith basic type PEXR2002 as the outbound parameter.

For bank collections from companies affiliated with SAP In-House Cash, use message type DIRDEBwith basic type PEXR2002 as the outbound parameter.

For bank statements from the in-house cash center to affiliated companies, use message type FINSTAwith basic type FINSTA01 and process code FINS as the inbound parameter.

When you create PAYEXT, EUPEXR is created automatically. Recommendation: Create a port towhich EUPEXR can be sent since this IDoc type is not required in SAP In-House Cash. You candelete this file defined for the port at specific intervals.

Prerequisites

You have defined the in-house cash center as your house bank and defined the EDIpartner profile and the EDI-compatible payment methods there. See the section

Customizing for Subsidiary Companies → Define In-House Cash Center as House Bank .

Procedure

All of the ALE settings are in the IMG under:


IMG: SAP NetWeaver → SAP Web Application Server → IDoc Interface / Application Link Enabling (ALE)

SALE

Page 21/64




1. Define Logical System

You have to define the logical systems. Here you define the system for the subsidiary andthe system for SAP In-House Cash.

If the subsidiary is in the same system as the in-house cash center, the system entryalready exists since the underlying table is cross-client.


IMG: IDoc Interface / Application Link Enabling (ALE)→ Basic Settings →

Logical Systems → Define Logical System

SALE

Detailed Settings


Log.System Logical system Example: TNFCLNT401

Name Name

2. Assign Logical System to Client

Here you assign a client to the subsidiary system.



→ Logical Systems → Assign Logical System to Client

SALE

Detailed Settings


Client Client Example: 401

City City

Logical system Logical system The logical system youdefined (see step 1)

Example:TNFCLNT401

Std currency Standard currency

Changes andtransports for client-

specific objects

Changes andtransports for client-

specific objects

Select indicator: Changeswithout automatic

recording



Changes to Repositoryand cross-clientCustomizing allowed

Protection: clientcopier andcomparison tool

Protection regardingclient copy programand comparison tools

Protection level 0: Norestriction

Restrictions Restrictions Indicator that startingCATT processes ispermitted

Page 22/64






Detailed Settings


Port Port EUPEXPORT Any value

Description Description Send EUPEX to file port

Physical directory Select the physical directoryindicator

Choose Access Test to test the access to the file.

6. Process Partner Profiles Manually

Here you create the in-house cash center as your house bank in partner type B.



Settings → Port Maintenance → Partner Profiles

WE20

Select Partner Type B.

Choose Create.

Detailed Settings


Partner no. Partner number Bank key Example: 99999999

Type US

Agent Agent User ID

Lang. Language


Detailed Settings



Receiver port Receiver port The port you generated

Output mode Output mode Indicator: Transfer IDocimmediately Only in test phase,otherwise backgroundprocessing



Copy the settings for message type PAYEXT for message type DIRDEB.


Page 24/64




Detailed Settings


Message type Message type EUPEXR

Receiver port Receiver port EUPEXPORT


Only in test phase,otherwise backgroundprocessing

Basic type Basic type IDCREF01


Choose Inbound Parameters

Detailed Settings


Message type Message type FINSTA

Process code Process code FINS Processing ofincoming payments




Trigger immediately

7. Process Partner Profiles Manually for Logical Systems

If the subsidiary is in the same system as the in-house cash center, you have to makethese entries for the logical systems. Make sure that the partner profile is active (partnerstatus A).



Settings→ Port Maintenance → Partner Profiles

WE20

Select Partner Type LS.

Choose your logical system.

Make detailed settings for inbound and outbound parameters as described in step 6.

If the subsidiary is in the same system as the in-house cash center, you effectively sendIDocs to the same system. This means that in partner type LS, the message typesPAYEXT, DIRDEB, and FINSTA have identical inbound and outbound parameters. Youonly define message type EUPEXR in the outbound parameters.

Result

The ALE settings are complete. Test your settings by running a process (for example, internalpayments) as soon as the business Customizing is complete.

Page 25/64




4 Business Customizing

Purpose

This section contains information about the Customizing settings in the systems of the subsidiarycompanies, the SAP In-House Cash system and the head office system. Business Customizing isaimed at adjusting the delivered cross-company functions to the requirements of a specific company.

This includes, for example:

• Customizing for the organizational units

• Customizing for the master data

• Process Customizing

Process Flow


4.1 Customizing Financial Accounting for SubsidiaryCompanies

Use

In this section you make the settings required for the payment program of the subsidiary companies:You define the in-house cash center as new house bank. You define a new payment method forpayments via the in-house cash center. You carry out the Customizing for the incoming electronicaccount statement from the in-house cash center. These settings are required for internal payments,central payments, and central cash receipt.

Group

Subsidiary 3

Subsidiary 2

Subsidiary 1

Organizational Unit: Subsidiary Company

Prerequisites

For the house banks defined, you define the relevant bank accounts for the company code under anaccount ID. Specify the external account number with the bank, the currency, and the G/L accountnumber of the relevant G/L account to make sure that the postings go to the corresponding accounts.Do not forget to create the bank clearing accounts.

Procedure

Make the settings according to the following navigation tables.

Page 26/64




1. Define New Payment Method for Bank Transfer or Bank Collection and Define it in theBank Determination


SAP Easy Access: Accounting→ Financial Accounting→ Banks →

Outgoings → Automatic Payment → Open Items

Menu: Environment → Maintain Config.

FBZP

Define the new payment method per country and for the company code of the subsidiary company.

For the payment method per country, set the indicator for required specifications in the master recordfor the bank connection. You must also set the Collection Authorization indicator for bank collection.See SAP note 460630.

Use the standard payment media program RFFOD_U.

For foreign currency payments, set the Foreign business partner allowed, Foreign currency allowed,Cust/vendor bank abroad allowed indicators in payment methods per company code.

2. Define In-House Cash Center as House Bank

To avoid problems when checking the length of the bank key or the bank number, usetransaction code FIHC. See also SAP notes 335278 and 376180.


IMG: Financial Accounting→ Bank Accounting → Bank Accounts → Define House Banks

FI12

Define the in-house cash center as your house bank and choose EDI partner profiles.

Here you process the partner profiles and the EDI-compatible payment methods.

3. Configure the Electronic Bank Statement

Here you fulfill the requirements for correctly posting all business transactions submitted bythe in-house cash center by means of electronic bank statement.


IMG: Financial Accounting→ Bank Accounting → Business Transactions

→ Payment Transactions → Electronic Bank Statement→ Make GlobalSettings for Electronic Bank Statement

FI12

Make a note of the chart of accounts assigned to your company code. The company

code/chart of accounts assignment is in the IMG under Financial Accounting → General

Ledger Accounting → G/L Accounts → Master Data → Preparations → Assign CompanyCode to Chart of Accounts.

Create the account symbols. The account symbol determines the G/L account which is to be postedto.

Detailed Settings


Account Account

determination: Account symbols

Recommendation: Incoming

payment, outgoing payment

Text Text of length 20

Page 27/64




Assign the account symbols to the accounts.

Detailed Settings


Act Symbol Bank statement:

account symbol

Example: outgoing payment,

incoming payment

Acct Mod. Bank statement:account modification

Example: +, +

Currency Bank statement:currency

Example: +, +

G/L Acct Accountdetermination: G/Laccount number

Example:

Outgoingpayment:+++++++++2,Incoming payment:+++++++++9

Acct Symb. Desc. Text of length 20

Create the key for posting rules. The posting rules represent typical posting transactions for the bankstatement.

Detailed Settings


Posting rule Posting rule Example: 0001, 0006

Text Text of length 40 Example: Incoming payment,outgoing payment

Define the posting rules. The account determination takes place via the posting rule. This provides theinformation required for posting (posting key, accounts, document type).

Detailed Settings


User Action andValues


Posting Rule Posting rule Example: 0001 Example: 0001 Example: 0006

Posting Area Posting area 1 2 1

Posting Key(D)

Posting key 40 40

Special G/LIndicator (D)

Special G/Lindicator

50

Acct (Debit) Accountdetermination:account symbols

Example: bank Example: Incomingpayment

Example:Outgoingpayment

Compression(D)

Posting Key(C)

Posting key

Special G/LIndicator (C)

Special G/Lindicator

Page 28/64




Acct (Credit) Accountdetermination:account symbols

Example: Incomingpayment

Example: Bank

Compression(C)

.

Doc. Type Bank statement:document type

Example: SA Example: DZ Example: SA

Posting Type Bank statement:posting type

1 8 4

On AccountPosting Key

Posting key forposting onaccount

ReversReas. Reason forreversal orinverse posting

Assign transaction types to group banks with identical external transaction codes.

Detailed Settings


Trans. type Transaction type Example: MT940

Name Text of length 40

Assign the business transactions to these posting rules dependent on the transaction type.

Detailed Settings



ExternalTransaction

External businesstransaction

020 051

+/- Sign +/- sign of incomingamount

- +

Posting Rule Posting rule Example: 0006 Example: 0001

Interpretation Algorithm

Interpretation algorithm Standard algorithm Standard algorithm

PlanningType,Transaction

Planning type, transaction

ProcessingType

Processing type 0 0

Assign the bank accounts to the transaction types.

Page 29/64




Detailed Settings


Note

Bank Key Bank key, usually bank

number

Bank key of your bank area

from SAP In-House Cash Bank Account

Bank account number Current account number

Trans. Type Transaction type Example: MT940

CurrencyClass

Class of currency key used

PlanningType

Planning type

Summarization

Summarization of bankstatement items

CompanyCode

Company code

Planning AccountName

Planning account name

For more information about the settings for bank statements, see the documentation.

Result

The in-house cash center is defined as your house bank.

You have created a payment method for payments via SAP In-House Cash.

You have made settings for electronic bank statements.

Page 30/64




4.2 Customizing the In-House Cash Center

Use

As a virtual house bank, the in-house cash center receives payment orders from subsidiary companies

in the form of PAYEXT IDocs and posts them to the corresponding current accounts. For centralpayments, the payment information is also forwarded to the financial accounting system of the headoffice. The in-house cash center creates and sends account-statement-relevant data in the form of aFINSTA IDoc.

GroupHead Office

In-House CashCenter

FinancialAccounting

Organizational Unit: In-House Cash Center

Prerequisites

Basic Customizing settings have been made for BCA.

Procedure

As of mySAP ERP 2004, you can find the implementation guide (IMG) for SAP In-House Cash under

the following path: SAP Customizing Implementation Guide → Financial Supply Chain Management → In-House Cash.

4.2.1 Basic Settings

1. Define In-House Cash Center as Bank Area

Menu Path

IMG: In-House Cash → Basic Settings → Bank Area → Define Bank Area

Detailed Settings


Note

Desc.Bank Area Name of the bankarea

Bank Country Bank country

Bank Key Bank key .

Page 31/64




Language Language

Bk Area Currency Bank areacurrency

The bank area currency isusually the same as the localcurrency of the company code towhich the bank area is assigned.

Cur.pre EURO Currency beforechangeover toEuro

Calendar Factory calendar

Time Post.Cut-Off Time ofautomatic postingcut-off

See documentation

Exch.Rate Type Exchange ratetype

Company Code Company code Each company codeis assigned to abank area.

GL Variant General ledgervariant

The variant can onlybe entered here ifpreviously defined.

The GL variant defines how thetransfer from bank area to FIgeneral ledger takes place.

Activate Log Activate log

IHC Active Activate bankarea as in-housecash center

X

You cannot subsequently change the company code and the general ledger variantbecause there is no check in Customizing for determining whether or not documents havealready been posted.

2. Set Up Number Ranges for Log

Navigation


IMG: In-House Cash → Basic Settings → Set Up Number Ranges for Log IHCN1

Create a number range interval for the log.

3. Authorization for Principle of Dual Control and Amount-Dependent Authorization: See Authorization Management

4. Set Up Number Ranges for IHC Payment Orders

Navigation


IMG: In-House Cash → Basic Settings → Bank Area → Set Up Number

Ranges for IHC Payment Orders

F9A5

For each bank area create a number range interval for IHC payment orders.

Page 32/64




5. Maintain Number Ranges of External Bank Account

Navigation


IMG: In-House Cash → Basic Settings → Bank Area → Maintain Number

Ranges Ext. Account Numbers

F9A5

Create a number range interval for each bank area. Choose whether you want internal or externalnumber assignment.

6. Set Up Container Fields for IHC Payment Orders

Menu Path

IMG: In-House Cash → Basic Settings → Bank Area → Set Up Container Fields for IHC PaymentOrders

7. Define How General Ledger Data Is Transferred to Financial Accounting

You can choose whether the FI general ledger and the bank current account are in the sameor separate systems.

Menu Path

IMG: In-House Cash → Basic Settings → Basic Settings - Postings → Set +/- Sign Postings/GLTransfer/Name Check

Detailed Settings


+/- OutgoingPayments

+/- sign foroutgoingpayments

The system proposesnegative signs bydefault.

Trans.Type FIGen.Led.

Transfer type ofgeneral ledgerdata to FI

The following cases arepossible:

FI general ledger and BCA arein the same or differentsystems

The FI general ledgeris in the same systemas BCA per default.

RFC Destination RFC Destination Only if BCA is in adifferent system to the

FI general ledger

Model View Model view of ALE model

Model view for general ledgertransfer

Only if BCA is in adifferent system to theFI general ledger

Condition Typefor Sales Tax

Condition type forsales tax

Check G/L Databefore Transfer

Check G/L databefore transfer

The default setting isto check the G/L databefore transfer.

Necessary Word

Length forIncorrect Letter

Necessary word

length for anincorrect letter

Page 33/64




Process the partner profiles if BCA is not in the same system as the FI general ledger. Definemessage type FIDCC1, basic type FIDCCP01 as input parameters in the SAP In-House Cash systemand as output parameters in the FI general ledger system.

8. Configure Texts for Incoming and Outgoing Payments

Here you have to define the texts for incoming and outgoing payments.

Navigation

Menu Path

IMG: In-House Cash → Basic Settings → Basic Settings - Postings→ Set Texts for Incoming /Outgoing Payments

Detailed Settings


La Language

Outg.Payts Outgoingpayment

D/C, +/-

Description Description Description for outgoingpayment

Texts in relevantlanguage

In-Paymnts Incomingpayment

D/C, +/-

Description Description Description for incomingpayment

Texts in relevantlanguage

9. Assign Check Digit Methods to In-House Cash Center

Navigation

Menu Path

IMG: In-House Cash → Basic Settings → Check Digit Calculation Methods→ Assign Check DigitMethods to Banks

Detailed Settings


Ctry Bank country

Bank Key Bank key

Meth Method Enter a method whichhas a procedurewithout checksassigned to it.

10. Activate SAP Component SAP In-House Cash


IMG: In-House Cash → Basic Settings → Business Transaction

Events/Event Control → Activate SAP Components

BF11

Page 34/64




Set the active indicator for the components SAP In-House Cash and Standard Accounting . Deactivatethe components BKK and TR-LO if you do not use them.

If there is an entry for IHB, delete it.

11. Activate Function Modules (P/S) for SAP In-House Cash



Events/Event Control → Activate Function Modules (P/S) SAP Application

BF31

Check whether the following function modules exist:

Payment transactions:

- 00010311 IHC SAMPLE_INTERFACE_00010311_IHC


- 00010320 IHC BCA_PREPARE_REVERSE_PO_FROM_CC

- 00010024 IHC_BCA_PN_PI_LIM_CHECK

- 00010030 IHC_BCA_PN_PI_RETRIEVE_VALUES

- 00010041 IHC_BCA_PN_PI_RETRIEVE_REFS

- 00011210 IHC_BCA_PN_PI_SET_XTRAKEY

Creation of bank statements:


General ledger transfer:




12. Activate Function Modules (Process) for SAP In-House Cash



Events/Event Control → Activate Function Modules (Process) SAP

Application

BF41

Check whether the following function modules exist:

- 00011012 SAMPLE_PROCESS_00011012_IHC

- 00011310 SAMPLE_INTERFACE_00011310_IHC2 (see SAP note 406037)

13. Create or Activate a Partner



Events/Event Control → Create/Activate Partner

BF12

Set the active indicator for the IHC partner.

Page 35/64




14. Define IHC Product of Partner



Events/Event Control → Activate Partner Product

BF22

Enter the RFC destination of your in-house cash center for the product IHC even if the in-house cashcenter and Financial Accounting are in the same client. Ignore any warning messages that mightappear.

15. Activate IHC Product of Partner



Events/Event Control → Activate Partner Product

BF23

Make sure there is an entry for the product IHC and the partner IHC.

16. Process Partner Function Modules per Publish & Subscribe Interface



Events/Event Control → Define Function Modules (P/S) of a Partner

BF32 (Table TBE32)

Detailed Settings

Field Name Description User Action and Values

Event Event for exporting process

data

00002810 and 00002850

Partner Identification of complementarysoftware partner

IHC

Product Product of complementarysoftware partner

IHC

No. Sequential number 1 and 0

Ctry ISO code of a country

Appl. Application indicator for BTE IHC

Function Module Partner function module BKK_IHB_BASTA_IN_CHECK

BKK_IHB_BASTA_2850E

Text on Fun.Module

Text on additional componentsper function module

17. Process Partner Function Modules per Process Interface

Make the following settings in transaction BF42 (table TPS32):

Page 36/64




Detailed Settings


Event Event for exporting processdata

00002810 and 00002850

Ctry ISO code of a country

Appl. Application indicator for BTE IHC

Function Module Partner function module IHC_APPL_XBS_POST

BKK_IHB_BASTA_2850P

Partner Identification of complementarysoftware partner

IHC

Product Product of complementarysoftware partner

IHC

4.2.2 Master Data

1. Process Products and Conditions

The products serve as a template and framework for accounts. For more information see thedocumentation.

If you need a new product, SAP recommends that you copy an existing product.

You can upload product attributes to a target client from the Customizing delivered byusing the FIPR_ATTRIBUTE_COPY_CLIENT report.

You can upload products to a target client from the Customizing delivered by using theFIPR_PRODUCT_CLIENT report.

Do not forget to activate the products and assign them to your bank area.

Menu Path

IMG: In-House Cash → Master Data → Product Definition → Product→ Assign Products toBank Areas

You always create conditions dependent on a condition area that you assign to theproduct. For more information about the conditions, see the documentation.


SAP Easy Access → In-House Cash → Conditions→ Condition

Assignment→

Edit

F98E

Page 37/64





IMG: In-House Cash → Master Data → Product Definition → Product → Change Product

FIPRD2

Define the condition area in the conditions.

2. Maintain Formats for Bank Statements

Enter one of these formats:

• FINSTA

• IHCPAP for bank statements in paper form instead of FINSTA IDoc

Menu Path

IMG: In-House Cash → Master Data → Account → Maintain Formats for Bank Statements

4.2.3 Account Management

1. Define Transaction Types

Menu Path

IMG: In-House Cash → Payment Processes in In-House Cash → Define Transaction Types

Define transaction types and set the indicator for the corresponding transaction type attribute. Theseindicators are primarily relevant for displaying and entering manual payment orders. For example: setthe indicators Ext. and Transfer for an external payment.

2. Define Clearing Partner

Menu Path

IMG: In-House Cash → Account Management → Payment Processes in In-House Cash → Define Clearing Partner

The clearing partner is the recipient responsible for forwarding a payment. This could be a differentsystem (an in-house cash center or a different company code) or the same system/client (RFCdestination NONE). If you make use of external payments you must at least enter the head office FI

system as the clearing partner. For local payments you must also enter the clearing partners(executing subsidiaries).

Page 38/64




3. Make Basic Settings for Payment Processes

Menu Path

IMG: In-House Cash → Payment Processes in In-House Cash → Make Basic Settings forPayment Processes

Here you process the basic settings for manual and automatic IHC payment orders:a) Manually created IHC payment orders: These settings concern the interface between thecomponents SAP In-House Cash (FIN-FSCM-IHC) and Accounting (FI). In accordance with thesettings that you make here, the data from payment orders that you have created manually in SAP In-House Cash are converted, and the converted payment order data is transferred to the table forpayment requests in Accounting .

b) Automatically created IHC payment orders: These settings concern the interface between anexternal system and the components SAP In-House Cash (FIN-FSCM-IHC) and Financial Accounting (FI). The interface converts the data from payment orders transferred from an external system to thein-house cash center via IDocs.

The payment orders can be for internal payments or payments to external partners. The followingtables control the processing of internal and external payment orders. SAP In-House Cash transfersexternal payments to the table for payment requests in FI. Process entries for the bank collection.

For more information, see the implementation guide (IMG).

Make the following detailed settings in each bank area:

Detailed Settings: Processing Transaction Types in Bank Area


Bank Area Name of the bank area IHC

Transact. Transaction type EXTPAY

Processing Payments processing in IHC F

ExDocProvP External document for provisional paymentindicator

Define here which predefined transaction types you want to use in which bank area. You can decideper transaction type whether you want provisional or final posting.

Detailed Settings: Settlement Accounts


Bank Area Bank area IHC

Crcy Account currency EUR

SettlmtCat Settlement category Provisional

Item Type Category of item Payer

+/- Credit/debit memo indicator

Transact. Transaction type EXTPAY

BPartner Business partner number (Subsidiary)

Account number Account number for current account

No entries are necessary for final postings without currency gains/losses.

Page 39/64




Detailed Settings: Posting Data


Bank Area Bank area

SettlmtCat Settlement category

Item Type Category of item

+/- Credit/debit indicator

Transact. Transaction type

Medium Medium

Pay Meth Payment method

TA Type Transaction type

Enter the corresponding BCA transaction type in your bank area for each credit and debit note. Youcan also enter a BCA transaction type for each transaction type.

Detailed Settings: Settlement Installments FX

If the transaction currency is not the account currency, you use the new currency swap function tocarry out the translation. The secondary selling rate or secondary buying rate is used per default todetermine the exchange rate. You can differentiate between provisional and final postings for eachsettlement category. The selling rate is used for debit postings. Credit postings use the buying rate.The primary rate is the market exchange rate actually used for settlement in In-House Cash. Allexchange rates are taken from the TCURR table.

You can calculate exchange rates separately for manual individual payments.



SettlmtCat Settlement category Provisional

PrimSellRt Primary selling rate

SecSellRt Secondary selling rate

PrimBuyRt Primary buying rate

SecBuyRt Secondary buying rate

Detailed Settings: Accounts for Clearing Partner



Partner Recipient for forwarding an externalpayment

Crcy Currency key

SettlmtCat Settlement category

Account Number Account number for current accounts

Enter the corresponding mutual clearing accounts per currency. The current accounts defined here,and not the settlement account current accounts, are used for external payments and cross bank areapostings.

Page 40/64




Detailed Settings: Payment Method Data

Field Name Description

Bank Area Bank area

Partner Recipient for forwarding an external payment

Trns.Cur. Transaction currency

RecBankKey Recipient country key of bank


Del. PayMd Delivered payment method

Del.PMSuppl Delivered payment method supplement

P Payment method for this payment

PmtMthSu Payment method supplement

No entries are necessary here for internal payments.

Detailed Settings: Communication Data


Bank Area Bank area

Partner Recipient for forwarding an external payment

Trns.Cur. Transaction currency

Rec.Partn.Type Partner type of the recipient


Partn.No. Partner number of the recipient

Msg.Var. Logical message variant

Msg.Funct. Logical message function

Account Number Account number for current accounts

Ctry Country key of the bank

Bank Number Bank number

No entries are necessary here for internal payments.

Detailed Settings: Routes


Bank Area Bank area

Route IHC route

Partner IHC: Recipient for forwarding an external payment

4. Define Default Setting for Transaction Type

Menu Path

IMG: In-House Cash → Payment Processes in In-House Cash → Define Default Setting forTransaction Type

You will need to make these settings for manual payment orders.

Page 41/64




5. Define Transaction Type for Automatic Payments

Menu Path

IMG: In-House Cash → Payment Processes in In-House Cash → Define Transaction Type for Automatic Payments

You determine here how the incoming PAYEXT or DIRDEB IDoc is further processed with messagetype PEXN.

6. Set Up Creation of Payment Requests for Inbound IDoc in FI

You have to make entries for each account in the in-house cash center.

Menu Path

IMG: In-House Cash → Account Management→ Payment Processes in In-House Cash →

Outgoing Payment Orders → Set Up Creation of Payment Requests for Inbound IDoc in FI

Enter the account details, posting accounts and processing parameters for the clearing partner. Theseentries are required for PAYEXT with message type PEXC or PEXC_PI in FI.

7. Instructions for FI

You need to make entries here for instruction codes and instruction keys per bank area. You canprocess several instructions per instruction code (or instruction number) in the Define InstructionCodes for FI IMG activity. In the Define Instruction Keys IMG activity you can enter a maximum of fourinstructions for each instruction key.

Menu Path

IMG: In-House Cash → Account Management → Payment Processes in In-House Cash →

Outgoing Payment Orders→

Instructions for FI→ Define Instruction Codes for FI

→ Define Instruction Keys

Also enter processing parameters for the clearing partner. An instruction key can contain up to fourinstructions. You must now decide whether you want to use instruction keys or instructions. This datais forwarded to the executing FI. In FI, corresponding instructions are derived from the incoming

instructions. (IMG: Financial Accounting → Accounts Receivable and Accounts Payable→ Business

Transactions→ Outgoing Payments → Automatic Outgoing Payments → Payment Media → Data

Medium Exchange → Define Instruction Keys (Table T015W)).

8. Define Account Determination for Incoming Account StatementsThis is the central payment receipt process. You define which items from an incoming bank statementare to be posted to SAP In-House Cash.

When the bank statement is received, the payment note is checked. If these entries exist in thefollowing table, the incoming payment is posted to the corresponding current account.

Menu Path

IMG: In-House Cash → Account Management → Payment Processes in In-House-Cash →

Central Cash Receipt / Incoming Bank Statements→ IHC Account Determination from PaymentNotes

Page 42/64




Detailed Settings


BkArea Bank area Your bank area

Acct No. Current account number

Item Sequential number

Admin No. Note to payee line item

Payt Notes Character string in the payment notes ofbank statement

9. Settings for the Electronic Bank Statement of External Bank

You only carry out this step if the in-house cash center manages a separate account at the head officehouse bank for each affiliated company. The relevant in-house cash center can be determined on thebasis of the following information:

a. External bank number of the house bank and external account number of the accountin the house bank that the head office holds for the affiliated company

b. Bank number and account number of the payer’s bank

c. Assignment of posting category to business transaction code

The items in an incoming bank statement can thus be posted to the internal account number and thebank area in SAP In-House Cash.

Menu Path


Central Cash Receipt / Incoming Bank Statements→ IHC Account Determination from ExternalBank Account

Detailed Settings


Bank Number Bank number House bank of the head office

Bank Account Bank Account House bank of the head office

Currency Currency of the external bankaccount

Bank Number Bank number of partner bank House bank of paying customer

Partner Bank Account

Partner bank account House bank of paying customer

Bank Area Bank area Your bank area from SAP In-House Cash

Account Number Account number for currentaccount

Account to which the incoming payment isto be posted

10. Define Transaction Types for Incoming Payment

Menu Path


Central Cash Receipt / Incoming Bank Statements→ Define Transaction Types for IncomingPayment

Page 43/64




Detailed Settings


Bank Area Bank area

TransTyp Transaction type

BTC Business transaction code

+/- Credit/debit indicator


TrTypeChrg Transaction type charges

11. Set Up Account Determination for Incoming Payment

Menu Path

IMG: In-House Cash → Account Management → Payment Processes in In-House-Cash → Central Cash Receipt / Incoming Bank Statements → Set Up Account Determination for IncomingPayment

Detailed Settings


CoCd Company code

House Bk Short key for a house bank

Acct ID Short key for account detailsBank Area Bank area

FI Acct in IHC IHC: FI customer/vendor account in IHC

Header acct forCentral IncomingPayments

IHC: Header account for payments frombank statement with no recipient

12. Change Message Control

Menu Path

IMG: In-House Cash → Account Management→ Payment Processes in In-House-Cash →

Central Cash Receipt / Incoming Bank Statements→ Change Message Control

For more information, see the documentation for the IMG activity.

13. Set Up Route Processing

Menu Path


Cross-Bank Area Posting → Set Up Route Processing

Page 44/64




14. Account Management Basic Functions

See also the implementation guide (IMG) documentation for this section.

15. Maintain Accounts for Payment Transactions

Process the one-time account and the clearing account per bank area and currency.

Menu Path

IMG: In-House Cash → Account Management → Maintain Accounts for Payment Transactions

This IMG activity is mandatory but payment orders initiated externally (per PAYEXT IDoc)are not posted to these accounts in SAP In-House Cash.

16. Define Account Determination1. Define business transaction codes

2. Maintain transaction types (double click on transaction type)

3. Assign offsetting transaction types

4. Maintain posting categories

5. Assign posting categories to transaction types

SAP recommends that in SAP In-House Cash, you use posting category 70, transaction type 0150,and business transaction code 020 for debit notes. For credit notes, SAP recommends postingcategory 71, transaction type 5110, and business transaction code 051. If required, add to theCustomizing settings, for example, for bank collection.

4.2.4 Periodic Tasks (General Ledger Transfer)

1. Maintain General Ledger Variant for General Ledger Transfer

To keep the maintenance required for assigning several bank areas to a minimum, you can creategeneral ledger variants as transfer templates and assign them to several bank areas. In the generalledger variant, transaction types are grouped in general ledger transactions. The accounts aregrouped in general ledger groups. These details enable you to specify the transfer precisely.

Menu PathIMG: In-House Cash → Periodic Tasks → General Ledger Transfer → Maintain GL Variants

1. Maintain General Ledger Transaction for General Ledger Transfer

A general ledger transaction groups postings for several transactions in the current account systeminto a single transaction that enables assignment to a general ledger account or posting type.

General ledger transaction for account determination for transfer to FI. Here you have to assign ageneral ledger transaction to each transaction type involved in the payment transaction.

One general ledger transaction is created for each general ledger variant.

Menu PathIMG: In-House Cash → Periodic Tasks → General Ledger Transfer → Maintain GL Transaction

Page 45/64




2. Assign Payment Transaction Type to General Ledger Transaction

For the general ledger transfer, assign a general ledger transaction type to each transaction type inthe current account system. You can assign several payment transaction types to one general ledgertransaction type.

Navigation

Menu Path

IMG: In-House Cash → Periodic Tasks → General Ledger Transfer → Assign Transaction Typefor Payment Transaction to GL Transaction

3. Maintain General Ledger Group

You can use general ledger groups to group current accounts into account groups. You assign anaccount to an account group (relevant for the general ledger transfer) when you create the account bymaintaining the corresponding field. In Customizing you define possible general ledger groups.

Navigation

Menu Path

IMG: In-House Cash → Periodic Tasks → General Ledger Transfer → Maintain GL Group

4. Determine Current Accounts for General Ledger Account Assignment

If you use additional keys, see SAP note 576679. For more information see the SAP documentation.

Menu Path

IMG: In-House Cash → Periodic Tasks → General Ledger Transfer → Define GL Account

Assignment: Current Accounts

5. Define Accounts for Receivables and Payables for the General Ledger Transfer

You have to configure the receivables and payables accounts to which the balances transferred fromthe current account system are distributed.

The balance of an account is first transferred to a clearing account (general ledger clearing account).The balance is then transferred to the corresponding receivables or payables account depending onthe +/- sign.

Menu Path

IMG: In-House Cash → Periodic Tasks → General Ledger Transfer → Transfer PostingsPayables/Receivables

Once you have defined the general ledger transfer, you have to assign the general ledgergroup to the product. Since the products are used as templates for creating a currentaccount, the general ledger group is the default value in the control data for the accountdetermination.

Page 46/64




Navigation


IMG: In-House Cash → Master Data → Product Definition → Product → Change Product

FIPRD2

Choose Account Fields → Master Data → General Ledger Group.

Here you can define a default value for the general ledger group.

Test the Result

You have now made all the settings for the general ledger. Test your settings.

Set Job Distribution for the Bank Statement Mass Run

Menu Path

IMG: In-House Cash → Periodic Tasks → Parallel Processing → Set Job Distribution

4.2.5 Authorization ManagementIn the following IMG activity you process the entries for In-House Cash payment orders in addition tothe authorization management IMG activities.

1. Principle of dual control

Navigation

Menu Path

IMG: In-House Cash → Basic Settings → Authorizations for IHC Payment Orders→ Set UpPrinciple of Dual Control

1. Amount-Dependent Authorizations

Navigation

Menu Path

IMG: In-House Cash → Authorization Management→ Amount-Dependent Authorizations

In the following IMG activities, you can process the entries for payment orders generated in BCA.

3. Maintain Authorization Types

See SAP note 506628.


IMG: In-House Cash → Authorization Management→ Maintain Authorization Types

F9AUTH

Page 47/64




4. Define Field Groups Relevant to Authorization

Menu Path

IMG: In-House Cash → Authorization Management → Define Field Groups Relevant to Authorization

5. Generate and Assign Authorization


IMG: In-House Cash → Authorization Management→ Generate and Assign Authorization

PFCG

6. Amount-Dependent Authorizations: Maintain Amount Limit/Principle of Dual Control forPayment Order


IMG: In-House Cash → Authorization Management → Amount-Dependent Authorizations → Maintain Amount Limit/Principle of DualControl for Payment Order

F9POAUTH

Detailed Settings


BkAr Bank area Your bank area

Intern. Prod. ID Internal product ID


AuGr Authorization group A1

Amt. Bank Area Amount in bank area currency

Contr. Indicator: Check by 2 users required (dual control)

7. Amount-Dependent Authorizations: Maintain Amount Limit/Principle of Dual Control forPayment Item


IMG: In-House Cash → Authorization Management → Amount-

Dependent Authorizations → Maintain Amount Limit/Principle of DualControl for Payment Item

F9ITAUTH

Detailed Settings



Intern. Prod. ID Internal product ID


AuGr Authorization group A1 Amt. Bank Area Amount in bank area currency

Contr. Indicator: Check by 2 users required (dual control)

Page 48/64




8. Amount-Dependent Authorizations: Maintain Amount Limit for Hold


IMG: In-House Cash → Authorization Management → Amount-

Dependent Authorizations → Maintain Amount Limit for Hold

F9HLDAUTH

Detailed Settings



Internal ProductID

Internal product ID

AuthorizationGroup

Authorization group A1

Amount Bank

Area Currency

Amount in bank area currency

4.2.6 Integration in SAP Cash Management

1. Set Up Financial Status

Make the following settings for integrating current accounts in the cash position and liquidity forecastbefore general ledger transfer.


IMG: In-House Cash → Periodic Tasks → Transfer Financial Status to

SAP Cash Management → Set Up Financial Status

IHCCM0

1. Make entries for the cash management data:

Cash management variants

CM variant alias (corresponds to your company code)

Finally posted status alias (for example, I1)

Planned status internal alias (for example, I2)

Planned status external alias (for example, I2)

2. Process the cash management groups, the assignment of bank areas and the assignment ofaccounts. For more information about settings, see the help documentation.

2. Integration in SAP Cash Management: Check the Consistency of the Settings

If you want to integrate with cash management, check the consistency of your settings:


IMG: In-House Cash → Periodic Tasks → Transfer Financial Status to

SAP Cash Management → Check the Consistency of the Settings

IHCCM3

Page 49/64




3. Integration in SAP Cash Management: Provide IHC Data for Cash Management Systems

The IHC_CM_TRANSF_SAPCM business add in (BAdI) for updating SAP Cash Management is activein the standard system. If you do not want integration with SAP Cash Management you can deactivatethis BAdI here.

Menu Path

SAP Easy Access: In-House Cash → Transfer Financial Status to CM → Transfer IHC FinancialStatus to CM

4.3 Customizing the Group Head Office

Use

In this section you make the settings required for the group head office:

• Payment request program

• Electronic bank statement from the head office house bank to the head office

GroupHead Office

In-House Cash

Center Financial

Accounting

Organizational Unit: Financial Accounting of Head Office

Prerequisites

You have defined the G/L accounts of the head office company code including the bank clearingaccounts to guarantee the postings to these accounts.

Procedure

4.3.1 Process Payment Program for Payment Requests

For central payments, use the payment program for payment requests (transaction F111).

1. Define Global Settings


IMG: Financial Accounting→ Bank Accounting → Business

Transactions→ Payment Transactions → Payment

Handling → Define Global Settings

F8BG

Here you make the settings for the origin indicator.

Page 50/64




2. Make Settings for the Origin Indicator



Transactions→ Payment Transactions → Payment

Handling → Enter Origin Indicators

F8BG

SAP recommends that you set the indicator for planned amounts. In this case, the paymentprogram for payment requests (transaction F111) does not check planned amounts.

3. Define Account Determination for Bank Clearing Account

For payment transactions with bank accounts you have to define the bank sub accounts to beposted to in the general ledger. The accounts are specified per house bank account, paymentmethod, and currency. If no currency is defined, the account applies for all currencies.

The bank sub accounts must be created for the company code and be completely maintained.



Transactions→ Payment Transactions → Payment Request → Define Clearing Accounts for Recipient Bank for AccountTransfer

F8BG

(Table T018V)



Transactions→ Payment Transactions → Payment Handling →

Bank Clearing Account Determination → Define AccountDetermination.

F8BG

(Table T042Y)


IMG: Financial Accounting→ Accounts Receivable and

Accounts Payable → Business Transactions → Outgoing

Payments→ Automatic Outgoing Payments→ Payment

Method/Bank Selection for Payment Program → Set Up BankDetermination for Payment Transactions

Click on Bank Accounts.

FBZP

(Table T042I)

Tables T042I (configuration of F110 payment programs) and T042Y (configuration ofF111 payment programs) must be consistent. The consistency of the entire table ischecked; not only at company-code level. See SAP note 481197.

Check the consistency as follows:

Menu Path

IMG: Financial Accounting→ Bank Accounting → Business Transactions → Payment

Transactions→ Payment Handling → Bank Clearing Account Determination → Check Account Determination.

Page 51/64




4.3.2 Configure Electronic Account Statement of the Head Office External House Bank to FI

Menu Path

IMG: Financial Accounting→ Bank Accounting → Business Transactions → Payment

Transactions→ Electronic Bank Statement → Make Global Settings for ElectronicBank Statement

Make your settings for the chart of accounts used by the company code of the head office.

Result

You have completed the Customizing settings for central payments and central payment receipt.

4.3.3 Integration with Cash Management

1. Define Source Symbols

Menu Path

IMG: Cash and Liquidity Management → Cash Management → Basic Settings → Define Source Symbols

Create a source symbol for In-House Cash. If an indicator is set, the source symbol is assigned to thecash position otherwise it is allocated to the liquidity forecast.

2. Define Planning Levels

Menu Path

IMG: Cash and Liquidity Management → Cash Management → Master Data → G/L Accounts→ Define Planning Levels

Here you make the settings for the planning levels.

Detailed Settings


Note

Level Planning level Example: I1, I2, I3

SC Sign control No entry

Source Source symbol Example: IHC

Short Text Planning level short text IHC-IST, IHC-PLINT, IHC-PLEXT

Planning LevelLong Text

Planning level long text

3. Define Cash Management Account Name

Menu Path

IMG: Cash and Liquidity Management → Cash Management → Structuring → DefineCash Management Account Name

Make settings in the head office company code.

Page 52/64




Detailed Settings


Note

CM Acct Planning account name Example:CLPARTNER,

COMPANY01,COMPANY02

G/L Acct Bank account / bank clearingaccount

No entry

Bank Account Bank account number No entry

CMF Cash management andforecast only

Set the indicator

Description Description

4. Define Groupings and Maintain HeadersMenu Path

IMG: Cash and Liquidity Management → Cash Management → Structuring →

Groupings → Define Groupings and Maintain Headers

5. Maintain Structure

Menu Path

IMG: Cash and Liquidity Management → Cash Management → Structuring →

Groupings → Maintain Structure

Detailed Settings


Note

Grouping Grouping for cash position,liquidity forecast,concentration

Example: IHC, IHC,IHC

T Line type Example: E, G, G At least one level andone group

Selection Selection for cashmanagement

Example: I+

CLPARTNERCOMPANY++

CoCd Company code

ChAc Chart of accounts

Exclude Exclude

Sum. Term Summarization term Example: **

CLPARTNER

COMPANIES

Summ. Acct Summarization account

SCOCD Summarization companycode for cash concentration

Page 53/64






Procedure for In-House Cash Center

Make the following settings in the in-house cash center :

Menu Path


Outgoing Payment Orders → Automatically Created Payment Orders

Activate the Split indicator for all business partners that use KIDNO. This ensures that the KIDNOis forwarded.

Menu Path

IMG: In-House Cash → Account Management →Basic Functions in Account Management → Maintain Field Label for Customer Fields

Enter six entries per language and bank area if these are not yet entered. Use the value help forfield names. Enter KIDNO as the first field name. The other fields can have any name other thanKIDNO. The fields are only required for technical reasons.

For more information, see the documentation for the IMG activity.

See SAP notes dealing with KIDNO.

Result

You have configured FI for subsidiary companies and In-House Cash to enable you to use the KIDNO.

Page 55/64




5 Configuring Component-Specific Master Data

Purpose

This section provides you with information about master data that is not replicated or not replicatedsufficiently.

Process Flow


5.1 Create Business Partner Roles in SAP In-House Cash

Use

You create the business partner once as a central data object and it is used by different SAPapplications, including SAP In-House Cash, in different roles.

To create master data for a current account you have to assign certain roles to the business partner,such as account holder and bank statement recipient .

Prerequisites

Check whether the following basic settings exist in the system:


IMG: Cross-Application Components → SAP Business Partner →

Business Partner → Basic Settings → Number Ranges and Groupings → Define Number Ranges

BUCF

Detailed Settings


No. Number range number 01

From number From number 000000000001

To number To number 999999999999

Current number Current number 0

Ext Indicator for internal (‘ ‘) or external (‘X’) number

range

Check whether the following basic settings exist in the system:

Menu Path

IMG: Business Partner → Basic Settings → Business Partner Roles → Define BP Roles

Set the Std Assignment BP Role indicator for role BKK030.

Procedure


SAP Easy Access → Accounting → Financial Supply Chain

Management → In-House Cash → Business Partners

BP

Page 56/64




1. Create account holder: The account holder is the owner of the current account. Exactly oneaccount holder is assigned to each account.

If the field VBUND is to be transferred to the general ledger, choose Control to define thetrading partner company in the control data. See also SAP notes 406037 and 522747 andother SAP notes.

2. Create authorized drawer: The authorized drawer is not the owner of the account. You can assignseveral authorized drawers to each account.

3. Create account maintenance officer: The account maintenance officer is usually an internalemployee that looks after specific accounts.

4. Create bank statement recipient.

5. Create contact person: The contact person must be a natural person.

5.2 Create Current Account

For more information, see the online documentation. Recommendation: Update the posting datebefore you start to create the current account.


SAP Easy Access → In-House Cash → Account→ Create F9K1

Note the following special features:

Account Balancing tab page

Process the frequency, the key date, and the next date for account balancing. If the account is not tobe closed, enter frequency 1 and next date 12/31/9999.

Account Statements tab page

If bank statements should be sent to companies in SAPScript instead of a FINSTA IDoc, enter theaccount statement format IHCPAP and dispatch type 01. Refer to SAP note 603362.

You can trigger manual account statements several times per day. However, this does not apply tomass runs. Mass runs can only be started once a day because a day is the smallest possible unit forprocessing frequencies of account statements. As soon as an account statement has been generatedin a mass run, the system automatically increases the date in the account by one day. This means thatyou are unable to generate a second account statement for this date.

Control Data tab page

Remember to define the general ledger group for the general ledger transfer.

Result

You have defined the subsidiary companies as business partners in the business partner roles. Youhave created current accounts for the subsidiary companies.

Page 57/64




6 Ongoing Settings

6.1 Current Settings for Updating the Posting Date forPayment Transactions and Closing

Use

This section contains information about the settings required in daily operations:

• Increase posting cut-off for payment transactions: All payments are then entered with the laterposting date.

• Increase posting date for closing postings: Carry out this step once you have completed allclosing work.

The following steps describe the manual process. To make the settings automatically, in the IMG youcan define a fixed time for the posting cut-off.

Procedure

1. Update Posting Date for Payment Transactions


SAP Easy Access → In-House Cash → Periodic Processing → Posting

Date → Payment Transactions

F9B1

Detailed Settings

Field Name Description User Action and Values NoteBank Area Bank area

New Posting Date Posting date

2. Update Posting Date for Closing Manually

Navigation


SAP Easy Access → In-House Cash → Periodic Processing → Posting

Date → Closing

F9L4

Detailed Settings


Bank Area Bank area

New DateBalancing Posting

Current postingdate forbalancing in bankarea

Result

The posting dates for payment transactions and closing are updated.

Page 58/64




6.2 Ongoing Settings for Integration with SAP CashManagement

Use

This section contains information about the settings required in daily operations:The current account data in In-House Cash is available in SAP Cash Management once the IHCfinancial status has been transferred. You can also plan this step as part of your daily tasks.

Procedure

Transfer IHC Financial Status to CM

Navigation


SAP Easy Access → In-House Cash → Transfer Financial Status to CM IHCCM2

Result

You can evaluate the cash position and liquidity forecast.

In the IHC financial status online analysis the provisionally posted payment orders are placed in theplanned incoming or outgoing payments. The finally posted payment orders are in the postedbalances.

Page 59/64




7 Tips and Tricks

Use

This section is a self-help section.

7.1 PAYEXT IDoc is not created

Procedure

1. Check whether you have maintained the variant for program RFFOEDI1 with the relevantparameters under Printing and Data Media for the payment program for payment requests(transaction F111).

2. Make sure you have set the indicator Create Payment Media under Schedule Payments in theF110 payment program.

3. Check whether you have processed the EDI-compatible payment methods in the data for theIHC house bank in your company code.

7.2 FINSTA IDoc is not created

Procedure

1. Make sure the SAP In-House Cash component is active.


In-House Cash → Basic Settings → Business Transaction Events/Event

Control → Activate SAP Components

BF11

2. Deactivate the simulation run indicator in the control parameters when you create bankstatements. IDocs are not created in simulation runs.

7.3 Forwarding of payment requests failed

Procedure

Check your Customizing settings if forwarding payment requests (for example to your clearing partner)failed. This error can occur in the following circumstances:

• The system is unable to find a route and a clearing partner (in case of an error, this information iswritten to the log).

• The IDoc communication data is incomplete.

• ALE Customizing is incomplete.

Check the routes:

Menu Path


Cross-Bank Area Posting → Set Up Route Processing

Page 60/64






8 Reverse

Procedure

The following functions are available for reversing provisionally or finally posted payment orders:


Internal payments, central payments, central incoming payments

In-House Cash → Account Management→ IHC Payment Orders → Payment Order Browser

Choose the payment orders you want to reverse. Go to change modus.Use the delete function to reverse the payment order.

IHC0

Payment requests that were generated with PAYEXT (if they are still open) are reversed bymeans of RFC.

Page 62/64




9 Application Security Guide for SAP In-HouseCash

9.1 IntroductionThis guide is intended to give you an overview of security aspects and some recommendations as tohow you can apply them in SAP In-House Cash.

The following topics can be found in the SAP Web AS Security Guide for ABAP technology.

Topic Content

User Authentication This section describes the security aspects ofuser authentication, for example, user IDs andpasswords, password rules and preventingunauthorized logons.

SAP Authorization Concept This section gives an overview of the SAPauthorization concept and how you can use it toprotect your applications from misuse.

Protecting Your Productive System This section describes how you can preventunwanted changes from being made in yourproductive system by means of the Change andTransport System (CTS) and the TransportManagement System (TMS).

Secure Store & Forward Mechanisms (SSF) andDigital Signatures

This section deals with the security aspects ofusing public keys for digital signatures encryptionfunctions.

Special Topics Security measures that you can or must employfor certain topics.

Read SAP note 30724 regarding data security and security in SAP systems.

9.2 Security Measures for Saving DataIf you are required to submit information, all relevant master data (customer, vendors) and transactiondata (invoice details) are available in the subsidiary company.

Communication between subsidiaries and the in-house cash center is based on IDocs. When thesubsidiary starts payment programs F110 / F111, subsidiary master data and transaction data arewritten to the log in FI and automatically transferred to the following IDoc types:

• PAYEXT and DIRDEB contain detailed information about the payment, such as the number ofthe payment run, data about the payment recipient, the recipient bank, amount and paymentnotes.

• When you create PAYEXT or DIRDEB, EUPEXR is created automatically in the subsidiarycompany.

Create a port to which EUPEXR can be sent, since this IDoc type is not required in SAPIn-House Cash. You can delete the file defined in the port at specific intervals.

Page 63/64




• In the case of external payments (in other words, the recipient's account is not in the samebank area as the payer's account), a PAYEXT or DIRDEB IDoc is sent from the in-house cashcenter to the executing FI system. The information received is the same as described in theprevious section.

• The in-house cash center generates internal bank statements for subsidiaries. The FINSTA is

generated and sent. It contains information relevant to the bank statement, for example,payment notes.

• If financial accounting of the head office is not in the same system as the in-house cashcenter, an IDoc can be used during end-of-day processing for communication between the in-house cash center and financial accounting. The FIDCC1 contains all balances groupedduring balance sheep preparation to enable them to be posted subsequently to the generalledger.

You need to be able to display the IDocs so that the process is clear and also for tax auditingpurposes. If the IDocs are no longer required, they can be deleted.

9.3 AuthorizationsThe role of in-house cash supervisor is delivered with SAP In-House Cash. TheSAP_FSCM_IHC_Supervisor role is found in the profile generator (transaction PFCG) and can bemodified. Due to detailed information contained in the PAYEXT, DIRDEB and FINSTA IDocs werecommend that you restrict authorization to manage or to display the IDocs or to grant only certainusers authorization.

As part of the SAP authorization concept, the authorization object IHC_ACTION is available for IHCpayment orders. You can define a range of authorization restrictions for creating, viewing, changingand processing payment orders. For example, you can restrict authorization to individual accounts orassign amount-dependent authorizations. You will find more information in the documentation.

Since other components are also involved in SAP In-House Cash processes (FI, BCA), the relevantauthorizations must also be granted or restricted in these components (for example, displayauthorization for current accounts) if the user is allowed to execute these transactions.

9.4 Data ProtectionThe processor in SAP In-House Cash has authorization to view all postings and turnover in the currentaccounts of subsidiary companies. Authorization cannot be restricted depending on the paymentrecipient.

We recommend that you do not process personnel payments from SAP HR via SAP In-House Cash for reasons of data protection. Detailed data about the payment recipient is contained in the PAYEXT.

9.5 ALE

When you create the ALE, make sure that the ALE connection is checked carefully if a system copy ismade. This is to prevent IDocs from a test system from being sent unintentionally to a productivesystem.

Documents

Config in House Cash