Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
1|Page
For More Details -Contact Us
FSCM – IN-House Cash Center – Configuration Document – EC1
Contents
1
BUSINESS CONFIGURATION IN THE HEADQUARTERS SYSTEM: BASIC SETTINGS 6
Set up Number Ranges for Log
6
1.2
Create Bank Key for IHC
6
1.3
Define Bank Area
7
1.4
Set Up New Posting Date
7
1.5
Creating Business partner Roles for In-House Cash
8
1.6
Configure Field Attributes per BP Role
8
1.7
Create Accounts
1.8
Product Definition
1.9
Condition Assignment
1.10
Master Data for Current Account
14
1.11
Maintain Business Partner
17
1.12
Partner Profile
17
1.13
Define House Banks
18
1.14
Partner Profile
20
1.15
Create technical account for IHC: FI Customer/Vendor Account in IHC
21
1.16
IHC: Header Account for Centralized Incoming Payments
22
1.17
Set Up Number Ranges for IHC Payment Orders
23
1.18
Maintain Number Ranges Ext. Account Numbers
23
1.19
Set +/- Sign Postings/GL Transfer/Name Check
24
1.20
Set Texts for Incoming / Outgoing Payments
24
1.21
Set Format for Payment Notes
25
1.22
Business Transaction Events / Event Control → Create/Activate Partner
25
Ad
i
ty
a
.C
ha
lla
1.1
9
11
13
2|Page
FSCM – IN-House Cash Center – Configuration Document – EC1
1.23
Define Partner Product
26
1.24
Define Function Modules (P/S) of a Partner
26
1.25
Define Function Modules (Process) of a Partner
26
2
BUSINESS CONFIGURATION IN THE HEADQUARTERS SYSTEM: MASTER DATA 28
Enter Basic Settings for Conditions
28
2.2
Set Up Condition Areas
28
2.3
Set up Transaction Types – Condition Calculation
29
2.4
Transaction Types for Transaction Interest Posting
29
2.5
Setup Transaction Types for Direct Charge posting
30
2.6
Define Limit Categories
2.7
Define Account Locking Reasons
2.8
Maintain Account Relationship Types
2.9
Maintain Dispatch Type for Bank Statements (Old)
.C
ha
lla
2.1
30
31
32
33
33
3.1
Define Transaction Types
33
3.2
Define Clearing Partner
34
3.3
Maintain Transaction Types
35
3.4
Maintaining Logical System for Headquarters (Transfer from IHC -> FI)
36
3.5
Port Maintenance
37
3.6
Maintain Partner Profiles
37
3.7
Define Logical system
38
3.8
Make Basic Settings for Payment Processes
39
3.9
Define Default Setting for Transaction Type
43
3.10
Define Transaction Type for Automatic Payments
43
3.11
Define Business Transaction Codes
44
3.12
Check – Maintain Transaction Types
44
Ad
i
ty
a
3 BUSINESS CONFIGURATION IN THE HEADQUARTERS SYSTEM: ACCOUNT
MANAGEMENT
3|Page
FSCM – IN-House Cash Center – Configuration Document – EC1
3.13
Maintain Authorization Groups
45
3.14
Maintain Amount Limit/Principle of Dual Control for Payment Order
45
3.15
Maintain Amount Limit/Principle of Dual Control for Payment Item
46
Define Transaction Types for Incoming Payment
46
4.2
Define House Banks
47
4.3
Bank Determination for Payment Transaction
48
4.4
Set Up Creation of Payment Requests for Inbound IDoc in FI
49
4.5
Set Up Account Determination for Incoming Payment
50
4.6
Bank Clearing Account Determination
51
4.7
Assign Offsetting Transaction Types
4.8
Maintain Media and Payment Method
4.9
Maintain Note Dialog Box for Payment Transaction Locks
53
4.10
Maintain Accounts for Payment Transactions
53
4.11
Assign Return Reasons and Return Transaction Types
54
4.12
Tolerance Days for Forward Order
54
ha
lla
4.1
.C
4 BUSINESS CONFIGURATION IN THE HEADQUARTERS SYSTEM: CUSTOMIZING OF
OTHER APPLICATION COMPONENTS
46
51
5.1
Ad
i
ty
a
52
Maintain GL Variants
55
5.2
Maintain GL Transaction
55
5.3
Assign Transaction Type for Payment Transaction to GL Operation
56
5.4
Maintain GL Group
56
5.5
Transfer Postings Payables/Receivables
57
5.6
Define GL Account Assignment: Current Accounts
57
5.7
Specify Sequence of Mass Processing
58
5 BUSINESS CONFIGURATION IN THE HEADQUARTERS SYSTEM: GENERAL LEDGER
TRANSFER
55
IN-HOUSE CASH BUSINESS CONFIGURATION IN THE SUBSIDIARIES SYSTEM
59
4|Page
FSCM – IN-House Cash Center – Configuration Document – EC1
6
BUSINESS CONFIGURATION IN THE SUBSIDIARIES SYSTEM: BASIC SETTINGS 59
6.1
Create Accounts
59
6.2
Classify G/L Accounts for Document Splitting
60
61
61
61
62
63
6.4
Define House Banks
6.4.1
Set Up Bank Determination for Payment Transactions
63
64
6.5
Global Settings for Electronic Bank Statements
65
6.6
Create Vendor – Subsidiary
69
7.1
8
70
CONFIGURING COMPONENT-SPECIFIC MASTER DATA
Create Variant for Payment Run F110
70
CONFIGURING COMPONENT-SPECIFIC MASTER DATA – HEADQUARTERS -
71
.C
7
ha
lla
6.3
Set up Payment Method in subsidiary
6.3.1
Set Up All Company Codes for Payment Transaction
6.3.2
Set Up Paying Company Codes for Payment Transactions
6.3.3
Set Up Payment Methods per Country for Payments Transaction
6.3.4
Set Up Payment Methods per Company Code for Payments Transaction
Create Variant for Payment Run F111 – External Payments
71
8.2
Create Variant for Payment Run F111 – Check Payments
72
8.3
Classify G/L Accounts for Document Splitting in Headquarters System.
73
Ad
i
ty
a
8.1
5|Page
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
In-House Cash Business Configuration in the Headquarters
System
1 Business Configuration in the Headquarters
System: Basic Settings
1.1 Set up Number Ranges for Log
The purpose of this activity is to create a number range to log payment orders for
technical reasons. These numbers are not displayed in the user interface.
ha
lla
Menu Path  Financial Supply Chain Management  In-House Cash  Basic
Settings  Set Up Number Ranges for Log
ty
a
.C
Transaction Code: IHCN1
Ad
i
1.2 Create Bank Key for IHC
IMG Path  None
Transaction Code: FIHC
6|Page
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.3 Define Bank Area
The purpose of this activity is to set up the cash center in headquarters
Ad
i
ty
a
.C
ha
lla
IMG Path  Financial Supply Chain Management  In-House Cash  Basic Settings
 Bank Area  Define Bank Area
