TABLE OF CONTENTS
1. Configurations and Process
1.1. Desktop Setting (
Browser setting, Security settings, JRE version etc.)
For the Finacle CBS application, the
configuration details are specified in the below attached zip file.
1.2. Printer Setting
(Passbook)
For the proper printing of the
passbook, the Passbook Printer needs to be configured as per the below
specified document.
1.3. ATM Process
document and PIN Management
Please see below the word document for the
complete ATM Process and its PIN management.
text incomplete in above boxes
1.4. E-Banking Password
Printing and PIN Printing
Please see below the word
document for the complete E-Banking password and PIN printing.
2. Common Issues
2.1. Passbook not printing
2.1.1. Name of
the office or the customer address being
printed wrongly in Passbook
Issue Reported : For.e.g It is reported by the counter
PA at Srikakulam HO, the name of the PostOffice in the passbook front page
is showing as SRIKALAHAS, ANDHRA PRADESH, INDIA, 532001. instead of SRIKAKULAM,
ANDHRA PRADESH, INDIA, 532001.
Solution: Check the city
code linked to the address of the Post office or the customer address. Then
validate the city code description in the menu HRRCDM. Either the HRRCDM city
code in the customer's address / Post office address has to be changed in the
address details or the description of the particular code has to be changed in
HRRCDM menu.
HRRCDM access is given to DOP Operations team to maintain the details.
2.1.2. Passbook
not enabled at the account level
Solution: The passbook is not enabled at the
account level. The same has to be modified at the account level for passbook
printing.
For PPF account, the menu HACM has
to be used for modification of the field A/C statement in the General Details
tab.
For SCSCC accounts, the menus
CSCAM/SCSSMAV to be used
For MIS accounts, the menus CMISAM/MISAMAV to be used
2.2. Signature related
errors
2.2.1. Signature
view issues due to desktop settings not proper
Solution: Please check the desktop settings
and then try viewing the signature.
2.2.2. Signature
view issues due to access not provided
Solution: The issue is present due to the
access not provided to the particular user. The changes have to done in the
user creation by modifying the USER GROUP NAME to ADMIN
User to contact the DOP Operations
team to get the issue rectified.
2.2.3. Signature/photograph
view issue
Error
Screen shot
Solution
Check for the
signature view from other user id and other location, preferably DOP Operations
Team. Issue may be with the desktop settings. The above issue is not occurring
for the below user id as per the screenshot attached.
Solution Screenshot
2.2.4. Signature
view issues - Steps to identify the exact issue
Issue Reported : Signature is not displayed
Solution: The signature not displayed might
be due to several factors like
·
Desktop
Setting not done properly ]
·
Access
not given to the user. ] Explained in 1.2.1 ,1.2.2 and 1.2.3 above
·
Signature
not uploaded properly
If signature is not uploaded in
Finacle, system will show the below details:
·
Signature
not migrated due to huge size.
Any signatures present in Sanchay Post database which is above 30kb size
shall be dropped while migrating in Finacle. After the data upload, as a part
of the recon details, Infosys shall provide the details of signatures dropped
during upload. POs need to ensure that when the customer whose signtaure is
dropped comes to the PO, fresh signature mandate is captured using a new 'account opening form' and customer's transaction
is allowed based on the fresh signature mandate. POs to ensure that the account
opening form is clearly identified by writing 'Signature mandate' on top of
first page of the form . They should also clearly mention the CIF id and
account number on the form. The form shall be sent to CPC for scanning and
upload of signature in Finacle.
2.9. Issues in Clearing
2.9.1. Inward
clearing issues – Duplicate instrument
Solution
In all such cases, the instrument has to be
modified or marked as reject in the inward
clearing
process. Attaching the document with the
step by step process.
2.9.2. Instrument
is post dated
Solution
In
such cases, the below step by step process has to be followed
1.
Invoke HMICZ , select function as 'Revoke Suspension' and
enter the zone code
2.
In HICTM menu, select modify function and click on Go.
3.
Next screen click on Accept
4.
The next screen shows the records which has the post
dated instrument date. Modify the record with the proper instrument date and
submit
5.
Verify through another user
6.
Invoke HMICZ and suspend the zone.
7.
Invoke HMICZ and run 'Validation run' and 'Validation
report'
8.
Invoke HMICZ and Post the zone
9.
Invoke HMICZ and close the zone
2.9.3. Instrument
type is invalid for scheme
Solution
The
account 0025387513 belongs to the scheme code SBGEN, hence the issue. The
instrument type CHQ is not valid for this scheme code. If the cheque number in
invalid then also this error is thrown. The account entered here should belong
to the scheme type SBCHQ.
2.9.4. How to
change from SBGEN to SBCHQ if it is a cheque
account and migrated as SBGEN and how to enter available blank cheque numbers?
Transfer the account to SBCHQ using the menu
HACXFRSC and issue the cheques via HICHBA menu.
HACXFRSC Menu Screen shot.
2.9.5. Outward
Clearing Issue - Sort code not present for a particular bank and branch combination
Issue Reported : When we
lodge the Outward Cheques for clearing the sortcodes related to the concerned
cheques ( Nasirabad Bank Branch Codes ) are not being accepted by the
software.So How will we enter the Bank Branch related sortcodes without
having any Bank code in search option for that particular Branch of Bank.
Kindly arrange the all Bank related Codes Or some other solution for
feeding.
Solution
Sort code means MICR Code.
1.The
cheque can be lodged under the sort code of the 'service branch' of the same
bank, if that code is available in Finacle
is it
mandatory to select Service Branch Code? Can any other branch code of same bank
available in data base be selected?
Answer:
Any valid sort code can be selected.
2.If
the sort code of the service branch ( main branch that participates in clearing
for that bank ) is not available, then please use the menu HBRTM to add the
missing sort code as per the attached document.
HBRTM
manu has not been given to post office. This solution to be executed by DOP CBS
Operational Team only.
3.
Once the above is done, cheques can be lodged in outward clearing.
2.9.6. Process
of handling RBI Circular intimating about a new Bank & Branch:
Circular from RBI intimating about any new bank
shall be received at the local SO/HO. The SO/HO need to forward the said
circular to the DOP Operations team which shall create the new Bank code in the menu option
HBKTM and the new branch code in HBRTM. The MICR city code bank code and branch
code as entioned in the RBI circular shall need to be input during branch code
creation.
In case the Bank is already is in Finacle CBS
(by confirming through Inquiry mode in
HBKTM) - a branch code has to be created in HBRTM.
The naming convention of the bank / branch code is to have the MICR branch
code itself.
For DOP CBS Operational Team only.
2.9.7. How to
handle Outstation Cheque in Finacle?
Use HIRM menu and follow below mentioned
steps:-
1. Invoke
the menu HIRM.
2. The
details of the cheque and the account number has to be keyed in using the Lodge
option.
3. Finacle
will automatically collect the collection charges.
4. Verification
should be done for the lodged cheque.
5. Send
the cheque physically to the outstation location.
6. If the
cheque is cleared - intimation coming from outstation location - the Realize
function needs to be invoked in HIRM menu and submitted.
7. If the
cheque is dishonoured - the dishonour function to be invoked and submitted in
HIRM menu option.
2.9.8. What is
the procedure for outstation ' AT PAR' cheques. For these kind of cheques no
service charge has to be collected)
Solution : The details in charges tab should be
deleted in case the charges are not to be collected for 'At Par' cheques.
2.9.9. Carving
could not be done due to scheme errors.
Issue Reported : Error Screen shot
Solution
Please always click on the Show exception button to get
the issue description.
If the cheque / instrument is
not issued/ passed /stopped then this message comes up. Even other errors are
also listed related to exceptions like Insufficient available balance , etc.
In case of such error what is
to be done has not been mentioned.
2.10.
Transaction posting failure in Inward
clearing
Solution
There is no write permission for the role id of
the user who is trying to post it , hence the issue. In HRPM menu, for the
scheme code to which the above account in the screenshot belongs should be
given write permission.
This is for DOP CBS IT Operation Team only as
HRPM menu is not available for post office users.
2.10.1. Loan
account closure issue
Error
Screen shot
Solution
The above error occurs
when the balance is not zero for the loan account. This means that payoff has
not been done for the account. Please complete the payoff process and then
close the loan account
2.10.2. Premature
closure issues
Error
Screen shot
Solution
The above screenshot
is not an error actually. It is showing the messages as part of user
information during premature account closure. If unsure of the closure
proceeds, please do a trial closure, check the report and then proceed with
actual closure of the account.
2.10.2.1. Unprocessed
records in outward clearing for this A/c
Issue Reported : While doing SB Account conversion from SBGEN to SBCHQ by
using HACXFRSC menu for the SB Account the error showing that "Unprocessed
records in outward clearing for this A/c".
Solution :
1)Invoke
HOCI (Outward Cheques Inquiry ) to know the unprocessed instruments
present for the account and get the zone details (Zone code, Zone date).
2)Invoke
HOIQ and give Outward Clearing Zone Code as respective Zone Code and
Outward Clearing Zone Set ID as ALL and Outward Clearing Zone Date as
respective Zone date and get the Zone sol id from the details.
3)If
zone is not regularized, invoke HMCLZOH under the respective zone sol id and
regularize and proceed further transferring the account.
2.11.
Cash/Teller account
related errors
2.11.1.
RD loan account payoff
done through cash receipt
This error will be
thrown in offices migrated in the middle of the month. (ie on or after 2nd)
In
case of Loan Disbursement or Loan Repayment the value date will be
automatically changed to 01st of the month as interest is calculated
from the 1st of the month for loans. As Cash account of that office
will not be available as on 1st (since the office has migrated in
the middle of the month) this error is thrown in Supervisor while verification.
This error will be thrown only in the month of migration and from 2nd
month cash be used for repayment or disbursement.
Workaround to
overcome this error
“In
case of Loan disbursement – Instead of Cash (even if it is below Rs.20,000)
select Transfer and show RD Loan Disburement office account (Account number ending
with 323) and pay by cheque or cash from this office account. ( CTM menu is to be
used for this )
In
case of Loan repayment – Instead of repaying through cash accept loan repayment
through Transfer. Transfer can be from RD Loan Repayment office Account (Account
number ending with 323) or SB account of customer (if available) (CTM Menu to
be used for this).
2.11.2.
Transaction not getting
posted in CTM/HTM menu
Solution :
The user who is trying to do the operation
doesn’t have a teller account linked to his employee id, hence the issue.
Either the teller should be posting the
transaction or the user trying to post the transaction should be getting a
teller account attached to his employee id.
2.12.
Menu not available to particular user
Issue Reported : When the user tried to invoke
any menu, an error is displayed as Menu Not avaialble for the user.
Solution : Please contact DOP Operations Team at Chennai for the required access to be given to the specified user for
the particualr menu id.
2.13.
User already logged in and User Account got
locked.
Issue Reported : When the user tried to close the
browser with out proper logout, again on loggin in, it gives error message as
User Already logged in.
Solution : Please contact DOP Operations Team at Chennai for the unlocking the
user id.
2.14.
User_Menu_ID is undefined
Issue Reported : When the user tried to login and
invoke any menu, it gives an error message as User_Menu_ID is undefined.
Temporary Solution : Logout from
Finacle Application. Make Internet Browser as your default browser. Press F-12,
Clear all cookies and history. Then try to Logging through default browser i.e (Internet
Explorer)
Mr. sakthivelu Sir to confirm
the above changes regarding pressing of F-12.
2.15.
EOD Issues
2.15.1.
Steps to ensure a fast EOD
Identify all the transactions which are in
Entered Status and un-Posted/Partially posted status.
These Transactions needs to be verified in
each post office by using relevant menu at the earliest and before the EOD
starts.
If still any transaction is not getting
posted then use HTM to post that transaction.
If still transaction is not getting posted,
contact FSI Helpdesk immediately.
2.15.2.
Steps to Inquire EOD blocking validations.
·
Pending Transactions,
Unposted, unverified transactions – HFTI menu should be used.
·
Pending inward Zone to be
closed - HIMCZ/HICTM menu should be
used.
·
Pending Unverified Accounts –
HAFI menu should be used
·
Pending Unverified Inventory
Transaction List – HIMC/HICHB
·
HSVALRPT report can be invoked
to view the blocking validation for each sol
·
For each sol/set the same can
be viewed in a custom report in HPR menu. Report Name is EOD – Blocking
Validation Report – Under development
2.16.
Finacle Not Available or Finacle is Down
2.16.1.
Instructions for Users at Post Office
What will be the result of using below
instruction is not mentioned.
The
below list of instructions is for the users at the Post offices to raise a
helpdesk request during CBS-Finacle connectivity issues ( Finacle not
accessible)
1)
The IncidentReporting.jsp page
has to be typed in the browser, the complete path of which can be like http://DOPFSIHELP/.....incidentReporting.jsp (to be provided once the page is made active)
2)
The below page appears with
the details of the user’s computer on the left panel and a section to enter the
user details on the right panel.
The
fields which are marked with an asterisk (*) are mandatory.
3)
The city of the user can be
chosen from the dropdown provided
4)
On selection of a city, all
the pin codes under the city are shown in the Pin Code dropdown
5) On selection of a pin code, all the post
offices under the pin code are shown in the Post Office Name dropdown with the
first one selected
6)
On entering all the mandatory
fields and a valid 10 digit contact number , the submit button has to be
clicked
7)
On successful submission of
the page with the user computer details and the user details, the confirmation
page appears
2.16.2.
Instructions for L1 Support
Who will use this option and why it is
required in FAQ?
The
below list of instruction is for the L1 support personnel to view the list of
problems logged by the post office users
1) The CBS_Support.jsp page has to be typed in the browser, the
complete path of which can be like http://10.122.97.69:8082/CBS/CBS_Support.jsp. The below page appears
with today’s date in yyyy-mm-dd format as default and the list of issues logged
2)
The date range can be changed
in yyyy-mm-dd format to view the list of issues for that date range
2.17.
Andheri Connectivity Issue
Issue Reported : Initially 2 systems are connected with Finacle. Later on when 2 new
system are connected, they are not working properly.
Solution : For
the newly added two systems, desktop configuration is not done. Once the
configuration is completed as per the provided PDF, it started working fine.
2.18.
Menu getting locked after repeated use.
Issue Reported : When one menu is continuously used for long time, application is
getting locked. User needs to log out and login again.
Solution : Need
to analyze.
If solution is not ready, please remove this
issue.
2.19.
Getting runtime error when user tries to
transfer or copy the set number already existing in the outward clearing zone
which is not in open status
The user needs to be instructed that any
changes that need to be done in clearing zone, the zone status needs to be
revoked from previous status (which in this case is suspended ‘S’) to open
status ‘O’ and then try to do the required operation.
2.20.
MICR zone not closed. All the instruments are
not verified.
Issue Reported : All the Instruments are not verified during
ZONe closure issue is coming.
Screenshot :
Solution:
1) In HICTM menu verify the instrument. If the instrument
is having some error please delete the instrument or mark it as Inward reject
in HICTM menu modify mode and then try verifying.
2) In HMICZ,
suspend the zone and then do a validation run.
3) After this,
post the instrument thru HMICZ menu.
4) If the
posting is successful, please close the zone thru HMICZ menu
2.21.
The nonsytem or Teller cash accounts are not
allowed in this transaction subtype
Issue Reported : Trying to move the amount
from Vault account to teller cash account. Specified error message is
displayed.
Screenshot :
Solution : The User is not marked as
Teller. Please modify the user as Teller and then try posting the transaction.
2.22.
ECS Set ups to be done
Example
for Bangalore GPO
1. HSBM
menu to have the SOL 56000100 as Service branch and Member SOL(s) as mentioned
in the excel shared by Mr. Gopi. There are different ECS user number for
Bangalore alone – but all participate through Bangalore GPO – so only one ECS
user number will be populated. The downloaded file can be modified if the ECS
user number needs to be corrected.
2. Navigate
to menu HSCFM – SOL ID (the Sol ID of the post office participating in ECS
clearing example – Bangalore GPO).
a.
ECS USER NUMBER
Treasury
free text 1 in HSCFM ---
5603181
b.
User Bank Account number
Treasury free text 2 in HSCFM.--> 3007000000
c.
User defined limit for
individual credit items..
MRS Name field in HSCFM SOL 150000
d.
MICR Center , Bank and Branch code –
560 111 002.
2.23.
Clearing Report not available.
Issue Reported: All
Clearing Transactions should be listed in a single report, no such report is
available currently.
Screenshot for the
new Report:
Solution: New Report named Post Office Clearing Detail Report has been made
available in HFINRPT
1. Clearing report can
be generated in HFINRPT which will enlist all the clearing transactions for
given date.
2. Clearing
Transactions for Office accounts will also be listed in the same report.
3. Input Parameters
required for the report are: Date, Sol/Set Id and Scheme Code.
2.8.1.
Report output is grouped by Scheme Type, GL Subhead and Sol Id wise.
Total and Grand Totals are provided.
