Hyderabad structured Financial Messaging System Frequently Asked Question Prepared By: Jaurkar Mangesh & sfmshelpDesk idrbt




Дата канвертавання18.04.2016
Памер199.56 Kb.


Institute for Development and Research in Banking Technology

HYDERABAD

Structured Financial Messaging System

Frequently Asked Question


Prepared By:

Jaurkar Mangesh & SFMSHelpDesk

IDRBT

June 2007

Confidential and controlled document.

Unauthorised access or copying is prohibited.


TABLE OF CONTENTS

1. SFMS Gateway /Online /Offline Branch FAQ ‘s …………………………….. 3


2. NEFT FAQ ‘s ………………………………………………………………………23


FAQ's for SFMS Gateway/Online/Offline Server

  Sno.

  FAQ 

  Solution 

Common Issues

1 )

Error Code : USLG026022 - Security verification unsuccessful

  1. Check that the correct Certificate name is selected during login into SFMS Application / Certificate select is Invalid / Expired / Check system date is set correctly .if problem persists Contact SFMS Helpdesk.

  2. Please check the URL typed in the Browser whether the URL is pointing the Brach Server/Gateway ( OR ) If the URL is correct, Kindly ensure that the User is already registered into the SFMS Application( OR ) Kindly ensure that the User ID and IFSC Code are correct. Kindly note that the User ID is case sensitive

2)

Facing performance problem at SFMS Gateway and Online Branch,
Message flow is slow at branch server.

1. To Improve the performance please check the following :
a ) Check whether every week or 15 days (depend on message volume) archiving is taking place via Report scheduler, Report scheduler at Gateway /Online Branch and NEFT Archive process should be kept running after day end, this process do the archiving of all old messages from the database.(refer the archival back topic in respective manuals)
Set up the archival period and time in configuration file to set up the parameters refer the below files
At Gateway config file is : SFMS\jakarta-tomcat-3.2.3\webapps\SFMSGW\WEB-INF\classes\sfmsgw\coms\core\utils\SFMSConfGW.properties
Check and set the parameter :

ARCHIVE_PERIOD=15

Above parameter is to set number of days

ARCHIVE_SCHDLR_TIME=1900


For online branch config file is : SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\coms\core\utils\SFMSConf.properties
ARCHIVE_PERIOD=10

Above parameter is to set number of days

ARCHIVE_SCHDLR_TIME=1830

Above parameter is to set archival time


For NEFT config file : SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\neft\config\NEFTAppConf.properties
ARCHIVE_TIME=1800

ARCHIVE_PERIOD=15




  1. Secondly administrator need to take archival back up from admin tool of SFMS Gateway/Branch and NEFT every 15days or every week depending on the message volume

  2. See that every 15 days or every month Database reorganization activity is carried out for SFMS database




  1. DBA must fine tune all database parameters to get the optimum performance and better utilization of resource’s

  2. Good Amount of free space need to be maintained on the Database Drive and Application Drive




3 )

The page cannot be displayed’ during Login to SFMS

Cause :

1) If the Servlet engine is down i.e. TOMCAT is stopped

2) IIS web server / SFMS Website is down

3) Jakarta configuration under SFMS website is corrupted



Corrective action :

1) Check TOMCAT service is running State , if the service is stopped start the tomcat from the SFMS Admin tool / Or from the command prompt by typing the command tomcat run

2) Check under IIS service >> Default Website is in running state, if the website is stopped select the Default website right click and start.

3)Check under IIS >>Default website >> Jakarta folder under SFMS website , if the Jakarta folder is corrupt showing red dot select the folder and delete it

To Reconfigure Jakarta first delete the Jakarta folder present under list of ‘Default website’ now insert SFMS Offline v3.0 CD in to the CD Drive and double click CRTSFMS.exe file present within the CD


4 )

During Login to SFMS Application via browser getting error message ‘User Already Connected ‘

Cause :

When the old session of the user is running at the server



Corrective action :

User needs to disconnect his session at the server.

To do this open SFMSAdminBR tool ,select Monitor Tab >> enter User id and IFSC click the Get Status Button and remove disconnect Tick Mark from the check box and click button again to Get status .


5 )

SFMS Screen Appears unusual, text matter and text box’s are Disturbed

Cause :

