SFMS-CBS Interface Specification Document Summary

INSTITUTE FOR DEVELOPMENT AND RESEARCH
IN BANKING TECHNOLOGY,
HYDERABAD

SFMS-CBS Interface Specification Document
VERSION 1.0

1 Software Units Layout, Madhapur, Hyderabad 500 081
November 2006

SFMS-CS !nterfa"e Spe"ifi"ation #o"u$ent

This is a controlled document. Unauthorised access, copying, replication and
usage for a purpose other than for which this is intended are prohibited.

DOCUMENT E!E"SE NOTICE
%oti"e %o& ' 1&0
C(ient ' !#)*
+ro,e"t ' SFMS

Document Detai#$%

Name &er$ion No' De$cription
SFMS-CS !nterfa"e Spe"ifi"ation
#o"u$ent
1&0 *his do"u$ent pro-ides the
spe"ifi"ations and pre-
re.uisites for inte/ratin/ SFMS
with CS

evi$ion Detai#$%
"ction ta(en
)a**+*e#ete+c,an-e.
/rece*in-
/a-e No'
Ne0
/a-e No'
evi$ion
De$cription

Chan/e )e/ister seria( nu$bers "o-ered'
*he do"u$ents or re-ised pa/es are sub,e"t to do"u$ent "ontro(&
+(ease 0eep the$ up-to-date usin/ the re(ease noti"es fro$ the distributor of the do"u$ent&
*hese are "onfidentia( do"u$ents& Unauthorised a""ess or "opyin/ is prohibited&

1ppro-ed by' #ate' dd-$$$-yyyy
2 3
1uthorised by' +ro,e"t Leader #ate' 44-%o--4005
2 3

T"T" C6%SUL*1%C7 S8)9!C8S /a-e iii of 12

DOCUMENT E&ISION !IST

C(ient ' !#)*
+ro,e"t ' SFMS
#o"u$ent %a$e' SFMS-CS !nterfa"e Spe"ifi"ation #o"u$ent

)e(ease %oti"e )eferen"e 2for )e(ease3' SFMS-CS !nterfa"e Spe"ifi"ation #o"u$ent -ersion 1&0

%ote' *he re-ised senten"es are $ar0ed with (eft borders&

ev'
No
evi$ion
Date
evi$ion
De$cription
/a-e
No
/rev
/a-e
No
"ction Ta(en "**en*a+
Ne0
/a-e
e#ea$e
Notice
eference

T"T" C6%SUL*1%C7 S8)9!C8S /a-e iv of 12

ABOUT THIS DOCUMENT

Purpose
This document explains step-by-step procedures to use the SFMS-CBS Interface.
Scope
This document provides the specifications and pre-requisites for SFMS-CBS Interface
on indo!s Server. "part from providin# the basic installation and confi#uration
procedures$ this document also deals !ith %e#ular Monitorin# "ctivities and user parts
of mana#in# SFMS-CBS Inte#ration on indo!s.

Intended Audience
This document is intended for the ban&'s system administrators and support
personnel. "dministrators are presumed to have sufficient operational &no!led#e of
the IBM M( Series.

Structure of this Document
1. Introduction
This chapter contains an overvie! of SFMS$ CBS and current Ban& ")I.
. Appro!ch
This chapter explains the approach for the SFMS-CBS Interface.
". Mess!#e Structures
This chapter explains the messa#e structures used for the SFMS-CBS
Interface.
$. M% Confi#ur!tions
This chapter explains the M( confi#uration details for the SFMS-CBS
Interface
&. 'e#u(!r Monitorin# Acti)ities
This chapter details the %e#ular Monitorin# "ctivities of the SFMS-CBS
Interface.
*. CBS Director+
This chapter #ives a brief introduction of the CBS IFSC *irectory usa#e.
,. CBS Mess!#e -istin#
This chapter #ives a brief introduction of the CBS Messa#e +istin#.
.. CBS 'eport
This chapter #ives a brief introduction of the CBS %eport usa#e.
/. S0MS He(pdes1
This chapter #ives details of the SFMS ,elpdes&

Mode of Distri2ution
This document and related documents !ill be placed on the I-FI-.T !ebsite.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e v of 12

A22re)i!tions !nd Acron+ms Used
Term Description
"-*B "ndhra Ban&
")I "pplication )ro#rammin# Interface
C" Certifyin# "uthority
CBS Core Ban&in# System
C-%B Canara Ban&
C%+ Certificate %evocation +ist
,TT)S Secure ,ypertext Transfer )rotocol
I*%BT
Institute for *evelopment and %esearch in Ban&in#
Technolo#y
IFSC Indian Financial System Code
I-FI-.T Indian FI-ancial -.T!or&
+*") +i#ht!ei#ht *irectory "ccess )rotocol
M( Messa#e (uery
M/% Messa#e /ser %eference
-.FT -ational .lectronic Funds Transfer
)0I )ublic 0ey Infrastructure
)I )articipant Interface
%" %e#istration "uthority
%MI %emote Method Invocation
%T1S %eal Time 1ross Settlement
SFMS Structured Financial Messa#in# System.
SM"C Server Messa#e "uthentication Code
ST) Strai#ht Throu#h )rocessin#
TCS Tata Consultancy Services
/M"C /ser Messa#e "uthentication Code
/T% /nique Transaction %eference

T"T" C6%SUL*1%C7 S8)9!C8S /a-e vi of 12

