Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-BCA (Application Component) Bank Customer Accounts⤷
FKB (Package) Bank Customer Accounts: Central Objects
IMG Activity
| ID | SIMG_BA-CA-V_TBKKG3 | Maintain Transaction Types |
| Transaction Code | S_KK4_13000100 | IMG Activity: SIMG_BA-CA-V_TBKKG3 |
| Created on | 19990830 | |
| Customizing Attributes | SIMG_BA-CA-V_TBKKG3 | Maintain Transaction Types |
| Customizing Activity | SIMG_BA-CA-V_TBKKG3 | Maintain Transaction Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_BA-CA-V_TBKKG3 |
In this section you set the transaction types relevant for payment transactions.
Structure
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.
Example
Transaction types can be: debit memo, credit memo, returned debit memo, cash deposit, cash payment, and so on.
For each of these transaction types you can specify
- what checks are carried out before the item is updated. This is with regard to the business partner check, the check for the permitted functionalities/blocks of the account, the limit check, the check of a specified value date and checks to see if collection authorizations, direct debit orders or check blocks exist.
- if the transaction type represents a credit or a debit.
- if updating should take place subject to final payment.
- on what position type the transaction type is based, and if any guaranteed amounts (e.g. Eurochecks) apply.
- if reversing or value date specification is possible.
- if an item should receive priority for post processing.
- if online entry is possible for the transaction type.
- to what business transaction code the transaction type corresponds.
Standard settings
SAP supplies pre-configured transaction types. We recommend you review these and adapt them to suit your requirements.
Recommendation
Identify the transaction types needed using the following criteria:
- the transaction types you need in payment transactions. These must be reconciled with the transaction types (for example, in the case of EFT, the text key and text key enhancements) you use in your payment transaction system.
- the transaction types you use for internal purposes (interest and charge updating, and so on).
- the transaction types needed for updating an account balancing.
- the corresponding offsetting transaction types (for example, credit - debit and return transaction types.
In doing so, note that transaction types are defined cross bank area.
According to agreegments concercing bank transfer transactions, there must be an account number check and name comparison at the bank acting as end beneficiary for single transfers (German regulation). However, these checks are only relevant for certain transaction types and for recipient postings. By using an attribute you can control if such an account number check and name check is to be carried out for the transaction type.
To do this, select the indicator 'Account call check'.
You define the variants for the name check with the business partner. The names are saved per business partner and in this area you can also display and maintain them. The check is carried out using Business Transaction Event (BTE 00011600). Using the account number, this event reads the name of the account holder and the authorized drawers assigned to the account. Then the system compares the names with the names in the payment item. If they concur, the system posts the item, if they do not, the item is transferred to post processing.
Activities
Define all transaction types you need.
Further notes
The transaction types needed are usually displayed in the previous payment transaction system under text key enhancements. The conversion of text keys to the corresponding transaction types must take place in the payment transaction system. This must then transfer the appropriate transaction types to the SAP system.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_BA-CA-V_TBKKG3 | 0 | I310005601 O | |
| SIMG | SIMG_BA-CA-V_TBKKG3 | 1 | KFM0000005 | FSCM In-House Cash |
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 |
| V_TBKKG3 | V - View | SM30 | 0000000000 | Maintain Transaction Types |
History
| Last changed by/on | SAP | 20000723 |
| SAP Release Created in |