Screen resolution is not as per the SFMS requirements



Corrective action :

Check the desktop resolution – Right Click on Desktop >> select properties >> click on Advance Tab >> Check the pixel as 1024 x 768 pixels



6)

In Side Sender and Receiver processes getting following Alert

There are some Failed Outgoing/Incoming Messages in the Application for gateway(s) XXXXXXXXXXX, Kindly process them”


XXXXXXXXXXX represents the IFSC Code(s)

Cause :

Some messages Failed during Incoming /Outgoing due some or the other reason , this alert can be on gateway or at branch


Corrective Action :

Login into SFMS Browser Application and navigate to Message  Failed Messages Incoming Messages  Kindly look into the Reason and understand the cause for failure And Reprocess the Message after taking the corrective action.

Incase the problem persists, kindly take a screenshot before and after clicking on the Failed Incoming message and send the screenshots along with log files from the location :\SFMSLog\log to SFMS Helpdesk


7)

Failed Messages menu is not displayed under Message menu in the SFMS Application

Failed Message Processing privilege might not have been assigned to the User who has logged in
Corrective Action:

Login in to the SFMS Application as a Super Card User and navigate to User Administration  Role Profile  Open the Role Profile of the User with whom the problem is occurring  Click on the Modify  select the Failed Message Processing option  click on Save  Now logout from the SFMS Application (if the User is already logged in) and then login again and check whether the Failed Message Link is displayed Under Message



8

An alert window with the message “New Message Received will be displayed on the server where SFMS is installed.

The alert window is displayed on the Server where SFMS is installed on receipt of a new message including system and proliferation messages.

The count value will be increased when the new message received, provided the alert window is not closed. In case the alert window is closed, the alert window will be displayed again when the New Message is received.



9

Status is not changing to Acknowledged or Delivered

Possible cause s :

  1. First confirm that Sender and receiver processes are running fine aon the server, Gateway and at the next node

  2. In Gateway server -- confirm sender and receiver MQ channel are in the running state

  3. In case of Offline branch checkup with the Network conntivity

  4. Check in the Failed Message Listing for failure of Outgoing message

10

Message Status is NAK / Negative Acknowledgment

Cause:

NAK stand for Negative Acknowledgment, it occurs if the authorizer certificate is expired /server certificates are wrong or expired or message has been tampered /systems Date/time set are wrong



Corrective Action

Open the message and click on the Reason for Negative Acknowledgement and take corrective action based upon the Reason Code.


If the problem still persists, send the screenshots before and after opening the message and the Reason for failure to SFMS HelpDesk.


General Errors

Note 1

A password users account will be LOCKED when the password user performs three unsuccessful attempts with improper password to login to the application. The status of the user will be changed to LOCKED and such user can be enabled again only by a Smart Card User

Note 2

At Gateway :Whenever the server certificate of Gateway is expired, the Gateway has to obtain the new server certificates and the new server certificates should be placed in the sendercertificates folder at the Gateway and the Gateway encryption certificate should be placed in the recipientcertificates folder at all the Branches and also in HUB.

11

AT Gateway : Broadcast / Multicast Message sent did not reached the destination branches

Broadcast message has to be authorized by gateway Administrator at the gateway.

At Gateway:

To authorize the message, go to the broadcast listing and click on incoming messages and click on Authorize button


12

Message is in ‘To be Sent’ state for long time


Cause : a . Sender receiver processes are stopped

b. MQ ‘Sender Channel’ from branch to Gateway may be down (in Inactive/Stopped/Retrying state) c. The Message may be failed state



13

While drafting SFMS message tabbing out the Amount field getting Alert message “Amount allowed is 1000”

Cause :

User drafting the financial message is not allowed to create the message more then INR 1000 ,



Corrective action :

To Allow user for creating message more then 1000, Goto >>User Administration menu>> select Group Profile >>Currency Group >> select the group >>click modify button >>now change the Amount limit in front of INR

14

After Installation of SFMS Offline, I find only one IFSC listed in the Directory List /IFSC list

After the installation of an Offline server, there will only one IFSC listed under the IFSC list, User first need to send one test message to the listed Active IFSC and get the Delivery notification to confirm offline installation is perfect

