Config Guide Sap in House Cash

5/26/2018

ConfigGuideSapin HouseCash-slidepdf.com

SAP In-House Cash: Configuration Guide

Release mySAP ERP 2004

http://slidepdf.com/reader/full/config-guide-sap-in-house-cash

1/64

5/26/2018


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 the express permission of SAP AG. The information in this publication is subject to change without notice and 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 software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks 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 Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. 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 herein as well as their respective logos and trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

Page 2/64 http://slidepdf.com/reader/full/config-guide-sap-in-house-cash

2/64

5/26/2018



22.6.2004

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, menu names, menu paths and menu options. Cross-references to other documentation.

Example Text

Emphasized words or phrases in body text, graphic titles and tables titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names and key concepts of a programming language when they are surrounded 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 of installation, upgrade and database tools.

Example Text

Exact user entry. These are words or characters that you enter in the system exactly as

they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

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


3/64

5/26/2018



22.6.2004

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


4/64

5/26/2018



1

22.6.2004

Introduction

1.1 SAP In-House Cash: The Components Purpose

The SAP In-House Cash component is a solution for processing internal and external payment transactions within a group or company. It reduces the amount of external bank accounts and crossborder payments required.

Implementation Considerations The head office financial accounting system used by SAP In-House Cash is based on Release mySAP ERP 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 the corresponding 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


5/64

5/26/2018



22.6.2004

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 mutual dependencies. 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-House Cash training course (FSC120), knowledge of the processes of SAP In-House Cash, and knowledge of BCA.

Documentation For more information about the documentation and demo scripts available, see SAPNet under the alias 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 find errors in the configuration guide, enter a message for the component SAP In-House Cash, (FINFSCM-IHC) in the SAP Service Marketplace under the Internet address service.sap.com/messages .

1.3 SAP Notes Before you start to configure this business scenario, read the following SAP notes. This summary contains 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 Group Objects

522747

Partner Company Not Filled in General Ledger Transfer

527431

EUPEXR IDoc Created with Status 63


6/64

5/26/2018



22.6.2004

537404

Customizing Value Date: Payment Order per IDoc

576679

General Ledger Transfer to G/L Accounts Managed by Company

494777

Customer Enhancement in Electronic Account Statement

406037

IHC General Ledger Transfer

501068

Bank Statement Subsequent Processing: InHouse Cash

To get a comprehensive and up-to-date overview of the SAP notes for a business scenario and the relevant mySAP.com application components, use the search function for notes on the SAP Service Marketplace under the Internet address service.sap.com/notes .


7/64

5/26/2018



22.6.2004

2 General Settings for Creating New Company Codes Use These settings are only necessary when creating new company codes. If you do not have to create new company codes, the settings already exist in the system.

Procedure Make your settings according to the following navigation tables.

1.

Define Tolerance Groups for Employees

Menu Path

Transaction Code

IMG: Financial Accounting → Financial Accounting Global Settings → →

OBA4

→

Document Line Item Define Tolerance Groups for Employees There must be at least one entry for each company code. If you leave the name of a tolerance group empty for a company code, this entry will apply to all employees who are not assigned to any tolerance group (see 2).

2.

Assign Users to Tolerance Groups

Menu Path IMG: Financial Accounting → Financial Accounting Global Settings → Document → Line Item Assign Users/Tolerance Groups

→

If the name of the tolerance group is empty under 1, you do not have to make an entry here.

3.

Define Tolerance Groups for G/L Accounts

Menu Path IMG: Financial Accounting → General Ledger Accounting → Business Transactions → Open Item Clearing → Clearing Differences → Define Tolerance Groups for G/L Accounts There must be at least one entry for each company code.

4.

Define Tolerances for Customers

Menu Path IMG: SAP Banking → SAP Business Partner for Financial Services → Settings for Financial Services → Communication → Settings for FI Customer → Payment Data → Define Tolerances (Customers) There must be at least one entry for each company code.


8/64

5/26/2018



5.

22.6.2004

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

Menu Path

Transaction Code

IMG: Corporate Finance Management → Transaction Manager →

F8B4

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

6.

Define Factory Calendar per Currency

Menu Path

Transaction Code

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

Menu Path

Transaction Code

IMG: Corporate Finance Management → Basic Analyzer Settings → Automatic Integration of Financial Objects in Transaction Master Data → Other Transactions → BCA Account → Activate/Deactivate Financial Object Integration

RMIBKKA

Deactivate the Component Active indicator.


9/64

5/26/2018



3

22.6.2004

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 and distributing 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, (transaction WE60). see the documentation for Application Link Enabling (ALE) and IDoc

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 from the view of the system in which SAP In-House Cash and Financial Accounting for the group head office 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 type PAYEXT 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 with basic 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, use message type PAYEXT with basic type PEXR2002 and the transaction code PEXC as the inbound parameter. The clearing partner can either be a company code or a different bank area. You can also have two clearing partners in the same client. In this case the recipient and sender systems are the same. Use the RFC destination NONE. If SAP In-House Cash is in a different system from Financial Accounting of the head office, use the following parameters for transferring the general ledger from the in-house cash center to financial accounting:

•

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.


10/64

5/26/2018



22.6.2004

For external payments, consistent bank master data (table BNKA) may be necessary for the different affiliated 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 library under Cross-Application Components  Business Framework Architecture (CA-BFA)  ALE Business Process Library (CA-BFA-ABL)  Cross-Application Business Processes  Bank Distribution.

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: Menu Path

Transaction Code

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 systems for SAP In-House Cash, the subsidiaries and Financial Accounting of your head office. If Financial Accounting of your head office is in the same client as SAP In-House Cash, you should make an entry here to show that an RFC connection is not used, for example, LOCAL.

Menu Path

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE)→ Basic Settings → Logical Systems → Define Logical System

SALE

Detailed Settings Field Name

Description

Log.System

Logical system

Name

Name

2.

User Action and Values

Note Example: TNFCLNT400

Assign Logical System to Client Here you assign a client to the system for SAP In-House Cash. Generally, the customer has already made this assignment.

Menu Path

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE)→ Basic Settings → Logical Systems → Assign Logical System to Client

SALE


11/64

5/26/2018



22.6.2004


