FAQ – User

India Post

Savings, NSS, ATM, Agents/Agents Portal, Reports

FINACLE CBS – FAQs & User Guide

Version History

Ver. No.

Ver. Date

Phase

Revised By

Description

Reviewed By

0.1

21-02-2014

Gayathri Perumal

Initial draft

Table of Contents

51.Configurations and Process

51.1.Desktop Setting ( Browser setting, Security settings, JRE version etc.)

51.2.Printer Setting (Passbook)

51.3.ATM Process document and PIN Management

51.4.E-Banking Password Printing and PIN Printing

62. Agent Portal Issues

62.1.Errors in Agents Portal

62.1.1.Agent ID Creation in e-Banking

62.1.2.Accounts not visible for the Agents

62.1.3.Agent IDs manually created in Finacle contains space and dot.

62.1.4.Not able to login with the Agent ID or Password provided.

73. Savings Module Issues

73.1.SB Account closure issues

73.1.1.Dormant SB Account closure issues

83.1.2.Dormant SB account closure issue

93.1.3.SB account closure - Referral Error case

103.1.4.SB closure - Closure verification error because of non-zero balance

113.1.5.SB closure - Closure after Suspension of CIF

113.1.6.SB closure - Status in HACLI menu

123.2.Savings Account Opening/Modification/Transfer Errors

133.2.1.SB account opening error

133.2.2.SB account modification error related to joint account holders

153.2.3.User is unable to create credit transactions on SBDIS accounts

153.2.4.Error faced when credit transaction is attempted on Silent(Dormant Account)

163.3.SB Tellerwise Report(Savings LOT) - transactions of a user missing

163.4.Error while doing a transaction in CTM menu

173.5.SB account Error when transferring account from one scheme to another scheme

183.5.1.Scheme Mismatch Error

183.5.2.Freezed account

193.6.Inquiring Accounts using BO Code

213.7.Issue in HFTI Menu

234. Agent Related Issues

234.1.Commission credited to agent’s SB account even after cancellation of NSC certificates

244.2.Getting error while modifying the agent id in HDSAMM Menu

244.2.1.Unverified Account exists

254.2.2.The date must be later than or same as the BOD date.

264.3.Agent you input has not linked to the current scheme code

274.4.Default and rebate fee calculation not matching.

284.5.Unable to post transaction in HAGTXP menu due to freezed account

294.6.Cheque not cleared in HAGTXP

314.7.Parent Record does not exist

324.8.No of installments pending are less than paying installments

334.9.RD accounts Not shown in the Agent portal.

334.10.Invalid Agent Id Error

344.11.Agents trying to post with Agent Type as SAS

345. NSS Module Issues

345.1.NSS TDS Charges related issues.

345.1.1.When debit transaction is attempted, TDS charge transactions are created but need to be reversed.

355.1.2.When user tries to collect closure TDS charges from HCACC directly, the error - 'Interest Credit has not happened for this account.Please run HACINT for this account'

366. ATM card/CCMM menu issues

366.1.Card is not activated

366.2.No SB accounts exists for the specified cif id

376.3.Invalid card number

376.4.Hotlisting of a particular Card Failed

376.5.ATM Pin Generation Failed

376.6.Not able to Modify Closed Cards

386.7.Account is already attached with a card

386.8.Error while linking

396.9.Invalid account number

396.10.Invalid kit number

396.11.Process of activation of cards

397.Report Issues

397.1.Live Accounts Report

407.2.Sol Id Not proper

418.Formats

418.1.Issue reporting Format

418.2.Escalation Matrix

1. Configurations and Process1.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.

Finacle Desktop

setting version1 1.zip

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.

Passbook_printer_s

ettings.zip

1.3. ATM Process document and PIN Management

Please see below the word document for the complete ATM Process and its PIN management.

Creation of

Placeholder ATM Suspense Account for 4 Sol.doc

Interim process of

handling ATM operations during Pilot.doc

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.

Finacle Ebanking

Procedure-PasswordPrinting.docx

Ebanking-pin.pdf

2. Agent Portal Issues1.5. Errors in Agents Portal1.5.1. Agent ID Creation in e-Banking

Issue Reported : Please create Agent ID in e-banking as it was not part of migrated agents.

Solution: The Agent ID should be first created in Finacle using the menu HDSAMM by the post office . After that, the Agent ID should be shared with Help Desk for creating the Agent ID in e-banking as well.

1.5.2. Accounts not visible for the Agents

Possible reasons for ACCOUNTS NOT VISIBLE FOR AGENTS

· Same Agent might have SAS and MPKBY agency.

· Duplicate agent ids are present. While renewal instead of correcting the existing ID, new agent ID has been created resulting in Duplicate IDs. Further in many post offices it is seen that SB account number is linked even to these duplicate agent IDs.

· If multiple IDs are present to same agents, PO should refer to correct MPKBY ID from the excel sheet provided during Data Migration Transformation and check whether the RD accounts are linked to this ID.

When the agent logs in, accounts are not visible. Please link the accounts.

Solution: The account linkage for the Agent has to be done in Finacle by the PO user by going to account modification menu for each account.

1.5.3. Agent IDs manually created in Finacle contains space and dot.

Issue Reported : Agent IDs manually created in Finacle contains space and dot.

Solution: Agent IDs created in Finacle should not contain space or a dot. Agents Portal will not allow creation of such agent id’s.

1.5.4. Not able to login with the Agent ID or Password provided.

Issue Reported : Not able to login with the Agent ID or Password provided.

Solution: Passwords are case sensitive i.e. lower case and upper case characters should be entered as is. If the agent enters password wrongly 10 times, the Agent ID gets disabled.

3. Savings Module Issues

1.6. SB Account closure issues1.6.1. Dormant SB Account closure issues

Issue Reported : Since the SB account being closed is dormant, the account closure transaction is not verified and gives the below error

Solution

The closure process has to be cancelled and the account status to be modified to Live before closing it.

Steps

· Cancel the closure operation in HCAAC menu. While cancelling an user info will be shown that the transaction has to be manually reversed. After the cancel operation in HCAAC, the transaction has to be deleted in HTM.

· If the account has to be closed , then after cancelling the transaction in HTM menu by selecting Modify function.

· Modify the account status of the SB account in CASBAM menu from Silent to Live and verify it

· Close the account now in HCAAC and verify it.

1.6.2. Dormant SB account closure issue

Issue Reported : Since the SB account being closed is dormant, the account closure transaction is not verified and gives the below error

Solution

The closure process has to be cancelled and the account status to be modified to Live before closing it.

Steps

· Cancel the closure operation in HCAAC menu. While cancelling an user info will be shown that the transaction has to be manually reversed. After the cancel operation in HCAAC, the transaction has to be deleted in HTM.

· If the account has to be closed , then after cancelling the transaction in HTM menu by selecting Modify function.

· Modify the account status of the SB account in CASBAM menu from Silent to Live and verify it

· Close the account now in HCAAC and verify it.

1.6.3. SB account closure - Referral Error case

Issue Reported : Referral Error comes up when closure of SB account is attempted. This occurs whenever the SB account is linked to another TDA(Fixed Deposit type) account as interest repayment account.

Solution

· Before submitting the SB account for closure, a check on the Dependent A/c section in Closure tab has to be made. The accounts where the SB accounts are linked are shown in the section as in the below screen shot :

· If the listed accounts are not closed, then the SB account has to be removed as interest repayment account from all such accounts

· If the listed accounts are already closed, then the Menu HTDBATCH has to be run for those listed accounts

· After all the above steps are completed the user can retry SB closure

1.6.4. SB closure - Closure verification error because of non-zero balance

Issue Reported : When verifying the closure of SB account, user faces the error " The account closure can proceed only if the balance is zero."

Solution:

1. When account closure is initiated in HCACC, system automatically creates transaction to debit entire balance on the given SB account and this transaction id is shown in the result message

2. The user should get this transaction posted and verified, so that the balance of the account becomes Zero

3. If the transaction id is not noted, the same can be found out by listing all transactions of the account using HFTI and checking the status of the transactions

4. Once the transactions are posted and verified and account balance has become zero, the user can proceed with verification of SB closure.

1.6.5. SB closure - Closure after Suspension of CIF

Issue Reported : When creating debit transactions on SB accounts whose CIF has been suspended, the user faces CIF suspened error.

Solution:

1. Option 1 - Unsuspend the CIF using CMRC and then proceed with the transaction

2. Option 2 - In case of death claim, proceed directly to closure of SB account using HCAAC, post and verify the system created transaction and verify closure

1.6.6. SB closure - Status in HACLI menu

Issue Reported : For a closed SB account status is shown as active instead of closed in HACLI menu

Solution:

In HACLI menu the status of the account that is displayed is the status of the account during closure.

To view the account closure status and account closure date invoke HASFM menu in inquire mode and click on the flag next to the account id and navigate to additonal info tab.

Here user will be able to view the account closure date and status of the account.

1.7. Savings Account Opening/Modification/Transfer Errors1.7.1. SB account opening error

Issue Reported : When opening accounts using CASBAO or transferring account using HACXFSOL, user faces the error - 'Account Combination already exists'

Solution:

1. As per requirements of DOP, system checks the various combinations of accounts allowed for that scheme code and Sol. For example. In a SOL, a CIF can have either a single SBGEN or SBCHQ account, but not both.