Then send the branch details( i.e IFSC,Branch Name ,Address, City ) to the Gateway Admin for proliferation Once Branch is proliferated SFMS user should open the SFMS Admin tool >>goto Offline Connectivity  Tab>>Click Update button , this step will update the complete IFSC directory list ( updation will take around half hour ),

Before proliferation branch can send Intra bank messages and After proliferation branch is enabled to send Inter bank messages.


15

After Authorizing the message status at the branch remains in ‘To_Be_Sent /Send status.

Status is not changing to Acknowledged or Delivery



First confirm that Sender and receiver processes are running fine at the branch, Gateway and at the destination branch (recipient branch) .

In case message status won’t change then ones Logout and login and then check the message status



In Online server -- confirm sender and receiver MQ channel are in the running state  

16

Under the Header part of the SFMS Application it is showing Test,Test,Test ?

Also Under directory / listing menu it is showing bank, branch, city and address as Test ?



For a freshly installed offline server it appear as test,

Once branch details are proliferated at IDRBT HUB, status at branch change to Bank Name, branch name ,and city .

To proliferate the branch details, place the request to your Gateway admin with the following details

IFSC


Bank Name

Branch Name

Branch Address

City Name

And properties file

After branch IFSC is proliferated then click the Update button present under the SFMSAdmin Tool under Offline Connectivity Tab



17)

Received messages once printed it does’t appear in the list of incoming messages?

Once the message is printed its status will change as Printed and to view the messages follow the steps listed below.

1) Go to Message -> Incoming Messages.

2) In incoming messages in search on  Message Status.

3) In Value tab select PRINTED.

Click on search button. This will list all the printed messages.


18)

During uninstallation of Third party software for SFMS Ver 3.0 ending abruptly by stating that " Installer terminated prematurely"

Corrective action :

 1. First step is to remove the ThirdParty software from the Add and Remove programs present under the Control panel, if any error message pops up during uninstallation then simply restart the system

2. Remove the path related SFMS,Mysql,MQClient,jdk1.3.1 from the Classpath and path present within the Environmental variables of the System

2. Delete folder SFMS, myql,Mysql drivers, Mqclient, jdk1.3.1,JRE folder and all other folders belonging to SFMS and third party from C drive

3. Restart the system and proceed with the installation as per the manual


19)

During installtion of an SFMS v.3.0 Offline Software getting Error 1722

Corrective action :

1.First check that Offline installation is carried out at C drive(Windows Default Drive) and  check <IFSC>.properties file is correctly placed in C: Drive .

2. Check Machine is having an IP address set, if not set up the IP to the machine and proceed with installation


  1. If problem continue then remove the path related to SFMS (Path starting with C:\SFMS\.. )from the Path and Classpath from the  Environmental variables

  2. Remove the my.ini file from the c:\WINNT drive

5. If problem continues do not clicking Ok to the Error message goto command prompt and type following command

c:.\> java CheckIFSC c:\SFMS

Send the complete snap shot of error to sfmshelp@idrbt.ac.in



20)

Message Status is NAK / Negative Acknowledgment

NAK stand for Negative Acknowledgment, it happen if the authorizer certificate is expired /server certificates are wrong or expired or message has been tampered /systems Date/time set are wrong

Open the message and click the for the Reason code.



21)

Broadcast / Multicast Message sent did not reached the destination branches

First broadcast message have to be authorized by gateway Administrator at the gateway, then the message will reach the specified destination branches

At Gateway:

To authorize the message, go to the broadcast listing and click on incoming messages and click on Authorize button.



Note 3

1. While registering the User, if the serial number is in seven characters remove the initial zeros and the space and enter the remaining four characters without any space in capital , That means, if the serial number is displayed as 0093 8B, enter 938B only while registering that User into the SFMS Application.
2. If there is considerable decrease in performance, set the Debug level in SFMS Admin to false and steps are mentioned below: Go to Admin tool -> Parameter tab -> Key value tab -> select SFMSDEBUG (flag) against the Parameter and set the new value as false (if Old value is true) ->click on save button.

22)

Getting an General Exception Error in receiver Process at the Offline server. // Illegal status of the message

Cause :

There are different reason to get “General exception” Error message,

One of the reason is if Offline server is reinstalled.