1.4 Set Up New Posting Date
Purpose: If a bank area has been newly created, this bank area must be linked to the
posting date before a posting cut-off can be performed.
IMG Path  Accounting  Financial Supply Chain Management  In-House Cash 
Periodic Processing  Posting Date Payment Transaction
Transaction Code: F9B1
7|Page
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.5 Creating Business partner Roles for In-House Cash
ha
lla
Purpose: Create the technical business partner once as a central data object and it is
used by different SAP applications, including SAP In-House Cash.
To create master data for a current account, you have to assign certain roles to the
business partner. This technical account we need for the technical bank accounts.
Ad
i
ty
a
Transaction code: BP
.C
IMG Path  Accounting  Financial Supply Chain Management  In-House Cash
 Business Partners  Maintain Business Partners
1.6 Configure Field Attributes per BP Role
IMG Path  Financial Supply Chain Management  Treasury and Risk Management
 Basic Functions  SAP Business Partner for Financial Services  General Settings
 Basic Settings  Field Groups  Configure Field Attributes per BP Role
8|Page
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
Select BP Role: BKK010 (Description: Account Holder)  Choose Field Grouping
On Change View “Field Group BP Role” Overview Screen – Data set choose
Identification Numbers and change following entry:
Fld groups
User action and Values
Hide
empty
Req.entry
empty
Opt.entry
empty
Display
empty
Mark it
Ad
i
ty
a
.C
ha
lla
Not spec
1.7 Create Accounts
The purpose of this activity is to specify the clearing account number of the G/L
account on which the payment amount should be posted in FI.
IMG Path  Accounting → Financial Accounting → General Ledger → Master
Records → G/L Accounts → Individual Processing → Centrally
Transaction Code – FS00
9|Page
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
10 | P a g e
Aditya.Challa
.C
1.8 Product Definition
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
ty
a
Purpose: Define the products that are to be managed within the Bank Current
Accounts system. Products can be seen as a summary of functionalities that you later
assign to the individual accounts. This allows you to offer special products, tailormade to suit a certain customer group.
Ad
i
IMG Path  Financial Supply Chain Management  In-House Cash  Master Data
 Product Definition  Product  Change Product