2. Check the accounts for that sol using account searcher in CASBAM by entering the CIF ID and the SOL and procedurally checking the listed accounts

1.7.2. SB account modification error related to joint account holders

Issue Reported : When modifying accounts of SBPEN/SBPWC/SBBAS , user may face the error - ' Only one Joint account holder permitted' or ' No Joint account permitted for old / widow Pension account'

Solution:

1. As per requirements of DOP, SB pension schemes (SBPEN/SBPWC) can have only one and SBBAS accounts can have no joint account holder

2. User has to check the related party details and make sure that DOP requirements are met before submitting the modification

1.7.3. User is unable to create credit transactions on SBDIS accounts

Solution :

As per the scheme setting of the SBDIS scheme , no credit transaction can be performed on SBDIS account. This can be confirmed by viewing the scheme settings of SBDIS using HGSPI menu.

1.7.4. Error faced when credit transaction is attempted on Silent(Dormant Account)

Solution :

As per the scheme settings , no credit transaction can be performed on Silent(Dormant) accounts. To create transactions on such accounts:

1. Modify the account using CASBAM -->

a. change the account status to active

b. select the revival date from the calendar icon

2. Verify the account

1.8. SB Tellerwise Report(Savings LOT) - transactions of a user missing

Issue Reported : When Tellerwise report (Savings LOT) is generated for a Sol/Set Id, transactions created by some users will not be reflected in the report

Solution : The Tellerwise report only displays those transactions that were created by users who have cash accounts linked to their ids.If a user doesn’t have cash linked to his/her id, then such transactions will not be listed in the report. This is the agreed upon design of the report.

1.9. Error while doing a transaction in CTM menu

Issue Reported : While doing a transaction of SB or SSA Accounts in CTM menu error showing that "cash acount for the entered currency is not available"

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.

1.10. SB account Error when transferring account from one scheme to another scheme1.10.1. Scheme Mismatch Error

Issue Reported : When transferring accounts using HACXFRSC form one SB scheme to another , user may face the error - 'Scheme Mismatch - Account can't be transferred'

Solution:

1. As per requirements of DOP, the transfer of SB accounts is possible only between schemes of the same product group. When destination scheme code belongs to a different product group compared to the source scheme code, then the error is faced.

2. The valid transfer scenarios are :

a. Product group SBSGP : SBGEN <--->SBCHQ

b. Product group SANPG : SBSAN<---> SBSWC

c. Product group SPNGP : SBPEN<---> SBPWC

1.10.2. Freezed account

Issue Reported: Clarification on how to transfer between sol's when account is freezed

Solution:

1.In HAFSM menu the account needs to be inquired and the current freeze status to be noted down.

2. In HAFSM menu the account needs to be un-freezed and verified.3.Through HACXFER menu the account can be transferred from one sol to another.4.In HAFSM menu the account needs to be freezed and verified such that the account freez state will be reverted as in the step [01].

1.11. Inquiring Accounts using BO Code

Issue Reported: Clarification on how to inquire accounts using BO Code.

Solution:

1) Invoke HACSP menu.

2) Enter the Sol ID, Scheme code, Open Date (Low), Open Date (High), Free Code No. and Free Codes fields as specified in the below screenshot.

3) Sol ID for which the BO’s are applicable and account list is required.

4) Scheme Code is SBGEN or RDIPN, since generally in BO’s only SB and RD accounts are available.

5) Open Date (Low) and Open Date (High) are the account opening date’s. All the accounts which are opened in this Date Range will be listed.

6) BO details are available in the Free Code 10 field in GAC table and hence 10 should be entered in the Free Code No field.

7) In Free Codes field, enter the actual BO code and select from the searcher also.

8) After entering all these details click on Submit.

9) All the accounts for the specified criteria will be displayed. PFB screenshot for the same.

1.12. Issue in HFTI Menu

Issue Summary : HFTI menu not fetching the results. Information on Deposits exceeding 2 Lakhs in POSB Scheme

Issue Raised :

1) income tax office is asking about the certificate puchesed for RS. 100000 or above in financial year 2014-15. please intimate what is the menu option to extract this report in finacle .

2) Sir, Income Tax department has asked information on deposits exceeding Rs 02 Lakhs in POSB Scheme. Therefore many offices have raised query on menu option in finacle. Hence it is kindly requested to provide menu for extracting information on deposits exceeding Rs 02 Lakhs

Solution Provided :

Please use HTFI menu to fetch the transactions made above Rs. 100000 or Rs 200000.

Please invoke HFTI menu and enter the Sol Set ID as 34200100 and the A/c Sol ID as 34200100. Please enter A/c Sol ID value mandatorily.

Also enter the transaction Amount Low and High values as desired.

Transaction Start Date and End Date can also be entered.

It will fetch the results as expected. PFB screenshots for the same. Please check and confirm closure.

4. Agent Related Issues

1.13. Commission credited to agent’s SB account even after cancellation of NSC certificates

Issue Reported: Even after cancellation of NSC certificates having denomination of Rs.1000/- each, commission of Rs.45/- got credited to the agent’s SB account 0624681487 for each NSC account.

Solution: Please invoke HACLI menu and inquire for the Agent’s SB Account. Check for the details in Narrative column. It will display the Agent ID. Scheme Code and the Account Number. If the Account Number’s displayed are not the actual verified account number, then please sum the deposit amt of all such records. This amount has to be reversed. For reversing the Agent Commission Transaction, please invoke HACMDB menu and for the Commission Payable Account and Tax account modify the System Only Flag value as NO. After this, invoke HTM menu and Debit the Agent Commission SB Account and Tax account and Credit the Commission Payable Account with appropriate amount respectively. Once the transaction is posted and verified, reverse the modified values in HACMDB menu for the Commission Payable Account and Tax account the System Only Flag value as YES.

1.14. Getting error while modifying the agent id in HDSAMM Menu

1.14.1. Unverified Account exists

Issue Reported: While trying to modify the agent id details in HDSAMM menu on click of submit, getting the error as “Unverified account exist”

Solution: There might be some unverified accounts exist for the specified agent id at the time of agent modification. For the unverified accounts the user can get the account details by invoking HAFI menu and giving the details like SOL Set ID, Authorized as Non Authorized, Table Short Name as GAM, reference number as two blank spaces, Function Code as A, Entered by as the created user Id of respective accounts and get the account details and get them verified and proceed further modifying the agent details.

1.14.2. The date must be later than or same as the BOD date.

Issue reported: Error in adding the new KVP s to the agent MIG0035973. While invoking the menu HDSAMM for modifying the agent details with new KVP the following error occurs with "This tab contains error" in General and "The date must be later than or the BOD Date" in the product details . The date in the Commission parameters has also been changed to the current date.

Solution: Modify the agent id by invoking HDSAMM menu and change the next commission date to some future value date in the product tab for all the scheme code and then try submitting. It will work as expected.

1.15. Agent you input has not linked to the current scheme code

Issue Reported: At the time of account opening, after adding the agent id, getting the error as shown in the screenshot on click of submit.

Solution: The agent id which is being used for the account opening is not linked to the specified scheme code. Hence the specified error is coming. Kindly modify the attached agent id by invoking HDSAMM menu by adding the specified scheme code in the product tab.

1.16. Default and rebate fee calculation not matching.

Issue Reported: While posting RD Bulk list by HAGTXP menu, the accounts are not getting posted. The screen shot error attached by menu HPR shown as calculated default fee not matching actual DF.

Details of Agent:

Agent ID: MIG0029921

Date: 04-12-14

Reference no: C1693566 for Rs 3939/-

Note: This customer prepared list for November and December month 2014. One list (ref no: C1693714) posted with correct default fee.

Solution: Installment for November (ref no: C1693714) i.e. 22-11-2014 has been paid on 12-12-2014 for which default fee of Rs.5/- has been collected already. User is now trying to pay the installment for December month with default fee where there is no default fee. Hence the specified error is coming at the time of HAGTXP. Please prepare a fresh list for all the specified accounts and proceed for payments.

1.17. Unable to post transaction in HAGTXP menu due to freezed account

Issue Description: While doing RD transaction posting through HAGTXP, Transaction failed due to the below error

Solution: Please invoke HASFM menu to view the status of the account mentioned in the report. If the account is in freezed status unfreeze the account using HASFM and continue with posting of transaction. User can contact CEPT team for the reason of freezed status of the account.

1.18. Cheque not cleared in HAGTXP

Issue Description: While doing RD bulk posting through HAGTXP, getting the error as “Cheque not cleared” even though cheque is already cleared as shown in the screenshot.

Solution: Please check if the entries are present for the clearing account no acid, cheque no in tran_particular column and transaction amount in DTD or HTD table for value date between e banking ref date and value date of HAGTXP. To get the clearing place holder, please select parameter_value from c_cpvalue custom table where parameter_id='CLEARING_PL_RD'. Based on the value of the clearing place holder and sol id of the agent, get the clearing account no. Please check total transaction amount (including default, rebate fee and RD installment amount) for the combination of bank identifier and e banking ref no with ready_post flag as Y and del_flg as N.

If the entries are not present in HTD or DTD table, then the specified error is coming.

As per functionality, cheque should get cleared between e banking ref date and value date for the transaction amount.

Workaround for this issue –

1. Invoke CXFER for the back value dated transaction and transfer the amount from the account (replace the clearing account last digit i.e 017 to 007) to clearing account no i.e. ending with 017 with back value dated between e banking ref date and value date.