Description

Client

Client

City

City

Logical system

Logical system


Example: 400

Logical system that you defined in 1

Std currency

Standard currency

Changes and transports for clientspecific objects


Indicator Changes without automatic recording

Cross-client object changes


Changes to Repository and cross-client Customizing allowed

Protection: Client copier and comparison tool

Protection regarding client copy program and comparison tools

Protection level 0: No restriction

Restrictions

Restrictions

Indicator that starting CATT processes is permitted

3.

Note

Example: TNFCLNT400

Define Target Systems for RFC Calls Here you define the subsidiary system as the target system. If Financial Accounting of the head 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 the case of external payments, the fixed RFC destination NONE can be used for the IDoc port.)

Menu Path

Transaction Code

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

SM59



Choose R/3 connections → Create.


Description

RFC Destination

RFC destination

Connection Type

Connection type

Description

Description

Logon/Security

Logon data





3

Save and click on Test Connection to test the connection.

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


12/64

5/26/2018


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

22.6.2004

Modeling and Implementing Business Processes, Maintain Distribution Model, and Distribute 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.

Menu Path

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE) → Modeling and Implementing Business Processes → Maintain Distribution Model and Distribute Views

BD64



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


Description

Short text

Short text

Technical name Start date

Technical name Start date

End date

End date


Note

Example: IHC

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 InHouse Cash to subsidiary companies. Detailed Settings Field Name

Description


Note

Model view

Model view

The model view you defined

Example: IHC

Sender

Sender

Logical system of head office

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 bank collections (IDoc DIRDEB) from the subsidiary to SAP In-House Cash. For bank collections you can copy PAYEXT.


13/64

5/26/2018



22.6.2004


Description


Note

Model view

Model view


Example: IHC

Sender

Sender


Example: TNFCLNT401

Receiver

Receiver


Example: TNFCLNT400

Message type

Message type

PAYEXT

Payment order





Description


Note

Model view

Model view


Example: IHC

Sender

Sender


Example: TNFCLNT401

Receiver

Receiver


Example: TNFCLNT400

Message type

Message type

DIRDEB

Preauthorized withdrawal

5.

Generate Partner Profiles

Menu Path

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE) → Modeling and Implementing Business Processes → Partner Profiles → Generate Partner Profiles

BD82


Description


Note

Model view

Model view


Example: IHC

Partner system

Partner system


Example: TNFCLNT401

Output mode 

6.

Indicator: Transfer IDoc immediately Choose Execute to generate the partner profile.

Distribute Model View

Menu Path

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE) → Modeling and Implementing Business Processes → Maintain Distribution Model and Distribute Views

BD64



Select your model view.



Choose Edit → Model View → Distribute.



Select the subsidiary system as the target system.


14/64

5/26/2018



22.6.2004

In the subsidiary system, check whether the distribution model has been distributed. For technical purposes, the system generates message type SYNCH in the partner profiles of partner type LS in the outgoing direction. Therefore, you do not need to create message type 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 in the same client.

Menu Path

Transaction Code

SAP Easy Access → Tools → ALE → ALE Administration → Runtime Settings → Port Maintenance

WE21



Choose Create to create a transactional RFC port.


Description


Port

Port

Let the system generate a port name or assign your own port name

Description

Description

Send IDocs to self

RFC destination

RFC destination

NONE



Note

Choose Save to create a transactional RFC port.

Carryoffice out the following activity only if SAP In-House Cash and Financial Accounting of the head are in the same client. Menu Path

Transaction Code


WE21



Choose Create to create a transactional RFC port.


Description


Port

Port

Let the system generate a port

Note

name or assign your own port name Description

Description

Loopback to local system

RFC Destination

RFC destination

NONE



Choose Save to create a transactional RFC port.


15/64

5/26/2018



8.

22.6.2004

Process Partner Profiles for Business Partners Manually See SAP note 429133. For ALE communication, you have to define partners with inbound and outbound parameters.

Menu Path

Transaction Code

SAP Easy Access → Tools → ALE → ALE Administration → Runtime Settings → Partner Profiles

WE20



Select Partner Type BP .



Choose Create.


Description


Partner no.

Partner number

Business partner number

Type Agent

US Agent

User ID

Language

Language



Note

Choose Outbound Parameters.


Description


Message type

Message type

FINSTA

Receiver port

Receiver port

The port you generated

Output mode

Output mode

Indicator: Transfer IDoc immediately

Basic type

Basic type

FINSTA01

Syntax check

Syntax check

Select



Note

Choose Inbound Parameter .

Detailed Settings Field Name Message type

Description Message type

User Action and Values DIRDEB

Note

Process code

Process code

PEXN (used to be PEXR)

Processing of incoming payments

Syntax check

Syntax check

Select

Processing by function module


Trigger immediately

Only in test phase, otherwise Trigger by background program


16/64

5/26/2018



22.6.2004


Description


Message type

Message type

PAYEXT

Process code

Process code

PEXN

Syntax check

Syntax check

Select



Trigger immediately

Note



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

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

9.



Select the partner.



Choose Create Copy .

Process Partner Profiles Manually for Logical Systems Here you process the clearing partners in partner type LS.

Menu Path

Transaction Code

SAP Easy Access → Tools → ALE → ALE Administration → Runtime Settings → Port Maintenance → Partner Profiles

WE20

To do this, proceed as described above. 

Choose Create.


Description


Note

Partner no.

Partner number

Logical system of Financial Accounting

For example, LOCAL

Partn.Type

LS

Agent

Agent

Lang.

Language



User ID



17/64

5/26/2018



22.6.2004


Description


Note

Message type

Message type

DIRDEB

Message code

Message code

IHC

This field needs to be filled if FI of head office is in the same client as IHC because the field can be used to outsort outbound processing.

Message function

Message function

FI

See above

Receiver port

Receiver port


Port with destination NONE if FI of head office is in the same client, otherwise port with RFC destination of FI’s logical system.

Output mode

Output mode


Basic type

Basic type

PEXR2002

Syntax check

Syntax check

Select

Field Name

Description


Message type

Message type

PAYEXT

Message code

Message code

IHC


Message function

Message function

FI

See above

Receiver port

Receiver port



Output mode

Output mode