11 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
12 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.9 Condition Assignment
Define the interest percentage for credit and debit and charges. This is for credit
clearing between subsidiaries and headquarters.
IMG Path Accounting  Financial Supply Chain Management  In-House Cash 
Conditions  Condition Assignment  Edit
Ad
i
ty
a
.C
ha
lla
Transaction Code: F98E
13 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.10 Master Data for Current Account
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.
IMG Path Accounting  Financial Supply Chain Management  In-House Cash 
Account  Create
Ad
i
ty
a
.C
ha
lla
Transaction Code: F9K1
14 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
15 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
16 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.11 Maintain Business Partner
Additional clearing center for a foreign currency. For example: in this case a clearing
center for currency Dollar. Create business partner: SUB_USA.
IMG Path Accounting  Financial Supply Chain Management  In-House Cash 
Business Partners  Maintain Business Partners
Ad
i
ty
a
.C
ha
lla
Transaction Code: BP
1.12 Partner Profile
This activity defines the partner profile for the bank business partner in the
subsidiary to allow processing of IDoc messages with the headquarters system for
scenario In-House Cash.
IMG Path Tools -> ALE -> ALE Administration -> Runtime Settings -> Partner
Profiles
Transaction Code: WE20
17 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
1.13 Define House Banks
Define house bank for outgoing payments
IMG Path Financial Accounting (New) → Bank Accounting → Bank Accounts →
Define House Banks
Transaction Code: FI12
18 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
19 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.14 Partner Profile
Define an additional clearing center for a foreign currency. For example: in this case
a clearing center for currency USD. Create bank account for business partner
sub_USA.
Ad
i
ty
a
.C
ha
lla
IMG Path Tools -> ALE -> ALE Administration -> Runtime Settings -> Partner
Profiles
Transaction Code: WE20
20 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.15 Create technical account for IHC: FI
Customer/Vendor Account in IHC
The purpose of this activity is to create current account, which the FI that imports
the bank statement holds in the in-house cash center. All external payments incoming bank statement- will be posted in this account.
IMG Path Accounting  Financial Supply Chain Management  In-House Cash 
Account  Create
Ad
i
ty
a
.C
ha
lla
Transaction Code: F9K1
21 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.16 IHC: Header Account for Centralized Incoming Payments
Payments for which the system was not able to automatically determine a recipient
are posted to this account
IMG Path Accounting  Financial Supply Chain Management  In-House Cash 
Account  Create
Ad
i
ty
a
.C
ha
lla
Transaction Code: F9K1
22 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.17 Set Up Number Ranges for IHC Payment Orders
The purpose of this activity is to create a number range for the IHC payment orders.
This is the central business data object within the IHC application.
IMG Path Financial Supply Chain Management  In-House Cash  Basic Settings
 Bank Area  Set Up Number Ranges for IHC Payment Orders
.C
ha
lla
Transaction Code: IHCN3
1.18 Maintain Number Ranges Ext. Account Numbers
ty
a
The purpose of this activity is to create a number range for the IHC bank account
numbers, the central master data object in IHC
Ad
i
IMG Path Financial Supply Chain Management  In-House Cash  Basic Settings
 Bank Area  Maintain Number Ranges Ext. Account Numbers
Transaction Code: F9A5
23 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.19 Set +/- Sign Postings/GL Transfer/Name Check
Must specify whether the FI general ledger of the In-House Bank (IHB) and the bank
current accounts are in the same or separate systems. The G/L is located in the ERP
system of the headquarters
Ad
i
ty
a
.C
ha
lla
IMG Path Financial Supply Chain Management  In-House Cash  Basic Settings
 Basic Settings - Postings  Set +/- Sign Posting/GL Transfer/Name Check
1.20 Set Texts for Incoming / Outgoing Payments
Maintain texts in the language of the IHB. For every language you can define here
the abbreviation displayed and also the description for outgoing and incoming
payments. The way you set the indicator only influences the display form.
IMG Path Financial Supply Chain Management  In-House Cash  Basic Settings
 Basic Settings – Postings  Set Texts for Incoming / Outgoing Payments
