Pages

Thursday, October 20, 2016

New Change In BO Account Opening In Sub Offices.

We are all aware that RICT is coming soon. Very Soon all BO will be given RICT Devices in which all transactions will be carried out. As a part of this method while opening a new account in RICT machines, a unique number will be generated. This unique number we have to enter while opening account at Sub office.

Since all offices are not yet migrated to RICT, Finacle will throw a warning message.

“RICT Unique number is not entered. Do you want to proceed”

This is only warning message and the root cause of the message is due to deployment of new patch in the production server.
The details of the patch which was deployed in production server is as below.

The field RICT unique number is for entering the unique number generated in RICT device while opening of new accounts (SB / RD / TD). So, while opening new accounts, if BO is selected, then the warning message mentioned above will be displayed and the offices can skip this by selection YES option if RSI FSI rollout has not happened.

In future after implementation of RICT while opening the BO accounts in SO/HO we need to enter the unique number generated in RICT device at BO level.

Note :-

In finacle we generally get the 3 different kind of messages in general while doing finacle operations they are mentioned below.

1. Warning message
2. Exception message
3. Error message

Generally warning message code will start with 'W'

Exception message code will start with'ED'

Error message code will start with 'E'.

In finacle generally we can ignore warning and exceptions in general and we can proceed the transaction even system will allow to proceed the transactions.

But when we get Error message the system will not allow to proceed further as this will occur when we perform the transaction against the DOP rulings or if there is any issue in the system.

Hence if there is any error message immediately report to the respective CPC with latest error screenshots and detailed description for the solution.

No comments:

Post a Comment