Basic type

Basic type

PEXR2002

Syntax check

Syntax check

Select

Note


18/64

5/26/2018



Field Name

Description


Message type

Message type

SYNC

Receiver port

Receiver port


22.6.2004

Note


Output mode

Output mode


Basic type

Basic type

SYNCHRON

Syntax check

Syntax check

Select

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

Description


Note

Message type

Message type

FIDCC1 or

Sending FI documents for G/L transfer

FIDCC2

If SAP In-House Cash and Financial Accounting for the head office are not in the same BCA, you system have toas use message type FIDCC1. Receiver port

Receiver port


Output mode

Output mode


Basic type

Basic type

FIDCCP01 or

Port with RFC destination of the FI’s logical system

FIDCCP02 Syntax check

Syntax check

Select



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



Choose Inbound Parameters


19/64

5/26/2018



22.6.2004


Description


Note

Message type

Message type

DIRDEB

Message code

Message code

IHC


Message function

Message function

FI

See above

Process code

Process code

PEXC

Create payment requests

Syntax check

Syntax check

Select

Processing by

Processing by

Trigger immediately

function module

function module



Description


Note

Message type

Message type

PAYEXT

Message code

Message code

IHC


Message function

Message function

FI

See above

Process code

Process code

PEXC

Create payment requests

Syntax check

Syntax check

Select



Trigger immediately


Copy the settings for message type PAYEXT for preauthorized withdrawal (bank collection) with message type DIRDEB. The following inbound parameter must only be maintained if Financial Accounting of your head office is not in the same client as your SAP In-House Cash.


20/64

5/26/2018



22.6.2004

Field Name

Description


Note

Message type

Message type

FIDCC1 or

Sending FI documents for G/L transfer

FIDCC2 Process code

Process code

FID1 or

If SAP In-House Cash and Financial Accounting for the head office are not in the same system as BCA, you have to use process code FID1.

FID2

Syntax check

Syntax check

Select



Trigger immediately

Only in test phase, otherwise Trigger by background 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 from the view of the subsidiary company. For payment orders from companies affiliated with SAP In-House Cash, use message type PAYEXT with basic type PEXR2002 as the outbound parameter. For bank collections from companies affiliated with SAP In-House Cash, use message type DIRDEB with basic type PEXR2002 as the outbound parameter. For bank statements from the in-house cash center to affiliated companies, use message type FINSTA with basic type FINSTA01 and process code FINS as the inbound parameter. When you create PAYEXT, EUPEXR is created automatically. Recommendation: Create a port to which EUPEXR can be sent since this IDoc type is not required in SAP In-House Cash. You can delete 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 EDI partner 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: Menu Path IMG: SAP NetWeaver → SAP Web Application Server Application Link Enabling (ALE)

Transaction Code IDoc Interface /

→

SALE


21/64

5/26/2018



1.

22.6.2004

Define Logical System You have to define the logical systems. Here you define the system for the subsidiary and the system for SAP In-House Cash.

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

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE)→ Basic Settings → Logical Systems → Define Logical System

SALE


Description

Log.System

Logical system

Name

Name

2.



Assign Logical System to Client Here you assign a client to the subsidiary system.

Menu Path

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE) → Basic Settings → Logical Systems → Assign Logical System to Client

SALE


Description


Client

Client

City

City

Logical system

Logical system

Std currency

Standard currency



Select indicator: Changes without automatic recording



Changes to Repository and cross-client Customizing allowed

Protection: client copier and comparison tool

Protection regarding client copy program and comparison tools

Protection level 0: No restriction

Restrictions

Restrictions

Indicator that starting CATT processes is permitted

Note Example: 401

The logical system you defined (see step 1)

Example: TNFCLNT401


22/64

5/26/2018



3.

22.6.2004

Configure Systems in Network, Define Target Systems for RFC Calls Here you define the SAP In-House Cash system as your target system.

Menu Path

Transaction Code

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

SALE

→

Create RFC Connections

Choose R/3 Connections → Create. Detailed Settings Field Name

Description

RFC Destination

RFC Destination

Connection Type

Connection type

Description

Description

Logon/Security

Logon data


Note

3

Choose Test connection to test the connection.

4.

Generate Partner Profiles

Menu Path

Transaction Code

IMG: IDoc Interface / Application Link Enabling (ALE) → Modeling and Implementing Business Processes → Partner Profiles → Generate

BD82

Partner Profiles Detailed Settings Field Name

Description


Note

Model view

Model view

Your model view

Example: IHC

Partner system

Partner system

Logical system for in-house cash center

Example: TNFCLNT400


Only in test phase, otherwise background

Output mode

processing 

5.

Choose Execute to generate the partner profile.

Process EUPEXPORT See SAP note 527431.

Menu Path

Transaction Code


WE21



Choose Create to create a file port.


23/64

5/26/2018



22.6.2004


Description


Note

Port

Port

EUPEXPORT

Any value

Description

Description

Send EUPEX to file port

Physical directory

Select the physical directory indicator



6.

Choose Access Test to test the access to the file.

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

Menu Path

Transaction Code


WE20



Select Partner Type B.



Choose Create.


Description


Note

Partner no.

Partner number

Bank key

Example: 99999999

Type

US

Agent Lang.

Agent Language



User ID



Description


Message type

Message type

PAYEXT

Receiver port

Receiver port


Output mode

Output mode


Basic type

Basic type

PEXR2002

Syntax check

Syntax check

Select

Note

Only in test phase, otherwise background processing

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





24/64

5/26/2018



22.6.2004


Description


Message type

Message type

EUPEXR

Receiver port

Receiver port

EUPEXPORT

Output mode

Output mode


Basic type

Basic type

IDCREF01

Syntax check

Syntax check

Select



Note

Only in test phase, otherwise background processing

Choose Inbound Parameters

Detailed Settings Field Name Message type

Description Message type

User Action and Values FINSTA

Note

Process code

Process code

FINS


Syntax check

Syntax check

Select



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 make these entries for the logical systems. Make sure that the partner profile is active (partner status A). Menu Path

Transaction Code


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 send IDocs to the same system. This means that in partner type LS, the message types PAYEXT, DIRDEB, and FINSTA have identical inbound and outbound parameters. You only define message type EUPEXR in the outbound parameters.

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


