Hierarchy
⤷ IS-B-BCA (Application Component) Bank Customer Accounts
⤷ FKB (Package) Bank Customer Accounts: Central Objects
IMG Activity
ID | SIMG_BA-CA-KCLL | Define Sender Structure |
Transaction Code | S_KK4_13000118 | IMG Activity: SIMG_BA-CA-KCLL |
Created on | 19990830 | |
Customizing Attributes | SIMG_BA-CA-KCLL | Define Sender Structure |
Customizing Activity | SIMG_BA-CA-KCLL | Define Sender Structure |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_BA-CA-KCLL |
In this section you set the sender structure you want your transfer program to use. The sender structure describes the structure of the data which are to be imported from another system into the SAP system.
The data from the external system such as account master data, balances, standing orders, and items are saved to an ASCII file. The SAP system reads the data using the sender structure and transfers it to the receiver structure. From the receiver structure, the data is directed to the appropriate application, for example, to the account. The data is checked and saved within the application. You can read about this process in a log after it takes place.
The SAP system automatically proposes a sender structure appropriate to the receiver structure. All fields are purely defined as character fields, and sorted alphabetically. You can change this should the need arise.
Example
Requirements
Standard settings
Recommendation
We recommend that you leave the sender structure similar to that of the receiver structure, and make the necessary adjustments for the transfer of the data from the external system to the ASCII file.
Activities
- Choose NEW ENTRIES to create a new sender structure.
- Assign the sender structure a short description and a real name.
- If there is a structure in the ABAP Dictionary which has a similar structure to the sender structure to be maintained, you can enter this ABAP Dictionary structure in "Template Table".
- Set the TRANSFERTYPE for the sender structure. Each type of data which can be transferred has its own transfer type. The transfer type determines the receiver structure and the technical communication between the transfer program and the application. The following transfer types are relevant for bank customer accounts (BCA):
- 70 - BCA account balances (structure IBKKBADIEX)
- 71 - BCA account items (structure IBKKITDIEX)
- 72 - BCA account master data (structure IBKK_DI_AC) with deposit banking (see comment 1)
- 74 - BCA account standing order (structure IBKKSO_DI_SO)
- 75 - BCA account balancing (structure IBKK9_DI1)
- Enter the data dictionary structure in the table below.
- Under 'Item' enter '1'. Because you will only use a dictionary structure in your sender structure, you can ignore the other items in this area.
- Choose the name of the Data Dictionary structure (DDIC). The name must begin with RKCT, and you must add exactly three other characters, for example RKTCA01.
- Mark the line and go to the detail display of the given structure by clicking on the magnifying glass icon.
- From the menu, choose Sender structure -> Include template. (if you get a deletion message, choose continue)
- Check the data type of the structure. Make sure that under 'Type', you only use character types (C). If there are still packed types (P) in your sender structure, change them as follows:
- Delete the table name of the send field.
- Choose Continue.
- Replace "P 9 2" with "C 25 0".
- Leave the table field empty, otherwise the packed data will be used.
- Save your entries.
Note
Comment 1 (regarding transfer type 72)
The structure IBKK_DI_AC has been extended for deposit banking.
The old data transfer takes place in two steps, using two different files:
- Activity category 01, create account
- Activity category 02, change account and account status active (0010) for deposit banking.
Further notes
Check in the Data Dictionary that the structure RKCTxxx is present and aktiviert wurde.
Business Attributes
ASAP Roadmap ID | 152 | Design data acquisition |
Mandatory / Optional | 2 | Optional 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-KCLL | 0 | I310005621 | Periodic Tasks |
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 |
KCLL | T - Individual transaction object | KCLL | BACA01 | Generate Sender Structure |
History
Last changed by/on | SAP | 20020128 |
SAP Release Created in |