2. Please make sure the same transaction particular is entered.

3. Kindly enter the value date between e banking ref date and value date of HAGTXP.

4. Post this transaction

5. Then try posting through HAGTXP.

1.19. Parent Record does not exist

Issue description: There is an agent having agent id MIG0024641 with the SOL id 11002300 generate a schedule with the Ref No. NDC1735952. When we run it in HAGTXP in finacle it generate an error i.e. PARENT RECORD DOES NOT EXIST FOR THE RECORD for whole accounts.

Solution : For the specified E-Banking Ref No. NDC1735952, for all the records, instead of the cheque_no_for_RD field, cheque_remarks field is updated, which is wrong.

Else the bank_identifier name entered for the set of RD accounts with sme cheque number will different. Either a space was introduced or name typed wrongly.

EG: SBI can be entered as S B I or State Bank of India. Due to this, specified error message is displayed to the user.

In these case, user can delete the corresponding records and update the delete reason accordingly and then try posting the remaining records.

For the deleted records, please ask the Agent to prepare the fresh list in E-Banking Agent Portal and then try posting in HAGTXP menu.

1.20. No of installments pending are less than paying installments

Issue description: While posting the RD bulk list, we are getting an error "NO OF INSTALLMENTS ARE LESS THAN THE PAYING INSTALLMENTS" for one account and it is not allowing us to post. When tried to do manual extension of RD account, system shows an error as “This is a linked loan account” . PFB screenshots for reference.

Solution: All the installments are already paid for the specified RD account and the user is trying to pay the installment without extending. Please extend the RD account to proceed with RD bulk posting. But if there is any loan account attached to it, only after doing the loan payoff, RD account can be extended

1.21. RD accounts Not shown in the Agent portal.

Issue description: Though RD accounts are linked with the agent id’s none of the accounts are coming in the agent portal.

Solution: As per functionality, if the accounts are freezed or closed or discontinued, such accounts are not being shown in the agent portal. Please ask the user to invoke HAFFM menu to unfreeze the account if it is required and then proceed with agent portal.

1.22. Invalid Agent Id Error

Issue description: When User is trying to open an account with agent id attached, user is getttting error as "Invalid Agent Id"

Solution: User will not be able to use the agent id for account opening unless it is verified.Please inquire the Agent Id using HDSAMM menu.If it shows the below error please verify the agent id and continue with openeing of account.

1.23. Agents trying to post with Agent Type as SAS

Issue Reported : When the user tried to invoke HAGTXP menu in Modify mode, an error is displayed as Inavlid Agent Type and Scheme Code Combination.

Solution : SAS type of Agents do not have access to post RD bulk posting. The Agent Type for that particular Agent ID needs to be modified as either PRS or MPB in HDSAMM menu. Post this modification, user will be able to do posting in HAGTXP menu. Appropriate Agent ID need to be modified as the commission structure differs for both.

5. NSS Module Issues

1.24. NSS TDS Charges related issues.1.24.1. When debit transaction is attempted, TDS charge transactions are created but need to be reversed.

Issue Reported : When teller tried to debit NSS account and the 15g/15h flag is not set as Y then 20% charge is collected as TDS. If the customer then produces the required documentation or the entire debit transaction is to be cancelled then charge collected is to be reversed

Solution : The process of charge reversal is

1. Invoke HCHRT --> Reverse --> NSS account Id --> Go --> select the transaction --> submit --> Note the reference number

2. Verify the same using: HCHRT -->verify --> Reference Number --> submit

Important Points:

1. If the customer has submitted the 15g/15h form, the user has to attach the same at the account level by modifying the account using CASBAM

2. The TDS charge collected for NSS accounts is not visible in HTDSIP and cant be reversed using HRFTDS

3. The TDS charge collection for NSS87 accounts depends only on 15g/15h flag at account level and not the tax code at CIF level

1.24.2. When user tries to collect closure TDS charges from HCACC directly, the error - 'Interest Credit has not happened for this account.Please run HACINT for this account'

Issue Reported : When teller directly proceeds to collect TDS charges on NSS account using HCACC then the above error is faced.

Solution : The process to collect TDS charges at closure of NSS87 account is

1. Invoke HCAAC and try to close the NSS87 account

2. If the TDS charges are to be collected , then

a. the system displays the appropriate error message asking the user to use HCACC to collect charges

b. the system internally triggers interest application so that Interest gets credited before charge can be collected

3. Invoke HCACC and try to collect charges

4. If the same above mentioned error message comes up, check if the interest has been applied using the menu HACLI

5. Once the interest transaction is visible for the account in HACLI, proceed for charge collection

6. If the interest is not credited even after a few minutes, a ticket is to be raised

6. ATM card/CCMM menu issues

1.25. Card is not activated

Issue Description: Card is not getting activated.

Solution: For the specified card, if it is personalized, check whether the kit number is entered. As per the functionality kit number should not be entered for personalized cards. Remove the kit number using modify mode in CCMM menu and proceed further. The card will be activated.

If any wrong details have been given, user can use Delete Mode to delete the already existing details and add the correct details again using ADD Mode in CCMM menu.

Check whether the card is in inactive status. If the card is in either Delivered or inactive status then only the card can be activated.

1.26. No SB accounts exists for the specified cif id

Issue Description: When the user is trying to add a cif id or verify, user is getting an error like "No SB accounts exists for the specified cif id"

Solution: If The sol_id with which the user tries to add the ATM card request in CCMM menu is different from the home sol id of that cif id this error occurs.

Please ask the user to add the ATM card request in the home sol id.

1.27. Invalid card number

Issue Description: When the user is trying to modify card details user is getting error as "Invalid Card number"

Solution: If it is a personalized card,this error occurs mostly when the card details are not updated in the YCS database.

Invoke CCMM menu in inquire mode. it shows details of YCS database. If the status is still as REQ in inquire mode. It means the card is not yet activated.

Hence the user is not able to modify the card details. Please download the file in CCDM menu and the card needs to be activated in YCS. Then the user can modify the details in CCMM menu.

1.28. Hotlisting of a particular Card Failed

Issue Description: User is not able to hotlist a card in modify mode. Error message is getting displayed.

Solution: A card can only be hotlisted if it is in active status. If the card is not currently active it cannot be hotlisted.

Hot listing of the card will directly update the status in CMS. In CMS, if the card is not active, then hot listing fails.

1.29. ATM Pin Generation Failed

Issue Description: The ATM PIN is not generated even if the status is changed to ATM PIN Request in modify mode.

Solution: In CCMM menu in modify mode, action should be selected as ATM Pin Request. Later on in CCDM menu, Renewal/Re-issue file needs to downloaded and uploaded in CMS DB. Flow has to be completed.

If the flow is not completed the PIN Generation will fail.

1.30. Not able to Modify Closed Cards

Issue Description: User is not able to modify the Card.

Solution: Invoke CCMM in inquire mode and check for the status of the card.If the current card status is closed, no more modification is allowed for the cards. Only hotlisting can be done for closed cards.

If the status is closed and the user wants to make the card active, please delete the card and add a new card.

Error message is being displayed for the same.

1.31. Account is already attached with a card

Issue Description: Unable to issue ATM card because of the error message Account is already attached with a card.

Solution: For this cif id and foracid, already a new card request may already have been raised. It may be either in verified or non verified state. Hence while raising new card request specified error will occur. Kindly verify the previous card and use it (if the previous card is in unverify state) or delete the card and raise a new card request(if the previous request is no longer needed).

1.32. Error while linking

Issue Description: Unable to link an account to ATM card, showing error as "There is no account exists in this sol id".

Solution: The specified cif id and account number belongs to some other sol. Hence the user is not able to link the card.

Invoke HACLI menu and find the sol id of the account and kindly change the sol id of the account and try again. Please check.

1.33. Invalid account number

Issue Description: While trying to issue card to sb account, "Invalid Account" Error occurs.

Solution: The given SB account does not belongs to the cif id mentioned. Hence the error occurs. Kindly give the correct account number or select account number from searcher. If searcher does not display data then no SB accounts have been opened under that cif Id.Kindly open an account and proceed issuing a card.

1.34. Invalid kit number

Issue Description: While trying to personalized card, error is thrown as "Invalid kit number".

Solution: The kit number has already been used to raise a new card request for another cif. Hence the same kit number cannot be used, that is why the error is being thrown. Please use a different kit number to raise a new card request.

If the Kit number is not used previously, then raise a request to ATM team.

1.35. Process of activation of cards

Issue Description: Clarify on the process of Activation of cards.

Solution:

1. Invoke CCMM menu and raise a new card request and verfiy the same.

2. Invoke CCDM menu and download the New Customer Registration file with sol id and cif verification date as input and download the file and send it to YCS db. The card will be activated

2. Report Issues

2.1. Live Accounts Report

Issue Description: In MIS url, for the live accounts report only 31 days report is being generated.

Solution: It is as per DOP requirement only to include only 31 days report for Live Accounts in MIS url.

2.2. Sol Id Not proper

Issue Description: While generating reports, the office name is getting displayed wrongly instead of the correct sol name.

Solution: These kind of issues might occur due to network slowness. Kindly generate the report after some time and then the correct names will be displayed.

3. Formats3.1. Issue reporting Format