24 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.21 Set Format for Payment Notes
Define format of payment notes for payment orders that are entered in the IHC.
ty
a
.C
ha
lla
IMG Path Financial Supply Chain Management  InBasic Settings –
Ad
i
1.22 Business Transaction Events / Event Control →
Create/Activate Partner
IMG Path Financial Supply Chain Management → In-House Cash → Basic Settings
→ Business Transaction Events / Event Control → Create/Activate Partner
Transaction Code: BF12
25 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
1.23 Define Partner Product
IMG Path Financial Supply Chain Management → In-House Cash → Basic Settings
→ Business Transaction Events / Event Control → Define Partner Product
Transaction Code: BF22
ha
lla
1.24 Define Function Modules (P/S) of a Partner
IMG Path Financial Supply Chain Management → In-House Cash → Basic Settings
→ Business Transaction Events / Event Control → Define Function Modules (P/S) of a
Partner
Ad
i
ty
a
.C
Transaction Code: BF32
1.25 Define Function Modules (Process) of a Partner
IMG Path Financial Supply Chain Management → In-House Cash → Basic Settings
→ Business Transaction Events / Event Control → Define Function Modules (Process)
of a Partner
Transaction Code: BF42
26 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
27 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
2 Business Configuration in the Headquarters
System: Master Data
2.1 Enter Basic Settings for Conditions
The purpose of this activity is to create basic settings for the conditions, including
calculation of interest income tax
Ad
i
ty
a
.C
ha
lla
IMG Path Financial Supply Chain Management → In-House Cash → Master Data →
Conditions → Enter Basic Settings for Conditions
2.2 Set Up Condition Areas
Several condition areas could be used to distinguish between fundamentally
different groups of subsidiaries. At least one condition area is needed.
IMG Path Financial Supply Chain Management → In-House Cash → Master Data →
Conditions → Set Up Condition Areas
28 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
2.3 Set up Transaction Types – Condition Calculation
The purpose of this activity is to define transaction types for condition related
transactions on IHC bank accounts. You can freely define the transaction types that
are to have transaction interest and transaction charges posted. In the next step you
assign the corresponding transaction type for each transaction for which transaction
interest or charges are to calculated, with which they are to be posted.
.C
ha
lla
IMG Path Financial Supply Chain Management → In-House Cash → Master Data →
Conditions → Set Up Transaction Types - Condition Calculation → Set Up Transaction
Types for Transaction Charge Posting
2.4 Transaction Types for Transaction Interest Posting
Ad
i
ty
a
IMG Path Financial Supply Chain Management  In-House Cash  Master Data
 Conditions  Set Up Transaction Types - Condition Calculation  Set Up
Transaction Types for Transaction Interest Posting
29 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
2.5 Setup Transaction Types for Direct Charge posting
2.6 Define Limit Categories
ha
lla
IMG Path Financial Supply Chain Management → In-House Cash → Master Data →
Conditions → Set Up Transaction Types - Condition Calculation → Set Up Transaction
Types for Direct Charge Posting
The standard limit categories 01 – 06 should be kept. Additional limit categories can
be defined, but for them to be functional, additional programming is required.
.C
In this section you define the categories of limits and also standard limits to which
you can relate when creating accounts.
Ad
i
ty
a
A limit that you assign to an account is always of a certain category. In the standard,
SAP differentiates the limit categories overdraft limit, internal and external
disposition limit. These limit categories control the cover check for the account
within payment transactions as well as balance-dependent conditions. Since the limit
categories are each linked to functionality, we recommend you do not change them.
Creating additional limit categories requires adding additional functionality.
You can also define standard limits to which you can relate when referring accounts.
IMG Path Financial Supply Chain Management  In-House Cash  Master Data
 Limits  Define Limit Categories
30 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
2.7 Define Account Locking Reasons
Create locking reasons for certain transactions of functions within the IHC
You use lock reasons to individually lock functions (defined for a product) for an
account.
You assign a lock reason with the functions, transaction types, and payment media
that are no longer to be used.
You can assign a function to more than one lock reason. Since you can assign an
account with more than one lock reason, the functions locked in the lock reasons can
also overlap.
Ad
i
ty
a
.C
ha
lla
IMG Path Financial Supply Chain Management  In-House Cash  Master Data
 Account  Define Account Locking Reasons
31 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
.C
2.8 Maintain Account Relationship Types
ty
a
The purpose of this step is to define relationship types in account hierarchies. Do not
change the standard types.
In this section you can set the different types for account hierarchies.
Ad
i
A hierarchy consists of a root account and any number of sub-accounts. You can then
assign any number of sub-accounts to each of these sub-accounts. You can set the
number of hierarchy levels for each hierarchy type. There is a restriction, however,
for interest compensation. In this case, the number is limited to 2 levels.
IMG Path Financial Supply Chain Management  In-House Cash  Master Data
 Account  Maintain Account Relationship Types