Corrective action :
Send the complete Screen shot of the Error message and latest SFMSlog files present under c:\SFMS\SFMSLog\logs\ at sfmshelpdesk , Before sending follow the given steps :
1) Go to Admin tool -> Parameter tab -> Key value tab -> select SFMSDEBUG (flag) against the Parameter and set the new value as true (if Old value is false) -> click on save button.

After setting the above variables ,now again restart all the processes and Zip and send the log files from location :\SFMSLog\log using winzip and the screen shot of the error .

 Mail the zip file to sfmshelp@idrbt.ac.in

Note: Please revert back the changes after sending us the log files.

One of the Precautionary measure to Avoid the problem:

At SFMS Server keep daily/ alternate or as per the bank policy Database backup using SFMS Admin tool.

Incase Offline server is reinstalled then it’s important to restore the Backup file and set the last Message Sequence number using Admin tool , Goto Admin tool >>Click Parameter Tab >>select Sequencenum tab >> insert the new Sequence number ( Suppose last message Seq. no. send was 46 then you need to reset the new sequence number as 47 , to know the last message seq no contact your gateway Admin)

Steps to restore backup file is as follow 


  1. Open the Command prompt

  2. At command prompt type:

C:\> mysql –u SFMS -pSFMS

Mysql>use sfms

Mysql>source 

Where as to restore backup under oracle database with help of DB Administrator.



23 )

During Login to SFMS via browser, one may face the Error message “An ActiveX control on this page is not safe. Your current security settings prohibit running unsafe controls on this page. As a result, this page may not display as intended.”

Cause :

Internet Explorer Settings are not done.



Corrective action :

Check for the Internet explorer Settings – Set up properties of Internet Explorer as given in User manual.



24 )

During initiating Sender Or Receiver processes, one may face the error message "Security Exception occured" // similar type of error related to Security / certificates

Cause :

Error comes up if the server certificates are not present in necessary folder / certificates have expired / certificates are corrupt / certificates replaced by wrong set of certificates / system date/time is incorrect



Corrective action :

1) Make sure that server certificates are present under the respective folder as per the manual i.e. sender certificates should be placed at \SFMS\common\com\sendercertificates

2) See that receivers certificates are present at the following path \SFMS\common\com\recipientcertificates

3) More details given below:

Branch Server signing, encryption -- public and private keys* to be copied to:[INSTALLDIR]\SFMS\common\com\sendercertificates directory.

* These keys refer to the following:

IFSC0000123.cer (signing public key)

IFSC0000123.key (signing private key)

IFSC0000123enc.cer (encryption public key)

IFSC0000123enc.key (encryption private key)

(Please note that these are examples only – where IFSC refers to Bank Code and 0123 to the Branch Code.)

b) Gateway encryption public key** to be copied to: [INSTALLDIR]\SFMS\common\com\receipientcertificates

**IFSCenc.cer is the example for the Gateway encryption public key, where IFSC refers to Bank Code.

Note:-


  1. The IDRBT CA certificate (ie., CACert.cer) will be automatically loaded by the software during installation in the following directory: [INSTALLDIR] \ SFMS\ ommon\ com\CAcertificates directory.

  2. Also Check weather System Date and time are set as current date and tiem.

Websphere MQ Errors

25 )

MQ Exception error Code 2059 / 2009 with Completion code 2.

Cause : Error is because of network outage / unable to establish Connection to Gateway, Reason is because of the Network Outage server is unable to communicate to the gateway

Corrective action :

1) Check up for the proper network connectivity between the branch and Gateway

2) Check SFMS MQ manager at gateway is in running state and port at which SFMS MQ Manager set is Open at the gateway

(Confirm the MQ Manager port number from gateway admin, usually port number is 1417 )

To test the connectivity between branch and gateway run following command from the Offline server at the command prompt :

C:\>ping -t  <GWIPaddress>

Example c:/> ping -t 10.0.67.116 . If ping command is working fine with out Request time out then check branch is able to telnet the Gateway IP

C:\>telnet   <GWIPaddress> 1417

3. If both above command fails contact Network admin/Network provider

4. If network is fine then check the following parameter in SFMSConf.properties file, 

        a) SFMSConf.properties file present at the following path in branch server :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-        INF\classes\sfmsbr\coms\core\utils


        b) Open the file with notepad >> Search for the Parameter HOSTNAME and confirm the  IP address(Gateway IP) present against the HOSTNAME