Before raising the defect or while lodging the defect, the below specified word document needs to be updated by DOP and the same uploaded by the HD team in Meops, so that the issue resolution time is reduced.

Template_For_Lodgi

ng_the_defect.doc

3.2. Escalation Matrix

PFB the excel sheets for the escalation matrix.

FSI-CBS_Escalation_

Matrix_for_FSI_-_Final_Draft_v0.2.xlsx

FSI-CBS_Escalation_

Matrix_for_Non-Severity_Issues_-_Final_Draft_v0.1.xlsx

FSI-CBS_Escalation_

Matrix_Apps_Infra_Support_-_Final_Draft_v0.2.xlsx

21

Finacle CBS FAQ’s & User Guide

Sheet1

S.NoApplicationFSI EngineerFSI Project Manager

1FinacleName : Manivannan AyyamperumalMail Id : manivannan_a01@infosys.comPhone : 91 8939834655Name : Amit DubeMail Id : Amit_Dube@infosys.comPhone : 91- 9840003023

2ECMSName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444Name : Deepthi TMail Id : Deepthi_T@infosys.com@infosys.comPhone : 91- 9840269338

3PLI -Agent PortalName :   Gaurang DeshpandeMail Id : Gaurang_Deshpande@infosys.comPhone : 91 9730949809Name :   Swapnil NarkhedeMail Id : Swapnil_Narkhede@infosys.comPhone : 91 9960874874

4PLI-Customer PortalName :   Neha MathurMail Id : Neha_Mathur03@infosys.comPhone : 91 9623789318Name :   Pooja NigamMail Id : Pooja_Nigam@infosys.comPhone : 91 9028228090

5PLI-NBF PortalName :   Vivek IngaleMail Id : Vivek_Ingale@infosys.comPhone : 91 8055868631Name :   Shobha BhandariMail Id : Shobha_Bhandari@infosys.comPhone : 91 9960713991

6PLI - McCamishName :   Rajeev RanjanMail Id : rajeev_ranjan17@infosys.comPhone : 91 9096457324Name :   Arvind AmbedkarMail Id : arvind_ambedkar@infosys.comPhone : 91 9158006689

7Sanchay PostName :   SrivathsaniMail Id : srivathsani_m@infosys.comPhone : 91 9790971412Name :   Shiv KumarMail Id : Shiv_Kumar10@infosys.comPhone : 91 8041564786

8PLI - Data Migration Insurance (PLI DM)Name :   Senthil Babu BabuMail Id : Senthil Babu Babu@infosys.comPhone : 91 9940644953Name :   Ashok Shanmuga SundaramMail Id : Ashok_S08@infosys.comPhone : 9840445347

Revision

Infosys

FSI-DOP

FSI - Escalation Matrix-Non Severity Issue

INFOSYS TECHNOLOGIES LTD.

Document Revision History

Ver #DateAuthorComments

0.128-Feb-14Infosys

Finacle

Elapsed Time Contacts

To be resolved by 2 business days Name: Selvaraja Jeyakumar Mail Id: Selvaraja_J@infosys.com Phone: 91-9840003023

To be resolved by 4 business days FSI Project Manager Name: Vinoth M. C. K. Mail Id: vinoth_mck@infosys.com Phone: 91-7829917612

To be resolved by 6 business days FSI Senior Manager Name: Amit Dube Mail Id: Amit_Dube@infosys.com Phone: 91-9902016444

To be resolved by 8 business days FSI Operation Support Manager Name: Srihari Gopalan Mail Id: srihari_gopalan@infosys.com Phone: 91-9940283013

PLI

Elapsed Time Contacts

To be resolved by 2 business days Name: Rajeev Ranjan Mail Id: rajeev_ranjan17@infosys.com Phone: 91-9096457324

To be resolved by 4 business days PLI Project Manager Name: Rajanarayan Pradhan Mail Id: rajanarayan_202565@infosys.com Phone: 91-8446022164

To be resolved by 6 business days PLI Senior Manager Name: Arvind Ambedkar Mail Id: arvind_ambedkar@infosys.com Phone: 91-9158006689

To be resolved by 8 business days PLI Operation Support Manager Name: Srihari Gopalan Mail Id: srihari_gopalan@infosys.com Phone: 91-9940283013

_1456150121.doc

Interim process of handling ATM operations during Pilot

· It has been decided to launch 4 ATMs at T.Nagar HO(T.N), Chembur HO(Mah), Delhi GPO and IPHO(Delhi) as a Pilot for 1000 ATMs.

· Only POSB ATM/Debit cards can be used in these ATMs.

· ATM/Debit Card requests will be captured in Finacle by the Post Offices and request form alongwith KYC documents will be submitted to their CPC for scanning and uploading as a Change Request Form.

· CPC Bangalore will generate Files on daily basis (detail given in below process for CPC) and upload into YCS Card Management Application.

· PIN will be generated at CPC Bangalore and despatched to the address of the applicant through service registered mail.

· Card Embossing File will be sent by CPC Bangalore to the Card Vendor (presently at Chennai) via e Mail who will deliver Cards after printing at DMCC Chennai.

· DMCC Chennai will prepare Post Office-wise bundles (for personalized cards) and send the same to the concerned Post Offices via service Insured Packet.

· DMCC will send Insta Cards to CPC Bangalore via service Insured Packet.

· CPC Bangalore will create Welcome Kits in Finacle and prepare one envelope containing Welcome Letter, ATM/Debit Card and PIN. Bundles of Welcome Kits will be prepared at CPC and despatched to the concerned Post Offices via service Insured Packets.

· Post Offices concerned will maintain stock and issue registers for personalized cards and Welcome Kits separately in manuscript and take applicant’s signature against delivery in the issue register and make corresponding entries in the stock registers.

· Maximum balance of Welcome Kits to be retained in a post office will be 125. When stock is reduced to 25, further indent of next 100 Welcome Kits should be sent through YCS application by post office.

· On viewing the indent, CPC Bangalore will generate subsequent Welcome Kits and despatch to the post offices.

· ATM/Debit Card will be issued to Post Office Savings Bank (POSB) Savings Account Holders who have balance of Rs.25000/- at the time of applying ATM/Debit Card.

· Initially, following services will be available to POSB customers at ATMs:-

· Cash Withdrawal

· Fast Cash

· Balance Inquiry

· Mini Statement

· Funds Transfer (Funds Transfer within OWN(linked) Savings Accounts)

· Funds Transfer (Funds Transfer within Savings Accounts of POSB)

· Pin Change

· Maximum amount that can be withdrawn from ATMs in a single day will be Rs.25000/- and Rs,10,000/- at a time.

· If any existing Account Holder desires to get ATM/Debit Card, application on the prescribed form alongwith KYC documents (if account is opened before migration) is to be obtained.

Process to be followed at 4 HPOs, CPC Bangalore and Bangalore GPO.

· Depositor who wants to have ATM/Debit Card will submit application in the prescribed form at the post office where account stands.

· Counter PA and Supervisor have to see as to whether the account was opened before or after migration to CBS. If account was opened prior to migration, full KYC documents as required as per Master Circular No.1/2012 should be taken.

· Both PA and Supervisor will verify balance in the account and signatures on the application with the information/signatures available in Finacle. They will enter their names and place their signatures at the relevant place in application form.

· PA and Supervisor have to ensure that all fields are properly filled by the depositor. Only literate depositor can apply for ATM/Debit Card.

· ATM Suspense Account has been created for all these 4 post office by DOP IT Team and account numbers are as follows:-

T.Nagar

600017000813

Delhi GPO110006000814

IPHO

110002000815

Chembur HO 40071000816

· These ATM Cash A/Cs are locally defined for each & every post office and attached to their Vault Account.

· On the day of cash loading, cash will be handed over to the representative of Vendor i.e NCR and following financial entry has to be passed in Finacle:-

Use HTM Menu Option

Debit ATM Suspense Account and Credit Post Office Vault Account for the amount of cash.

· Postmasters of these 4 HPOs will be provided two ATM Admn. Cards and Keys of ATM as well as ATM Room. Postmaster will handover one ATM Admn. Card to representative if NCR alongwith Cash. A receipt will be taken in the treasurer’s Cash Book. A remittance advice (RA) of the cash should be sent to Bangalore GPO by these 4 post offices as and when cash is handed over to Vendor showing as Cash remitted to Bangalore GPO.

· Bangalore GPO will take that RAs into its account as Cash received from OHO and show as Cash in ATMs in its Cash Book.

· CPC Bangalore will generate report of the transactions happened in ATM on next day by using menu HFTI and putting SWT in the field Channel. Total Amount debited or credited in Savings Account Scheme in all ATMs will be intimated to Bangalore GPO by CPC Bagalore which will enter the amount in Bangalore GPO Cash Book in SB Deposit/Withdrawal through ATMs and net amount will be adjusted against the entry of Cash in ATMs shown in its cash book.

· The following operations will be done in Post Offices via CCMM (Custom Card Maintenance Menu) by Counter PA and Supervisor when the customer (Account Holder) approaches the Post Office and requests for ATM/Debit Cards. DoP will issue Debit Cards. The process is same for personalized and instant cards. Personalized Cards have Card Holder’s name embossed on the card.

The criteria page and details page of the menu option is provided below.

Criteria Page - CCMM (Custom Card Maintenance Menu)

· Details Page - CCMM (Custom Card Maintenance Menu)