32 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
2.9 Maintain Dispatch Type for Bank Statements (Old)
The purpose of this activity is to maintain possible types of dispatch for bank
statements.
Define dispatch types for bank statements. You can make account-specific
assignments for these when you maintain the accounts.
The dispatch type you set is passed on to the bank statement interface at the same
time the bank statement is transferred. There must be an evaluation and operative
implementation of the indicator in the method responsible for printing the bank
statement.
ty
a
.C
ha
lla
IMG Path Financial Supply Chain Management → In-House Cash → Master Data →
Account → Maintain Dispatch Type for Bank Statements (Old)
Ad
i
3 Business Configuration in the Headquarters
System: Account Management
3.1 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.
Use different transaction types to distinguish transactions that should be treated
differently either in the IHB (for example, regarding charges, interest, or G/L) or in
the subsidiaries during bank statement processing.
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House Cash → Define Transaction Types
33 | P a g e
Aditya.Challa
.C
3.2 Define Clearing Partner
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
Ad
i
ty
a
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).
In this IMG activity you set up clearing partners to which you want to forward
external payment orders.
All payment orders for external recipients (the recipient's account is not in the same
bank area as the payer of the payment order) are forwarded to a clearing partner.
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House Cash → Define Clearing Partner
34 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
ha
lla
3.3 Maintain Transaction Types
In this step, you define BTC-transaction types. These are transaction types of the
payment ITEMS. Each payment order is associated with a transaction type like
INTPAY. The two payment items of each payment order are associated with the BTCtransaction types defined here.
Ad
i
ty
a
.C
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Basic Functions in Account Management → Maintain Transaction
Types
35 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
3.4 Maintaining Logical System for Headquarters (Transfer
from IHC -> FI)
Within SAP, a logical system is a client. Logical system names must be created and
assigned to the clients in an SAP system.
This maintenance is cross-client based; that is, you only need to perform it once in
each SAP system. If your logical system has already been created in one client, then
it is available in all other clients of this SAP system.
SAP Net weaver -> Application Server -> IDoc Interface / Application Link Enabling
(ALE) -> Basic Settings -> Logical Systems -> Define Logical System
Ad
i
ty
a
.C
ha
lla
Transaction Code: BD54
36 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
3.5 Port Maintenance
Tools -> ALE -> ALE Administration -> Runtime Settings -> Port Maintenance
ty
a
.C
ha
lla
Transaction Code: WE21
3.6 Maintain Partner Profiles
Ad
i
Tools -> ALE -> ALE Administration -> Runtime Settings -> Partner Profiles
Transaction Code: WE20
37 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
3.7 Define Logical system
SAP Netweaver -> Application Server -> IDoc Interface / Application Link Enabling
(ALE) -> Basic Settings -> Logical Systems -> Define Logical System
Transaction Code: BD54
38 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
3.8 Make Basic Settings for Payment Processes
.C
Process the basic settings for manual and automatic IHC payment orders:
Manually created IHC payment orders
Ad
i
ty
a
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 In-House
Cash are converted, and the converted payment order data is transferred to the
table for payment requests in Accounting.
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 of internal and external payment orders.
SAP In-House Cash transfers external payments to the table for payment requests in
FI and processes entries for the bank collection.
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House Cash → Make Basic Settings for
Payment Processes
39 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
40 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
41 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
42 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
3.9 Define Default Setting for Transaction Type
The purpose of this step is to manually enter payment orders in the IHB and to
define the default transaction type.
ha
lla
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House Cash → Define Default Setting for
Transaction Type
.C
3.10Define Transaction Type for Automatic Payments
These settings determine the transaction type of the payment order created in the
IHB for each payment method delivered in an incoming payment instruction.
Ad
i
ty
a
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House Cash → Define Transaction Type for
Automatic Payments
43 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
3.11Define Business Transaction Codes
Define IHB-specific Business transaction codes (BTC).
ty
a
.C
ha
lla
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Basic Functions in Account Management → Define Business
Transaction Codes
3.12Check – Maintain Transaction Types
Ad
i
A payment order within payment transactions consists of at least two payment items
- an ordering party item and one or more recipient items. A transaction type
characterizes the updating of such a payment item.
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Basic Functions in Account Management → Maintain Transaction
Types
44 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
3.13Maintain Authorization Groups
Authorization groups to control access to the account master and product. You also
need authorization groups to define amount-dependent authorizations.
Ad
i
ty
a
Transaction Code: F9AUTH
.C
IMG Path  SAP Banking → Customer Accounts → Authorization Management→
Maintain Authorization Groups
3.14Maintain Amount Limit/Principle of Dual Control for
Payment Order
IMG Path  Financial Supply Chain Management → In-House Cash → Authorization
Management → Amount-Dependent Authorizations → Maintain Amount
Limit/Principle of Dual Control for Payment Order
45 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
3.15Maintain Amount Limit/Principle of Dual Control for
Payment Item
ty
a
.C
ha
lla
IMG Path  Financial Supply Chain Management → In-House Cash → Authorization
Management → Amount-Dependent Authorizations
→ Maintain Amount
Limit/Principle of Dual Control for Payment Item
Ad
i
4 Business Configuration in the Headquarters
System: Customizing of other application
components
Financial Accounting (New)
For all external bank accounts used by the In-House Bank to make disbursements,
receive payments for subsidiaries or pool cash; specify the house banks and bank
accounts in the company code of the IHC legal entity.
4.1 Define Transaction Types for Incoming Payment
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House → Central Cash Receipt / Incoming
Bank Statements → Define Transaction Types for Incoming Payment
46 | P a g e
Aditya.Challa
4.2 Define House Banks
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
Define house bank for outgoing payments
IMG Path  Financial Accounting (New) → Bank Accounting → Bank Accounts →
Define House Banks
Ad
i
ty
a
.C
Transaction Code: FI12
IMG Path  Financial Accounting (New) → Bank Accounting → Bank Accounts →
Define House Banks
Transaction Code: FI12
47 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
4.3 Bank Determination for Payment Transaction
In this activity, you make settings that the payment program uses to select the banks
or bank accounts from which payment is to be made. You define the following:

Ad
i
ty
a
.C
Ranking order of banks
You specify which house banks are permitted and rank them in a list.
 Bank accounts
For each house bank and payment method (and currency, if required), you
specify which bank account is to be used for payments.
 Available amounts
For each account at a house bank, you enter the amounts that are available for the
payment run. You enter separate amounts for incoming and outgoing payments.
Specifying available amounts enables you to control which bank account is to be
used for payments. You can specify the amounts depending on the value date at the
bank.
IMG Path  Financial Accounting (New) → Accounts Receivable and Accounts
Payable → Business Transaction → Outgoing Payments → Automatic Outgoing
Payments → Payment Method/Bank Selection for Payment Program → Set Up Bank
Determination for Payment Transactions
48 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
.C
4.4 Set Up Creation of Payment Requests for Inbound IDoc in FI
Determine how external payments should be processed by each clearing partner.
ty
a
In this activity you enter all settings for creating FI payment requests if incoming
payment IDocs are forwarded from an IHC Center to FI for external payment with the
F111 payment program.
Ad
i
IMG Path  Financial Supply Chain Management → 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
49 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
4.5 Set Up Account Determination for Incoming Payment
Determine how the bank statement containing transactions for subsidiaries are
posted in the IHC.
In this IMG activity you specify the FI account and In-House Cash Center to which you
want to post the inbound bank statement.
You also define a header account for payments for which the system was unable to
automatically determine a recipient
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House → Central Cash Receipt / Incoming
Bank Statements → IHC Account Determination from External Bank Account
50 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
4.6 Bank Clearing Account Determination
ha
lla
Define the bank sub-accounts to be posted to in the general ledger for payment
transactions with bank accounts. The accounts are specified by house bank account,
payment method and currency. If a currency is not specified, the account applies to
all currencies.
Ad
i
ty
a
.C
IMG Path  Financial Accounting(New) → Bank Accounting → Business Transaction
→ Payment Transaction → Payment Handling → Bank Clearing Account
Determination → Define Account Determination
4.7 Assign Offsetting Transaction Types
In this step, you define corresponding pairs of BTC-transaction types.
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Basic Functions in Account Management → Assign Offsetting
Transaction Types.
51 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
4.8 Maintain Media and Payment Method
.C
The purpose of this activity is to define payment media and methods.
Ad
i
ty
a
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Basic Functions in Account Management → Maintain Media /
Payment Method
52 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
4.9 Maintain Note Dialog Box for Payment Transaction Locks
Define whether blocks should be checked
ha
lla
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Payment Processes in In-House Cash →Basic Functions in Account
Management → Maintain Note Dialog Box for Payment Transaction Locks
.C
4.10Maintain Accounts for Payment Transactions
Per bank area and currency you must specify one of each account. Define a technical
IHB account for clearing and a technical IHB account for CpD (Suspense).
Ad
i
ty
a
IMG Path Financial Supply Chain Management → In-House Cash → Account
Management → Maintain Accounts for Payment Transactions
53 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
4.11Assign Return Reasons and Return Transaction Types
Define Reasons for returns and assign to returned transaction types
ty
a
.C
ha
lla
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Returns → Assign Return Reasons and Return Transaction Types
Ad
i
4.12Tolerance Days for Forward Order
Enter the number of days in the future for which a payment order can be created.
IMG Path  Financial Supply Chain Management → In-House Cash → Account
Management → Default Values → Tolerance Days for Forward Order
54 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
5 Business Configuration in the Headquarters
System: General Ledger Transfer
5.1 Maintain GL Variants
ha
lla
In this step, you make basic settings for the G/L-variant, for example, which posting
keys should be used in FI.
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.
Ad
i
ty
a
.C
IMG Path  Financial Supply Chain Management → In-House Cash → Periodic Tasks
→ General Ledger Transfer → Maintain GL Variants
5.2 Maintain GL Transaction
Define GL Transactions used per GL variant.
IMG Path Financial Supply Chain Management → In-House Cash → Periodic Tasks →
General Ledger Transfer → Maintain GL Transaction
55 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
5.3 Assign Transaction Type for Payment Transaction to GL
Operation
BCA transaction types need to be assigned to GL transactions to define the
systematic of GL account determination. Keep the standard settings and amend for
any additionally defined transaction types.
ty
a
.C
ha
lla
IMG Path Financial Supply Chain Management → In-House Cash → Periodic Tasks
→ General Ledger Transfer → Assign Transaction Type for Payment Transaction to
GL Operation
5.4 Maintain GL Group
Ad
i
IHC accounts can be assigned to different G/L groups according on how their G/L
account determination during the FI transfer should be.
We use two different G/L groups for ordinary IHC accounts and technical IHC
accounts.
IMG Path Financial Supply Chain Management → In-House Cash → Periodic Tasks
→ General Ledger Transfer → Maintain GL Group
56 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
5.5 Transfer Postings Payables/Receivables
For those transactions that require credit and debit postings on separate GL
accounts these separate account have to be specified here.
The balance of an account first transferred to a clearing account (clearing account
general ledger) is then transferred to the appropriate receivables/payables account,
depending on +/- sign. These accounts can be specified separately for every clearing
account. Netting of accounts is taken into consideration.
ty
a
.C
ha
lla
IMG Path Financial Supply Chain Management → In-House Cash → Periodic Tasks
→ General Ledger Transfer → Transfer Postings Payables/Receivables
Ad
i
5.6 Define GL Account Assignment: Current Accounts
In this section you define which accounts are to be posted to first when the current
account system items are transferred to the general ledger. You can make these
entries depending on the general ledger group, the general ledger transaction and
the account currency.
Use this table to determine for any kind of IHC account (G/L Group) and kind of
transaction (G/L Transaction) to which FI G/L-accounts the IHC-transactions should
be posted during general ledger transfer.
IMG Path Financial Supply Chain Management → In-House Cash → Periodic Tasks
→ General Ledger Transfer → Define GL Account Assignment: Current Accounts
57 | P a g e
Aditya.Challa
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
5.7 Specify Sequence of Mass Processing
Ad
i
One or several chains of reports can be defined, that alternatively can be executed
during the daily end-of-day processing. Only 1 chain is defined here.
You can call this process with transaction F9N11: “End-of-Day Processing”
Transaction Code: SE38
58 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
In-House Cash Business Configuration in the Subsidiaries System
6 Business Configuration in the Subsidiaries System:
Basic Settings
6.1 Create Accounts
Specify the account number of the G/L account on which the payment amount
should be posted.
ha
lla
SAP Menu Path  Accounting → Financial Accounting → General Ledger → Master
Records → G/L Accounts → Individual Processing → Centrally
Ad
i
ty
a
.C
Transaction Code: FS00
59 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
6.2 Classify G/L Accounts for Document Splitting
.C
Each business transaction that is entered is analyzed during the document splitting
procedure. In this analysis, the system determines for each line item whether it is an
item that remains unchanged or an item that should be split.
ty
a
In order that document splitting recognizes how the individual document items are
to be handled, you need to classify them. You do this by assigning them to an item
category. The item category is determined by the account number
Ad
i
IMG Path  Financial Accounting (New) → General Ledger Accounting (New) →
Business Transaction → Document Splitting → Classify G/L for Document Splitting
60 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
6.3 Set up Payment Method in subsidiary
6.3.1
Set Up All Company Codes for Payment Transaction
Ad
i
ty
a
.C
ha
lla
IMG Path  Financial Accounting (New) → Accounts Receivable and Accounts
Payable → Business Transaction → Outgoing Payments → Automatic Outgoing
Payments → Payment Method/Bank Selection for Payment Program → Set Up All
Company Codes for Payment Transaction
6.3.2
Set Up Paying Company Codes for Payment
Transactions
Path  Financial Accounting (New) → Accounts Receivable and Accounts Payable →
Business Transaction → Outgoing Payments → Automatic Outgoing Payments →
Payment Method/Bank Selection for Payment Program → Set Up Paying Company
Codes for Payment Transactions
61 | P a g e
Aditya.Challa
6.3.3
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
Set Up Payment Methods per Country for Payments
Transaction
Path  Financial Accounting (New) → Accounts Receivable and Accounts Payable →
Business Transaction → Outgoing Payments → Automatic Outgoing Payments →
Payment Method/Bank Selection for Payment Program → Set Up Payment Methods
per Country for Payments Transaction
62 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
Set Up Payment Methods per Company Code for
Payments Transaction
ha
lla
6.3.4
Ad
i
ty
a
.C
Path  Financial Accounting (New) → Accounts Receivable and Accounts Payable →
Business Transaction → Outgoing Payments → Automatic Outgoing Payments →
Payment Method/Bank Selection for Payment Program → Set Up Payment Methods
per Company Code for Payments Transaction
6.4 Define House Banks
The IHC must be setup as a house bank in the company code of the subsidiary. All
IHC accounts that the subsidiary holds with the IHC must also be entered here.
Path  Financial Accounting (New) → Bank Accounting → Bank Accounts → Define
House Banks
63 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
Ad
i
ty
a
.C
ha
lla
Transaction Code: FI12
6.4.1
Set Up Bank Determination for Payment Transactions
Path  Financial Accounting (New) → Accounts Receivable and Accounts Payable →
Business Transaction → Outgoing Payments → Automatic Outgoing Payments →
Payment Method/Bank Selection for Payment Program → Set Up Bank
Determination for Payment Transactions
64 | P a g e
Aditya.Challa
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
ty
a
6.5 Global Settings for Electronic Bank Statements
Ad
i
The processing of electronic bank statements needs to be setup for the IHC bank
account as well like for any other bank account. The subsidiary will receive electronic
bank statements in FINSTA IDOC format from the IHC.
In this activity you make the global settings for the account statement. There are
four main steps to be carried out:
Create account symbol. 2. Assign accounts to account symbol. 3. Create keys for
posting rules and 4. Create a transaction type.
Path  Financial Accounting (New) → Bank Accounting → Business Transactions →
Payment Transactions → Electronic Bank Statement → Make Global Settings for
Electronic Bank Statement
65 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
66 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
67 | P a g e
Aditya.Challa
Ad
i
ty
a
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
68 | P a g e
Aditya.Challa
FSCM – IN-House Cash Center – Configuration Document – EC1
6.6 Create Vendor – Subsidiary
You must create vendors for all external deliveries or payments.
Path  Accounting  Financial Accounting  Accounts Payable  Master Records
 Create