25/64

5/26/2018



4

22.6.2004

Business Customizing

Purpose This section contains information about the Customizing settings in the systems of the subsidiary companies, the SAP Cash system and functions the head to office Business Customizing is aimed at adjusting theIn-House delivered cross-company the system. requirements of a specific company. This includes, for example:

Customizing for the organizational units

Customizing for the master data

Process Customizing

•

•

•

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

4.1 Customizing Financial Accounting for Subsidiary Companies 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 for payments via the in-house cash center. You carry out the Customizing for the incoming electronic account statement from the in-house cash center. These settings are required for internal payments, central payments, and central cash receipt.

Organizational Unit: Subsidiary Company

Group Subsidiary 3 Subsidiary 2 Subsidiary 1

Prerequisites For the house banks defined, you define the relevant bank accounts for the company code under an account ID. Specify the external account number with the bank, the currency, and the G/L account number 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.


26/64

5/26/2018



22.6.2004

Define New Payment Method for Bank Transfer or Bank Collection and Define it in the Bank Determination

Menu Path

Transaction Code

SAP Easy Access: Accounting → Financial Accounting → Banks → Outgoings → Automatic Payment → Open Items

FBZP

Menu: Environment → Maintain Config. 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 record for 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, use transaction code FIHC. See also SAP notes 335278 and 376180. Menu Path

Transaction Code

IMG: Financial Accounting → Bank Accounting Define House Banks

Bank Accounts →

→

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 by the in-house cash center by means of electronic bank statement.

Menu Path

Transaction Code

IMG: Financial Accounting → Bank Accounting → Business Transactions → Payment Transactions → Electronic Bank Statement → Make Global Settings 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 Company Code to Chart of Accounts. Create the account symbols. The account symbol determines the G/L account which is to be posted to. Detailed Settings Field Name

Description


Account

Account

Recommendation: Incoming

determination: Account symbols

payment, outgoing payment

Text

Note

Text of length 20


27/64

5/26/2018



22.6.2004

Assign the account symbols to the accounts. Detailed Settings Field Name

Description


Act Symbol

Bank statement:

Example: outgoing payment,

account symbol

incoming payment

Acct Mod.

Bank statement: account modification

Example: +, +

Currency

Bank statement: currency

Example: +, +

G/L Acct

Account determination: G/L account number

Example:

Acct Symb. Desc.

Note

Outgoing payment:+++++++++2, Incoming payment: +++++++++9

Text of length 20

Create the key for posting rules. The posting rules represent typical posting transactions for the bank statement. Detailed Settings Field Name

Description


Posting rule

Posting rule

Example: 0001, 0006

Text

Text of length 40

Example: Incoming payment, outgoing payment

Note

Define the posting rules. The account determination takes place via the posting rule. This provides the information required for posting (posting key, accounts, document type). Detailed Settings Field Name

Description




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/L Indicator (D)

Special G/L indicator

Acct (Debit)

Account determination: account symbols

50 Example: bank

Example: Incoming payment

Example: Outgoing payment

Compression (D) Posting Key (C)

Posting key

Special G/L Indicator (C)

Special G/L indicator


28/64

5/26/2018



Acct (Credit)

Account determination: account symbols

Compression (C)

22.6.2004

Example: Incoming payment

Example: Bank

.

Doc. Type

Bank statement: document type

Example: SA

Example: DZ

Example: SA

Posting Type

Bank statement: posting type

1

8

4

On Account Posting Key

Posting key for posting on account

ReversReas.

Reason for reversal or inverse posting

Assign transaction types to group banks with identical external transaction codes. Detailed Settings Field Name

Description


Trans. type

Transaction type

Example: MT940

Name

Text of length 40

Note

Assign the business transactions to these posting rules dependent on the transaction type. Detailed Settings Field Name

Description



External Transaction

External business transaction

020

051

+/- Sign

+/- sign of incoming amount

-

+

Posting Rule

Posting rule

Example: 0006

Example: 0001

Interpretation Algorithm

Interpretation algorithm

Standard algorithm

Standard algorithm

Planning Type, Transaction

Planning type, transaction

Processing Type

Processing type

0

0

Assign the bank accounts to the transaction types.


29/64

5/26/2018



22.6.2004


Description

Bank Key

Bank key, usually bank

Bank key of your bank area

number Bank account number

from SAP In-House Cash Current account number

Bank Account Trans. Type

Transaction type

Currency Class

Class of currency key used

Planning Type

Planning type

Summarizati on

Summarization of bank statement items

Company Code

Company code

Planning Account Name

Planning account name


Note

Example: MT940

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.


30/64

5/26/2018



22.6.2004

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 central payments, the payment information is also forwarded to the financial accounting system of the head office. The in-house cash center creates and sends account-statement-relevant data in the form of a FINSTA IDoc.

Organizational Unit: In-House Cash Center

Group

Head Office In-House Cash Center

Financial Accounting

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


Description

Desc.Bank Area

Name of the bank area

Bank Country

Bank country

Bank Key

Bank key


Note

.


31/64

5/26/2018



Language

Language

Bk Area Currency

Bank area currency

Cur.pre EURO

Currency before changeover to Euro

Calendar

Factory calendar

Time Post.Cut-Off

Time of automatic posting cut-off

Exch.Rate Type

Exchange rate type

Company Code

Company code

Each company code is assigned to a bank area.

GL Variant

General ledger variant

The variant can only be entered here if previously defined.

Activate Log

Activate log

IHC Active

Activate bank area as in-house cash center

22.6.2004

The bank area currency is usually the same as the local currency of the company code to which the bank area is assigned.

See documentation

The GL variant defines how the transfer from bank area to FI general ledger takes place.

X

You cannot subsequently change the company code and the general ledger variant because there is no check in Customizing for determining whether or not documents have already been posted. 2.

Set Up Number Ranges for Log

Navigation Menu Path

Transaction Code

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

IHCN1

Create a number range interval for the log. 3.

4.

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

Set Up Number Ranges for IHC Payment Orders


Transaction Code

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

F9A5

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


32/64

5/26/2018



5.

22.6.2004

Maintain Number Ranges of External Bank Account


