Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-IHC (Application Component) FSCM In-House Cash⤷
FIN_IHC (Package) Payment Order In-House Cash
IMG Activity
| ID | IHC_MAIN_CUST | Make Basic Settings for Payment Processes |
| Transaction Code | S_PLN_62000243 | (empty) |
| Created on | 20040301 | |
| Customizing Attributes | IHC_FIHBO | Maintain IHC reference number for pairing cross-company code documents |
| Customizing Activity | IHC_MAIN_CUST_OB | Make Basic Settings for Payment Processes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | IHC_MAIN_CUST_DC |
Use
In this IMG activity you make bank-area-dependent settings.
Requirements
Standard settings
Activities
Processing Transaction Types in Bank Area
Here you specify which transaction types are allowed in a bank area and how you want to post them:
If a transaction type is not available here, it cannot be selected or used when a payment order is created in a bank area.
Correspondingly, the system cannot process an IDoc if the transaction type used for the inbound IDoc has not been defined for each bank area to which a posting is to be made.
Settlement Accounts
Here you define the following accounts:
- Current accounts for provisional postings
- Settlement accounts for provisional and final postings
Note that the entries for final postings are only logical in combination with the settlement posting type.
The transaction type and business partner fields are optional. This lets you further differentiate between the accounts you want to post to. If you differentiate by transaction type, ensure that credit/debit indicator corresponds to the transaction type attributes.
Always define the settlement and provisional accounts in the currency of the current accounts that will be posted to finally.
Posting Data
Define the posting parameters here that the system needs in order to post the current account items. The transaction type field is optional. Make sure that the transaction type and the credit/debit indicator match.
Settlement Rates
In the case of a currency conversion, the exchange rate type you enter here is used to calculate the amounts for posting to the current accounts and the settlement amounts for posting to the current account system. If there is a currency conversion for debit items, the selling rate is transferred, and the buying rate is transferred if the currency is converted for a credit item.
The secondary rates are rates used to calculate the payer or offsetting account item. The system uses the difference between the primary and secondary rates to calculate the settlement items.
The clearing partner field is optional. In the case of external payments, you can use this field to define rate types based on the clearing partner.
Accounts for Clearing Partner
Enter current accounts for each clearing partner here for clearing payment orders that have been forwarded. Postings are made to these offsetting accounts when payment orders are forwarded to a clearing partner for external payments.
Offsetting accounts must be created for each clearing partner and currency in which payment orders should be forwarded to the clearing partner. You can also define different accounts for the different settlement categories.
Payment Method Data
You define the payment method here which will be contained in the outbound IDoc to a certain clearing partner.
If no suitable entry is found for an outbound IDoc, the system forwards the original payment method and payment method supplement as contained in the inbound IDoc.
You can also define the payment method in the outbound IDoc for manual payments. Enter a transaction type for manual payments and leave the delivered payment method field empty.
Communication Data
Enter the parameters for communication between an IDoc and a clearing partner here. Define the following parameters for each currency in which you want to forward payment orders to a clearing partner:
- Communication parameters for sending IDocs with ALE:
- Partner type of the recipient
- Partner number of the recipient
- Message code
- Message function
When the outbound IDoc (with which a payment order is forwarded to a clearing partner) is generated, these values are transferred to the control record. They are required for sending the IDoc and for correct inbound processing in the recipient system. The message code and message function fields are optional and their values are freely definable. However, they must correspond to the entries in the partner profile applying to inbound IDocs in the recipient system. This lets you determine whether the recipient should process the inbound IDoc as an incoming IHC payment for cross bank area payments (transaction code PEXN) or as an incoming FI payment for external payments with payment program F111 (transaction code PEXC).
- Posting parameters:
- Bank country
- Bank key
- Account Number
These account details are written to the outbound IDoc as the sender bank details and are used to identify the sender in the recipient system.
To carry out cross bank area payments, a sender account must be entered here in the recipients SAP In-House Cash component. This account must correspond to an account in the current account system of the recipient IHC bank area.
For carrying out external payments in the FI of the recipient, account details must be entered here (any but they must be unique) for identifying the sender when the Inbound IDoc is processed in the recipient system.
In order to be able to identify the IDoc sender and process the IDoc in the recipient system the following must apply: The account must correspond to the account details of the clearing partner entered in the recipient system for processing inbound IDocs. You can find the account details in the Set Up Creation of Payment Requests for Inbound IDoc in FI activity. The bank details entered are only used for internal identification and can be selected at your discretion. They do not have to represent a real bank account.
By selecting different account details, payment requests can be created in different company codes in the recipient system.
Route
Enter the recipient (clearing partner) to which the system should forward an external or cross-bank-area payment as an IDoc.
Example
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IHC_VC_CL | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20040301 |
| SAP Release Created in | 500 |
