Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-LOC (Application Component) Localization⤷
ID-FI-EPIC-BACOM-BL (Package) Globalization: E-Payment Int. Bank Comm. Business Logic
IMG Activity
| ID | EPIC_C_BCDV | Define Bank Communication Details |
| Transaction Code | S_VBS_01000012 | (empty) |
| Created on | 20111110 | |
| Customizing Attributes | EPIC_C_BCDV | Define Bank Communication Details |
| Customizing Activity | EPIC_C_BCDV | Define Bank Communication Details |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | EPIC_C_BCDV |
Use
After you determine which bank communication types that you want to enable in the system, you enter the ABAP repository objects that you have created for each bank communication type in this Customizing activity. You assign, as needed, the following for each combination of company code, house bank, bank account, and bank communication type:
- Structure with dialog parameters
- Structure with (other) parameters. Note that you only need to enter this structure if the communication has to also be triggered from a tab page other than the Query Bank tab page. This is the case, for example, for queries about the status of items to be paid.
- Structure for output table
- Structure for other results
- Implementing class
You can also determine which bank communication client that your SAP ERP system uses to communicate for each bank communication type by entering the RFC destination that should be used for the client.
Your SAP ERP system usually uses the Unicode character set UTF-8 to encode the messages that you send to the bank. If your bank requires a different encoding character set, enter the correct encoding value in the corresponding field for the respective bank communication types.
Note:
If the technical settings of your bank require that a bank communication comprises more than one step, that is, more than one pair of request and response messages, make the necessary settings for the following fields for the multiple steps in the Define Bank Communication Steps Customizing activity:
- RFC destination
- Encoding character set
- Logon user, if needed for your implementation of the request message
Then you can leave these fields for the multi-step bank communication types empty in this Customizing activity. The settings made in the Define Bank Communication Steps Customizing activity overrule any settings that you make here.
Requirements
You have defined the bank communication types that you want to use for each house bank in the Define Bank Communication Types Customizing activity.
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| EPIC_C_BCDV | CN | China |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | EPIC_C_BCDV | 0 | HLA0009204 | Accounts Payable |
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 |
| EPIC_C_BCDV | V - View | SM30 |
History
| Last changed by/on | SAP | 20111110 |
| SAP Release Created in | 607 |