Transaction Code

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 external number 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 Payment Orders

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 same or separate systems.

Menu Path IMG: In-House Cash → Basic Settings → Basic Settings - Postings → Set +/- Sign Postings/GL Transfer/Name Check


Description

+/- Outgoing Payments

+/- sign for outgoing payments

Trans.Type FI Gen.Led.

Transfer type of general ledger data to FI

RFC Destination

RFC Destination

Model View

Model view of ALE model

Condition Type for Sales Tax

Condition type for sales tax

Check G/L Data before Transfer

Check G/L data before transfer

Necessary Word

Necessary word

Length for Incorrect Letter

length for an incorrect letter


Note The system proposes negative signs by default.

The following cases are possible: FI general ledger and BCA are in the same or different systems

The FI general ledger is in the same system as BCA per default.

Only if BCA is in a different system to the FI general ledger Model view for general ledger transfer

Only if BCA is in a different system to the FI general ledger

The default setting is to check the G/L data before transfer.


33/64

5/26/2018



22.6.2004

Process the partner profiles if BCA is not in the same system as the FI general ledger. Define message type FIDCC1, basic type FIDCCP01 as input parameters in the SAP In-House Cash system and 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


Description


La Outg.Payts

Language Outgoing payment

D/C, +/-

Description

Description

Description for outgoing payment

In-Paymnts

Incoming payment

D/C, +/-

Description

Description

Description for incoming payment

9.

Note

Texts in relevant language

Texts in relevant language

Assign Check Digit Methods to In-House Cash Center

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


Description

Ctry

Bank country

Bank Key

Bank key

Meth

Method


Note

Enter a method which has a procedure without checks assigned to it.

10. Activate SAP Component SAP In-House Cash Menu Path

Transaction Code

IMG: In-House Cash → Basic Settings → Business Transaction Events/Event Control → Activate SAP Components

BF11


34/64

5/26/2018



22.6.2004

Set the active indicator for the components SAP In-House Cash and Standard Accounting . Deactivate the 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 Menu Path

Transaction Code

IMG: In-House Cash → Basic Settings → Business Transaction 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 Menu Path

Transaction Code

IMG: In-House Cash → Basic Settings → Business Transaction 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 Menu Path

Transaction Code

IMG: In-House Cash → Basic Settings → Business Transaction Events/Event Control → Create/Activate Partner

BF12

Set the active indicator for the IHC partner.


35/64

5/26/2018



22.6.2004

14. Define IHC Product of Partner Menu Path

Transaction Code

IMG: In-House Cash → Basic Settings → Business Transaction 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 cash center and Financial Accounting are in the same client. Ignore any warning messages that might appear.

15. Activate IHC Product of Partner Menu Path

Transaction Code

IMG: In-House Cash → Basic Settings → Business Transaction 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 Menu Path

Transaction Code

IMG: In-House Cash → Basic Settings → Business Transaction Events/Event Control → Define Function Modules (P/S) of a Partner

BF32 (Table TBE32)


Description


Event

Event for exporting process data

00002810 and 00002850

Partner

Identification of complementary software partner

IHC

Product

Product of complementary software 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 components per function module

17. Process Partner Function Modules per Process Interface Make the following settings in transaction BF42 (table TPS32):


36/64

5/26/2018



22.6.2004


Description


Event

Event for exporting process data

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 complementary software partner

IHC

Product

Product of complementary software 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 the documentation.

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 by using the FIPR_ATTRIBUTE_COPY_CLIENT report. You can upload products to a target client from the Customizing delivered by using the FIPR_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 Bank Areas

Product Definition → Product → Assign Products to

→

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

Transaction Code

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

F98E

Assignment → Edit


37/64

5/26/2018



Menu Path

22.6.2004

Transaction Code

IMG: In-House Cash → Master Data Change Product

Product Definition

→

→

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. These indicators are primarily relevant for displaying and entering manual payment orders. For example: set the 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 different system (an in-house cash center or a different company code) or the same system/client (RFC destination 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).


38/64

5/26/2018



3.

22.6.2004

Make Basic Settings for Payment Processes

Menu Path IMG: In-House Cash → Payment Processes in In-House Cash Payment Processes

Make Basic Settings for

→

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 the components SAP In-House Cash (FIN-FSCM-IHC) and Accounting (FI). In accordance with the settings that you make here, the data from payment orders that you have created manually in SAP InHouse Cash are converted, and the converted payment order data is transferred to the table for payment requests in Accounting . b) Automatically created IHC payment orders: These settings concern the interface between an external 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 the in-house cash center via IDocs. The payment orders can be for internal payments or payments to external partners. The following tables control the processing internal andrequests external in payment orders. SAPfor In-House Cash transfers external payments to the tableoffor payment FI. Process entries 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 Field Name

Description


Bank Area

Name of the bank area

IHC

Transact.

Transaction type

EXTPAY

Processing

Payments processing in IHC

F

ExDocProvP

External document for provisional payment indicator

Define here which predefined transaction types you want to use in which bank area. You can decide per transaction type whether you want provisional or final posting. Detailed Settings: Settlement Accounts Field Name

Description


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.


39/64

5/26/2018



22.6.2004

Detailed Settings: Posting Data Field Name

Description

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. You can 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 to carry out the translation. The secondary selling rate or secondary buying rate is used per default to determine the exchange rate. You can differentiate between provisional and final postings for each settlement 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. All exchange rates are taken from the TCURR table. You can calculate exchange rates separately for manual individual payments.

Field Name

Description


Bank Area

Bank area

IHC

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 Field Name

Description


Bank Area

Bank area

IHC

Partner

Recipient for forwarding an external payment

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 area postings.


40/64

5/26/2018



22.6.2004

Detailed Settings: Payment Method Data Field Name

Description

Bank Area

Bank area

Partner


Trns.Cur.

Transaction currency

RecBankKey

Recipient country key of bank

Transact.

Transaction type

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 Field Name

Description

Bank Area

Bank area

Partner


Trns.Cur.

Transaction currency

Rec.Partn.Type

Partner type of the recipient

Transact.

Transaction type

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 Field Name

Description

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 Transaction Type

Define Default Setting for

→

