DE ERP SAP

Application Design Document.docx

EBS MT940 Configuration Document

P2P-API-INT01

API – Int_Kyiba Inbound

AP&I
 DE ERP SAP
Application Design Document.docx

1.1 Purpose
The purpose of developing this interface object is to ensure that all financial transactions from Kyriba
- are automatically matched and cleared with open items in cash clearing accounts across all
company codes that hold a bank account with SAP/Kyriba.

SAP consists of a standard Electronic bank Statement (EBS) program that can fulfill this
requirement. The Electronic Bank Statement functionality is designed in SAP S/4 HANA to do
automatic bank account reconciliations.

1. Bank of America : The following Bank Accounts are in scope for the EBS – MT940

2. JP Morgan Chase: The following Bank Accounts are in scope for the EBS – MT940
3. Deutsche Bank : The following Bank Accounts are in scope for the EBS – MT940
4. Bank of China : The following Bank Accounts are in scope for the EBS – MT940

1.2 S4 Configuration

All configuration related to EBS inbound processing will be done in t-code OT83 or it can be done
through SPRO configuration as mentioned below

Financial Accounting > Bank Accounting > Business Transactions > Payment Transactions >
Electronic Bank Statement > Make Global Settings for Electronic Bank Statements
 DE ERP SAP
Application Design Document.docx

1. Assign Bank accounts to transaction types:

In this node we need to define which Banks and corresponding Bank account numbers which
are part of EBS file processing and postings.

Below screen shot shows which JPM Bank Key and account numbers are configured for EBS
processing

Company code and Transaction Types are assigned to Bank account numbers belongs to
respective company codes.

Company code 4630 is assigned to three Bank Accounts which are in EBS scope, these account
numbers Banking transactions will be received in MT940 format.

2. Create Account symbols

Account symbols are defined to identify the transaction type in EBS statement and GL accounts
are assigned to each Account symbols. Account symbols are assigned to Posting Keys.
 DE ERP SAP
Application Design Document.docx

SAP delivered standard Account symbols, either we can use standard Account symbols or we
can define our own Account symbols. Above Account symbols starting with Z* are defined for
Boing BDSI company codes.

3. Assign GL accounts to Account Symbols:

GL accounts masking can be made to simplify and reduce defining number of GL accounts. GL
accounts with 1006++++ implies all GL accounts configured in House Bank account
determination starting with 1006 will be used to post corresponding account number postings
when EBS file is processed.

Account Modification controls account determination for Bank Sub accounts. With the help of
this field, you can direct the posting to a differentiate bank subaccount instead of a standard one.
 DE ERP SAP
Application Design Document.docx

Leave this field blank (or enter the mask "+") if you do not want to use an account modification.

Account Modification Currency Key of the currency in which amounts in the system are
managed. Leave this field blank (or use masking "+") if you do not want to us different currencies
in the G/L account.

4. Define Keys for Posting Rules

Posting Rule Keys are used in defining Posting rules, where Posting Keys are assigned to
Account symbols. Posting rules are assigned to external transaction codes.

Above user defined Posting keys are defined for MT940 file format postings.

5. Define Posting Rules

Posting rules are key to post to right GL account based on the nature of the transaction types in
EBS files. Posting rules are linked to Posting Area either post to Ledger or sub Leger, Posting
keys and Account symbols. Later Posting rules are assigned to External transaction types
 DE ERP SAP
Application Design Document.docx

6. Create Transaction Types:

transaction type ZBDSI is created for all MT940 EBS postings. External transaction types of
MT940 file are assigned to this transaction type

7. Assign External Transaction types to Posting Rules

 DE ERP SAP
Application Design Document.docx

8. File Processing

The technical configuration will be carried through the automated program which will pull the daily
(Previous Day Reporting –PDR) file through TCODE: FEB_FILE_HANDLING. This will be used
for the mapping the file with AL11 in such manner that after the execution of each file, it will be
automatically move into the archive folder which will be kept for 7 days and then it will be deleted
automatically as per Boeing standard practice.
 DE ERP SAP
Application Design Document.docx

The Inbound AL11 path needs to be discussed and updated. However, here is our
understanding. We need to create one common SR with 4 different packages to ensure
that we have 4 different sfolders for each bank under as mentioned under:

 BDSI
o KYRIBA
 BOFA
 Archive
 Error
 From SAP
 To SAP
 JPMC
 Archive
 Error
 From SAP
 To SAP
DE ERP SAP
Application Design Document.docx