Ad
i
ty
a
.C
ha
lla
Transaction Code: FK01
69 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
7 Configuring Component-Specific Master Data
.C
7.1 Create Variant for Payment Run F110
Ad
i
ty
a
For the payment runs (transaction code F110) that are used to make internal
payments to other subsidiaries, create a variant for the payment program
(RFFOEDI1) used in the subsidiary system.
This variant selects the paying company codes, for example, 1010, and the payment
method 3 for internal payments, 4 for external payments via the IHC. Also check the
Generate SAP IDOC box.
Transaction Code: SA38
Choose Execute.
On the Internal Payment Medium – Payment Orders by EDI screen make
following entries:
70 | P a g e
Aditya.Challa
.C
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
ty
a
8 Configuring Component-Specific Master Data –
Headquarters 8.1 Create Variant for Payment Run F111 – External Payments
Ad
i
Transaction Code: SA38
On the ABAP: Program Execution screen make the following entry:
Choose Execute.
On the Internal Payment Medium – Payment Orders by EDI screen make
following entries:
71 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
.C
8.2 Create Variant for Payment Run F111 – Check Payments
ty
a
For the payment runs (transaction code F111) that are used to make payments to
the House Bank, create a variant for the payment medium program (RFFOEDI1) used
in the headquarter system.
Transaction Code: SA38
Ad
i
On the ABAP: Program Execution screen make the following entry:
Choose Execute.
On the view Internal Payment Medium – Check (without check management)
screen make following entries:
72 | P a g e
Aditya.Challa
ha
lla
FSCM – IN-House Cash Center – Configuration Document – EC1
.C
8.3 Classify G/L Accounts for Document Splitting in
Headquarters System.
ty
a
Each business transaction that is entered is analyzed during the document splitting
procedure. In this analysis, the system determines for each line item whether it is an
item that remains unchanged or an item that should be split.
Ad
i
In order that document splitting recognizes how the individual document items are
to be handled, you need to classify them. You do this by assigning them to an item
category. The item category is determined by the account number
IMG Path  Financial Accounting (New) → General Ledger Accounting (New) →
Business Transaction → Document Splitting → Classify G/L for Document Splitting
73 | P a g e
Aditya.Challa