The various functions which can be performed in CCMM (Custom Card Maintenance Menu) is explained below

· Add – This option will be used when Account Holder requests for a ATM/Debit Card.

· Criteria Screen - Select A (Add) & Search (or Type) the CIF Number. Press Go

· Details Screen - Click on A(Add) & choose the Account Number for which the card is to be issued

· Details Screen – Select Primary Account Flag = Y . The card will have only one primary account.

· Details Screen – The choice of card can either be personalized or instant. Personalized cards will bear the Name of the holder & Instant Cards will not bear the name of the holder.

· Details Screen – Select Card Type = P for Personalized Cards, if customer requests for a personalized card.

· Details Screen – Select Card Type = I for Instant Cards & provide the Instant Card KIT Number, if the customer requests an instant card.

· Details Screen – Select “New Card Request”

· Submit

· Note

· Personalized Cards

· If customer has multiple Saving Accounts & wants to link to same card with all or selective accounts, Post Office should create a request for the Primary Card first.

· When the customer visits the Post Office for collecting the card , Use CCMM(Modify Option) & place a request for activation

· Use CCMM(Modify Option) & link other account to the card.

· Instant Cards

· If customer has multiple Saving Accounts & wants to link to the same card, Post Office should create a request for the Primary Card first.

· Ask the customer to place a request for linking on the subsequent visit , Use CCMM(Modify Option) & link other account to card.

· Modify – This option will be used when Account Holder requests for Linking, Delinking, Activation, Replacement and Hotlisting of Cards. Select M (Modify) & Search (or Type) the CIF Number or Card Number or Both CIF Number & Card Number. Press Go. The details of the cards for the CIF Number or Card Number or combination of Card Number and CIF Number will be displayed

· Linking – This option will be used when the Account Holder requests for linking additional Saving Accounts with the card

· Details Screen – Press A(Add), Select the Account Number which is required to be linked. Select the “Primary Account Flag” as N.

· Select Action = LNK (Linking) & Press Submit

· Delinking – This option will be used when the Account Holder requests for de-linking Saving Accounts with the card

· Details Screen – Select Action = DLN(De Linking) & Press Submit

· Activation – This option will be used when the Account Holder comes to the post office to collect the card. Activation is only applicable for Personalized Cards

· Details Screen – Select Action = ACT(Activation) & Press Submit

· Hot Listing – This option will be used when the Account Holder requests for hot listing of the card in event of

· Card is Lost

· Details Screen – Select Action = “Hot Listing” & Press Submit

· Card is Damaged

· Details Screen – Select Action = “Hot Listing Damaged” & Press Submit

· Card is Stolen

· Details Screen – Select Action =”Hot Listing Stolen” & Press Submit

· Replace

· Details Screen – Select Action = “Hot Listing and Replacing Card & Press Submit

· Replacement – This option will be used when the Account Holder requests for replacement of the card

· Details Screen – Select Action = Replacement & Press Submit

· ATM Pin Request – This option will be used when the Account Holder requests for subsequent Pin.

· Details Screen – Select Action = “ATM Pin Request” & Press Submit

· Verify – This option will be used to verify the A (Add) or M (Modify) option. The Hot listing of cards in CMS (Card Management System) will be done during the verification in CBS (Finacle) by Supervisor. Subsequent to Verification, other processing will be done by Bangalore CPC during the End of Day

· Cancel – This option will be used to cancel the A (Add) or M (Modify) Operation conducted by the PA before verification in case of any mistake.

· Inquire – This option will be used to inquire the details in CMS (Card Management System). Either CIF Number or Card Number or Both CIF Number and Card Number can be provided as an input on the criteria page and details will be listed in the “Details Screen”

· History – This option will be used to inquire the request in CBS (Finacle). The enquiry will display the date on which the account holder has requested for the maintenance.

Process to be exclusively followed at Bangalore CPC

· The following operations will be done in Bangalore CPC via CCDM (Custom Card Download Menu). These files are processed automatically by CMS (Card Management System) and details of how to check the errors will be explained in the CMS (Card Management System) User Manuals.

The various extracts which can be downloaded in CCDM (Custom Card Download Menu) is explained below.

· Branch Registration File – This file contains the details of the SOL ID created in CBS (Finacle) for creating post offices in CMS (Card Management System). This activity is required to be done on the day of migration. CMS (Card Management System) has the details of the supervisor & address of the post offices where the “Welcome Kits” will be dispatched to.

· New Customer Registration File – This file contains all the customers across post offices who have requested for card.

· Account Details File – This file contains requests of all the customers across post offices who have requested for Linking/Delinking of additional accounts to existing cards.

· Address Details File – This file contains the address of all customers who have been issued cards & have made changes to their address.

· Renewal/Re-issue File – This file contains requests of all the customers who have placed a request for Renewal/Re-Issue

· Reconciliation File – This file contains all financial transactions done during the day & is used during the reconciliation of ATM Transactions.

Finacle

SOP – Printing Password in PIN MAILER for E-banking

Version 0.1

Submitted

by

Infosys

Revision History

Date

Version

Description

Author

6-Feb-2014

0.1

Printing Password in PIN MAILER for E-banking

Darshan_H

Review and Approvals

Date

Name & Role

Comments

Table of Contents1.Introduction41.1.Purpose of the document41.2.Prerequisites42.Steps to run the automated PasswordPrintingBatch.bat batch in Windows53.Steps to run the PWDPRINTBATCH in Windows/Unix machine using ScheduleInsertUtility and SchedulerInitializer74.Appendix: Files with task data for different users and passwords to be printed9

Introduction

Purpose of the document

This document describes the steps for Password Printing activity after setting the Login/Transaction passwords for any user.

· The password printing will be executed by the batch program.

· The Batch program will be setup on a desktop machine, (dedicated only for password printing) which is connected to the pin mailer printer.

· The batch program can be run by only the users who have access to it.

Prerequisites

Following are the pre-requisites required before starting the procedures:

1. The Login/Transaction passwords for a user (Retail/Customer/Agent/Super-Agent/RM).

2. FEBA Batch setup.

3. Login credentials to the Windows to run the batch.

4. Printer connected to the desktop where the batch is run.

5. Connectivity to the e-banking DB where the batch is setup

6. Connectivity to the Core FI where the batch is setup

Steps to run the automated PasswordPrintingBatch.bat batch in Windows

1. Login to the password printing machine and double click on the shortcut to batch file.

Or The PasswordPrintingBatch.bat will be present in the FEBA batch folder.

2. The batch will show the different options available for password printing.

The Bank User has to choose the required option for password printing.

3. The password will be printed to the pin mailer printer according to the chosen option and the password printing task will be completed.

4. The PDF of the passwords will be present the reports folder

Note:

· The user should have access to run the batch. That means the username with which the user has logged into the windows machine should have an entry in the CUSR table with UserType=’5’.

· Check that the desktop has connectivity to the e-banking Database.

Steps to run the PWDPRINTBATCH in Windows/Unix machine using ScheduleInsertUtility and SchedulerInitializer

We can also run the PWDPRINTBATCH files in manual mode using following files in the FEBA folder. (The machines should have connectivity to the printer)

1. the ScheduleInsertUtility.bat and SchedulerInitializer.bat in windows machine

2. the ScheduleInsertUtility.sh and SchedulerInitializer.sh in Unix machine

1. In the FEBA batch folder: Run the ScheduleInsertUtility.

The user will be prompted for the following and should provide appropriate values:

a. Enter the Schedule Name * ::

The user has to provide a unique name for the schedule.

Usually Taskname_date_no is preferred

Ex: PWDPRINTBATCH_7feb_2014_01

b. Enter the Schedule Name * ::

For password printing upload: PWDPRINTBATCH

c. Enter the Schedule Task Data ::

The taskdata change according to the type of user, user’s profile, type of password etc.

The taskdata for different types of users can be checked in the files present in params folder.

Ex: For agents’ login password the task data will be as follows:

NO_OF_RECORDS_PER_CHUNK=10;REPORT_NAME=pwdprint;REPORT_FORMAT=PDF;ACTIVATE_USER=

Y;MENU_PROFILE_LIST_TO_ENABLE=DOPADMIN|DOPADUSR|DOPRMUSR|DOPAGN|DOPSPAGN;USER_TY

PE=B;PWD_USER_ID=*.*;PASSWORD_TYPE=SGNPWD;PRINT_TO_PRINTER=Y;

d. Enter the Schedule Pattern * ::

Enter : * * * * * * * (Format can be changed as required)

e. Enter the Max Number of Occurrences ::

1 ( the schedule will 1 time)

f. Enter the Holiday Option : (Blank)

g. Enter the Start Time of Schedule :: (Blank)

h. Enter the End Time of Schedule :: (Blank)

Once done, the schedule will be inserted successfully.

Following is the screen shot of the ScheduleInsertUtility run in windows machine.

2. Once the schedule is inserted successfully , run the SchedulerInitializer.

Appendix: Files with task data for different users and passwords to be printed

Confidential

Infosys, Feb-2014

Page 9 of 9

TaskData.zip

RetailSgnOn.txt

PWDPRINTBATCHNO_OF_RECORDS_PER_CHUNK=10;REPORT_NAME=pwdprint;REPORT_FORMAT=PDF;ACTIVATE_USER=Y;MENU_PROFILE_LIST_TO_ENABLE=RVIEWUSR|RTXNUSER;USER_TYPE=R;PWD_USER_ID=*;PASSWORD_TYPE=SGNPWD;PRINT_TO_PRINTER=Y;* * * * * * *1