CONTENTS
1 Introduction................................................................................................
2.2 SFMS 3vervie!......................................................................................4
2.5 CBS 3vervie!........................................................................................4
2.6 Current Ban& ")I 3vervie!......................................................................4
Appro!ch..................................................................................................../
5.2 "pproach...............................................................................................7
5.5 Mandatory %equirements.......................................................................25
5.6 Messa#e Flo!.......................................................................................26
5.8 Security...............................................................................................28
" Mess!#e Structures .................................................................................1&
6.2 /ser Messa#e.......................................................................................29
6.5 "c&no!led#ement Messa#e....................................................................5:
6.6 -on-*elivery arnin# Messa#e...............................................................52
6.8 *elivery -otification Messa#e.................................................................55
6.9 3pen -otification Messa#e.....................................................................56
6.; -e#ative "c&no!led#ement Messa#e.......................................................58
6.< /ser -e#ative "c&no!led#ement Messa#e...............................................59
6.4 Ban&")I %esponse Messa#e...................................................................5;
$ M% Confi#ur!tions....................................................................................,
8.2 (ueue and Channel Confi#urations at SFMS.............................................5<
8.5 (ueue and Channel Confi#urations at CBS...............................................5<
8.6 )rocedure for creation of (ueues and Channels........................................5<
8.6.2 (ueues..........................................................................................5<
8.6.5 Channels........................................................................................54
& 'e#u(!r Monitorin# Acti)ities..................................................................."3
9.2 CBS %eceiver .......................................................................................65
9.5 %e#ister CBS........................................................................................66
9.6 .nable IFSC as CBS...............................................................................68
9.8 *elete IFSC from CBS............................................................................69
* CBS Director+..........................................................................................."*
;.2 CBS IFSC *irectory Screen *escription....................................................6;
;.5 CBS IFSC *etails Screen........................................................................6<
;.6 CBS IFSC +istin#...................................................................................6<
;.6.2 =ie! CBS IFSC *etails.....................................................................6<
;.6.5 Search...........................................................................................6<
, CBS Mess!#e -istin#.................................................................................".
<.2 SFMS to CBS Messa#es..........................................................................67
<.5 CBS to SFMS Messa#es..........................................................................82
. CBS 'eport..............................................................................................$$
/ S0MS He(pdes1........................................................................................$,
7.2 /sin# e-mail.........................................................................................8<
7.5 /sin# Telephone...................................................................................8<
7.6 SFMS 1roups in Ban&s...........................................................................8<

T"T" C6%SUL*1%C7 S8)9!C8S /a-e vii of 12

1 INT'ODUCTION
1.1 S0MS O)er)ie4
Structured Financial Messa#in# System >SFMS? is an Inter and Intra ban& messa#in#
system !ith a three-tier architecture 5,ub1ate!ayBranch Server
>3ffline@3nline?6. Some of the maAor functions and features of the SFMS areB
SFMS branch server is the source for creatin# messa#es and the SFMS 1ate!ay
and ,/B route the messa#e from one branch to another.
SFMS is a modularised and inte#rated !eb-enabled multi-layered messa#in#
soft!are that runs on the central server >,/B?$ ban& #ate!ays and online@offline
servers facilitatin# the electronic exchan#e of financial and non-financial
messa#es.
SFMS caters to the messa#e security requirements of authentication$
authorisation$ inte#rity$ privacy$ non-repudiation and &ey mana#ement.
SFMS has a !ell-defined .xternal "pplication )ro#rams Interface >")I? to send
and receive messa#es usin# Strai#ht Throu#h )rocessin# >ST)?.
)rovidin# appropriate Messa#e (uery >M(? facilities at each level.
1. CBS O)er)ie4
To 2e fi((ed 2+ CBS
1." Current B!n1 API O)er)ie4
The current ban& ")I$ based on %MI technolo#y$ is an external application interface
for le#acy ban&in# pac&a#es. This development is a part of the branch server
component for the benefit of external applications li&e Core Ban&in#$ Inte#rated
"ccountin# System >I"S? etc.
The .xternal Interface Specifications are defined in the SFMS .xternal "pplications
Specifications *ocument v 6.:.
-e! ban& ")I$ based on M( Series is defined in the subsequent sections.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 3 of 12

APP'OACH
.1 Appro!ch
The prime requirement of the SFMS-CBS Interface is to have a minimum of one
online server represented in the approach dia#ram belo!.
The SFMSCCBS interface approach is as follo!s.

2. CBS must be re#istered !ith the concerned SFMS online branch server.
5. "ll the messa#es sent from CBS must have a Sender IFSC$ .xternal Sequence
-umber D .xternal "pplication I*
6. Sender and %eceiver functionalities developed at SFMS usin# M( Series to
send@receive messa#es at SFMS areB
Sender 0unction!(it+7 This functionality constructs the messa#es meant for
Core Ban&in# Interface based on the %eceiver IFSC Code and "pplication
Identifier in a pre-defined Bloc&" and Bloc&8 format. The messa#es are stored
in the correspondin# M( (ueue connected to the CBS.
'ecei)er 0unction!(it+7 This functionality continuously polls on the M(
queue connected to the CBS and #ets the available messa#es. It also verifies
and validates the messa#es and updates the same in the SFMS database.
*urin# the verification and validation of messa#es$ the reason for failure is
returned in a pre-defined messa#e format to the correspondin# CBS.
8. CBS #ets messa#es from the SFMS in a desi#nated M( queue. There !ill be t!o
M( queues confi#ured at both SFMS and CBS. 3ne for sendin# and another for
receivin# messa#es.
9. The SFMS user messa#es should be in Bloc&" and Bloc&8 format. )lease refer to
/ser messa#e section for the format.
;. The messa#es routed from SFMS to CBS !ill be based on IFSC Code and .xternal
"pplication I*. The messa#es routed from CBS to SFMS !ill be based on the
Sender IFSC and .xternal "pplication I*.
<. " messa#e sent from CBS to SFMS can be uniquely identified usin# the
combination of Sender IFSC$ .xternal "pplication I* and Sequence number.
Similarly$ a messa#e received from SFMS to CBS can be uniquely identified usin#
the %eceiver IFSC Code$ Service Identifier and Sequence number
4. The IFSCs participatin# in CBS must be added as online branches at SFMS
1ate!ay. They must be added in the online branch server as !ell. These IFSCs
must be proliferated as functional.
7. CBS branches !ill #enerate messa#es in the SFMS format and send to SFMS
throu#h M( queue.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 4 of 12

2:. " messa#e from any external application li&e )I or from any SFMS branch meant
for CBS branches !ill flo! throu#h SFMS online server to the correspondin# CBS.
It is the responsibility of the CBS to further process the messa#e.
22. The CBS IFSC listin# is provided at the branch to vie! the IFSCs enabled as CBS.
25. The CBS messa#e listin# and CBS report is provided at the branch to vie! the
messa#es that have been sent to and received from the CBS.
NoteB
The messa#es sent@received bet!een SFMS and CBS throu#h the
queues are in strin# format.
The messa#e communication bet!een SFMS and CBS is not in
encrypted mode.
If a CBS branch is connected to the )I server as a )I client and has
been added to the SFMS branch and identified as a CBS branch as per
the current approach$ necessary chan#es need to be done at )I server
so that the messa#es !ill flo! from SFMS.
The resend option for messa#es sent to CBS$ is not provided due to
functional constraints at CBS.
In case of reAection messa#es in -.FT li&e -:6 and -:7$ CBS should be
able to handle the transactions under the messa#e as it may contain
the transactions !hich are not actually #enerated by CBS >These may
be created from the same IFSC but not throu#h CBS interface$ for
example$ Create messa#e option?

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 50 of 12

0i#ure 17 Dia-rammatic "pproac, of t,e SFMS-CBS Interface Me$$a-e Inte-ration

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 55 of 12
CNB Ban(
Core ban(in-
Interface
SFMS
CNB
On#ine
Server
M6
Connection
CNB 7ate0a8
SFMS "NDB
On#ine+
Off#ine
Server
SFMS
CNB
Off#ine
Server
"NDB
7ate0a8
T7S
/I
M6
Connectio
n
CNB
Core Ban(in- 5
CNB
CBS Branc,
CNB CBS
Branc,
CNB Ban(
Core ban(in-
Interface
M6
Connection
CNB
Core Ban(in- 2
CNB
CBS Branc,
CNB CBS
Branc,
"## fi-ure$ 0it, t,i$ co#or are M6 Connection$

. M!nd!tor+ 'e8uirements
1iven belo! are the mandatory requirements for the SFMS-CBS InterfaceB
2. The online server should be installed for the SFMS-CBS Interface.
5. The sender@receiver functionalities for the SFMS-CBS Interface should be at the
online server.
6. /M"C is mandatory for all the messa#es ori#inatin# from the CBS for Strai#ht
Throu#h )rocessin# >ST)?.
8. Incase of failures in messa#e format or certificate problems SFMS !ill send
response messa#e to the CBS. )lease refer to Messa#e Structures section for
Ban&")I response messa#e format
9. The messa#e len#th should not be #reater than 2: 0B as per the SFMS system
requirement specifications
;. SFMS !ill send ac&no!led#ement@ne#ative ac&no!led#ment$ delivery
notification$ open notification$ user -ac& and non-delivery !arnin# for the
messa#es sent by CBS dependin# on the scenario.
<. For all the user messa#es sent by the SFMS to CBS$ CBS should send a response
bac& to SFMS for updatin# the status at SFMS. The Ban&")I %esponse format !ill
be used for this purpose.
4. "ll in!ard %T1S messa#es sent by )I !ill be routed to CBS alon# !ith the /T%
and M/%.
Incase of in!ard %T1S messa#es >%7:@%:7?$ CBS has to compare !ith the
correspondin# out!ard %T1S messa#es >%82@%85? sent from CBS$ on the
basis of M/%.
Incase of In!ard %T1S messa#es >%82@%85?$ CBS has to chec& for uniqueness
on the basis of /T%.
7. Incase of -.FT messa#es flo! !ill be the same as that of the normal SFMS
messa#es.
2:. SFMS !ill validate the uniqueness of the messa#es sent by CBS on the basis of
Sender IFSC$ Sequence -umber and .xternal "pplication I* specified in Bloc&".
22. SFMS expects the messa#e in a predefined Ban&")I user messa#e format.
Messa#es that are not in the predefined format !ill be !ritten into a lo# file at
the SFMS end. Messa#es that cannot be processed at SFMS !ould also be !ritten
into a lo# file at the SFMS end.
25. 3nce the online server is enabled !ith the SFMS-CBS interface$ the SFMS
administrator should set the values for the parameters for "dmin IFSC and
default CBS. )lease refer to the E"fter Installation' section in the
%eadmeFSFMSF6.2.5 file for settin# the above parameters.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 52 of 12

." Mess!#e 0(o4
The flo! of messa#es from SFMS to CBS and vice versa is mentioned belo!.
Case 2B C-%B CBS Branch @ C-%B Core Ban&in# to %T1S )I
Messa#e flo!s from C-%B CBS Branch @ C-%B Core Ban&in# -G C-%B Core
Ban&in# Interface -G C-%B SFMS 3nline Server -G C-%B SFMS 1ate!ay -G
%T1S )I.
Case 5B %T1S )I to C-%B CBS Branch @ C-%B Core Ban&in#
Messa#e flo!s from %T1S )I -G C-%B SFMS 1ate!ay -G C-%B SFMS 3nline
Server -G C-%B Core Ban&in# Interface -G C-%B CBS Branch @ C-%B Core
Ban&in#.
Case 6B "-*B SFMS 3nline Server to C-%B CBS Branch @ C-%B Core Ban&in#
Messa#e flo!s from "-*B SFMS 3nline Server -G "-*B SFMS 1ate!ay-G SFMS
,/B -G C-%B SFMS 1ate!ay -G C-%B SFMS 3nline Server -G C-%B Core
Ban&in# Interface -G C-%B CBS Branch @ C-%B Core Ban&in#.
The vice versa is also true.
Case 8B C-%B SFMS 3ffline to C-%B CBS Branch @ C-%B Core Ban&in#
Messa#e flo!s from C-%B SFMS 3ffline -G C-%B SFMS 1ate!ay -G C-%B SFMS
3nline server -G C-%B Core Ban&in# Interface -G C-%B CBS Branch @ C-%B Core
Ban&in#.
The vice versa is also true.
Note'
If multiple CBS are confi#ured under the SFMS-CBS Interface$ the messa#e
routin# !ill be based on the external application I* specified in the messa#e.
If multiple CBS are confi#ured$ it must be ensured that one amon# them is
identified as default CBS. )lease refer to the installation procedure in the
%eadmeFSFMSF6.2.5 file for settin# the default CBS.
If IFSC is re#istered under a sin#le CBSB
"ll the user messa#es received by the branch !ill automatically be
routed to the queue correspondin# to the CBS.
If IFSC is re#istered under multiple CBSB
Messa#es received !ith the external application I* as the name of the
CBS !ill be routed to the correspondin# CBS queue.
Messa#es received !ithout any external application id !ill be routed to
the default CBS queue.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 59 of 12

Messa#es received !ith an external application id !hich does not
match the CBS names under !hich the IFSC is confi#ured !ill be routed to
the default CBS.
.$ Securit+
In SFMS !e have 5 si#natures as follo!sB
/M"C
SM"C
/M"C is #enerated on non-encrypted messa#e usin# a smart card. It fulfills user
security requirements.
SM"C is #enerated on encrypted messa#e usin# server certificate. It fulfills server-
to-server security requirements
hen a messa#e is comin# from external applications to SFMS$ it can have the user
si#nature >/M"C?. For security reasons$ SFMS uses 3pen SS+ !ith ).M format.
The messa#e structure that is bein# sent throu#h M( to the next -ode should be in
the format of Bloc&"$ Bloc&8 and /M"C >3ptional in case of -on ST)?.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 51 of 12
(o"01
(o"0 :
UM1C

" MESSA9E ST'UCTU'ES
".1 User Mess!#e
The follo!in# fields >Bloc&" of the SFMS messa#es to and from external applications?
are required for the external applications in order to #enerate a valid SFMS messa#e.
Inde: M!nd!tor+;
Option!(
0ie(d
N!me
0ie(d
-en#th
D!t!
T+pe
Description
1. M Bloc& "
Be#in
Identifier
6 Char Bloc& " Be#in Identifier should
be <A7
5. M Sender
Ban&
application
identifier
6 "lpha /niquely identifies the Ban&
application.
This is the identifier !ith
!hich ban& application is
re#istered at the branch
server.
6. M Messa#e
Identifier
6 "lpha
-umeric
"pplication Identifier
031- /ser to /ser
8. M Input@
3utput
Identifier
2 Char I@3 Identifier
O=Output
I=Input
9. M Messa#e
Type
6 "lpha
-umeric
I-FI-.T messa#e type
;. M Sub
Messa#e
Type
6 "lpha
-umeric
I-FI-.T Sub messa#e type. If
Sub Messa#e Type is blan&$
then fill !ith HHH.
<. M Sender
IFSC
22 "lpha
-umeric
IFSC code of the Sender >IFSC
code to !hich the ban&
application is re#istered.?
4. M %eceiver
IFSC
22 "lpha
-umeric
IFSC code of the receiver
7. M *elivery
-otification
Fla#
2 -umber /sers to specify !hether
delivery notification is
required for the messa#e.
1 > ?ES
> NO
2:. M 3pen
-otification
Fla#
2 -umber /sers to specify !hether open
notification is required for the
messa#e.
1 > ?ES
> NO
22. M -on-
delivery
!arnin#
fla#
2 -umber Fla# to inform the user
!hether the non-delivery
!arnin# messa#e is required
or not. The possible values

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 5: of 12

areB 1 > ?es
> No
The default value for non-
delivery !arnin# fla# is E'.
25. M 3bsolescen
ce )eriod
6 -umber /sers to specify the period
after !hich a non-delivery
!arnin# is to be sent to the
sender$ applicable only if non-
delivery !arnin# fla# is
specified.
If -on-delivery !arnin# fla# is
5$ then this value should be
set to E:::'.

If -on-delivery !arnin# fla# is
2$ then obsolescence value
should be #reater than or
equal to ::5.
%an#e of the values for this
field can be bet!een ::5 to
777.
This is represented in absolute
number of units. .ach unit is
internally interpreted as equal
to 9 minutes.
For example$ 3bsolescence
period of ::6 units is
equivalent to 29 minutes.
26. M M/%
>Messa#e
/ser
%eference?
2; "lpha
-umeric
Ban& "pplication uses this
field for identifyin# the
messa#e. If it is less than 2;
then concatenate !ith H.
28. M )ossible
*uplicate
.mission
Fla#
2 -umber Fla# to indicate possible
duplicate emission
1 > ?ES
> NO
29. M Service
Identifier
6 "lpha *estination Ban& "pplication
identifier.
If not applicable$ it should be
defaulted to HHH.
2;. M 3ri#inatin#
date
4 -umber *ate on !hich the messa#e
!as created at Ban&
application C >????MMDD?
2<. M 3ri#inatin#
time
8 -umber Time on !hich the messa#e
!as created at Ban&
application C>HHMM?
24. M Testin# and 2 -umber Fla# to indicate test and

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 56 of 12

Trainin#
fla#
trainin# messa#e.
1 > ?ES
> NO
27. M Sequence
-umber
7 -umber /nique sequence number
#eneration by the external
application for the
identification of the messa#e
in external application system.
System messa#es for the user
messa#es #enerated by
external applications !ill carry
this sequence number. SFMS
")I reAects the messa#e if
there is no sequence number.
.xB If sequence number is 9
then user should send the
sequence number as
E::::::::9'
5:. M Filler 7 "lpha
-umeric
Filler for future use and
default value is HHHHHHHHH.
52. M /T%
>/nique
Transaction
%eference?
2; "lpha
-umeric
/nique Transaction %eference
1enerated for %T1S. ,ost
applications should default it
to HHHHHHHHHHHHHHHH
55. M )riority Fla# 5 -umber )riority fla# is used for routin#
the messa#es in %T1S
messa#es. For ,ost
applications the default value
is 77
56. M Bloc&" .nd
Identifier
2 Char Bloc&" .nd identifier should
be @
58. M Bloc&8
Be#in
Identifier
6 "lpha
-umeric
Bloc&8 be#in identifier should
be
<$7
59. M Bloc&8 "lpha
-umeric
Text bloc& of the messa#e.
+en#th of the messa#e cannot
exceed 2: 0B.
5;. M Bloc&8 .nd
Identifier
5 Char Bloc&8 .nd identifier should
be =@
5<. 3 Bloc&9"
Be#in
Identifier
; Char If the ban& application can
#enerate the /M"C then this
should be <UMAC7
If the ban& application does
not have the capability to
prepare the si#nature$ this
field can be left blan&.
54. 3 Bloc& 9" "lpha
-umeric
"uthoriser Si#nature. This is
an optional field$ !hich can be
filled by Ban& applications
!ith si#nature prepared in
)0CS< standard on B(oc1$
Inform!tion.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 52 of 12

field can be left blan&. If this
field is blan& the messa#es
!ill be forced to be in
I).-*I-1 "/T,3%IS"TI3-J
state in SFMS 3ffline@Branch
Server.
57. 3 Bloc&9"
.nd
Identifier
2 Char If the ban& application can
#enerate the /M"C then this
should be @
field can be left blan&.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 53 of 12

.xample for the incomin# messa#e structure to the SFMS branch server from the
ban& application is sho!n belo!B
K"BCBSF:232::HHHSBI-:::2::2SBI-:::2::5225::9abcdef#h25689;<45HHH5::6
:7:72:5:5::::25689HHHHHHHHHHHHHHHHHHHHHHHHHH77LK8B
B 5:BTT@65:
B65"B5::6:7:7I-%2::$
-L
K/M"CBMSi#natureGL
K"B Bloc& " be#in Identifier
CBS Ban& "pplication Identifier
F:2 Messa#e Identifier
3 Input@output Identifier >either I or 3?
2:: Messa#e type
HHH Sub Messa#e type >For IF- 574C:2$ this
field should be C:2$ for IF-2::
Messa#e$ this field should be HHH?.
SBI-:::2::2 Sender IFSC Code
SBI-:::2::5 .nd receiver IFSC Code
2 *elivery notification fla#
2 3pen -otification fla#
5 -on-delivery arnin# fla#
::9 3bsolescence )eriod
abcdef#h25689;<4 Messa#e /ser %eference >M/%?
5 )ossible *uplicate fla#
HHH Service Identifier
5::6:7:7 3ri#inatin# date
2:5: 3ri#inatin# time
5 Testin# and trainin# fla#
::::25689 Sequence -umber
HHHHHHHHHH Filler
HHHHHHHHHHHHHHHH /nique Transaction %eference.
77 )riority Fla#
L
Bloc& " end Identifier
K8B Bloc& 8 Be#in Identifier
B 5:BTT@65: Bloc& 8 text messa#e format
B65"B5::6:7:7I-%2::$
-L Bloc& 8 .nd Identifier
K/M"CB Bloc& 9" Be#in Identifier
MSi#natureG /ser Si#nature for "uthorisation
L Bloc& 9" .nd Identifier

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 54 of 12

". Ac1no4(ed#ement Mess!#e
1iven belo! are the fields in the ac&no!led#ement messa#e sent by SFMS to CBS
Inde: M!nd!tor+;
Option!(
0ie(d N!me 0ie(d
-en#th
D!t!
T+pe
Description
2 M Bloc&
Identifier
6 Char Bloc& Identifier
5 M Ban&
"pplication
Identifier
6 "lpha Ban& "pplication Identifier
6 M Messa#e
Identifier
6 "lpha
-umeric
Messa#e Identifier
F5: C "c&no!led#ement
Messa#e
8 M Input@3utput
Identifier
2 Char Input@3utput Identifier
I > Input
O > Output
9 M Sequence
number
7 -umber .xternal "pplication
Sequence -umber for !hich
this ac&no!led#ement is
intended.
; M Sender IFSC 22 "lpha
-umeric
IFSC code of 3ri#inatin#
SFMS branch.
< M *ate and
Time
25 -umber *ate and Time on !hich
messa#e is ac&no!led#ed
8 M Bloc& .nd
Identifier
2 Char Bloc& .nd Identifier
" sample ac&no!led#ement messa#e is #iven belo!B
K"BCBSF5:3:::::2:::SBI-:::2::25::<:6:62659L
K"B Bloc& Identifier
F5: "c&no!led#ment messa#e
3 Input@3utput Identifier
:::::2::: .xternal "pplication Sequence -umber
SBI-:::2::2 3ri#inatin# IFSC
5::<:6:62659 *ate and time on !hich the sender SFMS 1ate!ay
ac&no!led#es messa#e
L Bloc& .nd Identifier

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 20 of 12

"." Non=De(i)er+ A!rnin# Mess!#e
1iven belo! are the fields in the non-delivery !arnin# messa#e sent by SFMS to
CBS.
Inde: M!nd!tor+;
Option!(
0ie(d
N!me
0ie(d
-en#th
D!t!
T+pe
Description
2 M Bloc&
Identifier
5 M Ban&
application
Identifier
6 Char Ban& "pplication Identifier
6 M Messa#e
Identifier
6 "lpha
-umeric
Messa#e Identifier
F55 - -on-delivery arnin#
messa#e
8 M Input@3utp
ut
Identifier
I > Input
O = Output
9 M Sequence
number
7 -umber .xternal "pplication Sequence
-umber.
< M Sender
IFSC
22 "lpha
-umeric
IFSC code of 3ri#inatin# SFMS
branch.
4 M *ate and
Time
25 -umeric *ate and Time at !hich non-
delivery !arnin# messa#e is
#enerated.
7 M Bloc& .nd
Identifier
" sample non-delivery !arnin# messa#e is #iven belo!B
K"BCBSF553:::::2:::SBI-:::2::25::<:2:2555<L
F55 -on-delivery arnin# Messa#e
:::::2::: Creation sequence number of the messa#e
SBI-:::2::2 3ri#inatin# IFSC
5::<:2:2555< *ate and time on !hich non-delivery !arnin# messa#e
is #enerated.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 25 of 12

".$ De(i)er+ Notific!tion Mess!#e
1iven belo! are the fields in the delivery notification messa#e sent by SFMS to CBS.
Inde: M!nd!tor+;
Option!(
0ie(d
N!me
0ie(d
-en#th
D!t!
T+pe
Description
2 M Bloc&
Identifier
5 M Ban&
applicatio
n
Identifier
6 M Messa#e
Identifier
6 "lpha
-umeric
Messa#e Identifier
F56 - *elivery -otification
messa#e
8 M Input@3ut
put
Identifier
I > Input
O > Output
9 M Sequence
number
7 -umber .xternal "pplication sequence
number
; M Sender
IFSC
22 "lpha
-umeric
branch.
< M *ate and
Time
25 -umber *ate and time on !hich the
messa#e is delivered.
4 M Bloc& .nd
Identifier
" sample delivery notification messa#e is #iven belo!B
K"BCBSF563:::::2:::SBI-:::2::25::<:2:2555<L
F56 *elivery -otification Messa#e
SBI-:::2::2 IFSC code of the ori#inatin# SFMS branch.
5::<:2:2555< *ate and time on !hich the messa#e is
delivered.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 22 of 12

".& Open Notific!tion Mess!#e
1iven belo! are the fields in the open notification messa#e sent by SFMS to CBS.
Inde: M!nd!tor+;
Option!(
0ie(d
N!me
0ie(d
-en#th
D!t!
T+pe
Description
2 M Bloc&
Identifier
5 M Ban&
application
Identifier
6 "lpha
Numeri
c
Ban& "pplication Identifier
6 M Messa#e
Identifier
6 "lpha
-umeric
Messa#e Identifier
F58 - 3pen -otification
messa#e
8 M Input@3utp
ut
Identifier
I > Input
O > Output
9 M Sequence
number
7 -umber .xternal "pplication sequence
number
; M Sender
IFSC
22 "lpha
-umeric
branch.
< M *ate and
Time
25 -umber *ate and time on !hich the
messa#e is opened at
destination.
4 M Bloc& .nd
Identifier
" sample open notification messa#e is #iven belo!B
K"BCBSF583:::::2:::SBI-:::2::25::<:2:42<6:L
F58 3pen -otification Messa#e
SBI-:::2::2 IFSC code of 3ri#inatin# SFMS branch.
5::<:2:42<6: *ate and time on !hich messa#e is opened.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 29 of 12

".* Ne#!ti)e Ac1no4(ed#ement Mess!#e
1iven belo! are the fields in the ne#ative ac&no!led#ement messa#e sent by SFMS
to CBS.
Inde: M!nd!tor+;
Option!(
0ie(d
N!me
0ie(d
-en#th
D!t!
T+pe
Description
2 M Bloc&
Identifier
5 M Ban&
"pplicatio
n
Identifier
6 M Messa#e
Identifier
6 "lpha
numeric
Messa#e Identifier
F59--e#ative
"c&no!led#ement
8 M Input@3ut
put
Identifier
I=Input
O = Output
9 M Sequence
-umber
-umber
; M Sender
IFSC
22 "lpha
-umeric
IFSC of ori#inatin# SFMS
branch
< M *ate and
Time
25 -umber *ate and Time
M .rror code 8 -umber %eason code for -"C&
7 M Filler 7 "lpha
-umeric
Filler for future /se
2: M Bloc& .nd
Identifier
" sample ne#ative ac&no!led#ement messa#e is #iven belo!B
K"BCBSF593:::::2:::SBI-::::::25::<:6:6265952:9HHHHHHHHHL
F59 -e#ative "c&no!led#ment messa#e
I Input@3utput Identifier
SBI-::::::2 3ri#inatin# IFSC
5::<:6:62659 *ate and time on !hich the sender SFMS #ate!ay ne#atively
ac&no!led#ed the messa#e
52:9 .rror occurred !hile creatin# )0CSN< structure
HHHHHHHHH Filler for future use

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 21 of 12

"., User Ne#!ti)e Ac1no4(ed#ement Mess!#e
1iven belo! are the fields in the user ne#ative ac&no!led#ement messa#e sent by
SFMS to CBS.
Inde: M!nd!tor+;
Option!(
0ie(d
N!me
0ie(d
-en#t
h
D!t!
T+pe
Description
2 M Bloc&
Identifier
5 M Ban&
"pplication
Identifier
6 M Messa#e
Identifier
6 "lpha
numeric
Messa#e Identifier
F5;-/ser -"c& Messa#e
8 M Input@3utp
ut Identifier
I=Input
O=Output
9 M Sequence
-umber
-umber
; M Sender
IFSC
22 "lpha
-umeric
branch
< M *ate and
Time
4 M .rror code 8 -umber ill be empty for /na&
messa#e
2: M Filler 7 "lpha
-umeric
22 M Bloc& .nd
Identifier
" sample user ne#ative ac&no!led#ement messa#e is #iven belo!B
K"BCBSF5;3:::::2:::SBI-::::::25::<:6:62659HHHHHHHHHHHHHL
F5; /ser -ac& Messa#e
SBI-::::::2 IFSC code of 3ri#inatin# SFMS branch
5::<:6:62659 *ate and time on !hich the messa#e #ot user nac&ed
HHHH .rror Code !ill be empty for /na& messa#e
HHHHHHHHH Filler for future use

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 2: of 12

".. B!n1API 'esponse Mess!#e
1iven belo! are the fields in the Ban&")I response messa#e exchan#ed bet!een
SFMS to CBS.
Inde: M!nd!tor+;
Option!(
0ie(d
N!me
0ie(d
-en#th
D!t!
T+pe
Description
2 M Bloc&
Identifier
5 M Ban&
"pplicatio
n
Identifier
6 M Messa#e
Identifier
6 "lpha
numeric
Messa#e Identifier
F5<-Ban& ")I %esponse
Messa#e
8 M Input@3ut
put
Identifier
I=Input
O=Output
9 M Sequence
-umber
-umber
; M Sender
IFSC
22 "lpha
-umeric
branch
< M *ate and
Time
4 M Ban&")I
%esponse
Code
22 "lpha
-umeric
Ban&")I %esponse Code
2: M Bloc& .nd
Identifier
5 "lpha
-umeric
22 M Bloc& .nd
Identifier
" Sample ban&api response messa#e is #iven belo!
K"B CBSF5<I:::::2:::SBI-::::::55::<:6:62659)B")I::::::HHL
CBS Ban& "pplication Identifier OBan& "pplication Identifier in case
the response is for out#oin# user messa#e and service identifier
in case the response is for incomin# user messa#eP
F5< Ban& ")I %esponse Messa#e
SBI-::::::5 IFSC code of 3ri#inatin# SFMS branch OSender IFSC in case of
an out#oin# messa#e and %eceiver IFSC in case of incomin#
messa#eP
5::<:6:62659 *ate and time of the response messa#e
)B")I:::::: Ban& ")I %esponse code
HH Filler for future /se

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 26 of 12

$ M% CON0I9U'ATIONS
This chapter describes the various types of queue and channel confi#urations at
SFMS and CBS.
$.1 %ueue !nd Ch!nne( Confi#ur!tions !t S0MS
This section describes the queue and channel confi#urations to be done at SFMS end.
Create the follo!in# queues and channels under SFMS branch queue mana#er
M% O2Bects O2Bect N!me
+ocal (ueue SFMS.I-C3MI-1
%emote (ueue CBS.I-C3MI-1
Transmission (ueue (ueue Mana#er name of
CBS
Sender Channel SFMS.T3.CBS
%eceiver Channel CBS.T3.SFMS
The %emote (ueue for SFMS is CBS.I-C3MI-1$ provided the "pplication I* is CBS.
)lease refer to section 8.6 for more details on the procedure for creation of queues
and channels
$. %ueue !nd Ch!nne( Confi#ur!tions !t CBS
This section describes the queue and channel confi#urations to be done at CBS end.
M% O2Bects O2Bect N!me
+ocal (ueue CBS.I-C3MI-1
%emote (ueue SFMS.I-C3MI-1
Transmission (ueue (ueue Mana#er name of
SFMS Branch
Sender Channel CBS.T3.SFMS
%eceiver Channel SFMS.T3.CBS
The +ocal (ueue for CBS is CBS.I-C3MI-1$ provided the "pplication I* is CBS.
)lease refer to section 8.6 for more details on the procedure for creation of queues
and channels
$." Procedure for cre!tion of %ueues !nd Ch!nne(s
$.".1 %ueues
To create different (ueues$ follo! the path usin# M( .xplorer.
Conso(e 'oot Ae2Sphere M% %ueue M!n!#ers %ueues
$.".1.1 -oc!( %ueue
To create +ocal (ueueB

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 22 of 12

2. %i#ht-Clic& on %ueues Ne4 -oc!( %ueue.
5. 1ive the (ueue name$ description$ default persistence as Persistent
and usa#e as Norm!(.
$.".1. Tr!nsmission %ueue
To create Transmission (ueue
2. %i#ht-Clic& on %ueues Ne4 -oc!( %ueue.
5. 1ive the (ueue name >this !ill be the name of the CBS queue
mana#er?$ description$ default persistence as Persistent and usa#e as
Tr!nsmission.
$.".1." 'emote %ueue
To create %emote (ueue
2. %i#ht-Clic& on %ueues Ne4 'emote %ueue Definition.
5. 1ive the (ueue name$ description$ default persistence as Persistent$
remote queue name$ remote queue mana#er name$ and transmission queue
name.
$.". Ch!nne(s
To create different Channels$ follo! the path usin# M( .xplorer.
Conso(e 'oot Ae2Sphere M% %ueue M!n!#ers C8ueue m!n!#er
n!meD Ad)!nced Ch!nne(s.
$."..1 Sender Ch!nne(
To create Sender Channel
2. %i#ht-Clic& on Ch!nne(s Ne4 Sender Ch!nne(.
5. 1ive the channel name$ description$ connection name >exB
E2<5.2;.5.256>2828?' IP Address of the CBS to !hich you are connectin#.?$
and transmission queue name in 9ener!( tab.
6. In E:tended tab$ disconnect interval is set to 3 !nd B!tch siEe is set
to 1.
8. Clic& OF button to create the Sender ch!nne(.
$.".. 'ecei)er Ch!nne(
To create %eceiver Channel
2. %i#ht-Clic& on Ch!nne(s Ne4 'ecei)er Ch!nne(.
5. In 9ener!( tab #ive the channel name$ description.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 23 of 12

6. In E:tended tab B!tch siEe is set to 1.
8. Clic& 30 button to create the 'ecei)er ch!nne(.
NoteB The 'ecei)er ch!nne( name should be same as Sender Ch!nne(
name at the 'emote %ueue M!n!#er.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 24 of 12

& 'E9U-A' MONITO'IN9 ACTIGITIES
This chapter describes the re#ular monitorin# activities to be performed by the SFMS
administrator.
E"dmin Interface' is a 1raphical /ser Interface >1/I? developed for facilitatin# the
system administrators in monitorin# various services essential to SFMS.

Follo!in# are the steps to lo#in to the E"dmin Interface'B
2. Clic& on the EAdmin S0MS' shortcut icon on the des&top.
" dialo# box promptin# for User Id and P!ss4ord appears as sho!n in
Fi#ure 5.
5. .nter the User Id as S0MSB' and P!ss4ord as S0MS.
In order to ensure security and restrict unauthoriQed access to the system$ the SFMS
"dmin lo#in pass!ord can be chan#ed by the desi#nated system administrators once
the SFMS is installed.
0i#ure 7 S0MS Admin -o#in
The administrator #ains access to the follo!in# essential services of SFMS once
lo##ed inB
Tomcat
%eports Scheduler
Sender
%eceiver
Sender SFT
%eceiver SFT
File /pload
File *o!nload
CBS %eceiver
These services should al!ays be runnin# to access SFMS. These services can be
started by clic&in# the EStart' button a#ainst the respective services under Start
/p@Shut *o!n tab as sho!n in fi#ure 6. )lease refer SFMS 3nline Manual for the
details of services that need to be runnin# to access SFMS.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 90 of 12

0i#ure "7 S0MS Administr!tion Br!nch
"dmin interface contains different tabs as follo!sB
St!rtUp;ShutDo4n
To start and shutdo!n services.
Monitor
*isplays the user status.
B!c1 up
)rocedures for ta&in# bac&up of database and M( lo#s
P!r!meter
Facilitates definin# and alterin# file locations for File /pload and File *o!nload
at the branch. It also facilitates chan#in# SFMS "dmin pass!ord D database
pass!ord. It should be noted that the "dmin and database pass!ords are
one and the same. It also facilitates chan#es in the &ey value of parameters

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 95 of 12

such as chan#e of archive period$ session timeout etc.$ >This is also same as
the database pass!ord?.
&.1 CBS 'ecei)er
1iven belo! are the various approaches to start the CBS %eceiver serviceB
2. Select St!rtUp;ShutDo4n tab in admin interface and clic& on ESt!rt' button
a#ainst CBS %eceiver.
5. The process can also be started by usin# the follo!in# command at command
prompt.
C7HDB!)! sfms2r.2!n1!pi.'ecei)erCBS
This method is required !hen the above process started from the admin tool is
terminated due to some error.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 92 of 12

&. 'e#ister CBS
1iven belo! are the steps to re#ister the external applicationB
2. Select CBS tab in admin interface.
5. Select 'e#ister CBS tab.
6. .nter E.xternal "pp' and EConfirm .xt "pp' fields.
8. Clic& on %e#ister Button to %e#ister the .xternal "pp
9. The .xternal "pp re#isters successfully
NoteB 3nce a ne! CBS is re#istered$ the necessary queue confi#urations needs to be
completed to establish the connectivity bet!een SFMS and CBS. )lease refer to M(
Confi#urations section for the steps to be follo!ed. SFMS "dministration !indo!
needs to be restarted once a ne! CBS is re#istered.
0i#ure $7 S0MS Administr!tion Br!nch

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 99 of 12

&." En!2(e I0SC !s CBS
1iven belo! are the steps to enable IFSC as CBSB
2. Select CBS tab in admin interface
5. Select En!2(e I0SC !s CBS tab
6. Select any CBS from the drop do!n control >For Sin#le CBS it is not required?
8. Select any SFMS IFSC from the list box on the left.
9. Clic& on En!2(e !s CBS button to .nable IFSC as CBS
;. -o! the SFMS IFSC !ill be enabled as CBS
0i#ure &7 S0MS Administr!tion Br!nch

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 91 of 12

&.$ De(ete I0SC from CBS
1iven belo! are the steps to delete IFSC from CBSB
2. Select CBS tab in admin interface
5. Select De(ete I0SC from CBS tab
6. .nter EIFSC' and EConfirm IFSC' fields
8. Select any CBS from the drop do!n control >For Sin#le CBS it is not required?
9. Clic& on De(ete Button to delete IFSC from CBS
;. The IFSC !ill be deleted from CBS successfully
0i#ure *7 S0MS Administr!tion Br!nch

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 9: of 12

* CBS DI'ECTO'?
This chapter describes the CBS directory provided in the SFMS for chec&in# the
details of IFSCs enabled under CBS.
*.1 CBS I0SC Director+ Screen Description
+o#in to SFMS and clic& the lin&s Director+-G CBS I0SC -istin# to vie! the CBS
IFSC *irectory screen. /sin# the CBS IFSC *irectory screen you can perform a
search and vie! CBS IFSC details. The screen appears as follo!sB
-oteB The CBS IFSC *irectory screen can be accessed only at branch node
0i#ure ,7 CBS I0SC Director+
The CBS IFSC *irectory screen displays the follo!in# columnsB
Item Description
I0SC 3pens the IFSC *etails screen$ once IFSC is clic&ed
B!n1 *isplays the ban& name
Br!nch *isplays the branch name
Cit+ *isplays the city in !hich branch located
Address *isplays the address of the branch
E:t App *isplays the .xternal "pplication name
Se!rch On "llo!s criterion selection on !hich the search is based. The drop-do!n list

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 96 of 12

displays the follo!in#B
IFSC
Branch
City
.xt "pp
G!(ue "llo!s you to enter a value for the selected search criterion
Clic& to proceed !ith the search
*. CBS I0SC Det!i(s Screen
Clic& any entry in the IFSC column on the CBS IFSC *irectory screen to open the
CBS IFSC *etails screen. The IFSC *etails screen displays the follo!in#B
Item Description
IFSC *isplays IFSC in all modes. This field cannot be modified
Ban& -ame Field$ max 69 alphanumeric characters
Branch -ame Field$ max 69 alphanumeric characters
City Field$ max 29 alphanumeric characters
"ddress Field$ max 2:: alphanumeric characters
/ser I* /ser I* of the /ser !ho has authorised this IFSC's )roliferation messa#e.
*." CBS I0SC -istin#
+o#in to SFMS and Clic& the lin&s Director+=D CBS I0SC (istin# to vie! the CBS
IFSC *irectory screen. /sin# the CBS IFSC *irectory screen you can perform the
follo!in# tas&sB
=ie! CBS IFSC *etails
Search
*.".1 Gie4 CBS I0SC Det!i(s
3n the CBS IFSC *irectory screen$ clic& an IFSC to open the CBS IFSC *etails
screen.
*.". Se!rch
1iven belo! are the steps to perform the searchB
2. Select the search criteria on the CBS IFSC *irectory screen.
5. .nter the search value.
6. Clic& .

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 92 of 12

, CBS MESSA9E -ISTIN9
This chapter describes messa#e listin# for the messa#es sent@received from CBS.
This includes the messa#e sent from CBS to SFMS and vice versa.
The CBS Messa#es screen is as follo!sB
0i#ure .7 S0MS CBS Mess!#es Screen
+o#in to SFMS and Clic& the lin&s Messa#e %outin# -G CBS Messa#es menu to vie!
the follo!in#B
SFMS to CBS Messa#es
CBS to SFMS Messa#es.
NoteB If the lo##ed in IFSC is a CBS "dmin$ then the user !ill be able to vie! all the
messa#es sent@received from all the IFSCs under CBS. 3ther!ise the vie! !ill
display only messa#es related to the lo##ed in CBS IFSC.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 93 of 12

,.1 S0MS to CBS Mess!#es
This section describes the listin# of the messa#es sent from SFMS to CBS
0i#ure /7 S0MS TO CBS Mess!#e -istin#
The above screen depicts the listin# if the lo##ed in IFSC is CBS "dmin

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 94 of 12

0i#ure 137 S0MS TO CBS Mess!#e -istin#
The above screen shot depicts the listin# if the lo##ed in IFSC is a normal IFSC.
+o#in to SFMS and Clic& the lin&s Mess!#e 'outin# =DCBS Mess!#es =DS0MS to
CBS Mess!#es to open the messa#es from SFMS to CBS screen. 1iven belo! are
the tas&s that can be performed in this screenB
)erform Search
=ie! messa#e Status
The screen consists of the follo!in# fields and buttons:
Item *escription
Se!rch On Select a parameter to start a search based on the
parameter in the drop-do!n list.
G!(ue *rop-do!n list or text box$ dependin# upon the search
on parameter selected. +ists the criteria available for the
selected parameter. Select a criterion or enter the value
Se!rch
Clic& to proceed !ith the search

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 10 of 12

The Search function is available on all messa#es from SFMS to CBS. /sin# this
function$ you can perform searches based on a parameter selected from the Search
3n list.
The follo!in# table describes the list options available on the Search 3n listB
Item Description
E:t Se8uence Num2er Text field$ max of nine di#its. .nter the number.
S0MS Se8uence Num2er Text field$ max of nine di#its. .nter number.
Sender I0SC Text field$ max of 22 characters. .nter the Sender IFSC
'ecei)er I0SC

Text field$ max of 22 characters. .nter the %eceiver
IFSC >This field is visible only to CBS "dmin IFSC?
E:t App ID Text field$ three characters.
'ecei)ed On *rop-do!n lists for the date >yyyymmdd?
,. CBS to S0MS Mess!#es
This section describes the listin# of the messa#es sent from CBS to SFMS
0i#ure 117 CBS TO S0MS Mess!#e -istin#
The above screen depicts the listin# if the IFSC lo##ed in as CBS "dmin

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 15 of 12

0i#ure 17 CBS TO S0MS Mess!#e -istin#
The above screen shot depicts the listin# if the lo##ed in IFSC is a normal IFSC
Clic& Mess!#e 'outin# =D CBS Mess!#es =DCBS to S0MS Mess!#es to open the
messa#es from CBS to SFMS screen. 1iven belo! are the tas&s that can be
performed in this screenB
)erform Search
=ie! messa#e Status
The screen consists of the follo!in# fields and buttons:
Item Description
Se!rch On *rop-do!n list. Select a parameter to start a search based on the
parameter
G!(ue *rop-do!n list or text box$ dependin# upon the Search 3n parameter
selected. +ists the criteria available for the selected parameter. Select
a criterion or enter the value
Se!rch
Clic& to proceed !ith the Search

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 12 of 12

The Search function is available on all Messa#es from CBS to SFMS. /sin# this
function you can perform searches based on a parameter selected from the Search
3n list.
The follo!in# table describes the list options available in the Search 3n listB
Item Description
E:t Se8uence Num2er Text field$ max of nine di#its. .nter the number.
S0MS Se8uence Num2er Text Field$ max of nine di#its. .nter number.
Sender I0SC Text field$ max of 22 characters. .nter the Sender IFSC
>This field is visible only to CBS "dmin IFSC?
'ecei)er I0SC Text field$ max of 22 characters. .nter the %eceiver
IFSC
St!tus !t S0MS *rop-do!n list. Select the Messa#e Status
E:t App ID Text field. Three characters.
Cre!ted On *rop-do!n lists for the date >yyyymmdd?

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 19 of 12

. CBS 'EPO'T
The CBS %eport contains information of the CBS messa#es sent@received from your
node durin# a specified period. The selection of IFSC is simplified by providin# the
text box and IFSC Button to select the IFSC's as sho!n in the screen belo!.
2. +o#in to SFMS and Clic& the lin&s 'eports=DDem!nd 'eports.
0i#ure 1"7 Dem!nd 'eports in S0MS
5. Specify the follo!in#B
Item Description
'eport T+pe *rop-do!n list. Select CBS %eport
E:t App Id *rop-do!n list$ Select .xt "pp Id
IFSC The IFSC !hose report has to be
#enerated. If the IFSC is not
selected$ then the report !ill be
#enerated for all the IFSCs
Period /se the date list boxes to specify
the start and end dates of the
period for the report

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 11 of 12

6. Clic& to #enerate a report.
The report consists of the follo!in# informationB
Serial -umber
.xt Seq -o
SFMS Seq -o
In-3ut Indicator
Messa#e Type
Sender IFSC
%eceiver IFSC
Messa#e Status
%eceived 3n
Bloc& 8
8. To print the report$ in the %eport pop-up !indo!$ clic& 0i(e=DPrint. >3r )ress
CtrlRp?
0i#ure 1$7 S!mp(e CBS 'eport
NoteB If the lo##ed in IFSC is a CBS "dmin$ then the user !ill be able to vie! all the
messa#es sent@received from all the IFSCs under CBS. 3ther!ise the vie! !ill
display only the messa#es related to the lo##ed in CBS IFSC.

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 1: of 12


T"T" C6%SUL*1%C7 S8)9!C8S /a-e 16 of 12

/ S0MS HE-PDESF
SFMS ,elp *es& is mana#ed by TCS @ I*%BT at I*%BT$ ,yderabad. The 1ate!ay
"dministrators$ )roAect Mana#ers and other officials$ !ho !ant to utilise the services
of SFMS ,elp *es&$ should follo! the procedure #iven belo!B
/.1 Usin# e=m!i(
The users may send mails to sfmshelpSidrbt.ac.in to report problems and see&
#uidance of SFMS ,elp *es&. The e-mail could also be used to follo! up any call
already lo##ed in and@or if there is need to send an attachment to the ,elp *es&. In
such a case$ the E%equest -o' of call must be quoted in the mail.
/. Usin# Te(ephone
The users should try to avoid lo##in# in the help des& calls on telephone unless this
is absolutely necessary and ur#ent. In any case$ the users should first send e-mail
and then call on telephone in case of ur#ency. The telephone number allotted to
SFMS ,elp *es& mana#ed by TCS is 3$3="&"&1.* and I*%BT SFMS 1roup can be
reached on 3$3="&"$/.1=.$ E:t7 &1$;1&
/." S0MS 9roups in B!n1s
Ban&s should arran#e to form an SFMS 1roup$ preferably at the 1ate!ay location.
The #roup may consist of the 1ate!ay "dministrator and other officials mana#in#
SFMS !ithin the ban&. These officials should re#ister as members and all the calls
should be routed throu#h this #roup only$ in order to maintain continuity.
TTT .nd of the document TTT

T"T" C6%SUL*1%C7 S8)9!C8S /a-e 12 of 12

SFMS-CBS Interface Specification Document Summary

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SFMS-CBS Interface Specification Document Summary

Enviado por

Direitos autorais:

Formatos disponíveis

INSTITUTE FOR DEVELOPMENT AND RESEARCH

Você também pode gostar