Hierarchy
⤷ FI-LOC (Application Component) Localization
⤷ ID-FI-EPIC-BACOM-BL (Package) Globalization: E-Payment Int. Bank Comm. Business Logic
IMG Activity
ID | EPIC_C_BCTV | Define Bank Communication Types |
Transaction Code | S_VBS_01000011 | (empty) |
Created on | 20111110 | |
Customizing Attributes | EPIC_C_BCTV | Define Bank Communication Types |
Customizing Activity | EPIC_C_BCTV | Define Bank Communication Types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | EPIC_C_BCTV |
Use
To allow your users to communicate with your house banks, you have to decide which types of information you want to send to your banks and what you want to do with the responses. You have to decide which types of bank communication you want to implement. After you have implemented the necessary ABAP repository objects to make each type of bank communication for each bank possible, you assign a three-digit code to each bank communication type.
In this Customizing activity, you enter these codes and their descriptions. You also assign a usage category to each type of bank communication. The usage category determines where the communication is triggered on the Electronic Payment Integration (China) screen. For more information about the usage categories, see the field help in the Customizing view.
Requirements
For a list of the necessary ABAP repository objects, see Prerequisites for the Customizing for Electronic Payment Integration.
Standard settings
Activities
Example
You want to get the following kinds of information from your bank:
- Balance of your house bank accounts
- Changes to the status of items for payment that have been sent to the bank
- Details about the different transactions that were carried out for your house banks during a certain period of time.
To implement these three types of bank communication, you enter the following in this Customizing activity:
- 010 as the code, Get account balance as the description, and Standard (Dialog) as the usage category
- 020 as the code, Get payment status as the description, and Dialog and Payment Item Specific Query as the usage category
- 030 as the code, Get transaction details as the description, and Standard (Dialog) as the usage category
Your users can then trigger these types of communication as follows:
- All types can be triggered from the Query Bank tab page
- Queries about the payment status can also be triggered from the Process Items tab page
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_BCTV | CN | China |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | EPIC_C_BCTV | 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_BCTV | V - View | SM30 |
History
Last changed by/on | SAP | 20111110 |
SAP Release Created in | 607 |