Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 3

11/8/2019
SAP In-House Cash (FIN-FSCM-IHC)

Generated on: 2019-11-08
SAP ERP | 6.0 EHP8 SP13
PUBLIC
Original content: https://help.sap.com/viewer/da5ab0fa48b34143a25d0e08448f5219/6.18.13/en-US
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/viewer/disclaimer.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=22067557&topics=6deec5536a51204be10000000a1… 1/39
11/8/2019
Interfaces of Bank Customer Accounts

In this documentation, you nd all the interfaces used in SAP Bank Customer Accounts (BCA) . Some parts of the current
account system are also used by In House Cash (IHC) . The terminology used in the documentation has been adapted
accordingly. The interfaces described for standing order, check, externally initiated payment transactions and direct input are only
relevant for BCA.
You nd the interfaces listed in accordance with their technical special features, meaning that all RFC interfaces, Business
Transaction Events and direct input structures are summarized as such. At the beginning of the sub-chapters on RFC interfaces
and Business Transaction Events you can nd respective overview chapters in which the interfaces are arranged according to
processes.
Caution
Update discontinued
The lists of parameters and of structure objects were not updated in the descriptions of the individual interfaces. Use the
current data in the system.
RFC Interfaces
11/8/2019
De nition
A Remote Function Call is a programming interface by means of which you can access the business data and processes of the SAP
System from another application system.
Use and integration

You can nd information on how the RFC interface functions, what functions it offers and what the technical requirements are for
RFC for SAP and external systems for all currently supported platforms by choosing Components of SAP Communication
Technology .
Overview of the RFC Interfaces

This function enables you to call up interfaces from a system outside of Bank Customer Accounts (BCA) by using RFC-enabled
function modules.
The following tables list the RFC-enabled function modules in BCA.
Note
For more information about the function modules, see the documentation for the interfaces in transaction SE37.
Account Information
Name of Function Module Technical Name of Function Module
Get account list for bank keys BAPI_BANKACCT_GET_LIST_ALL
Get account list for business partner BAPI_BANKACCT_GET_LIST
Query detail data for account BAPI_BANKACCT_GET_DETAIL
Get a business partner for an account BAPI_BANKACCT_GET_BUPA
Query an account hierarchy BAPI_BANKACCT_GET_HIERARCHY
Account balance list for business partner BKK_RFC_BANKACCNT_GET_BALANCE
Get payment items for an account BAPI_BKK_ACCNT_GET_ITEM_LIST
Get root accounts for a hierarchy BAPI_BANKACCT_GET_ROOTACCOUNTS
Business Partner Information
Get total commitment of a business partner in BCA BAPI_BKK_TC_GET_LIST
Get business partner addresses for an account BKK_RFC_ACCNT_GET_PARTNER_ADDR
Calculating Conditions
11/8/2019
Continue condition calculation after interest income tax BAPI_COND_ CALC _AFTER_WHTAX
Update dispatch expense counter BAPI_COND_FORW_EXPENSES_COUNT
Get account balancing detail data BAPI_COND_CLOSE_ GET _ DATA
Account Actions
Create an account BAPI_BKK_ACCNT_CREATE
Simpli ed account creation BAPI_BKK_ACCNT_CREATE_EASY
Change an account BAPI_BKK_ACCNT_CHANGE
Close an account BAPI_BKK_ACCNT_CLOSURE
Get available amount of an account BAPI_BKK_ACCNT_GET_AV_AMOUNT
Get account balance BAPI_BKK_ACCNT_GET_BALANCE
Get account details BAPI_BKK_ACCNT_GET_DETAIL
Get payment items for an account BAPI_BKK_ACCNT_GET_ITEM_LIST
Get list of accounts for a business partner BAPI_BKK_ACCNT_GET_LIST
Product Information
Get product details BAPI_BKK_PROD_GET_DETAIL
Account Turnover Information
Query account turnovers BAPI_PAYM_ITEM_GET_LIST
Turnovers displayed by selection criteria BKK_RFC_ITEM_GET_LIST
Withdrawal Amounts and Special Revenue Allowance Amounts
Transfer withdrawal amounts and special revenue allowance BKK_FA_RFC_SET

amounts
Account Balances
Posting balance BAPI_COND_POST_DECRE_BALANCES
11/8/2019
Find posting turnovers and balances also for root accounts in BKK_RFC_COND_POST_DECRE_ BAL _HY
interest compensation
Value date balance BAPI_COND_ VAL _DECRE_BALANCES
Find value date-based turnovers and value date balances also for BKK_RFC_COND_ VAL _DECRE_ BAL _HY
root accounts in interest compensation
Pool balances BAPI_COND_DECRE_ BAL _POOLS
Bank Statement
Initiate a bank statement BAPI_BANK_STATEMENT_EXEC
Create a bank statement duplicate BAPI_BANK_STATEMENT_ GET
Externally Initiated Payment Transactions
Post and check ordering party item BAPI_PAYIT_POST_SENDER
Post and check recipient item BAPI_PAYIT_POST_RECEIVER
Post and check routing item BAPI_PAYIT_POST_CLEARING
Post a turnover item BAPI_PAYIT_POST_ITEM
Post and check ordering party item BAPI_PAYM_ITEM_POST_SENDER
Post and check recipient item BAPI_PAYM_ITEM_POST_RECEIVER
Post and check routing item BAPI_PAYM_ITEM_POST_CLEARING
Post a turnover item BAPI_PAYM_ITEM_POST_ITEM
Prenotes
Create prenote BAPI_BKK_PRENOTE_CREATE
Change prenote BAPI_BKK_PRENOTE_CHANGE
Delete prenote BAPI_BKK_PRENOTE_DELETE
Display prenote detail BAPI_BKK_PRENOTE_GET_DETAIL
Display list of prenotes BAPI_BKK_PRENOTE_GET_LIST
Payment Order
Post a payment order BKK_RFC_PAYM_ORDER_POST
11/8/2019
Check an ordering party item BKK_RFC_SND_ACCNT_CHCK
Check bank details BKK_RFC_CHCK_ACCNT
Forward Order
Change a forward order BAPI_BKK_FORWD_ORDER_CHANGE
Create a forward order BAPI_BKK_FORWD_ORDER_CREATE
Delete a forward order BAPI_BKK_FORWD_ORDER_DELETE
Get forward order details BAPI_BKK_FORWD_ORD_ GET _DETAIL
Get forward orders BAPI_BKK_FORWD_ORD_ GET _LIST
Standing Order
Create a standing order BAPI_BKK_STAND_ORDER_CREATE
Change a standing order BAPI_BKK_STAND_ORDER_CHANGE
Delete a standing order BAPI_BKK_STAND_ORDER_DELETE
Query all standing orders for an account BAPI_BKK_STAND_ORDER_GET_LIST
Display a standing order BAPI_BKK_STAND_ORDER_GET_DET
Create a standing order BAPI_STANDING_ORDER_CREATE
Change a standing order BAPI_STANDING_ORDER_CHANGE
Delete a standing order BAPI_STANDING_ORDER_DELETE
Display detail of a standing order BAPI_STANDING_ORDER_GET_DETAIL
Display all standing orders for an account BAPI_STANDING_ORDER_GET_LIST
Create a standing order BAPI_STANDING_ORDER_CREATE
Read product eld modi cations BAPI_BKK_STORFIELDMOD_GD
Check (Payment Form (PF)) Management
De ne checks in check (PF) management BAPI_CHEQUE_ORDER
Con rm print of check (PF) BKK_RFC_SET_STATE_ISSUED
BAPI for Transaction Commit *BAPI_BKK_TRANSACTION_COMMIT
BAPI for Transaction Rollback *BAPI_BKK_TRANSACTION_ROLLBACK
11/8/2019
General BAPIs
BAPI for Transaction Commit *BAPI_BKK_TRANSACTION_COMMIT
BAPI for Transaction Rollback *BAPI_BKK_TRANSACTION_ROLLBACK
Business Transaction Events