You will need to make these settings for manual payment orders. Page 41/64 http://slidepdf.com/reader/full/config-guide-sap-in-house-cash

41/64

5/26/2018



5.

22.6.2004

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 message type 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 details, postingwith accounts andtype processing parameters the clearing partner. These entriesthe areaccount required for PAYEXT message PEXC or PEXC_PI for in FI.

7.

Instructions for FI

You need to make entries here for instruction codes and instruction keys per bank area. You can process several instructions per instruction code (or instruction number) in the Define Instruction Codes for FI IMG activity. In the Define Instruction Keys IMG activity you can enter a maximum of four instructions 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 four instructions. You must now decide whether you want to use instruction keys or instructions. This data is 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 Statements This is the central payment receipt process. You define which items from an incoming bank statement are to be posted to SAP In-House Cash. When the bank statement is received, the payment note is checked. If these entries exist in the following 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 Payment Notes


42/64

5/26/2018



22.6.2004


Description


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 of bank 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 office house bank for each affiliated company. The relevant in-house cash center can be determined on the basis of the following information: a.

External bank number of the house bank and external account number of the account in 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 the bank area in SAP In-House Cash. Menu Path IMG: In-House Cash → Account Management → Payment Processes in In-House-Cash → Central Cash Receipt / Incoming Bank Statements → IHC Account Determination from External Bank Account


Description


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 bank account

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 current account

Account to which the incoming payment is to be posted

10. Define Transaction Types for Incoming Payment

Menu Path IMG: In-House Cash → Account Management → Payment Processes in In-House-Cash → Central Cash Receipt / Incoming Bank Statements → Define Transaction Types for Incoming Payment Page 43/64 http://slidepdf.com/reader/full/config-guide-sap-in-house-cash

43/64

5/26/2018



22.6.2004


Description

Bank Area

Bank area

TransTyp

Transaction type

BTC

Business transaction code

+/-

Credit/debit indicator

Transact.

Transaction type

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 Incoming Payment


Description

CoCd

Company code

House Bk

Short key for a house bank

Acct ID Bank Area

Short key for account details Bank area

FI Acct in IHC

IHC: FI customer/vendor account in IHC

Header acct for Central Incoming Payments

IHC: Header account for payments from bank 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 IMG: In-House Cash → Account Management → Payment Processes in In-House Cash Cross-Bank Area Posting → Set Up Route Processing

→


44/64

5/26/2018



22.6.2004

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 Determination 1. 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 posting category 71, transaction type 5110, and business transaction code 051. If required, add to the Customizing 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 create general ledger variants as transfer templates and assign them to several bank areas. In the general ledger variant, transaction types are grouped in general ledger transactions. The accounts are grouped in general ledger groups. These details enable you to specify the transfer precisely. Menu Path IMG: In-House Cash → Periodic Tasks

1.

General Ledger Transfer → Maintain GL Variants

→

Maintain General Ledger Transaction for General Ledger Transfer

A general ledger transaction groups postings for several transactions in the current account system into 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 a general ledger transaction to each transaction type involved in the payment transaction. One general ledger transaction is created for each general ledger variant. Menu Path IMG: In-House Cash → Periodic Tasks

General Ledger Transfer → Maintain GL Transaction

→


45/64

5/26/2018



22.6.2004

Assign Payment Transaction Type to General Ledger Transaction

For the general ledger transfer, assign a general ledger transaction type to each transaction type in the current account system. You can assign several payment transaction types to one general ledger transaction type. Navigation Menu Path IMG: In-House Cash → Periodic Tasks → General Ledger Transfer → Assign Transaction Type for 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 an account to an account group (relevant for the general ledger transfer) when you create the account by maintaining the corresponding field. In Customizing you define possible general ledger groups. Navigation Menu Path IMG: In-House Cash → Periodic Tasks

4.

General Ledger Transfer → Maintain GL Group

→

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 Assignment: Current Accounts

5.

General Ledger Transfer → Define GL Account

→

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 from the 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 on the +/- sign. Menu Path →

IMG: In-House Cash Periodic Tasks Payables/Receivables

→

General Ledger Transfer

→

Transfer Postings

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


46/64

5/26/2018



22.6.2004

Navigation Menu Path IMG: In-House Cash → Master Data Change Product

Transaction Code Product Definition → Product

→

Choose Account Fields → Master Data

→

FIPRD2

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 Management In the following IMG activity you process the entries for In-House Cash payment orders in addition to the authorization management IMG activities. 1. Principle of dual control Navigation Menu Path IMG: In-House Cash → Basic Settings → Authorizations for IHC Payment Orders → Set Up Principle 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. Menu Path

Transaction Code

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

F9AUTH


47/64

5/26/2018



4.

22.6.2004

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

Menu Path

Transaction Code

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

PFCG

6.

Amount-Dependent Authorizations: Maintain Amount Limit/Principle of Dual Control for Payment Order

Menu Path

Transaction Code

IMG: In-House Cash → Authorization Management → AmountDependent Authorizations → Maintain Amount Limit/Principle of Dual Control for Payment Order

F9POAUTH


Description


BkAr

Bank area

Your bank area

Intern. Prod. ID

Internal product ID

TA Type

Transaction type

AuGr

Authorization group

Amt. Bank Area

Amount in bank area currency

Contr.

Indicator: Check by 2 users required (dual control)

7.

A1

Amount-Dependent Authorizations: Maintain Amount Limit/Principle of Dual Control for Payment Item

Menu Path

Transaction Code

IMG: In-House Cash → Authorization Management → AmountDependent Authorizations → Maintain Amount Limit/Principle of Dual Control for Payment Item

F9ITAUTH


Description


BkAr

Bank area

Your bank area

Intern. Prod. ID

Internal product ID

TA Type

Transaction type

AuGr Amt. Bank Area

Authorization group Amount in bank area currency

Contr.

Indicator: Check by 2 users required (dual control)

A1


48/64

5/26/2018



22.6.2004

Amount-Dependent Authorizations: Maintain Amount Limit for Hold

Menu Path

Transaction Code

IMG: In-House Cash → Authorization Management → AmountDependent Authorizations → Maintain Amount Limit for Hold

F9HLDAUTH


Description


BkAr

Bank area

Your bank area

Internal Product ID