RetailTxn.txt

PWDPRINTBATCHNO_OF_RECORDS_PER_CHUNK=10;REPORT_NAME=pwdprint;REPORT_FORMAT=PDF;ACTIVATE_USER=Y;MENU_PROFILE_LIST_TO_ENABLE=DOPDRG|RUSER;USER_TYPE=R;PWD_USER_ID=*;PASSWORD_TYPE=TXNPWD;PRINT_TO_PRINTER=Y;* * * * * * *1

BankBoth.txt

PWDPRINTBATCHNO_OF_RECORDS_PER_CHUNK=10;REPORT_NAME=pwdprint;REPORT_FORMAT=PDF;ACTIVATE_USER=Y;MENU_PROFILE_LIST_TO_ENABLE=DOPADMIN|DOPADUSR|DOPRMUSR|DOPAGN|DOPSPAGN;USER_TYPE=B;PWD_USER_ID=*.*;PASSWORD_TYPE=*;PRINT_TO_PRINTER=Y;* * * * * * *1

BankSgnOn.txt

PWDPRINTBATCHNO_OF_RECORDS_PER_CHUNK=10;REPORT_NAME=pwdprint;REPORT_FORMAT=PDF;ACTIVATE_USER=Y;MENU_PROFILE_LIST_TO_ENABLE=DOPADMIN|DOPADUSR|DOPRMUSR|DOPAGN|DOPSPAGN;USER_TYPE=B;PWD_USER_ID=*.*;PASSWORD_TYPE=SGNPWD;PRINT_TO_PRINTER=Y;* * * * * * *1

BankTxn.txt

PWDPRINTBATCHNO_OF_RECORDS_PER_CHUNK=10;REPORT_NAME=pwdprint;REPORT_FORMAT=PDF;ACTIVATE_USER=Y;MENU_PROFILE_LIST_TO_ENABLE=DOPADMIN|DOPADUSR|DOPRMUSR|DOPAGN|DOPSPAGN;USER_TYPE=B;PWD_USER_ID=*.*;PASSWORD_TYPE=TXNPWD;PRINT_TO_PRINTER=Y;* * * * * * *1

RetailBoth.txt

PWDPRINTBATCHNO_OF_RECORDS_PER_CHUNK=10;REPORT_NAME=pwdprint;REPORT_FORMAT=PDF;ACTIVATE_USER=Y;MENU_PROFILE_LIST_TO_ENABLE=DOPDRG|RUSER|DOPRET;USER_TYPE=R;PWD_USER_ID=*;PASSWORD_TYPE=*;PRINT_TO_PRINTER=Y;* * * * * * *1

_1456151374.doc

Department Of Post

Template for Lodging the Defect in Meops

Document Name

Template for Lodging the Defect in Meops.doc

Version Rev

0.1

Content Owner

Gayathri Perumal

Date

05-Mar-2014

Author

Gayathri Perumal

Release

Document Information

Project Name:

DOP

Project Manager:

Vinoth M.C.K

Document Version No:

0.1

Prepared By:

Gayathri Perumal

Document Version Date:

05-03-2014

Reviewed By:

Gayathri Perumal

Preparation Date:

05-03-2014

Version History

Ver. No.

Ver. Date

Phase

Revised By

Description

Reviewed By

0.1

05-03-2014

Gayathri Perumal

Initial draft

0.2

12-03-2014

Gayathri Perumal

Updated the document

Contents

41.Defect Details

41.1Issue Faced in the Branch

41.2Issue faced by the User

41.3Issue Faced in the Menu

41.4Issue faced for the entity

41.5Screenshots

41.6Issue Summary

41.7Issue Description

41.8Is the issue faced by one user or all the users in the branch

41.9Is the issues faced in one branch or all the branches

41.10Is the issue is the repeated one? Is the solution provided earlier?

41.11If the issue is the repeated one, please provide the initial analysis by L1

1. Defect Details

For all the below specified points, updated comments by HD team is required for the fast issue analysis and quick issue resolution by L2 team.

1.1 Issue Faced in the Branch

1.2 Issue faced by the User

1.3 Issue Faced in the Menu

1.4 Issue faced for the entity

1.5 Screenshots

1.6 Issue Summary

1.7 Issue Description

1.8 Is the issue faced by one user or all the users in the branch

1.9 Is the issues faced in one branch or all the branches

< Need details as the issue faced by one branch or multiple branches >

1.10 Is the issue is the repeated one? Is the solution provided earlier?

1.11 If the issue is the repeated one, please provide the initial analysis by L1

CONFIDENTIAL

_1456150253.pdf

Version: 1.0

Author: Infosys LTD /Navee JoshiProject: DEPARTMENT OF POSTS (DOP-FSI)

Org Date: 10/01/2014

Rev Date: 10/02/2014Title : Ebank PIN Print Setup for DOP-FSI

Confidential

PD3Ebanking DB1 dpdcpidcsag1

PD4Ebanking DB2 dpdcpidcsag2

RAC

CBS: Finacle Core Web1

DPDCAXWEB5

CBS: Finacle Core Web1

DPDCAXWEB6

Web-Tier

2

Hardware Load

Balancer/IntranetEbanking PIN

Printing

Desktop

Bangalore

CPC

Ebanking app server1

Ebanking app server2

App-TierCore DB - Tier

PD3Finacle Core DB1 dpdcpidpsnbf1

PD4Finacle Core DB2 dpdcpidpsnbf2

RAC

EBanking DB -

Tier

1 Exception access

Dpdcpfjc.fsi.indiapost.gov.in (172.16.20.40) port:1433

DPDCPSAG-SCAN.fsi.indiapost.gov.in

172.20.4.112172.20.4.113172.20.4.114

Port 1932

DAKC-Mumbai

10.168.2.3810.168.2.39

Ebanking-pin.vsd

Ebank PIN

_1456150062.doc

Creation of ATM Suspense Account

1. Check the placeholder in HAPHM,Function = I , Account Placeholder = ATMSUSPENSE, if it exists you don’t have to create the placeholder via HAPHM. The place holder for ATM suspense account should be Cash

2. Check “Type of Cash A/c.” in HSCFM level, SOL Maintenance, the cash account should be modified from Teller to Teller/SYSTEM as ATM suspense Account is not attached to any Teller.

3. Subsequently change context SOL via (HCCS) & create 1 Office A/C per SOL for the post offices where ATM has been installed.

4. This account should be reviewed on a daily basis by PO(Post Offices)

Creation of ATM Suspense Account and verification - HACMDB

Select “Vault”

ATMSUSPENSE

ATM Suspense Account

Infra Support

E S C A L A T I O N M A T R I X - INFRASTRUCTURE PORTFOLIO

TechnologyPrimary contact Escalation contactTertiary escalation contactManagement EscalationDL & Ticket group

TrackName of the Primary contactContact email-idContact # Escalation Point 1Contact email-idContact #Escalation Point 2Contact email-idContact #DoP ContactContact email-idContact #L2 DoP DLL2 Ticket Group

AIXMonitoring Teamdop_ims_monitoring@infosys.com91-8939834388Mahesh Mahadev LakhangaonkarMahesh_L01@infosys.com91 -8698711550Ravish SharmaRavish_Sharma@infosys.com91-7259116213Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

LinuxMonitoring Teamdop_ims_monitoring@infosys.com91-8939834388Shibabrata DasguptaShibabrata_D@infosys.com91- 7767812365Ravish SharmaRavish_Sharma@infosys.com91-7259116213Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

Network Network Teamdop_ims_network@infosys.com91-8939834388Chandrasekar RamanChandrasekar_Raman@infosys.com91- 8939780384Raja Duraisingam IlangoRajaDuraisingam_I@infosys.com91 -8939824479Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

MonitoringMonitoring Teamdop_ims_monitoring@infosys.com91-8939834388Raja Duraisingam IlangoRajaDuraisingam_I@infosys.com91 -8939824479Ravish SharmaRavish_Sharma@infosys.com91-7259116213Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

PlatformMonitoring Teamdop_ims_monitoring@infosys.com91-8939834388Mukund LachyankarMukund_Lachyankar@infosys.com91 - 9049996491Raja Duraisingam IlangoRajaDuraisingam_I@infosys.com91 -8939824479Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

DB2Monitoring Teamdop_ims_monitoring@infosys.com91-8939834388Ashish Ashokrao BhokreAshish_Bhokre@infosys.com91 - 9820116501Raja Duraisingam IlangoRajaDuraisingam_I@infosys.com91 -8939824479Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

Windows and VmwareMonitoring Teamdop_ims_monitoring@infosys.com91-8939834388Muralidharan SubramanianMuralidharan_S12@infosys.com91- 9176248963Raja Duraisingam IlangoRajaDuraisingam_I@infosys.com91 -8939824479Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

BackupMonitoring Teamdop_ims_monitoring@infosys.com91-8939834388Abhinay Chakravarthy VarakanthamAbhinay_V@infosys.com91 -8095049200Raja Duraisingam IlangoRajaDuraisingam_I@infosys.com91 -8939824479Rishi Pratap SinghRishi_Singh@infosys.com91-9780035499