De nition
The business transaction eventis an event for which an SAP program extends the system without modi cation, depending on the
settings in Customizing.
Use
You use events to add individual functions to BCA. Events enable these additional functions without affecting the SAP
programming.
At the de ned event, data is transferred by the system by means of an interface to the function module. This can also pass data
back to BCA in accordance with a prede ned interface.
You can connect three types of additional components at every event:
SAP components
Function modules from software partners
Function modules developed by the customer Example
Before you save a new account master record, the system offers you the Determine General Ledger Group event. At this event you
can call up a separately developed function module that determines the general ledger group (for example, an industry) from
business partner data. Data transferred by means of the interface is entered in the appropriate eld on the account.
Structure
SAP provides sample function modules (called SAMPLES) for each event, which describe the interface and can be used as a
template for modules to be developed. To use a SAMPLE, copy it into your namespace and nish programming it.
Integration
P/S modules can be provided either by an SAP standard application, by an external software company, or you can create them
yourself. You activate or deactivate each function module in the Implementation Guide (IMG) for Bank Customer Accounts (BCA)
.
Conversion of the Events from Release 3.x to

4.x
Assignment of the processes
11/8/2019
Process up to 4.0A Process from 4.0A Short description
BITPO BKK_ITEM_POST Processing of payment items
BITRT BKK_ORDER_RETURN Return
BITAU BKK_ITEM_DIALOG Online editing of payment items
BPOPO BKK_ORDER_POST Processing of payment orders
BPOAU BKK_ORDER_DIALOG Online editing of payment orders
BBKST BKK_BANK_STATEMENT Bank statement
BCOMT BKK_CONDITION_MAINTAIN Edit conditions
BCLOS BKK_CLOSING Balancing
BCOCA BKK_CONDITION_CALCULATE Calculate condition
BCHEQ BKK_CHEQUE_NUMBER_CREATE Check management
BACCR BKK_ACCOUNT_CREATE Create account
BACDE BKK_ACCOUNT_DELETE Delete account
BGLFI BKK_GL_TRANSFER FI general ledger transfer
Assignment of the sample function modules
Event up to 4.0A Event from 4.0A Short description of the event
BITPO001 00010010 Ordering party item: Return result of post

processing
BITPO002 00010020 Planning/credit check: Formal check
BITPO003 00010021 Planning/credit check: Business partner
BITPO004 00010022 Planning/credit check: Account
BITPO005 00010023 Planning/credit check: Value date
BITPO006 00010024 Planning/credit check: Limit
BITPO010 00010030 Prepare data: Post
BITPO011 00010031 Prepare data: Park
BITPO012 00010032 Prepare data: Delete
BITPO013 00010033 Prepare data: Change
BITPO014 00010034 Prepare data: Release
BITPO015 00010035 Prepare data: Reverse
BITPO016 00010040 Data update: Terminate
BITPO017 00010036 Prepare data: Insert further items/positions
BITPO020 00010041 Data update: Execute
BITRT001 00010110 Returns: Noti cation
BITAU001 00010210 Payment item online: Authorization check
11/8/2019
BPOPO001 00010310 Payment order: Transfer data to

previous/feeder system
BPOAU001 00010410 Payment order online: Authorization check
BBKST001 00010510 Bank statement: Transfer data
BCLOS001 00010710 Balancing: End of mass run reached
BCOCA001 00010810 Capital yield tax (CYT): Transfer interest

data
BCOCA002 00010820 Condition determination: Transfer

differentiation value
BCOCA003 00010830 Balancing postings: Enter payment notes
BCOCA004 00010840 Balancing postings: Insert customer-de ned

items
BCHEQ001 00010910 Check number issuing: Request new

numbers
BCHEQ002 00010920 Check number issuing: Check for number

issued twice
BCHEQ003 00010950 Check (Cheque): Authorization check
BACCR001 00011010 Account master data: Account number

without check digit
BACCR002 00011020 Account master data: Transfer for new

creation
BACCR003 00011030 Account master data: Determine general

ledger group
BACCR004 00011011 Account master data: Account number with

check digit
BACDE001 00011110 Account master data: Transfer for deletion
BGLFI001 00011210 Account determination: Determine

additional key
BGLFI002 00011220 Data transfer: De ne if single transfer
BGLFI003 00011230 Business area: Determination
Messages in BTE Function Modules

Use
Within this function module, the output of any messages by means of ʻmessage’ or the transferring of a message to the message
handler is not allowed . Instead, table T_MESG must be entered. The contents of this table are then further processed by SAP
coding.
Table T_MESG (Structure IBKKMESG)
Field name Category Length Description
MSGTY CHAR 1 Category of the message (E;I, W,
11/8/2019
S, A)
ARBGB CHAR 20 Work area
TXTNR CHAR 3 Message number
MSGV1 CHAR 50 Message variable 1
Overview of the Business Transaction Events

Use
This function enables you to transfer data from Bank Customer Accounts (BCA) to external systems by using Business
Transaction Events (BTEs).
To use the BTEs, perform the following actions:
Create an appropriate function module with this interfacethat communicates with the system to be called up.
This means you need to copy the sample function module and add the required application logic (program part).
Enter the function module in the event table. For more information on the procedure for using function modules, see the
BCA Implementation Guide.
The following tables list the sample function modules for the interfaces and the BCA application process under which the event is
found in the system.
Note
For more information about the function modules, see the documentation for the interfaces in transaction SE37.
Payment Transactions
Payment Order
Function Module Name Technical Name and Process
Payment order: Check and change value dates SAMPLE_INTERFACE_00010120
Process: BKK_ORDER_POST
Include payment notes on payment orders and return orders SAMPLE_INTERFACE_00010121
Process: BKK_ORDER_DIALOG
Externally Initiated Payment Transactions
Function Module Name Technical Name of Function Module and Process
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=22067557&topics=6deec5536a51204be10000000a… 10/39
11/8/2019
Return the result of postprocessing of an ordering party SAMPLE_INTERFACE_00010010
Process: BKK_ITEM_POST
Internally Initiated Payment Transactions
Convert external account numbers with leading zeros SAMPLE_PROCESS_00011012
Transfer a payment order to payment transaction system SAMPLE_INTERFACE_00010310
Noti cation of deletion or reversal of a payment order SAMPLE_INTERFACE_00010320
Noti cation of returns SAMPLE_INTERFACE_00010110
Process: BKK_ORDER_RETURN
Create payment notes when taking the value date balances in the SAMPLE_INTERFACE_00011530
old account currency off the books.
Process: BKK_CURRENCY_EXCHANGE
Create payment notes when putting the value date balances in the SAMPLE_INTERFACE_00011531
new account currency on the books.
Checks During Posting of Payment Items
Prepare a payment item for the check SAMPLE_INTERFACE_00010020
Business partner check SAMPLE_INTERFACE_00010021
Account check SAMPLE_INTERFACE_00010022
Value date check SAMPLE_INTERFACE_00010023
Limit check SAMPLE_INTERFACE_00010024
Preparing to Post a Payment Item
Prepare posting SAMPLE_INTERFACE_00010030
11/8/2019
Prepare parking SAMPLE_INTERFACE_00010031
Prepare deletion SAMPLE_INTERFACE_00010032
Prepare change SAMPLE_INTERFACE_00010033
Prepare release SAMPLE_INTERFACE_00010034
Prepare reverse SAMPLE_INTERFACE_00010035
Prepare to post: Generate another payment item position SAMPLE_INTERFACE_00010036
Specifying the Language of a Posting Text
Payment transactions: language of posting text SAMPLE_INTERFACE_00010037
Updating or Deleting Prepared Payment Items
Delete all prepared payment items SAMPLE_INTERFACE_00010040
Update all prepared payment items SAMPLE_INTERFACE_00010041
Business Partner Check
Name comparison: Check the name of the BP against the alias table SAMPLE_INTERFACE_00011600
Process: BKK_CHECK_NAME
Bank Statement
Forward bank statement data SAMPLE_INTERFACE_00010510
Process: BKK_BANK_STATEMENT
11/8/2019
Event controlled bank statement SAMPLE_INTERFACE_00010038
Process:BKK_BANK_STATEMENT
Determine recipient of balance noti cation SAMPLE_INTERFACE_00012910
Process: BKK_BALANCE_NOTIFICATION
Forward balance noti cation data SAMPLE_INTERFACE_00012900
Process: BKK_BALANCE_NOTIFICATION
Tasks for Balancing