HOSTNAME=
       c) If HOSTNAME does not have the ipaddress of the gateway then change IP address of the Gateway and save the file. And now restart the processes and check

d) If problem continues contact Gateway Admin



26 )

Getting MQ Exception Error Reason 2085 ( This error occurs only at Gateway )

Cause :

This Exception occurs if any Offline branch queues (OFFL /SFTQ ) is missing / Second reason is because of receiving the message at gateway for the IFSC that is not present in Gateways database.



Corrective action :

Contact Helpdesk with latest SFMSlog files and error screen shot.



27 )

Facing MQ Exception error Reason Code 2053 ( Error occurs only at Gateway )

Cause :

When excess messages accumulated under the offline Queues(.OFFL) at Gateway , then the application throw the MQ Exception Error 2053 at gateway  



Corrective action :

(Imp Note :Carry out below procedure only under the presence of the IBM MQ Expert )

First Make the SFMS Debug level true under the SFMS Gateway Admin tool , now start the Receiver processes and note the Queue Name i.e. .OFFL

And now ask the respective IFSC branch in-charge to start up the sender and receiver process at the branch to bring down the Queue depth Or Identify the queue whose depth is above 5000 under SFMS Gateway queue manager[By default the queues under SFMS have a maximum depth up to 5000]

Now open the MQ Manager and select the particular Queue right Click select its properties >>click Extended Tab>>Increase the Maximum Queue Depth size to higher value , this step need to carried out only under the supervision of the MQ Expert. 




National Electronic Funds Transfer

Frequently Asked Questions

1.1.1What are the steps to be followed to configure the new Service-Center-IFSC in NEFT application?

Please do the following to configure the new Service Center IFSC in NEFT application:



    1. Stop all NEFT and SFMS processes including Tomcat

    2. Change the NEFT_IFSC to the new IFSC in :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\coms\core\utils\SFMSConf.properties file. This step needs to be done in all the offline branches if any

    3. Change the APPIFSC to the new IFSC in :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\neft\config\NEFTAppConf.properties file

    4. Register the external application EFT in the new IFSC as mentioned in section 8 of the NEFT Installation Manual attached

    5. Login to NEFT Admin and navigate to Parameter tab --> Bank API Parameter tab and change the Password to the one set in step d. Check that the Bank Identifier, Bank IFSC are populated with EFT and the new IFSC respectively

    6. Update the Service Center IFSC with the new IFSC in END_ENC_CERT_DTLS table. Contact SFMS Helpdesk for the same.

    7. Inform RBI about the new Service Center IFSC so that the necessary changes can be done at RBI also



1.1.2What are the steps to be followed when the physical IP address of the Service Center needs to be changed?

Please do the following to change the physical IP of the NEFT Server:



    1. When the queue depth of all the following queues becomes ZERO, stop the Sender Channels at Gateway (----GW.TO.----BR) and Branch (----BR.TO.----GW).


Under Branch QManager:

-----------------------------------------

----BRQ  (Local queue)

----BRSFTQ  (Local queue)

----GWQM (Transmission queue)

 

Under Gateway QManager:

-----------------------------------------

HOST.INCOMING  (Local queue)

----GWQ (Local queue)

----GWSFTQ (Local queue)

----BRQM (Transmission queue)

PI QManager (Transmission queue) --> this exists only when your bank interacts with RTGS.




    1. Change the IP address in the Sender Channels as mentioned below:

Right click on the Sender Channel of Branch (----BR.TO.----GW)-->select Properties --->Change the IP address to the new IP in  Connection Name field.

 

Right click on the Sender Channel of Gateway (----GW.TO.----BR)-->select Properties --->Change the IP address to the new IP in  Connection Name field.




    1. Change the IP in DB_URL of NEFTDBConfiguration.properties at location :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\neft\config

    2. Change the IP in DBURL of SFMSConf.properties at location :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\coms\core\utils

    3. Change the IP in DBURL of SFMSConfGW.properties at location :\SFMS\jakarta-tomcat-3.2.3\webapps\SFMSGW\WEB-INF\classes\sfmsgw\coms\core\utils

    4. Change the IP in SERVERIP of BankAPIConfig.properties at location :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\coms\core\utils.