mailto:Rishi_Singh@infosys.commailto:Rishi_Singh@infosys.commailto:Rishi_Singh@infosys.commailto:Rishi_Singh@infosys.commailto:Rishi_Singh@infosys.commailto:Rishi_Singh@infosys.commailto:Ravish_Sharma@infosys.commailto:dop_ims_monitoring@infosys.commailto:dop_ims_monitoring@infosys.commailto:dop_ims_network@infosys.commailto:Ravish_Sharma@infosys.commailto:Ravish_Sharma@infosys.commailto:Rishi_Singh@infosys.commailto:Rishi_Singh@infosys.com

App Support

E S C A L A T I O N M A T R I X - A P P L I C A T I O N P O R T F O L I O

Application portfolioPrimary contact Secondary escalation contactTertiary escalation contactDoP manager contact informationDL & Ticket group

TrackName of the 'In scope' applicationsName of the Primary contact at OnsiteContact email-idContact #Secondary EscalationContact email-idContact #Tertiary EscalationContact email-idContact #DoP ContactContact email-idContact #L2 DoP DLL2 Ticket Group

FinacleFinacle Core Selvaraja Jeyakumar,   Sundar Raj Karuppa SamySelvaraja_J@infosys.com,SundarRaj_K@infosys.com91- 9840003023/91 -8939834655Amit DubeAmit_Dube@infosys.com91 -9902016444Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Director CBSdirectorcbs-del@indiapost.gov.in

Finacle Ebanking/Mbanking  Arunsundar VadivelArunsundar_Vadivel@infosys.com91 7200093938Amit DubeAmit_Dube@infosys.com91 -9902016444Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Director CBSdirectorcbs-del@indiapost.gov.in

Finacle SASMadhumitha GanesanMadhumitha_Ganesan@infosys.com +91 9600399066Amit DubeAmit_Dube@infosys.com91 -9902016444Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Director CBSdirectorcbs-del@indiapost.gov.in

Finacle RBAVipin CVipin_C@infosys.com+91 9986851336Amit DubeAmit_Dube@infosys.com91 -9902016444Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Director CBSdirectorcbs-del@indiapost.gov.in

First Level escalationVinoth M. C. K.vinoth_mck@infosys.com+91 7829917612Amit DubeAmit_Dube@infosys.com91 -9902016444Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Director CBSdirectorcbs-del@indiapost.gov.in

ECMSECMSPrasath Subramani/Sathis Elangoprasath_subramani@infosys.com/sathiskumar_elango@infosys.com91 9840213444/91 9591073700Deepthi T Deepthi_T@infosys.com91 09840269338Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Director CBS/Amitabh Singhdirectorcbs-del@indiapost.gov.in/agmplidte@gmail.com

PLI - Agent PortalDesktop Web /Mobile Web--- Agent PortalGaurang DeshpandeGaurang_Deshpande@infosys.com91 9730949809Swapnil NarkhedeSwapnil_Narkhede@infosys.com91 -9960874874Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Amitabh Singhagmplidte@gmail.com

PLI - Customer PortalDesktop Web/Mobile web --- Customer Policy servicingNeha MathurNeha_Mathur03@infosys.com91 9623789318Pooja NigamPooja_Nigam@infosys.com91 -9028228090Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Amitabh Singhagmplidte@gmail.com

PLI - NBF PortalDesktop Web/Mobile web --- New BusinessVivek IngaleVivek_Ingale@infosys.com91 8055868631Shobha BhandariShobha_Bhandari@infosys.com91 -9960713991Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Amitabh Singhagmplidte@gmail.com

PLI - McCamishVPASPMACS, NBF, Reports, Worklow, PSWDRajeev Ranjanrajeev_ranjan17@infosys.com919096457324Arvind Ambedkararvind_ambedkar@infosys.com91 -9158006689Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Amitabh Singhagmplidte@gmail.com

Sanchay PostSanchay PostSrivathsanisrivathsani_m@infosys.com91 9790971412Shiv KumarShiv_Kumar10@infosys.com91 -8041564786Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Director CBSdirectorcbs-del@indiapost.gov.in

PLI - Data Migration Insurance (PLI DM)PLI Data Migration Issues (DPT, ETL issues, Migrated Data Issues)Senthil Babu BabuSenthilBabu_Babu@infosys.com9940644953Ashok Shanmuga SundaramAshok_S08@infosys.com91 -9840445347Srihari Gopalansrihari_gopalan@infosys.com91-8939824420Amitabh Singhagmplidte@gmail.com

mailto:Amit_Dube@infosys.commailto:arvind_ambedkar@infosys.commailto:Deepthi_T@infosys.commailto:prasath_subramani@infosys.com/sathiskumar_elango@infosys.commailto:directorcbs-del@indiapost.gov.inmailto:directorcbs-del@indiapost.gov.in/agmplidte@gmail.commailto:Shiv_Kumar10@infosys.commailto:directorcbs-del@indiapost.gov.inmailto:srihari_gopalan@infosys.commailto:srihari_gopalan@infosys.commailto:Selvaraja_J@infosys.com,SundarRaj_K@infosys.commailto:SenthilBabu_Babu@infosys.commailto:Arunsundar_Vadivel@infosys.commailto:Madhumitha_Ganesan@infosys.commailto:Vipin_C@infosys.commailto:Amit_Dube@infosys.commailto:Amit_Dube@infosys.commailto:Amit_Dube@infosys.commailto:Amit_Dube@infosys.commailto:directorcbs-del@indiapost.gov.inmailto:directorcbs-del@indiapost.gov.inmailto:directorcbs-del@indiapost.gov.inmailto:Ashok_S08@infosys.commailto:directorcbs-del@indiapost.gov.inmailto:srihari_gopalan@infosys.commailto:srihari_gopalan@infosys.commailto:srihari_gopalan@infosys.commailto:srihari_gopalan@infosys.commailto:vinoth_mck@infosys.commailto:agmplidte@gmail.commailto:agmplidte@gmail.commailto:agmplidte@gmail.commailto:agmplidte@gmail.commailto:agmplidte@gmail.commailto:rajeev_ranjan17@infosys.com

_1456142782/Passbook_printer_settings.zip

Passbook_printer_settings.doc

FINACLE ™

Infosys Department Of Post

© Infosys Limited

Printer Setup for Passbook

Olivetti PRS2 printer

File Name

Passbook_printer_settings.doc

Version. Rev

1.0

Authorized by

Gayathri Perumal

Date

26/12/2013

Document Information

Project Name:

DOP

Project Manager:

Vinoth M C K

Document Version No:

0.1

Prepared By:

Gayathri Perumal

Document Version Date:

Reviewed By:

Preparation Date:

26/12/2013

Version History

Ver. No.

Ver. Date

Phase

Revised By

Description

Reviewed By

0.1

26/12/2013

0.2

Contents

41.Passbook printer settings for olivetti prs2

1. Passbook printer settings for olivetti prs2

Steps for Configuring the Passbook Printer (Olivetti PRS2)

Step 1: Goto Control Panel -> Devices and Printers path.

Step 2: Select Generic IBM Graphics 9pin wide as the Default Printer.

Step 3: Please select the Printer Server Properties tab on the top as shown in above screenshot. Below screenshot will pop-up.

Step 4: In Forms tab, please click on Create a new form and in Form name, please type the Name as PassbookNew1.

Please specify the measurements for margins as shown in the below screenshot and click on Save Form and Click on OK button.

Step 5: In Devices and Printers path, right click on Generic IBM Graphics 9pin wide and select Printing Prefernces. Below specified screenshot will pop-up with Layout and Paper/Quality tabs.

Step 6: In Layout tab, please click on Advanced button as shown in the below screenshot.

Step 7: On Click of Advanced button, below specified screenshot will pop-up. Please select the Paper Size as PassbookNew1 and Print Quality as 240*216 dots per inch. Same setting as shown in below screenshot should be done.

Step 8: In Devices and Printers path, right click on Generic IBM Graphics 9pin wide and select Printer Properties. Below specified screenshot will pop-up with General, Sharing, Devices Setting tabs etc.

Step 9: Please click on the Devices Settings tab. Below specified screenshot will pop-up.

Step 10: Please select the Tractor Feed as PassbookNew1 and Manual Paper feed as PassbookNew1 and click on OK button.

Step 11: After doing the above changes, in General tab, automatically, in the Paper available section, the PassbookNew1 will be displayed as shown in the below screenshot.

Step 12: In IE browser, please select the Print -> Page set up as shown in the below screenshot.

Step 13: On click of Page Setup, below specified screenshot will appear. Please modify the settings as shown in the below screenshot. Please ensure the Page Size is selected as PassbookNew1 and Enable Shrink to Fit option is unchecked.

Also, the Headers and Footers section, all the fields needs to be selected as Empty.

Step 14: After doing the above changes, a sample passbook may be printed for the first page and the next page for confirmation and verification.

PAGE

Appreciation GuideVer. Rev. 1.0c

ReleaseNotes_v1 0_Dop_PPF.doc Ver.No. 0.1

Company Confidential

Sheet1

S.NoApplicationFSI EngineerFSI Project Manager

1FinacleName : Manivannan AyyamperumalMail Id : manivannan_a01@infosys.comPhone : 91 8939834655Name : Amit DubeMail Id : Amit_Dube@infosys.comPhone : 91- 9840003023

2ECMSName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444Name : Deepthi TMail Id : Deepthi_T@infosys.com@infosys.comPhone : 91- 9840269338

3PLI -Agent PortalName :   Gaurang DeshpandeMail Id : Gaurang_Deshpande@infosys.comPhone : 91 9730949809Name :   Swapnil NarkhedeMail Id : Swapnil_Narkhede@infosys.comPhone : 91 9960874874

4PLI-Customer PortalName :   Neha MathurMail Id : Neha_Mathur03@infosys.comPhone : 91 9623789318Name :   Pooja NigamMail Id : Pooja_Nigam@infosys.comPhone : 91 9028228090

5PLI-NBF PortalName :   Vivek IngaleMail Id : Vivek_Ingale@infosys.comPhone : 91 8055868631Name :   Shobha BhandariMail Id : Shobha_Bhandari@infosys.comPhone : 91 9960713991

6PLI - McCamishName :   Rajeev RanjanMail Id : rajeev_ranjan17@infosys.comPhone : 91 9096457324Name :   Arvind AmbedkarMail Id : arvind_ambedkar@infosys.comPhone : 91 9158006689

7Sanchay PostName :   SrivathsaniMail Id : srivathsani_m@infosys.comPhone : 91 9790971412Name :   Shiv KumarMail Id : Shiv_Kumar10@infosys.comPhone : 91 8041564786

8PLI - Data Migration Insurance (PLI DM)Name :   Senthil Babu BabuMail Id : Senthil Babu Babu@infosys.comPhone : 91 9940644953Name :   Ashok Shanmuga SundaramMail Id : Ashok_S08@infosys.comPhone : 9840445347

Revision

Infosys

FSI-DOP

FSI - Escalation Matrix

INFOSYS TECHNOLOGIES LTD.

Document Revision History

Ver #DateAuthorComments

0.131-Jan-14InfosysInitial Draft

0.218-Feb-14InfosysUpdated few contacts and formatting done

Finacle

Elapsed Time Severity level 1 Severity level 2 Severity level 3 Severity level 4

To be resolved by (within 2 hours) FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489

4 hours FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91 8039133604FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91-8039133604FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91-8039133604FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489

8 hours FSI Project Director Name : Amit DubeMail Id : Amit_Dube@infosys.comPhone : 91-9902016444FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91-8039133604FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91-8039133604FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489

16 hours FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Project Director Name : Amit DubeMail Id : Amit_Dube@infosys.comPhone : 91-9902016444FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91-8039133604FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91-8039133604

24 hours FSI Country Manager Name : Balamurugan PalanisamyMail id : Balamurugan_Palani@infosys.comPhone : 91-9790960811FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Project Director Name : Amit DubeMail Id : Amit_Dube@infosys.comPhone : 91-9902016444FSI Project ManagerName : Vinoth M. C. K.Mail Id : vinoth_mck@infosys.comPhone : 91-8039133604

36 HoursFSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91-9920630925FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Project Director Name : Amit DubeMail Id : Amit_Dube@infosys.comPhone : 91-9902016444

48 HoursFSI Region Head Name : Narasimhamoorthy PMail id : pnmoorthy@infosys.comPhone : 91-9880310497FSI Country Manager Name : Balamurugan PalanisamyMail id: Balamurugan_Palani@infosys.comPhone : 91-9790960811FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013

> 48 HoursFSI Region Head Name : Renganathan V. R.Mail id : Rengavr@infosys.comPhone : 91-9980540702FSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91-9920630925FSI Country Manager Name : Balamurugan PalanisamyMail id : Balamurugan_Palani@infosys.comPhone : 91-9790960811FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013

ECMS

Elapsed Time Severity level 1 Severity level 2 Severity level 3 Severity level 4

To be resolved by (within 2 hours) FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91 9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91 9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91 9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91 9841442489

4 hours FSI Project ManagerName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444FSI Project ManagerName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444FSI Project ManagerName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91 9841442489

8 hours FSI Project Director Name : Deepthi TMail Id : Deepthi_T@infosys.comPhone : 91- 9840269338FSI Project Director Name : Deepthi TMail Id : Deepthi_T@infosys.comPhone : 91- 9840269338FSI Project ManagerName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91 9841442489

16 hours FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013FSI Project Director Name : Deepthi TMail Id : Deepthi_T@infosys.comPhone : 91- 9840269338FSI Project ManagerName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444FSI Project ManagerName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444

24 hours FSI Country Manager Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013FSI Project Director Name : Deepthi TMail Id : Deepthi_T@infosys.comPhone : 91- 9840269338FSI Project ManagerName :   Prasath SubramaniMail Id : prasath_subramani@infosys.comPhone : 91 9840213444

36 HoursFSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91 9920630925FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013FSI Project Director Name : Deepthi TMail Id : Deepthi_T@infosys.comPhone : 91- 9840269338

48 HoursFSI Region Head Name : Narasimhamoorthy PMail id : pnmoorthy@infosys.comPhone : 91 9880310497FSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91 9920630925FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013

> 48 HoursFSI Region Head Name : Renganathan V. R.Mail id : Rengavr@infosys.comPhone : 91 9980540702FSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91 9920630925FSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91 9920630925FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91 9940283013

PLI

Elapsed Time Severity level 1 Severity level 2 Severity level 3 Severity level 4

To be resolved by (within 2 hours) FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489

4 hours FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489

8 hours FSI Project Director Name : Arvind Ambedkar Mail Id : arvind_ambedkar@infosys.comPhone : 91 9158006689FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164FSI EngineersName : Raghuraman PichumaniMail Id : Raghuraman_P01@infosys.comPhone : 91-9841442489

FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

16 hours FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Project Director Name : Arvind Ambedkar Mail Id : arvind_ambedkar@infosys.comPhone : 91 9158006689FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

24 hours FSI Country Manager Name : Sanjay Jhandial Mail id : sanjay_jhandial@infosys.comPhone : 91 9873021895FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Project Director Name : Arvind Ambedkar Mail Id : arvind_ambedkar@infosys.comPhone : 91 9158006689FSI Project ManagerName : RajanarayananMail Id : rajanarayan_202565@infosys.comPhone : 91 8446022164

36 HoursFSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91-9920630925FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Project Director Name : Arvind Ambedkar Mail Id : arvind_ambedkar@infosys.comPhone : 91 9158006689

48 HoursFSI Region Head Name : Narasimhamoorthy PMail id : pnmoorthy@infosys.comPhone : 91-9880310497FSI Country Manager Name : Sanjay Jhandial Mail id : sanjay_jhandial@infosys.comPhone : 91 9873021895FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013

> 48 HoursFSI Region Head Name : Renganathan V. R.Mail id : Rengavr@infosys.comPhone : 91-9980540702FSI Country Manager Name :Prakash JayaramMail id : Prakash_Jayaram@infosys.comPhone : 91-9920630925FSI Country Manager Name : Sanjay Jhandial Mail id : sanjay_jhandial@infosys.comPhone : 91 9873021895FSI Relationship Director/FS Head Name : Srihari GopalanMail Id :srihari_gopalan@infosys.comPhone : 91-9940283013

_1456142071/Finacle Desktop setting version1 1.zip

Finacle Desktop setting version1 1.pdf

Finacle Desktop Configuration for version

10.2.13

2 nd

Oct, 2013

YOUR INNOVATION PARTNER

Finacle Desktop Configuration and IE setting __________________________________________________________________________________

DISCLAIMER

This document is prepared based on the requirement for desktop configuration for Finacle 10.2.13 version presently used by the bank. Changes may be there in future as per the changes in the Finacle version or upgrade.

Version History

Ver. No.

Ver. Date Revised By Description Reviewed By

Rahasya Kaul, Amit Dube , Rajshekar 1.0 02.10.2013

Kavita Sumanth M. S Finacle Desktop Setting

__________________________________________________________________________________

2 of 49

Renu Kumari

Finacle Desktop Configuration and IE setting _________________________________________________________________________________

Table of Contents

1. FINCORE Settings ....................................................................................................... 4

1) INTRODUCTION .................................................................................................... 4

2) DESKTOP SETTING ............................................................................................... 4

3) FINACLE UBS INTERNET EXPLORER SETTINGS. ......................................... 4

4) SETUP SPECIFIC TO TRAINING DESKTOP. ..................................................... 26

5) INSTALLING CERTIFICATE ................................................................................. 26

2. Finacle e-banking Desktop requirements ................................................................. ..34

__________________________________________________________________________________

3 of 49

3. JAVA Control Panel Settings....................................................................................... ..35

4. Passbook Printer Settings....................................................................................... ..39

5. Settings for Signature enquiry throughSVS ...................................................48

6. Procedure to Import Registry key………………………………………..………….49

Finacle Desktop Configuration and IE setting __________________________________________________________________________________

1) FINCORE

1. Introduction

This document explains the desktop configuration and Internet Explorer settings for Finacle UBS Installation 10.2.13. This document explains Internet Explorer (version is IE8.0) Settings for Finacle Solutions.

2. Desktop Setting

Operating System: Windows 7/Windows XP Internet Explorer: Internet Explorer 8.0

Adobe flash player: Version 10.1.85.3 Java Version: Sun JRE 1.7.0_17 Adobe Reader: Version 8.0

3. Finacle UBS Internet Explorer Settings.

Please follow the below Internet Explorer settings for Finacle applications.

__________________________________________________________________________________

4 of 49

Finacle Desktop Configuration and IE setting __________________________________________________________________________________

Step Description

1. Click on Tools below fi