Control of End-of-Day Processing (main program, parallel processing)
End of a mass run reached SAMPLE_INTERFACE_00010710
Process: BKK_CLOSING
End of an end-of-day processing step SAMPLE_INTERFACE_00010720
Automatic restart of mass run for account balancing SAMPLE_INTERFACE_00010700
Correspondence
Fixing term agreement SAMPLE_INTERFACE_11035
Process: BKK_ACCOUNT_DIALOG
Creation or change of an account SAMPLE_INTERFACE_11060
Prenoti cation of term agreement maturity SAMPLE_INTERFACE_11036
Process: BKK_TERM
Calling term agreement SAMPLE_INTERFACE_11037
Process: BKK_TERM
Calculating Conditions
Transfer interest data for interest income tax calculation SAMPLE_INTERFACE_00010810
Process: BKK_CONDITION_CALCULATE
Determine the differentiation value SAMPLE_INTERFACE_00010820
11/8/2019
Fill the payment notes for balancing postings SAMPLE_INTERFACE_00010830
Balancing postings: Fill external payment notes SAMPLE_INTERFACE_00010831
Customer-de ned balancing postings SAMPLE_INTERFACE_00010840
Balancing: Dynamic balance calculation SAMPLE_INTERFACE_00010850
Balancing: Bonus relevance/calculation SAMPLE_INTERFACE_00010860
Select customer conditions SAMPLE_INTERFACE_00010610
Save customer conditions SAMPLE_INTERFACE_00010620
Display header information of customer conditions SAMPLE_INTERFACE_00010630
Display position information of customer conditions SAMPLE_INTERFACE_00010640
Check (Payment Form (PF)) Management
Request check (PF) numbers SAMPLE_INTERFACE_00010910
Process: BKK_CHEQUE_NUMBER_CREATE
Check for the existence of a check (PF) number SAMPLE_INTERFACE_00010920
Authorization check for checks (PF) SAMPLE_INTERFACE_00010950
Process: BKK_CHEQUE_DIALOG
Check stack management: Transfer check (cheque) data SAMPLE_INTERFACE_00010915
Check (cheque) lock noti cation SAMPLE_INTERFACE_00010960
Process: BKK_CHEQUE_DIALOG
Standing Order
Authorization check for standing orders entered from the dialog SAMPLE_INTERFACE_00010411
Process: BKK_STAND_ORDER_DIALOG
Calculate amount of standing order SAMPLE_INTERFACE_00011900
Process: BKK_STAND_ORDER_POST
11/8/2019
Create, change, delete a standing order: Customer-speci c SAMPLE_INTERFACE_00012000.

enhancements
Process: BKK_STAND_ORDER_DIALOG
Account Master Data

Creating an Account
Determine account number without check digit SAMPLE_INTERFACE_00011010
Process: BKK_ACCOUNT_CREATE
Determine account number (with check digit) SAMPLE_INTERFACE_00011011
Transfer account creation data SAMPLE_INTERFACE_00011020
Determine the general ledger group SAMPLE_INTERFACE_00011030
Turnover display by date selection SAMPLE_INTERFACE_00011215
Determine business area SAMPLE_INTERFACE_00011031
Authorization check for account master data SAMPLE_INTERFACE_00011040
Determine account ID SAMPLE_INTERFACE_00011055
Delete Accounts
Delete accounts SAMPLE_INTERFACE_00011110
Process: BKK_ACCOUNT_DELETE
Account Closure: Check the Existence of an External Reference Account
Account closure: Check the existence of an external reference SAMPLE_INTERFACE_00011015

account
Process: BKK_ACCOUNT_CLOSURE
Authorizations
11/8/2019
Authorization check for payment item SAMPLE_INTERFACE_00010210
Process: BKK_ITEM_DIALOG
Authorization check for payment order SAMPLE_INTERFACE_00010410
Process: BKK_ORDER_DIALOG
Transfer to FI General Ledger
Determine the additional key for account determination SAMPLE_INTERFACE_00011210
Process: BKK_GL_TRANSFER
De ne individual transfer SAMPLE_INTERFACE_00011220
Determining the business area SAMPLE_INTERFACE_00011230
Determine company number SAMPLE_INTERFACE_00011240
Determine additional elds SAMPLE_INTERFACE_00011300
Replace transfer interface SAMPLE_INTERFACE_00011310
Currency Changeover
Currency changeover: Check module SAMPLE_INTERFACE_00011411
(conversion report) Process: BKK_CURRENCY_EXCHANGE
Currency changeover: Update module (conversion report) SAMPLE_INTERFACE_00011510
Currency changeover: Business Information Warehouse SAMPLE_INTERFACE_00011520
Currency changeover of new limits SAMPLE_INTERFACE_00011420
Currency conversion: Convert limits SAMPLE_INTERFACE_00011425
Currency changeover check module after date entry SAMPLE_INTERFACE_00011410
11/8/2019
Tolerated Overdraft
Tolerated overdraft: Forward noti cation data SAMPLE_INTERFACE_00012800
Process: BKK_OVRDRFT_NOTIFICATION
General
Determining a CpD account if there are several bank areas with the same bank key in the system
Determine bank area from bank country/bank key/account number SAMPLE_INTERFACE_00011800
Process: BKK_BANKAREA
Information System
Authorization checks SAMPLE_INTERFACE_00011700
Process: BKK_AUTHORITY
Data Transfer Interfaces (Direct Input)