Internal product ID

Authorization Group

Authorization group

Amount Bank

Amount in bank area currency

A1

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 forecast before general ledger transfer.

Menu Path

Transaction Code

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 of accounts. 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: Menu Path

Transaction Code

IMG: In-House Cash → Periodic Tasks → Transfer Financial Status to SAP Cash Management → Check the Consistency of the Settings

IHCCM3


49/64

5/26/2018



3.

22.6.2004

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 active in the standard system. If you do not want integration with SAP Cash Management you can deactivate this BAdI here. Menu Path SAP Easy Access: In-House Cash Status to CM

Transfer Financial Status to CM

→

Transfer IHC Financial

→

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

•

•

Organizational Unit: Financial Accounting of Head Office

Group

Head Office In-House Cash Center

Financial Accounting

Prerequisites You have defined the G/L accounts of the head office company code including the bank clearing accounts 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 Menu Path

Transaction Code

IMG: Financial Accounting → Bank Accounting → Business Transactions → Payment Transactions → Payment Handling → Define Global Settings

F8BG

Here you make the settings for the origin indicator.


50/64

5/26/2018



2.

22.6.2004

Make Settings for the Origin Indicator Menu Path

Transaction Code

IMG: Financial Accounting → Bank Accounting → Business Transactions → Payment Transactions → Payment Handling → Enter Origin Indicators

F8BG

SAP recommends that you set the indicator for planned amounts. In this case, the payment program 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 be posted to in the general ledger. The accounts are specified per house bank account, payment method, 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. Menu Path

Transaction Code

IMG: Financial Accounting → Bank Accounting → Business Transactions → Payment Transactions → Payment Request → Define Clearing Accounts for Recipient Bank for Account Transfer

F8BG

Menu Path

Transaction Code

(Table T018V)

F8BG IMG: Financial Accounting → Bank Accounting → Business Transactions → Payment Transactions → Payment Handling → (Table T042Y) Bank Clearing Account Determination → Define Account Determination.

Menu Path

Transaction Code

IMG: Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Outgoing Payments → Automatic Outgoing Payments → Payment Method/Bank Selection for Payment Program → Set Up Bank Determination for Payment Transactions

FBZP (Table T042I)

Click on Bank Accounts.

Tables T042I (configuration of F110 payment programs) and T042Y (configuration of F111 payment programs) must be consistent. The consistency of the entire table is checked; 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.


51/64

5/26/2018


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

22.6.2004

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 Electronic Bank 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 1.

Integration with Cash Management Define Source Symbols Menu Path IMG: Cash and Liquidity Management Define Source Symbols

Cash Management → Basic Settings →

→

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

2.

Define Planning Levels Menu Path IMG: Cash and Liquidity Management → Cash Management → Master Data Accounts → Define Planning Levels

→

G/L

Here you make the settings for the planning levels. Detailed Settings Field Name

Description


Level

Planning level

Example: I1, I2, I3

SC

Sign control

Source

Source symbol

Example: IHC

Short Text

Planning level short text

IHC-IST, IHCPLINT, IHC-PLEXT

Planning Level Long Text

Planning level long text

3.

Note

No entry

Define Cash Management Account Name Menu Path IMG: Cash and Liquidity Management → Cash Management → Structuring → Define Cash Management Account Name Make settings in the head office company code.


52/64

5/26/2018



22.6.2004


Description


CM Acct

Planning account name

Example: CLPARTNER, COMPANY01, COMPANY02

G/L Acct

Bank account / bank clearing account

No entry

Bank Account

Bank account number

No entry

CMF

Cash management and forecast only

Set the indicator

Description

Description

4.

Note

Define Groupings and Maintain Headers Menu 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


Description


Grouping

Grouping for cash position, liquidity forecast, concentration

Example: IHC, IHC, IHC

T

Line type

Example: E, G, G

Selection

Selection for cash management

Example: I+

Note

At least one level and one group

CLPARTNER COMPANY++ CoCd

Company code

ChAc

Chart of accounts

Exclude

Exclude

Sum. Term

Summarization term

Example: ** CLPARTNER COMPANIES

Summ. Acct

Summarization account

SCOCD

Summarization company code for cash concentration


53/64

5/26/2018



22.6.2004

Define Planning Types Menu Path IMG: Cash and Liquidity Management → Cash Management → Structuring → Manual Planning → Define Planning Types


Description


Plg Type

Planning type

Example: I1, I2, I3

Plg Level

Planning level

Example: I1, I2, I3

Arch.Cat.

Archiving category

A, A, A

Auto Expir

Automatic expiration

Number Rng

Number range

Planning Type Text

Planning type text

Also process the field status definition.

4.4 Localization Use KIDNO is used in Scandinavian countries as a payment reference.

Procedure in FI for Subsidiary Companies Make the following settings in the Financial Accounting system of the subsidiary company: Menu Path IMG: Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Incoming Payments → Incoming Payments Global Settings → Payment Advice Notes (Incoming) Select Choose Selection Fields for Payment Advice Notes. Add KIDNO as a field name. Select Choose External Selection Fields for Payment Advice Notes. Add KIDNO as a field name. Choose Define Selection Rules. Define a selection rule of your choice for the KIDNO. Select Allocate Selection Fields. Assign an external and an internal selection field to the new selection rules.

Make the following settings in all affected customer master records: Choose the Payment Transactions tab page under Company Code Data. Enter the selection rules defined for KIDNO in the Payment Advice Notes screen area.


54/64

5/26/2018



22.6.2004

Procedure for In-House Cash Center Make the following settings in the in-house cash center : Menu Path IMG: In-House Cash → Account Management → Payment Processes in In-House Cash Outgoing Payment Orders → Automatically Created Payment Orders

→

Activate the Split indicator for all business partners that use KIDNO. This ensures that the KIDNO is 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 for field names. Enter KIDNO as the first field name. The other fields can have any name other than KIDNO. 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.


55/64

5/26/2018



5

22.6.2004

Configuring Component-Specific Master Data

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

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

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 SAP applications, 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: Menu Path

Transaction Code

IMG: Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings Define Number Ranges

BUCF

→


Description


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 Menu Path

Transaction Code

SAP Easy Access → Accounting → Financial Supply Chain Management → In-House Cash → Business Partners