Copy the same properties file to location :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\bankapi
Note: Substitute ---- with the four-character bank code

1.1.3What should I do when the error “ora-00020 Error: Maximum number of processes exceeded” occurs?

Set the following database parameters as shown below in NEFT database in SP File:


processes 1000

sessions 3000

open_cursors 9000

1.1.4How do I place my bank logo in SFMS / NEFT application?

Name the bank logo gif file as <4-digit bank code>.gif and place the same in :\SFMS\SFMS_HTML\IMAGES folder.

For example, to place the IndusInd bank logo, the gif file name should be INDB.gif as the bank code of IndusInd is INDB.

1.1.5Under RAS, dynamic IP is allocated by the RAS to the machine while connecting it to gateway. As a result there is no fixed IP of the SFMS PC. While applying NEFT patch in this PC, it is difficult to ascertain the IP of the machine, which is required to be written in BankAPIConfig.properties file. What should I do?

Please give the hostname in place of IP address.


1.1.6When does the T + 1 error occur in NEFT/SFMS?

When you try to reject the inward credit after T+1 business days then the T+1 error occurs.



1.1.7How do I create NEFT users in Service Center?

Refer to section 3 (Creation of NEFT User in SFMS) of NEFT Installation Manual.



1.1.8When a message is uploaded in SFMS, does it need to be verified and authorized or does it only need to be authorized?

You only need to authorize the message. You can authorize upto 100 messages at a time.



1.1.9What is scenario 1,2 and 3 in the context of database cleanup at the time of migration from Test to Live?



Scenario1:

  1. Bank didn’t have an online branch server before and has installed the same only for NEFT

  2. The bank has just 2 branches (one normal branch and one service center) in the online branch server and both the branches have just participated in NEFT testing

  3. The whole data from the SFMS database can be cleaned up.


Scenario2:

    1. Bank already has an online branch server before NEFT pilot testing

    2. Bank has created new IFSCs for service center and for the branch for creating and receiving NEFT messages

    3. Bank has used these new IFSCs only for NEFT testing

    4. The data from these new IFSCs in SFMS database can be cleaned up.


Scenario3:

          1. Bank already has an online branch server before NEFT pilot testing

          2. Bank has used already existing IFSCs, which were used for sending SFMS and RTGS messages, for NEFT testing.

          3. The NEFT message data from these IFSCs, used for NEFT testing, can be cleaned up.



1.1.10What is batch time and cut-off time? Which should be earlier?

Batch-time is the actual batch (time) that is declared by RBI to be used in NEFT settlements.

Cut-off time is the time at which flow of outward messages should stop at Service Center for that particular Batch-time. Every batch-time has an associated cut-off time. It is recommended that the banks keep the cut-off time at least 15 minutes earlier than the batch-time.
For example, the cut-off time of 1200 batch should be 1145 or earlier.

1.1.11Are intra-bank transactions supported in NEFT?

Yes. Intra-bank transactions are supported in NEFT.



1.1.12Are intra-branch transactions supported in NEFT?

No. Intra-branch transactions are not supported in NEFT. They need to be handled in the CBS.



1.1.13What is an Acknowledgement, Non-delivery warning, Delivery notification and Open notification message?



Acknowledgement Message: Acknowledgement message is received when a user message sent from a branch (node) is received at the next node, which is the bank's Gateway. When the sending branch receives the Acknowledgement message, the status of the outgoing message is updated to 'Acknowledged'.
Non-delivery Warning Message: A Non Delivery Warning is sent by the Gateway to the sending branch if the delivery notification is not received for a message in a stipulated time. The time can be specified in the units of 3 minutes
Delivery Notification Message: The recipient branch sends Delivery Notification message when it receives the message. When the sending branch receives the Delivery Notification from the recipient, the status of the outgoing message is updated to 'Delivered'.
Open Notification Message: An Open Notification is a message that is released from the recipient branch when the user opens the message received. When the Open Notification is received at the sending branch, the status of the outgoing message is updated to 'Opened'.

1.1.14What is the difference between a Return message and a Rejection message?

A return (298N07) message is created to return a credit received.

A rejection (298N03/298N09) message is created by the NEFT application when the Outward

Debit/return message fails some validations. 298N09 is created at NEFT Service Center and 298N03 at the RBI NEFT Center.