De nition
Direct input interfaces serve primarily for the transfer of external data from legacy or previous/feeder systems, current data is
usually transferred into BCA by means of RFC interfaces.
There are basically two options for transferring external data in the SAP system: the batch input procedure and the direct input
procedure. For the purposes of BCA, data is transferred from previous/feeder systems by means of the direct input procedure.
This offers considerable performance advantages as opposed to the batch input procedure.
Use
You can transfer data from external systems for the master data of the account and for balances, standing order and items of the
accounts. For this, SAP de nes a recipient structure in which SAP receives, checks and updates the data. You de ne your own
sender structure and also an assignment of the sender structure elds to the recipient structure elds. The conversion of the
formats, for example, numbers from CHAR25 to CURR, is done by the assignment of the sender and recipient structure.
Special formats apply for date elds and numbers:
The date must be transferred 8-digit in the form yyyymmdd. For the transfer of numbers the eld must contain the representation
of a decimal number, meaning a series of digits with optional +/- sign with a maximum of one decimal point.
Example : The date Dec. 31 1997 is transferred in the form 19971231 and the number -1.234,56 in the form -1234.56.
A unit (account, balance or item) can consist of several datasets. There are elds that occur exactly once per unit, for example, for
an account, the currency, and elds that can occur more than once per unit, for example, blocking reasons for an account. If a unit
11/8/2019
consists of several datasets, those elds that only occur once per unit must be lled for every dataset.
Example : You wish to create an account with the currency ʻUSD’ and blocking reasons ʻ1111’ and ʻ2222’. For the rst dataset
for this account you must enter ʻUSD’ in the currency eld and ʻ1111’ in the blocking reason, for the second dataset you enter ʻUSD’
in the currency eld and ʻ2222’ in the blocking reason.
Structure
Direct input account master data
Structure IBKK_DI_AC
Direct input account balances
Structure IBKKBADIEX
Direct input payment item
Structure IBKKITDIEX
Direct input standing order
Structure IBKKSO_DI_SO
Direct input account balancing
Structure: IBKK9_DI2
Transfer of Account Data

Structure
Caution
Update discontinued
The list of structure objects taken from the system has not been updated again. Use the current data in the system for this
purpose.
Structure IBKK_DI_AC
Field name Category Length Description Sub-structure
AKTYP CHAR 2 Activity IBKK_DI_HD
RLTP1 CHAR 6 Product Header
RLTP2 CHAR 6 Not needed
11/8/2019
BKKRS CHAR 4 Bank area
ACNUM_INT CHAR 10 Internal account number
ACNUM_EXT CHAR 35 Account number
PRODEXT CHAR 10 Product
XOFFER CHAR 1 Indicator: Account as

offer
XCHKDIG CHAR 1 Indicator: No check digits
OPENDATE DATS 8 Date account opened
DELDATE DATS 8 Date account closed IBKK_DI_A1
PRODDATE DATS 8 Go-live date of account Administrative data
BALDATE DATS 8 Date of balance transfer
STATUS_ADD CHAR 4 Account status

enhancement
BEGRU CHAR 4 Authorization group IBKK_DI_A2
GLGRP CHAR 4 General ledger group Operational data
GLKEY CHAR 4 Compensation key

general ledger
ACTEXT CHAR 60 Account description
WAERS CUKY 5 Currency
CONDGR1 CHAR 4 Condition group:

Interests
CONDGR2 CHAR 4 Condition group: Charges
CONDGR3 CHAR 4 Condition group: Value

dates
CAL_ID1 CHAR 2 Public holiday calendar

key 1
CAL_ID2 CHAR 2 Public holiday calendar

key 2
SHARE_ID CHAR 1 Indicator: Single, AND, or

OR account
XTHIRD CHAR 1 Indicator: To the bene t

of a third party
SECUR_ID CHAR 20 Securities ID
11/8/2019
CONDIND1 CHAR 1 Flag: Individual

conditions for interest
exist

conditions for charges
exist

conditions for value dates
exist
CONDIND4 CHAR 1 Flag: Interest scale exists
XACREF CHAR 1 Flag: Account is used as

reference account
XACCLO CHAR 1 Flag: Balancing to

reference account
XWHTAX CHAR 2 Flag: Relevant for capital

yield tax (CYT)
XCOLAUTH CHAR 1 Indicator: Check for

agreement of debit
collection
XVALREQ CHAR 1 Indicator: Value date

speci cation allowed
XOPITM CHAR 1 Indicator: Account with

OI management
XBLOCKDEBIT CHAR 1 Indicator: Debit lock
XBLOCKCREDIT CHAR 1 Indicator: Credit lock
XPOST_FEE_SEP CHAR 1 Indicator: Post charges

individually
LOCK_ID CHAR 4 Locking reason IBKK_DI_LO
CHIND_LO CHAR 1 Direct input: Type of Locks

change (U, I, D)
PARTNER CHAR 10 Business partner number IBKK_DI_BP
RLTYP CHAR 6 Business partner role Business partner

category
CHIND_BP CHAR 1 Direct input: Type of

change (U, I, D)
ADDRNUMBER CHAR 10 Address number
XBKSTORIG CHAR 1 Indicator: Recipient of

bank statement original
BKST_SENDTYPE NUMC 2 Dispatch type of a bank

statement
BKST_FORMAT CHAR 6 Format of a bank

statement
11/8/2019
REF_ACCATG CHAR 2 Reference account IBKK_DI_RF

category
CHIND_RF CHAR 1 Direct input: Type of Reference accounts

change (U, I, D)
INT_POST_METH NUMC 1 Reference account:

Interest posting method
NBANKS CHAR 3 Country key of the bank
NBANKL CHAR 15 Bank key
NACNUM CHAR 35 Account number
NIBAN CHAR 35 International bank

account number
NACHOLD CHAR 60 Account holder
TRNSTYPE CHAR 4 Transaction type
TRNSTYPE2 CHAR 4 Transaction type 2
PAYMETHOD CHAR 4 Payment method
XCHKDIG_R CHAR 1 Indicator: No check digit

calculation
DIRDEB NUMC 4 Direct debit order IBKK_DI_DD

number
POSNR NUMC 3 Direct debit order Direct debit orders

position
CHIND_DD CHAR 1 Direct input: Type of

change (U, I, D)
NAME CHAR 40 Name of account holder
AMOUNTLIM CURR 17 Amount limit
DEB_CUR CUKY 5 Currency for direct debit

order
CLOS_TYP CHAR 4 Balancing type IBKK_DI_CL
CHIND_CL CHAR 1 Direct input: Type of Periodic data

change (U, I, D)
PERIOD NUMC 3 Period
PER_UNIT CHAR 1 Period unit
KEY_DATE NUMC 2 Key date
NEXT_DATE CHAR 8 Next date
CURR_YEAR NUMC 4 Current year
CURR_NR NUMC 3 Sequential number
GLDATE DATS 8 Date of the last general

ledger transfer
11/8/2019
XINTEREST CHAR 1 Indicator: Balance

noti cation with interest
information
LIMTYPE CHAR 2 Limit category IBKK_DI_LI
VALIDTO CHAR 8 Valid to Limits
VALIDFROM DATS 8 Valid from
LIM_OK CHAR 1 Indicator: Limit released
LIM_CUR CUKY 5 Limit currency
CHIND_LI CHAR 1 Direct input: Type of

change (U, I, D)
LIMSUM CURR 17 Limit amount
SLIM_ID CHAR 2 ID reference limit
CASHBTYPE CHAR 4 Means of payment IBKK_DI_CH

position type
CHIND_CH CHAR 1 Direct input: Type of Checks (cheque):

change (U, I, D)
XNUMISSUE CHAR 1 Indicator: Check number