BP


56/64

5/26/2018



22.6.2004

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

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

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

3.

Create account maintenance officer: The account maintenance officer is usually an internal employee 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 date before you start to create the current account. Menu Path

Transaction Code

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 to be 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 the account 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 to mass runs. Mass runs can only be started once a day because a day is the smallest possible unit for processing frequencies of account statements. As soon as an account statement has been generated in a mass run, the system automatically increases the date in the account by one day. This means that you 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. You have created current accounts for the subsidiary companies.


57/64

5/26/2018



6

22.6.2004

Ongoing Settings

6.1 Current Settings for Updating the Posting Date for Payment 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 later posting date.

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

•

•

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

Procedure 1.

Update Posting Date for Payment Transactions

Menu Path

Transaction Code

SAP Easy Access → In-House Cash → Periodic Processing → Posting Date → Payment Transactions

F9B1

Detailed Settings Field Name Bank Area

Description Bank area

New Posting Date

Posting date

2.


Note

Update Posting Date for Closing Manually


Transaction Code

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

F9L4


Description

Bank Area

Bank area

New Date Balancing Posting

Current posting date for balancing in bank area


Note

Result The posting dates for payment transactions and closing are updated. Page 58/64 http://slidepdf.com/reader/full/config-guide-sap-in-house-cash

58/64

5/26/2018



22.6.2004

6.2 Ongoing Settings for Integration with SAP Cash Management 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 IHC financial status has been transferred. You can also plan this step as part of your daily tasks.

Procedure Transfer IHC Financial Status to CM Navigation Menu Path

Transaction Code

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 the planned incoming or outgoing payments. The finally posted payment orders are in the posted balances.


59/64

5/26/2018



7

22.6.2004

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 relevant parameters 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 the F110 payment program.

3.

Check whether you have processed the EDI-compatible payment methods in the data for the IHC 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.

Menu Path

Transaction Code

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 bank statements. 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 is written to the log).

The IDoc communication data is incomplete.

ALE Customizing is incomplete.

•

•

•

Check the routes: Menu Path IMG: In-House Cash → Account Management → Payment Processes in In-House Cash → Cross-Bank Area Posting → Set Up Route Processing


60/64

5/26/2018



22.6.2004

Check your settings for the clearing partner: Menu Path IMG: In-House Cash → Payment Processes in In-House Cash

Define Clearing Partner

→

Complete the detailed entries, paying particular attention to the communication data and routes: Menu Path IMG: In-House Cash → Payment Processes in In-House Cash Payment Processes

Make Basic Settings for

→

Check your entries for each account: 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

Check the ALE settings: Menu Path IMG: SAP NetWeaver → SAP Web Application Server Application Link Enabling (ALE)

Transaction Code IDoc Interface /

→

SALE

Complete the manual partner profiles: Menu Path

Transaction Code

SAP Easy Access → Tools → ALE → ALE Administration → Runtime Settings → Partner Profiles

WE20


61/64

5/26/2018



8

22.6.2004

Reverse

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

Transaction Code

Internal payments, central payments, central incoming payments In-House Cash → Account Management → IHC Payment Orders Payment Order Browser

→

IHC0

Choose the payment orders you want to reverse. Go to change modus. Use the delete function to reverse the payment order. Payment requests that were generated with PAYEXT (if they are still open) are reversed by means of RFC.


62/64

5/26/2018



22.6.2004

9 Application Security Guide for SAP In-House Cash 9.1 Introduction This guide is intended to give you an overview of security aspects and some recommendations as to how 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 of user authentication, for example, user IDs and passwords, password rules and preventing unauthorized logons.

SAP Authorization Concept

This section gives an overview of the SAP authorization concept and how you can use it to protect your applications from misuse.

Protecting Your Productive System

This section describes how you can prevent unwanted changes from being made in your productive system by means of the Change and Transport System (CTS) and the Transport Management System (TMS).

Secure Store & Forward Mechanisms (SSF) and Digital Signatures

This section deals with the security aspects of using public keys for digital signatures encryption functions.

Special Topics

Security measures that you can or must employ for certain topics.

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

9.2 Security Measures for Saving Data If you are required to submit information, all relevant master data (customer, vendors) and transaction data (invoice details) are available in the subsidiary company. Communication between subsidiaries and the in-house cash center is based on IDocs. When the subsidiary starts payment programs F110 / F111, subsidiary master data and transaction data are written 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 of the payment run, data about the payment recipient, the recipient bank, amount and payment notes.

When you create PAYEXT or DIRDEB, EUPEXR is created automatically in the subsidiary company.

•

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


63/64

5/26/2018



22.6.2004

In the case of external payments (in other words, the recipient's account is not in the same bank area as the payer's account), a PAYEXT or DIRDEB IDoc is sent from the in-house cash center to the executing FI system. The information received is the same as described in the previous 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 cash center, an IDoc can be used during end-of-day processing for communication between the inhouse cash center and financial accounting. The FIDCC1 contains all balances grouped during balance sheep preparation to enable them to be posted subsequently to the general ledger.

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

9.3 Authorizations The role of in-house cash supervisor is delivered with SAP In-House Cash. The SAP_FSCM_IHC_Supervisor role is found in the profile generator (transaction PFCG) and can be modified. Due to detailed information contained in the PAYEXT, DIRDEB and FINSTA IDocs we recommend that you restrict authorization to manage or to display the IDocs or to grant only certain users authorization. As part of the SAP authorization concept, the authorization object IHC_ACTION is available for IHC payment orders. You can define a range of authorization restrictions for creating, viewing, changing and processing payment orders. For example, you can restrict authorization to individual accounts or assign 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 relevant authorizations must also be granted or restricted in these components (for example, display authorization for current accounts) if the user is allowed to execute these transactions.

9.4 Data Protection The processor in SAP In-House Cash has authorization to view all postings and turnover in the current accounts of subsidiary companies. Authorization cannot be restricted depending on the payment recipient. 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 is made. This is to prevent IDocs from a test system from being sent unintentionally to a productive system.

9.6 Encryption You do not need to encrypt your data, however you may still decide to do so.


64/64

Config Guide Sap in House Cash

Recommend Documents