1.1.15What are the possible types of inward messages, which would be received through NEFT system?

Following are the incoming messages received by the service center/branch from RBI

1. 298N02 - Inward Credits

2. 298N03 - Rejection/Reschedule Transactions

3. 298N04 - EOB/EOD message

4. 298N08 - Nil Transaction message (This is received only up to the service center)


Following are the incoming messages received by a branch from Service center

1. 298N02 - Inward Credits

2. 298N03 - Rejection/Reschedule information from RBI

3. 298N04 - EOB/EOD message

4. 298N09 - Rejection/Reschedule information from SC

1.1.16What is the implication of N09 message and action to be taken by core-banking application on receipt of it?

A 298N09 message is sent by the service center when an outward debit transaction is rescheduled or rejected at service center. The information about whether a transaction is rejected or rescheduled can be found from the rejection code present in the message. Please refer to the list of rejection codes at Service Center. If the rejection code is 101 or 107 or 108 then that means the transaction is rescheduled and still live at the service center. If the rejection code is anything other than the three mentioned above then the transaction is rejected.

In case the transaction is rejected at Service Center then the transaction must be either resent after correction or reversed back in the core banking application

1.1.17What are the possible rejection/reschedule codes at the Service Center? Give details.




Sl. No.

Code

Description

Rescheduled (Yes /No)

Remarks



101

LATE ARRIVAL AT SC FOR THE BATCH SPECIFIED or

RECEIVED AFTER THE LAST BATCH FOR THE DAY



Yes

The N09 is sent to the sending branch but the transactions are still live in Service Center and don’t need to be resent.



102

INVALID SENDER BANK IFSC

No

The N09 is sent to the sending branch. The transactions rejected need to be resent after correction.



103

SENDER OR BENEFICIARY IFSC CAN NOT BE SC IFSC

No

The N09 is sent to the sending branch. The transactions rejected need to be resent after correction.



104

SENDER BANK AND BENEFICIARY BANK ARE SAME

No

The N09 is sent to the sending branch. The transactions rejected need to be resent after correction.



105

BATCH ID IS INACTIVE AT SC

No

The N09 is sent to the sending branch. The transactions rejected need to be resent after correction.



106

AMOUNT IS ZERO AT NEFT SC

No

The N09 is sent to the sending branch. The transactions rejected need to be resent after correction.



107

PAST VALUE DATE AT NEFT SC

Yes

The N09 is sent to the sending branch but the transactions are still live in Service Center and don’t need to be resent.



108

HOLIDAY AT NEFT SC

Yes

The N09 is sent to the sending branch but the transactions are still live in Service Center and don’t need to be resent.



109

DUPLICATE TRANSACTION NUMBER AT SC

No

The N09 is sent to the sending branch. The transactions rejected need to be resent after correction.



110

BENEFICIARY BANK CAN NOT BE RBI NEFT CENTER

No

The N09 is sent to the sending branch. The transactions rejected need to be resent after correction.



111

DUPLICATE RELATED REFERANCE NUMBER

No

A N09 message is sent back to the branch with the information about rejection of the transaction of type N07 for next available batch



1.1.18Can service center send and receive NEFT transactions?

No. NEFT service centre branch is a dummy branch for NEFT transactions. No transactions can be sent or received from/to that branch. But the service centre branch can participate in other messaging applications (like RTGS).


1.1.19When does a bank receive 298N08 message?

298N08 message is received from RBI only when there are no inward credits for a bank in a particular batch. This message is received only up to the service center and is not sent to branch.


1.1.20What are the possible rejection/reschedule codes at the RBI NEFT Center? Give details.





Sl. No.

Code

Description

Rescheduled (Yes /No)

Remarks



092

SENDER OR BENEFICIARY BANK NOT PARTICIPANT OF NEFT

No

The N03 is sent up to the sending branch. The transactions rejected need to be resent after correction.



093

BATCH DOES NOT EXISTS AT RBI

No

The N03 is sent up to the sending branch. The transactions rejected need to be resent after correction.



094

THIS BATCH DOES NOT EXISTS ON SATURDAY

Yes

The N03 is sent up to the sending branch but the transactions are still live at RBI and don’t need to be resent.



095

DUPLICATE TRANSACTION NUMBER AT RBI

No

