KT DOCUMENT ON EBS

Process flow:
Bank GSK Middleware SAP PI

SWIFT GSK Global Message

Bank Network WebSphere SWIFT_MT940
Sungard Sungard
statement Message
Bureau TRAX
data Broker

Enterprise Service

CERPS

Load bank
statement

File comes via MT940; message ID in CERPs: AB7EF533-9663-4E1C-2925-978FF55C7495

When we check in FTE_BSM, below is the statement appearing

FTE_BSM

1
 KT DOCUMENT ON EBS

Below is the bank statement as appearing in the system:

2
 KT DOCUMENT ON EBS

ISSUE 1: Missing bank statement (multiple issues received):

1st Step: Check if the bank statement is posted or not (most of the time it won’t be)

2nd Step: Check with the Middleware team if they have received the statement or not by sending
mail/transferring the ticket to them

 Ask the user for the MT940 file name for the missing bank statement
 Missing statement no and the date.

3rd Step: If MW confirms that the statement has passed through them, check with the PI team if the
same has been triggered from there end or not.

4th Step: PI team confirms with the message id on the status of it in CERPs.

5th Step: If it is a failure in CERPs, we can find the reason under SXMB_MONI with the message ID and
action accordingly.

Nature of errors:
1. Posting Rule missing for external transaction type

Message ID: 6E902E5C-8C1D-4313-1FE0-EF7B81F5CA03

 Failure because of missing external transaction type under OT83 (Routine for L2)

3
 KT DOCUMENT ON EBS

 Ask the business as to which posting rule needs to be maintained against external transaction
type 088 (as above)
 Maintain posting rule as provided by business (transportable routine)

2. No entry in the House bank table:

Message ID: CFC395E1-D5CF-47E3-09BA-B1409E648DEB

House Bank table is T012K

3. Bank details not in table T028B

Message ID: 2604C207-73FA-4331-2F9A-9027D8066410

4
 KT DOCUMENT ON EBS

Check in table T028B:

Once the bank statement is posted in the system, there is an Auto job ALL_R2R_FEBP* which post the
entries under FEBAN posting area 1.

Below is an example of the job and its posting:

Job: ALL_R2R_FEBP_DB_BK_STATEMENTS AK746354 13.01.2017 07:00:04

Bank details:-
House Bank: DBAT1
Acct ID: POBO1
Statement Date: 16.12.2016
Statement no. 249

Below is the screenshot where the bank statement got picked up in the job:

5
 KT DOCUMENT ON EBS

Below is the FEBAN screen where we can see that the posting have happened based on the
configuration:

6
 KT DOCUMENT ON EBS
System automatically picks up the GL account based on the configuration maintained under OT83
settings:
Steps to check the OT83 configuration:
1. Check for which transaction type the bank account has been maintained:

2. Check the posting rule assigned to the external transaction type:

3. Check the account symbols assigned to the posting rule:

4. Check the GL account assigned to the account symbols:

7
 KT DOCUMENT ON EBS

5. For the ++++ maintained under G/L account, system picks up the GL account from the House
Bank master data (T-code FI13). Below is the screenshot for reference:

For ++++6, system replaces the bank account GL’s last digit and will replace it with 6 (hence GL 1701036
is picked)

6. Below is the document posted under FEBAN:

8
 KT DOCUMENT ON EBS

For posting area 2 postings, we have an Autocash Process in GSK. Following posting rules are maintained
for the same: XX19, XX27, XX29 and XX39.

ISSUE 2: Auto run unsuccessful.

We receive multiple issues regarding the auto job run not completed. By this user means that the
postings didn’t happen under posting area 1 after the job is run.
1. We need to check the bank statement arrival time in CERPs under table U_12300
2. Check if the same got picked up in the job if the statement received before job is run.
3. Check for which posting rule the postings didn’t happen and investigate accordingly.