assignment when issued
by bank
XNUMHANDIN CHAR 1 Indicator: Maintain check

number on presentation
BALVALIDFROM DATS 8 Valid from IBKK_DI_BA
CHIND_BA CHAR 1 Direct input: Type of account settlement

change (U, I, D) control indicator
NOSTRO CHAR 1 Bank account category
.include CI_BKK46 Customer elds
Explanations: Substructure IBKK_DI_HD (Header)

AKTYP (activity category)
Three values are allowed for the eld AKTYP:
ʻ01’: Create: This involves a new account that is to be created.
ʻ02’: Change: An account that already exists is to be changed.
‚‚: (initial): This dataset still belongs to the previous account.
An account can consist of any number of datasets. The rst one must have activity ʻ01’ or ʻ02’ and all subsequent ones the activity
blank. All other elds from the sub-structures header, administrative data, operational data and customer elds must be entered
with the same value in all datasets for an account.
11/8/2019
Example: You wish to create an account with 3 datasets. The currency is to be EUR. For the rst dataset the eld AKTYP is
ʻ01’, for the next two it is blank. In all 3 datasets the eld WAERS must be ʻEUR’.
RLTP1 – RLTP9 (role category)
These elds must be blank. (The reason for these eld names is the mutual use of business partner and account)
ACNUM_INT(internal account number)
Leave the internal account number blank. It is issued automatically.
ACNUM_EXT (external account number)
You can specify the account number (with leading zeros, 35 digits!) or have it issued automatically.
PRODEXT (product)
The product. The version of the product is determined by virtue of the account opening date.
Explanations: Substructure IBKK_DIA1 (Administrative Data)

PRODDATE (Go-live date of account)
Date as of which the account is used productively in BCA.
The account settlement for periods balanced before this date are not posted.
BALDATE (Date of balance transfer)
Date as of which the balances from the legacy system are transferred into BCA.
Value dates in the past and postings in former account before this date are not possible. The interest calculation of the 1st period
begins on this date, provided it is before the account opening date.
Explanations: Substructure IBKK_DI_A2 (Operative Data)

ACTEXT (account description)
If the account description remains blank at the time of creation, it is automatically lled with the name of the account holder.
SHARE_ID (Indicator: Single, AND, or OR account)
ʻ1’: Single account
ʻ2’: AND (joint) account
ʻ3’: OR account
General explanations on the table controls

A table control can contain several lines per account. Every table control has a CHIND eld (change indicator) that speci es the
type of change per line. The key elds of a table control are always in front of the CHIND eld, the other elds of the table control
11/8/2019
are after the CHIND eld.
CHIND (change indicator)
There is one CHIND eld for every table control. This show the type of change in this table control per line.
ʻIʻ: Insert. Insertion of a line.
ʻUʻ: Update. Change to a line. Only meaningful for AKTYP ʻ02’.
ʻD’: Delete: Deletion of a line. Only meaningful for AKTYP ʻ02’. You need only ll the key elds.
If the CHIND eld remains blank, no changes are made.
Example : An account with 2 business partners and a lock for the currency ʻUSD’ is to be created.
Dataset 1 has AKTYP ʻ01’, WAERS ʻUSD’, CHIND_BP ʻI’ (insert business partner), the other elds of the business partner structure
are lled, CHIND_LO ʻI’; the other elds of the lock structure are lled.
Dataset 2 has AKTYP blank, WAERS ʻUSD’, CHIND_BP ʻI’, the other elds of the business partner structure are lled, CHIND_LO
blank; the other elds of the lock structure are blank.
Explanations: Substructure IBKK_DI_BP (Business Partner)

SENDTYPE (Dispatch type of a bank statement)
This eld is a numeric character eld. If it is to remain blank you must enter ʻ00’.
Until release 1.2 there was only one eld SENDTYPE for the account. As of release 2.0 you can use an own dispatch type for each
business partner.
Explanations: Substructure IBKK_DI_RF (Reference Accounts)

REF_ACCATG (reference account category)
ʻ01’: Account closure
ʻ02’: Account balancing
INT_POST_METH (interest posting method)
ʻ1’: Internal reference account with posting to referencing account
Explanations: Substructure IBKK_DI_DD (Direct Debit Orders)

POSNR (Direct debit order position)
Line number of a direct debit order. In line 1 is always the original order with the original name and the highest amount. In lines 2 to
x are alternative names with no amount. You may not change lines 2 to x but only insert or delete. You may also not change the
original line 1. If you wish to delete the whole order, it is sufficient to delete line 1.
11/8/2019
Explanations: Substructure IBKK_DI_CL (Periodic Data)

CLOS_TYP (Balancing type)
ʻ0001’: Bank statement
ʻ0002’: Cash concentration
ʻ0003’: Account balancing
PERIOD, PER_UNIT, KEY_DATE (period, period unit, key date)
PER_UNIT
ʻ1’: Calendar days
ʻ2’: Weeks
ʻ3’: Months
PERIOD
Speci es how many period units (PER_UNIT) will pass till the next balancing.
KEY_DATE
Key date of the balancing.
In the case of weeks, the day of the week (1 = Monday, 7 = Sunday)
In the case of months, the day of the month 31 = (last day of month)
Example:
Every day. PERIOD ‚001ʻ PER_UNIT ‚1ʻ
Every 3 weeks on Tuesdays: PERIOD ‚003ʻ PER_UNIT ‚2ʻ KEY_DATE ‚02ʻ
Every 6 months on the 15th: PERIOD ‚006ʻ PER_UNIT ‚3ʻ KEY_DATE ‚15ʻ
Every month on the last day of the month: PERIOD ‚001ʻ PER_UNIT ‚3ʻ KEX_DATE ‚31ʻ
NEXT_DATE (Next date)
Date of the next account settlement. If it remains empty, it is automatically set by the system based on PERIOD, PER_UNIT and
KEY_DATE. You can, however, always specify it.
CURR_YEAR, CURR_NR (current year, current number)
Normally speci ed by the system. However, in the case of the balancing type bank statement, it is meaningful to supply the
present statement number so that the bank statement numbers remain consecutive. During bank statement creation, the system
increases the sequential number by 1, meaning if you supply the sequential number 12, the next bank statement is numbered 13.
Explanations: Substructure IBKK_DI_LI (Limits)

LIMTYPE (Limit category)
11/8/2019
ʻ01’: Overdraft limit
ʻ02’: Internal credit/overdraft limit
ʻ03’: External credit/overdraft limit
Explanations: Substructure IBKK_DI_BA (account settlement Control Indicator)

NOSTRO (Bank account category)
ʻ1’: Vostro account
ʻ2’: Nostro account
Explanations: Customer Fields

Customer-own account data is saved in table BKK46. This consists of the account key and the include CI_BKK46. You can freely
de ne this include yourself. It is then not only included in table BKK46, but also in this direct input structure.
Explanations: Transfer of account data in deposit banking

The substructures IBKK_DI_BKK42_NTC, IBKK_DI_BKK58, IBKK_DI_BKKNTC, and IBKK_DI_BKKTERM have been added to the
IBKK_DI_AC structure. For more information, see the documentation on these substructures in the system.
Note that you need to transfer the account data in two steps in these cases:
1. Creation of the account using activity category 01
2. Transfer of the data for the amount notice and term agreement using activity category 02.
Transfer of Account Balances

Structure
Caution
Update discontinued
purpose.
Structure: IBKKBADIEX
ACNUM_IBAN CHAR 35 International bank account

number
REFNO_CR CHAR 20 Reference number of creation
11/8/2019
DATE_CR DATS 8 Date data medium created
DATE_VALUE DATS 8 Value date
DATE_POST DATS 8 Posting date
XNOGLITEM CHAR 1 Indicator: No update in general

ledger
TCUR CUKY 5 Transaction currency
T_AMOUNT CHAR 17 Amount in transaction currency
NACUR CUKY 5 Reporting account currency
NA_AMOUNT CHAR 17 Amount in reporting account

currency
ACUR CUKY 5 Account currency
A_AMOUNT CHAR 17 Amount in account currency
BUTXT CHAR 50 Posting text
REMARK CHAR 50 Comment on order/item
Additional explanations (optional elds are marked):

BKKRS (Bank area)
The bank area in which the account is located.
ACNUM_EXT (account number)
Account number in BCA. The account must be created in BCA and be active.
ACNUM_IBAN (International Bank Account Number) optional
International Bank Account Number.
REFNO_CR (Reference number of creation ) optional
Reference number of the creation.
DATE_CR (Date on which the data medium was created) optional
Date on which the data medium was created. The posting date of the account balance is recorded independently of this eld in the
administrative data of the corresponding payment item.
DATE_VALUE (value date)
The value date as of which the balance in BCA is effective.
DATE_POST (posting date)
Posting date of the balance or the corresponding payment item.
XNOGLITEM (Indicator: No update on general ledger)
With this indicator you de ne if the posting is to be updated on the general ledger. The value area and meaning are:
11/8/2019
XNOGLITEM = ʻX’: No update on general ledger
XNOGLITEM = ʻʻ: Update on general ledger
Caution
Caution
Incorrect use of this indicator can lead to inconsistencies in general ledger accounting.
TCUR (Transaction currency, NACUR (reporting account currency) optional,
ACUR (Account currency)
Transaction, reporting account and account currency keys.
T_AMOUNT (Amount in transaction currency), NA_AMOUNT (amount in reporting account currency) optional, A_AMOUNT
(amount in account currency)
Amounts of the balance in transaction, reporting account and account currency. The balances are updated on the database with
the speci ed +/- sign.
BUTXT (Posting text) optional
Posting text.
REMARK (Comment) optional
Comment on order/item
Transfer of Payment Items

Structure
Caution
Update discontinued
purpose.
Structure: IBKKITDIEX
ITEM_NO NUMC 5 Number of payment item
ITEM_POSNO NUMC 3 Position of payment item
NOTNO NUMC 3 Sequential payment note

number
11/8/2019
ACNUM_IBAN CHAR 35 International bank account
number
ALT_ACEXT CHAR 35 Original account number
ALT_IBAN CHAR 35 Original IBAN
REFNO_CR CHAR 20 Reference number of creation
REFNO_PAYM CHAR 20 Reference number from

payment transactions
REFNO_PN CHAR 12 Daybook
DATE_CR DATS 8 Date data medium created
TCUR CUKY 5 Transaction currency
T_AMOUNT CHAR 17 Amount in transaction currency
T_CHARGE CHAR 17 Charge in transaction currency
NACUR CUKY 5 Reporting account currency
NA_AMOUNT CURR 17 Amount in reporting Account

currency
NA_CHARGE CURR 17 Charge in reporting Account

currency
ACUR CUKY 5 Account currency
A_AMOUNT CHAR 17 Amount in account currency
A_CHARGE CHAR 17 Charge in account currency
EXCHNGRATE DEC 9 Exchange rate
MEDIUM CHAR 4 Medium
TRNSTYPE CHAR 4 Transaction type
S_TRNSTYPE CHAR 4 Original transaction type
RETURNK CHAR 2 Return reason
COUNTRY CHAR 3 ISO code of a country
X_ACTCHK_E CHAR 1 Indicator: Error in account check

digit
CHEQUE_TYP CHAR 4 Means of payment position type
CHEQUE_NO CHAR 20 Check number
ITEMCNT NUMC 5 Number of processed items
BUTXT CHAR 50 Posting text
REMARK CHAR 50 Comment on order/item
REF_ACEXT CHAR 35 Reference account number
REF_IBAN CHAR 35 Reference IBAN
11/8/2019
REF_NAME CHAR 40 Reference name of account
holder
REF_BANKS CHAR 3 Reference country key of the

bank
REF_BANKL CHAR 15 Reference bank key
XNOGLITEM CHAR 1 Indicator: No update on general

ledger (currently not used)
XVALDATSET CHAR 1 Indicator: Value date was

speci ed
PAYM_NOTE CHAR 65 Payment notes
PUBLIC_CONT_L1 CHAR 35 Long container eld
PUBLIC_CONT_S1 CHAR 20 Short container eld
PUBLIC_CONT_S2 CHAR 20 Short container eld

BKKRS (Bank area)
ITEM_NO (Number of payment item)
Sequential number of the payment item for data transfer.
ITEM_POSNO (Position of payment item)
Sequential position number of a payment item.
NOTNO (Sequential payment note number)
Sequential payment note line for a position of a payment item.
ACNUM_IBAN (International Bank Account Number) optional
International Bank Account Number.
ALT_ACEXT (Original account number) optional
Original account number.
ALT_IBAN (Original IBAN) optional
11/8/2019
Original IBAN.
REFNO_CR (Reference number of creation ) optional
Reference number of the creation.
DATE_CR (Date on which the data medium was created) optional
Date on which the data medium was created. The posting date of the account balance is recorded independently of this eld in the
administrative data of the corresponding payment item.
DATE_VALUE (value date)
The value date as of which the balance in BCA is effective.
DATE_POST (posting date)
Posting date of the balance or the corresponding payment item.
TCUR (Transaction currency, NACUR (reporting account currency) optional,
ACUR (Account currency)
Transaction, reporting account and account currency keys.
T_AMOUNT (Amount in transaction currency), NA_AMOUNT (amount in reporting account currency) optional, A_AMOUNT
(amount in account currency)
Amounts of the items in transaction, reporting account and account currency. The items are updated on the database with the
speci ed +/- sign.
T_CHARGE (Charge in transaction currency), NA_CHARGE (charge in reporting account currency) optional, A_CHARGE
(charge in account currency)
Charges contained in the items in transaction, reporting account and account currency. The items are updated on the database
with the speci ed +/- sign.
EXCHNGRATE (Exchange rate) optional
Exchange rate.
MEDIUM (Medium)
Medium with which the item was originally entered.
TRNSTYPE (transaction type)
Transaction type
S_TRNSTYPE (Original transaction type) optional
Original transaction type for EFT enhancement key.
RETURNK (Return reason) optional
Return reason.
11/8/2019
COUNTRY (ISO code of a country) optional
ISO code of a country.
X_ACTCHK_E (Indicator: Error in account check digit) optional
Error occurred during check digit procedure
CHEQUE_TYP (Means of payment position type) optional
Means of payment position type.
CHEQUE_NO (Check number) optional
Check number being managed in BCA.
ITEMCNT (Number of processed items) optional
Number of processed items.
BUTXT (Posting text) optional
Posting text.
REMARK (Comment) optional
Comment on order/item
REF_ACEXT (Reference account number) optional, REF_IBAN (reference IBAN) optional, REF_NAME (reference name of
account holder) optional, REF_BANKS (reference country key of bank) optional, REF_BANKL (reference country key of bank)
optional
Reference data.
XNOGLITEM (Indicator: No update on general ledger)
This indicator must be initial.
XNOGLITEM = ʻʻ: Update on general ledger
Caution
Caution
Incorrect use of this indicator can lead to inconsistencies in general ledger accounting.
XVALDATSET (Indicator: Value date was speci ed) optional
Value date has been speci ed in feeder system.
PAYM_NOTE (Payment notes)
Payment note line.
11/8/2019
Transfer of Standing Orders

Structure
Caution
Update discontinued
purpose.
Structure IBKKSO_DI_SO
AKTYP CHAR 2 Activity IBKK_DI_HD
RLTP1 CHAR 6 Not needed Header
BKKRS CHAR 4 Bank area IBKKSO_DI_H2
ACNUM_EXT CHAR 35 Account number Standing order header
SONO NUMC 10 Standing order number
TRNSTYPE CHAR 4 Transaction type IBKKSO_S1
PAYMETHOD CHAR 4 Payment method Initial screen
PERIOD NUMC 3 Period IBKKSO_S2
PER_UNIT CHAR 1 Period unit Administrative data
KEY_DATE NUMC 2 Key date
NEXT_DATE DATS 8 Next execution
SHIFT_WDAY CHAR 1 Shift work day
SUSP_FROM DATS 8 Suspended from
SUSP_TO DATS 8 Suspended until
LAST_DATE DATS 8 Last execution
TRNSTYPE_R CHAR 4 Transaction type

recipient
11/8/2019
RCV_BANKS CHAR 3 Country key of bank of
recipient
RCV_BANKL CHAR 15 Bank key of recipient
RCV_ACEXT CHAR 35 Account number of

recipient
RCV_NAME CHAR 40 Name of recipient
MEDIUM CHAR 4 Medium
STATUS CHAR 2 Status
TCUR CUKY 5 Transaction currency IBKKSO_S4EXT
T_AMOUNT_EXT CHAR 25 Amount Amount
TCUR_VAR CUKY 5 Transaction currency for IBKKSO_S6EXT

variable amounts
REM_AMOUNT_EXT CHAR 25 Remaining amount in Variable amount

transaction currency
PERCENTAGE NUMC 3 Percentage execution of a

standing order
MIN_AMOUNT_EXT CHAR 25 Minimum amount in

transaction currency
ROUNDING CHAR 2 Rounding for variable

standing order execution
NOTNO NUMC 3 Payment note number IBKKSO_DI_NT
CHIND_NT CHAR 1 Type of change Payment notes
PAYM_NOTE CHAR 65 Payment notes
For explanations on the various elds, see section .
Transfer of Account Balancing

Structure
Caution
Update discontinued
purpose.
Structure: IBKK9_DI2
CLOS_TYP CHAR 4 Balancing type
11/8/2019
CLOS_YEAR NUMC 4 Year of the balancing period
CLOS_NR NUMC 3 Number of the balancing period
TURNOVER_CLASS CHAR 4 Turnover class
CURR CUKY 5 Account currency
START_DATE DATS 8 Start date of period
END_DATE DATS 8 End date of period
END_DATE_I DATS 8 End date of interest calculation
DEBITS_INT CURR 17 Amount debit interest
CREDIT_INT CURR 17 Amount credit interest
OVERDR_INT CURR 17 Amount overdraft interest
SUPPLY_INT CURR 17 Amount for commitment

interest
ITEM_FEE CURR 17 Amount item charge
FORW_COST CURR 17 Amount dispatch expenses
ACCONT_FEE CURR 17 Amount account maintenance

charge
PERIOD_FEE CURR 17 Amount item charge
CSTMR_AMT CURR 17 Amount of customer
BALANCE CURR 17 Balance
WHTAX_AMT CURR 17 Tax
LCUR CUKY 5 Local currency
WHTAX_LAMT CURR 17 Tax in local currency
INTRATE_AV DEC 10 Average interest rate for credit

interests
XCONDEXCHANG CHAR 1 Swap conditions during account

settlement
XACCLO CHAR 1 Indicator: Balancing to reference

account

BKKRS (Bank area)
11/8/2019
CLOS_TYP (Balancing type)
Only balancing type ʻ0003’ is available at present for the account settlement. In future releases, further balancing types might be
added.
CLOS_YEAR (Year of the balancing period)
Year of the balancing period.
CLOS_NR (Number of the balancing period)
Sequential numbering is to be used in each balancing year. The rst period of a year is always ʻ001’.
TURNOVER_CLASS (turnover class) optional
Not yet in use. Therefore, this eld must not be lled.
CURR (account currency)
Account currency
START_DATE (Start date of period)
The start date needs to be the same as the end date of the previous period.
END_DATE (End date of period)
The turnovers of the account settlement were selected up to the end date of the period.
END_DATE_I (End date of interest calculation)
Interest was calculated for the turnovers up to the end date of interest calculation. END_DATE_I can be different from END_DATE,
for example, when using the interest calculation method 360/360. With this method, interest is calculated on the basis of 30-day
months. For a month with 31 days, END_DATE will therefore be the 31 st , and END_DATE_I will be the 30 th .
DATE_VALUE (Value date) optional
The value date on which the balancing was posted in the legacy system.
DATE_POST (Posting date) optional
The posting date on which the balancing was posted in the legacy system.
DEBITS_INT (amount debit interest) optional
The sum to be transferred is always the sum of the most recently calculated debit interest. This applies in particular for correction
periods for which the difference between the old and the new interest is not to be transferred.
If an old period has to be recalculated (for example, due to a value date in the past), then this amount is used to calculate the
difference. There will be an adjustment posting for the difference amount.
CREDIT_INT (amount debit interest) optional
The sum to be transferred is always the sum of the most recently calculated credit interest. This applies in particular for correction
periods for which the difference between the old and the new interest is not to be transferred.
11/8/2019
Any capital yield tax (CYT) that might have accrued must not be deducted.
OVERDR_INT (amount overdraft interest) optional
The sum to be transferred is always the sum of the most recently calculated overdraft interest. This applies in particular for
correction periods for which the difference between the old and the new interest is not to be transferred.
SUPPLY_INT (Amount of commitment interest) optional
The sum to be transferred is always the sum of the most recently calculated commitment interest. This applies in particular for
correction periods for which the difference between the old and the new interest is not to be transferred.
ITEM_FEE, FORW_COST, ACCONT_FEE, PERIOD_FEE, CSTMR_AMT (amount item charge, dispatch expenses, account
maintenance charge, period charge, amount of customer) optional
These elds are only for information purposes. Charges of old periods cannot be corrected. These elds are only displayed in the
overview of the completed periods.
BALANCE (balance)
account settlement balance This balance must include all postings with posting date and value date up to and including
END_DATE.
WHTAX_AMT, LCUR, WHTAX_LAMT (tax, local currency, tax in local currency) optional
These elds are only for information purposes. The CYT of old periods must be corrected in the CYT module owned by the
customer. The tax will only be displayed in the overview of the completed periods.
INTRATE_AV (average interest rate for credit interests) optional
Average interest rate for credit interests. You can ll this eld for information purposes. In BCA, there is no evaluation of this eld.
XCONDEXCHANG (Swap conditions during account settlement) optional
In BCA, nostro accounts are balanced using swapped conditions. This means that debit balances are calculated by using credit
interest and credit balances by using debit or overdraft interest. If you have also implemented this logic in your legacy system, you
can, for information purposes, ll this eld with an ʻX’. In BCA, there is no evaluation of this eld.
XACCLO (Indicator: Balancing to reference account) optional
If the account settlement in your legacy system is posted to a reference account, you can enter an ʻX’ here for information
purposes. In BCA, there is no evaluation of this eld.
Technical Explanations for Interfaces

11/8/2019
1. Data formats
1.1 Date elds
A date is transferred in a eld of the category DATS. The date is displayed in the form yyyymmdd.
Example
December 24, 2001 is represented as 20011224 (initial value is 00000000).
1.2 Number elds
Numbers are transferred in elds of the category NUMC: These are character elds that only permit numbers. Represent numbers
with leading zeros.
Example
The number 13 is displayed in a NUMC eld of length 4 as “0013”.
Note
Counters at SAP always begin with 1 and not with 0. If, for example, two application of funds lines are to be transferred, they
must be numbered “001! and “002”.
1.3 Return reason
Used for returned transfers, returned check and returned debits. As with the transaction types, the SAP system only recognizes its
own, neutral return reasons so conversion from the previous/feeder system is necessary.
Formats: CHAR 2
1.4 Country
In the SAP system the countries are maintained in accordance with the domain COUNTRY1. Accordingly, the previous/feeder
system must be converted from ISO3166 to SAP.
Format: CHAR 3 transfer is made in capitals and with left alignment.
1.5 Check digit error for account number
Used, for example, for text key 51000 53000 56000 67000 68000, although in the case of errors, the text key enhancement is
converted to 444. Make use of the normal transaction type and display the check digit error by setting the indicator in the
interface.
Format: CHAR 1, X eld
1.6 Special features of RFC interfaces
Amount elds in the RFC interfaces
Amounts are displayed in character elds of length 25.
Externally initiated payment transactions and RFCs
11/8/2019
These are displayed with left alignment, without +/- sign and without punctuation after the thousands. The division of positions
before and after the decimal point is displayed by a full stop (period).
Example
The amount 1,327.11 is displayed as 1327.11.
Other RFCs
These are displayed with left alignment, followed by a +/- sign and without punctuation after the thousands. The division of
positions before and after the decimal point is displayed by a full stop (period).
Example
The amount 1,327.11 is displayed as 1327.11 (debit) or 1327.11 (credit).
Exchange rate in RFC interfaces
If the transaction currency does not correspond to the account currency and conversion takes place in the previous/feeder
system, this is where you enter the exchange rate on which conversion was based.
Format: CHAR 10, four places before the decimal point, ve places after the decimal point, comma shown as full stop (period).
Example
Exchange rate 12, 12340 is displayed as 12.1234
2. Required eld REFNO_PAYM

Serves as reference from previous/feeder system to SAP. This enables the clear and unmistakable identi cation of payment items
in the various systems. By means of a report and depending on the structure of the reference number, comparison between SAP
and the respective previous/feeder systems is also possible.
3. Field ITEM_NO
This number clearly and unmistakably identi es a payment item and is independent of the bank area. Within each system, every
payment item has to have a clear and unmistakable ITEM_NO.

Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 3

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 3

Încărcat de

Drepturi de autor:

Formate disponibile

11/8/2019

SAP In-House Cash (FIN-FSCM-IHC)

SAP ERP | 6.0 EHP8 SP13

Original content: https://help.sap.com/viewer/da5ab0fa48b34143a25d0e08448f5219/6.18.13/en-US

For more information, please visit the https://help.sap.com/viewer/disclaimer.

Interfaces of Bank Customer Accounts

Use and integration

Overview of the RFC Interfaces

The following tables list the RFC-enabled function modules in BCA.

Name of Function Module Technical Name of Function Module

Get account list for bank keys BAPI_BANKACCT_GET_LIST_ALL

Get account list for business partner BAPI_BANKACCT_GET_LIST

Query detail data for account BAPI_BANKACCT_GET_DETAIL

Get a business partner for an account BAPI_BANKACCT_GET_BUPA

Query an account hierarchy BAPI_BANKACCT_GET_HIERARCHY

Account balance list for business partner BKK_RFC_BANKACCNT_GET_BALANCE

Get payment items for an account BAPI_BKK_ACCNT_GET_ITEM_LIST

Get root accounts for a hierarchy BAPI_BANKACCT_GET_ROOTACCOUNTS

Business Partner Information

Name of Function Module Technical Name of Function Module

Get total commitment of a business partner in BCA BAPI_BKK_TC_GET_LIST

Get business partner addresses for an account BKK_RFC_ACCNT_GET_PARTNER_ADDR

Name of Function Module Technical Name of Function Module

Name of Function Module Technical Name of Function Module

Update dispatch expense counter BAPI_COND_FORW_EXPENSES_COUNT

Get account balancing detail data BAPI_COND_CLOSE_ GET _ DATA

Name of Function Module Technical Name of Function Module

Create an account BAPI_BKK_ACCNT_CREATE

Simpli ed account creation BAPI_BKK_ACCNT_CREATE_EASY

Change an account BAPI_BKK_ACCNT_CHANGE

Close an account BAPI_BKK_ACCNT_CLOSURE

Get available amount of an account BAPI_BKK_ACCNT_GET_AV_AMOUNT

Get account balance BAPI_BKK_ACCNT_GET_BALANCE

Get account details BAPI_BKK_ACCNT_GET_DETAIL

Get payment items for an account BAPI_BKK_ACCNT_GET_ITEM_LIST

Get list of accounts for a business partner BAPI_BKK_ACCNT_GET_LIST

Name of Function Module Technical Name of Function Module

Get product details BAPI_BKK_PROD_GET_DETAIL

Account Turnover Information

Name of Function Module Technical Name of Function Module

Query account turnovers BAPI_PAYM_ITEM_GET_LIST

Turnovers displayed by selection criteria BKK_RFC_ITEM_GET_LIST

Withdrawal Amounts and Special Revenue Allowance Amounts

Name of Function Module Technical Name of Function Module

Transfer withdrawal amounts and special revenue allowance BKK_FA_RFC_SET

Name of Function Module Technical Name of Function Module

Posting balance BAPI_COND_POST_DECRE_BALANCES

Name of Function Module Technical Name of Function Module

Value date balance BAPI_COND_ VAL _DECRE_BALANCES

Pool balances BAPI_COND_DECRE_ BAL _POOLS

Name of Function Module Technical Name of Function Module

Initiate a bank statement BAPI_BANK_STATEMENT_EXEC

Create a bank statement duplicate BAPI_BANK_STATEMENT_ GET

Externally Initiated Payment Transactions

Name of Function Module Technical Name of Function Module

Post and check ordering party item BAPI_PAYIT_POST_SENDER

Post and check recipient item BAPI_PAYIT_POST_RECEIVER

Post and check routing item BAPI_PAYIT_POST_CLEARING

Post a turnover item BAPI_PAYIT_POST_ITEM

Post and check ordering party item BAPI_PAYM_ITEM_POST_SENDER

Post and check recipient item BAPI_PAYM_ITEM_POST_RECEIVER

Post and check routing item BAPI_PAYM_ITEM_POST_CLEARING

Post a turnover item BAPI_PAYM_ITEM_POST_ITEM