The N03 is sent up to the sending branch. The transactions rejected need to be resent after correction.



096

BENEFICIARY BANK IFSC IS SERVICE BRANCH

No

The N03 is sent up to the sending branch. The transactions rejected need to be resent after correction.



097

AMOUNT IS ZERO AT RBI

No

The N03 is sent up to the sending branch. The transactions rejected need to be resent after correction.



098

HOLIDAY AT RBI

Yes

The N03 is sent up to the sending branch but the transactions are still live at RBI and don’t need to be resent.



099

PAST VALUE DATE AT RBI

Yes

The N03 is sent up to the sending branch but the transactions are still live at RBI and don’t need to be resent.



100

NETTING IS COMPLETED FOR THIS BATCH

Yes

The N03 is sent up to the sending branch but the transactions are still live at RBI and don’t need to be resent.

1.1.21 “Connection refused to host: ” error occurred while starting Bank API Server. What should I do?

Please check the following:



    1. The SERVERIP is given correctly (as the Service Center IP) in BankAPIConfig.properties file in the following folders:

      1. :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\coms\core\utils

      2. :\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\bankapi




    1. If the SERVERIP is given correctly in step 1, please check if some other process is using the Bank API port (the port mentioned in BankAPI.bat), using the Tcpview utility. If the port is busy, please do either of the following:

      1. Kill the process that is using the Bank API port if possible, and restart the Bank API Server and NEFT processes

OR

      1. Change the Bank API port in BankAPI.bat and NEFTAppConf.properties file (both RECEIVER_RMI_PORT_NUMBER and SENDER_RMI_PORT_NUMBER) and then restart the Bank API Server, NEFT processes



1.1.22When is a transaction rescheduled in NEFT?

A transaction can be rescheduled at the Service Center or/and RBI NEFT Center.



At the Service Center:

  1. When a transaction is sent for say 1030 batch (batch time is put at the sending branch) and the transaction is received after the cut-off time of 1030 batch i.e. 1015. Then the transaction will be rescheduled to the next available batch on the same day.

  2. When a transaction is received at the service center after the last batch cut-off time then the transaction will be rescheduled to the next day first batch.

  3. An N09 message will be sent back to the sender branch when a transaction is rescheduled at the Service Center


At the RBI NEFT Center:

  1. When a transaction is received after the netting is done for a batch say 1030, then the transaction will be rescheduled to the next available batch on the same day.

  2. When a transaction is received after the netting is done for the last batch of the day then the transaction will be rescheduled to the next day first batch.

  3. An N03 message will be sent back to the service center (and from service center to the sending branch) when a transaction is rescheduled at the RBI NEFT Center.

1.1.23 To activate NEFT at SFMS Branch (offline or online)

Please follow the steps given below to make the offline server NEFT enabled.

1.Open the SFMSConf.properties file located at

:\SFMS\jakarta-tomcat-3.2.3\webapps\ROOT\WEB-INF\classes\sfmsbr\coms\core\utils

2.Change the values of the following properties as given below.

 

NEFT_REPORT=true

NEFT_ENABLE=true
NEFT_IFSC=

 

3.Restart the tomcat server and All SFMS Processes


1.1.24Where can I find the NEFT User manual on IDRBT site?

You can refer the NEFT user manual, which is uploaded on the IDRBT web site given below.

 http://www.idrbt.ac.in/index_fromsm.html?sfms.html?infinet

 

On this web page under SFMS->Manuals you will find NEFT User and Operations Manuals


1.1.25What will be the structure of ASCII report output when all the fields are selected while generating the report?


Following is the ASCII report structure when all the fields are selected while generating the report.

Field Name

Data Type (Length)

Message Type

Char (9)

Amount

Char (19) including decimal point

Message Sender Reference

Char (32)

Date of Batch

Char (8)

Batch Time

Char (4)

Benf. Branch

Char (11)

Benf. A/C Num

Char (35)

Benf. A/C Name

Char (50)

Sender Branch

Char (11)

Sender A/C Num

Char (35)

Sender A/C Name

Char (50)

Transaction Ref Num

Char (16)




For more information Or want to contribute any other information please write us at sfmshelp@idrbt.ac.in
Or reach us at (040)23535186 / 23533857. Board Numbers: (040)
23534981 -984 Ext.5214/ 5215





База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка