Latest Updates

**CIF Modification Issue is said to have been resolved.Please check**

Recent Posts...

Blogger Tips and TricksLatest Tips And TricksBlogger Tricks

Wednesday, 9 March 2016

CBS_FAQ_RD_NSC_PPF

  
Table of Contents







1. Common Issue to RD_PPF_NSC ISSUES.

1.1.   Issues in Certificates


1.1.1.      If any transaction is in entered status and on posting the transaction, it throws exception:

Exception would have the format - 3 letter code – Exception Description.
Following steps to be carried
·                       Credit & Debit legs accounts are proper
·                       Check the transaction is a valid one
·                       Then disable the exception through HEXCDM menu
·                       Post & verify the transaction (Then proceed with EOD)
·                       Then enable the exception through HEXCDM menu


1.1.2.       NSC/KVP accounts not fetched

Error Screen shot
Solution
The input criteria provided in the Registration No. field is incorrect. R has to be suffixed for Registration number. For similar error ,users should always cross check that all inputs provided is correct as sometimes wrong product type is given, some times wrond cif id is given.If all inputs are correct, then Cancel the closure through HCAACVTD menu and try closure once again through CACCAAC menu.Issue might have been due to slowness/network

1.1.3.      Certificate not available in Finacle ( record not migrated)

Issue Reported : At NSC Counter, A NSC is presented by Customer Of Rs.10000/- In the name of Shri Harish R Jakhete with Regn No. 80537 dated 21.10.2005  Certificate No.69EE265815 . But while Discharging the certificate, the error shown is as "No records fetched". Hence it is not possible for us to discharge the certificates.
Solution: There is a possibility that the certificates are not  migrated. Please check re-conciliation report if NSC was avilable in Sanchay Post or check data digitization sign off report if NSC were issued manually. Approach  DMCC.

1.1.4.      Issues during Discharge of Certificates

Whenever the Certificates are discharged, the cash transactions are done by the user for paying out the proceeds to the customer. At the same time, the NSC/KVP account needs to be closed by the teller in Finacle.

1.1.5.      While  transferring an account from one sol to another in HACXFSOL menu,error faced is “Fatal error. CMG details not found"

In such case,the user need to check if the cif id associated with the account or with the joint holder  is deleted or not by checking in CMRC menu in inquire mode.If it is deleted,then the user may not be able to transfer the account from one sol to another

1.1.6.      Certificate number is mising and is not attached to the Acocunt.

1.    Please check the status of an instrument using HIMI menu by providing details such as Date/Cerificate Alpha/Number etc.

1.1.7.      Not able to print Certificates

1.         The certificate needs to be printed as and when it is given to the customer.
2.         In case the certifcate is manually written and shared it with customer - a dummy print needs to be executed in Finacle. Ensure printed succesfully radio button is ticked and submitted during executing the menu HDRP.
3.         The critical point is certificate inventory should be moved from DL (double lock) to EM (Employee Location) as and when printing is required.
4. There Should never be a case where a customer is given a hand written certificate and print is fired later. This would lead to mismatch of certificate number.
5. In case certificate is wrongly printed  and the customer has returned or the post office is in possetion of the wrong certificate - a duplicate certificate needs to be printed using HDUDRP menu option.

1.2.    Account  opening issues


Issue Reported: While opening account in any scheme users are getting error as "The customer record is not entered through HCCFM menu option".

Solution:
User has to navigate the details page of CMRC for the CIF ID with which account needs to be created to create entry into HCCFM if does not exist. No need to submit the CMRC screen. Post navigating to details page try to create an account. If still error comes raise a ticket in Meops.

1.3.   RD issues:


1.3.1.      The unscheduled payment or demand satisfaction is done after the value date. Reverse them before doing payoff:

[01] If the loan principle repayment happened on or after 01st of a month, then loan interest is applicable for the current month as well.
[02] The HAPYOFF to be executed on or after 11th of the month for interest run, so that the loan can be closed.

1.3.2.       The withdrawal amount exceeds the difference between the principal  and lien amount:

What type of lien is being put in RD Accounts? As per discussions held with Mr. Vijayan, there was no need to put any lien in RD Accounts as Finacle is calculating default fee for the premigration defaults also.
Solution :
This issue occurs when there is a lien placed at the account which is being closed. This lien can be seen in the menu HALM. The lien has to be removed by making the expiry date as System Date and then the closure should be done.
There will be no Lien for default fee. DOP has agrred to waive it off.







1.3.3.      RD Opening (CRDOAAC):


A.    CMSG000292 - Debit Account is having -ve Balance:
Cause: This error will occur when Debit Account ID in transaction details part is not having sufficient balance to debit.
Solution: Either the given debit account need to be funded enough to debit or use any other account which is having enough credit balance to debit.

B.    W0205 - The value date must be more than the minimum value date for the account [14-01-2013]. in part tran no – 0
Cause: The above error will occur when the debit account in transaction details part is opened after the account opening value date on which transaction cannot be done with the mentioned value date.
Solution: use any account which is opened before the account opening value date.











C.    Error: - The cash account for the entered currency is not available.

Cause: The above error will occur when the user is not a teller and trying to do the CASH type of transaction.
Solution: Attach the CASH account to the user to make teller or proceed with transfer type of transaction.

1.3.4.      RD Modification (CRDACM):


A.    E4927 - acctCommonInfo.acctGeneralInfo.acctBasic.foracid----Cannot perform the requested operation. Account Maintenance Modification Pending verification.
Cause: The above error will occur when the user is trying to modify an account which is already modified and not verified.
Solution: Verify the previous modification before doing any other modification.

B.     E4221 - Document Due Date should be less than maturity date


Cause: Document due date entered is more than maturity date.
Solution: Document due date should be between account open date and maturity date.

1.3.5.      RD Payment (CRDP):


A.    Credit account is in Invalid status or total dormant

Cause: The above error will occur when the user is trying to do transaction on an account which is frozen due to nonpayment of installments.
Solution: Ideally payment should not be accepted for these account. If still payment need to be processed, check the pending installments in HPLIST and unfreeze the account through HAFSM.
B.    Error: - Transaction is not allowed on matured Deposits

Cause: The above error will occur when the user is trying to do transaction on the account which is already matured.
Solution: Ideally payment should not be proceed on matured account. If still payment need to be accepted please differ the maturity date in PMDDRD menu and then check the possibility of payment. Deferment can happen for maximum of 4 months only.

1.3.6.      RD Closure (CRDCAAC):


A.    RD Acct was successfully closed by the CPA, while verifying the record from Supervisor it showing an error "An unverified record exists for the [0983523996].The account cannot be closed

Solution:- A loan account was opened for the mentioned RD account which is not yet verified. Please cancel the loan account creation in CAOLARDV to proceed with RD account closure
B.    RD Maturity Date Falls on a Holiday and user wants to close the previous day.
In this case, Finacle will consider this as a Premature Closure and Full interest will not be paid.Hence user should always be cautious and wait for Maturity Date to be over for closing the account. User can close on the next day of Maturity date
C.    CMSG001051 - Lien Exists on the account
Cause: The above error will occur when there is an unpaid loan exists on the RD account.
Solution: Loan needs to paid first through HPAYOFF or HLAUPAY and then only RD closure can be processed.
Note: This error is not applicable in case of premature closure as the system will automatically deduct the loan from RD proceedings.
D.   Error - A time stamp error occurred.

Cause: The above error will occur when the account closure is happening on an account which is modified and not verified.
Solution: The account modification need to be verified or cancelled through CRDACM before closing.
If user is not able to verify or modfiy through CRDACM menu(When he tries to modify/cancel the modifications in CRDACM, the cursor automatically switches to Modify mode every time account no is entered and user gets the below mentioned error) like in below screenshot.
Solution:-The issue is because cif_id of the mentioned account has been suspended and modifications are pending for verification in CRDACM. The steps to be followed are:-
1.    Unsuspend the cif_id in CMRC and verify it
2.    Verify/Cancel the modifications in CRDACM for that account.
3.    Suspend the cif_id again in CMRC and verify.
4.    Proceed with death closure in CRDCAAC.  

E.    CMSG000095 - Advance Payments exists for this account

Cause: The above error will occur when there are advance payments exists on the account.
Solution: Account can be closed only after the date till advance payments paid. Till then account cannot be closed.
F.    Error: - Closure pending on SI for the account
Cause: The above error occurs when the user trying to close an account on which Standing Instruction (SI) is placed.
Solution: SI need to be removed in HSIM menu to proceed with RD closure.
G.   Close failed for undefined reason OR Scheme validation failed.

Cause: The above error will occur when the Repayment A/c. ID is dormant which will not accept any credit.
Solution: Either the mentioned repayment account need to be changed to Active or cancel the closure and use any other account as Repayment A/c. ID.

1.3.7.      RD Extension (PRDCM):


A.    W0205 - Continuation is not allowed as there are pending installments for this A/c.

Cause: The above error will occur when the user is trying to extend the account for which there are pending installments.
Solution: Check the pending installments in HPLIST. If there are pending installments, extension is not possible. Most of the cases user is trying to extend the accounts which are already extended. That time also the same error will occur.
B.    All the installments are already paid for the specified RD account and the user is trying to pay the installment without extending.
Solution:  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.4.   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


1.5.   Cash/Teller account related errors


1.5.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).








1.6.   NSC/KVP Issues:


1.6.1.      NSC account opened but verification is not happening


Solution:
The above error occurred when during account opening, only  instrument date has been entered and no other instrument details  entered 
In such cases, the transaction will not be posted and has to be deleted in HTM menu. Once the transactions are deleted , the accounts opening has to be cancelled and then new accounts have to be opened again with proper data entry.

1.6.2.      Bulk Discharge of Certificates not supported.

Issue Reported: All Certificates under a Registration Number due for Closure, cannot be closed in one go.

Screenshot for the new Menu:


Solution: New Menu CNSBCV has been created for Bulk Discharge of Certificates

1.       Using this menu Users can close UP TO 50 certificates belonging to same Registration Number and CIF Id combination can be closed in one attempt.
2.       Both NSC and KVP certificates can be closed using the menu.
3.       Bulk Closure can be used only if ALL the certificates under Registration Number and CIF Id combination are mature and due for closure, ELSE accounts need to be closed manually.
4.       Users can Close, Verify and cancel the Certificates using the same menu.
5.       Function Code, Registration Number, CIF ID and Product Type are the fields mandatory to be provided by the user.
6.       Other fields such as Sol Id, Closure Value Date and Closure Reason Code are auto populated.
7.       Only same sol operations are allowed in this menu so the field is un-editable.
8.       If customer does not want to receive cash and wants to specify a specific Repayment Account Number instead of Operative Account mentioned at Account Level, value can be entered in Repayment Account Field Provided.
9.       Once the closure request is initiated, the same needs to be verified by another user on the menu by providing same Registration Number and CIF Id combination.
10.   After verification the closure for the available mature certificates (maximum 50) will be initiated.
11.   Discharge Journal will be generated in HPR after 10mins, where user can check the status of individual account closure.
12.   If there are more than 50 accounts for a Registration Number and CIF Id combination eligible for closure, user needs to invoke the same menu recursively after one request is completed and report is generated in HPR.

1.6.3.      NSC Account Opened but not verified Issue

Its seen that sometimes during EOD, NSC accounts are in unverfied state and EOD user is deleting the transaction ids and verifying the Account Opening creation. In such cases, such NSC accounts cannot be used for any purpose. Hence the correct solution is that if user is deleting the transaction, user need to cancel the account openning through CSCOAACV menu.

1.6.4.      NSC/KVP Account Opening for a Minor

For NSC/KVP Account Opening for a Minor, the below error message appears.
“For this mode of operation, should enter more than one joint account”
1.   
Solution:Since the Account is opened for a Minor, please add guardian details in Related Party Details2 tab.




1.6.5.      Issue in NSC Certificate Printing through HDRP

While printing user gets error "Could not get reponse from server" as in below screenshot.
Before raising incident, user should check if printing is already happened or not for the account by "Inquiring" in CSCACM menu as below.
In the details page receipt alpha and receipt number will be updated if printing happened successfully.
If not, user need to wait for server slowness issue to be resolved by support team.User can get status from CEPT team on same and once slowness issue is resolved, user can try printing again

1.6.6.       NSC Account Opening-Wrong Instrument Details Issue

    Normally When instrument details are given wrong during NSC account opening, Finacle will throw error during NSC verification that Wrong Instrument details. At this time all the transactions will be in entered state. Branch user need to delete all the transactions at that time itself after checking through HFTI with user id who opened the accounts and cancel the account opening for the registration number using CSCOAACV menu. After this user can reopen with correct instrument details.
If this process ca be followed strictly before EOD, then there will be no issue. Otherwise EOD support users will try to post the transactions which they can post and delete only the problematic transaction with wrong instrument number. Next day user will be verifying the account number using HOAACVTD which is wrong. As a registration number with one account having zero balance will not work for other accounts as well.
b)Suppose, the user has left the Account opening as it is with wrong instrument details and support team has deleted transactions for the first account, then the process to be followed is as below.
1) Cancel the account opening for the Account where balance is zero using HOAACVTD menu.
2) Verify all other accounts where balance is non-zero and close these accounts.
3) Reopen again under another registration number.

1.7.   PPF Account Related Issues.

Many of the issues raised for PPF accounts can be handled manually from the front end menus. 

1.7.1.      The PPF account already linked to a Loan account hence cannot be closed

Issue Reported : PPF account linked to Loan Account cannot be closed.
Screenshot :
Solution :
Sl.no
Menu
Steps to be followed for successful PPF + Loan against PPF account closure
1
CPDTM
The Loan principal repayment needs to be done, [principal amount -> zero]
2
CLPR
Enter the Loan account, on submit it will be processed.
3
HACINT
Particular loan account should be entered. Calculated Interest amount will be applied in this menu, this value can be viewed in detail in HACLI menu/CLEAR BALANCE.
4
CPDTM
If the loan account is not yet matured, CPDTM - Interest repayment [which was calculated in steps 2/3], [ Interest amount -> zero]
5
CPWTM
Else If the loan account is Matured, CPWTM - Interest recovery [which was calculated in steps 2/3], [ Interest amount -> zero]
6
HCAAC
The Loan account should be entered and Loan against PPF can be closed here.
7
HCAAC
The PPF account should be entered and PPF account can be closed here. If it is pre-mature closure, Reason code should be entered in the closure tab.

Note [Rare case]: [01] If there is loan account of the PPF is closed then this steps go though. [02]
[02] The Cancel Function in HCAAC will cancel the account closure, The Closure transaction should be reversed manually.

 

1.7.2.      PPF Transfer out : Steps to be followed

Procedure:  
[01] In HINTTM menu, Change the interest table code for the PPF account to ‘ZERO’  with start date as the current Financial Year Start date and End date as 31-12-2099 date.
[02] Close the account from HCAAC menu. This can be done as pre-closure as well.(can be done by higher role person like Supervisor, etc.,).
[03] [This will ensure the interest application for current year is not applied to the Account at DOP and the interest for the full year can be applied in the new Bank during the next interest application.]

1.7.3.     PPF Transactions cannot be created from menus CXFER/HXFER

Solution : Only PPF Transaction menus (CPDTM/CPWTM) to be used for PPF Contribution / Withdrawal. In case of CHQ clearing, The CHQ has to be cleared and deposited into Office account, Then the fund has to be transferred to PPF account as TRANSFER/Normal Contribution in CPDTM menu.

1.7.4.      Loan interest amount to be collected for an already closed LNPPF account

1. Solution : As the LNPPF account is already closed, the interest amount can be directly paid to the Office(P&L) account.
[01] Invoke HTM Menu as Normal Transfer Transaction.(T/BI).
2.    [02] Enter the Cr. Account number as Office account number(P&L).
3.    [03] Enter the Dr. Account number as Customer’s operative account.
4.    [04] Enter the interest amount as the transaction amount.
[05] Enter the transaction particular as per this scenario.
5.    [06] Click on Submit.

1.7.5.      PPF withdrawal is not allowed if account is in minimum withdrawal period.

The screenshots shows that the PPF withdrawal not allowed
Solution : There are two cases in this.
[01] If withdrawal start date is 5 years from the end of account opening FY, which has not arrived, then the customer can avail the loan after the withdrawal start date.
[02] If the Loan eligibility start date started, the user can able to do a "Loan Disbursement", instead of taking a withdrawal.

1.7.6.      Matured PPF account with DISCONTINUED/INVALID status cannot be extended.

The screenshots shows that an error occurred during PPF extention.
Solution :
If a matured PPF account is in DISCONTINUED/INVALID state, it cannot be extended, also the account cannot be made active by paying late fee. Because
[01] Transactions not allowed after maturity and before extension.
[02] Extension not allowed if the state is DISCONTINUED or INVALID.

1.7.7.      Withdrawal is not allowed for extended PPF account if the eligible amount already withdrawn.

Clarification :  
[01]For an extended account the eligible withdrawl amount is [ 60% of it's Balance on maturity date - Sum of Withdrawal amount after maturity ]
[02] For this account the amount was already withdrawn in the previous years after maturity.
[03] Hence the amount shown with lesser value.


1.7.8.      Date of Account Opening of PPF to be changed for an account in which wrong data has been migrated as it is from sanchay post

Solution: The account open date cannot be corrected. In this case, the PPF account has to be closed and new PPF transfer-in account to be opened. In case of pre-closure, the user/CPA will not be having sufficient work class to do pre-mature closure. In such case, the supervisor or higher role person will be having access to do pre-mature closure of PPF account

1.7.9.      Fee transaction reversal for PPF account which has proper yearly subscriptions from other than CPDTM menu

For PPF accounts all the on-line transactions to be entered from CPDTM, CPWTM menus. On 2014-15 FY there are no transaction entered from CPDTM menu, hence even though there is a contribution the fee has been deducted. As the wrong Fee amount is collected as part of income, it can bear by a loss of same amount in P&L account. The collected fee amount has to be paid back from Office(P&L) account to the PPF account as a Normal Contribution transaction, the report code has to be used here as EXCPN

1.7.10.   PPF account holder name has been entered wrongly in Legacy, the same to be corrected.

PPF account number got mistakenly entered wrongly in legacy system and the same got migrated into Finacle. If the same requires correction then
Solution: The menu HAALM to be used for this correction. This requires verification as well.

1.7.11.   PPF account level name change

The PPF account level name can be changed from HAALM menu. The CIF level name can be changed from CMRC menu separately.


1.7.12.   Transactions cannot be created with back value date lesser than account opening date of PPF accounts.




For transfer-in accounts, the account opening date should be given as the actual account opening date in the previous bank. In case if the BOD date is given as account opening date then the history transactions can be uploaded, hence the account can be closed and new account to be opened with back account open date. Also the history transaction to be uploaded for the newly created account

1.7.13.   Extension to be done on matured PPF accounts to continue transactions.

The PPF accounts can be funded or partial withdrawal can be done on matured accounts, only after extension of the same in HCEXTN menu. For referring the account maturity date the menu CPPFAM – Inquiry function can be used

1.7.14.   Transactions cannot be done on INVALID PPF accounts

As per the requirement, if the sum of contribution in the FY of account opening date is less than 500, then such account will be marked as INVALID in EOY. Only closure is allowed on such accounts.

1.7.15.PPF account pre-closure issues

PPF pre-mature closure : If PPF account is not yet matured, but due to some exceptional reason like transfer-out the customer opting for closing/full withdrawal. It is termed as Pre-mature closure.

1.7.16.Same account number has been entered in Both Credit and Debit  Account fields of CPDTM

The screenshots shows that the user entered PPF account number in both the Credit A/c and Debit A/c fields.


Solution: Two Transactions needs to be created, one is for reversal transaction and the second one for actual required transaction.

1. Reverse Wrong TXN :
[01] Invoke CPWTM menu as Normal Withdrawal in TRANSFER mode 
[02] Enter the PPF account number in both Credit and Debit Account number Fields and tran amount same as in Wrong transaction,
[03] Enter the report code as "REVRS",
[04] Click on Submit

2. Enter new proper Transaction :
[01] Invoke CPDTM menu as Normal Contribution,
[02] Enter the Right account number in Credit A/c field and tran amount for the required new transaction ,
[03] Keep the report code as "CONTR", same as default populated value.
[04] Click on Submit

1.7.17.Same account number has been entered in Both Credit and Debit  Account fields of CPWTM.

The screenshots shows that the user entered PPF account number in both the Credit A/c and Debit A/c fields.
Solution: Two Transactions needs to be created, one is for reversal transaction and the second one for actual required transaction.




1.            Reverse Wrong TXN :
[01] Invoke CPDTM menu as Normal Contribution in TRANSFER mode 
[02] Enter the PPF account number in both Credit and Debit Account number Fields and tran amount same as in Wrong transaction,
[03] Enter the report code as "REVRS",
[04] Click on Submit.
2.            Enter new proper Transaction :
[01] Invoke CPWTM menu as Normal Withdrawal,
[02] Enter the Right account number in Credit A/c field and tran amount for the required new transaction ,
[03] Keep the report code as "WITDR", same as default populated value.
[04] Click on Submit.

1.7.18.   Wrongly credited into other PPF account

If some other PPF account  number being entered in CPDTM menu, then it has  to be handled manually.
Solution: Two Transactions needs to be created, one is for reversal transaction and the second one for actual required transaction.

1.       Reverse Wrong TXN : |A| Invoke CPWTM menu as Normal Withdrawal, |B| Enter the account number and tran amount same as in Wrong transaction, |C| Enter the report code as "REVRS", |D| Click on Submit.
2.       Enter new Transaction : |A| Invoke CPDTM menu as Normal Contribution, |B| Enter the account number and tran amount for the required new Right transaction, |C| Keep the report code as "CONTR", |D| Click on Submit.

1.7.19.   Wrongly Withdrawn from other PPF account

If some other PPF account  number being entered in CPWTM menu, then it has  to be handled manually.
Solution: Two Transactions needs to be created, one is for reversal transaction and the second one for actual required transaction.

1.       Reverse Wrong TXN : |A| Invoke CPDTM menu as Normal Contribution, |B| Enter the account number and tran amount same as in Wrong transaction, |C| Enter the report code as "REVRS", |D| Click on Submit.
2.       Enter new Transaction : |A| Invoke CPWTM menu as Normal Withdrawal, |B| Enter the account number and tran amount for the required new Right transaction, |C| Keep the report code as "WITDR", |D| Click on Submit.

1.7.20.   PPF account Transaction created with wrong amount by mistake

If wrong tran amount entered  for PPF account  By mistake, then it has  to be handled manually.
Solution: Two Transactions needs to be created, one is for reversal transaction and the second one for actual required transaction.

1.       Reverse Wrong TXN : |A| For wrong withdrawal transaction, use CPDTM to correct, For wrong deposit transaction use CPWTM to correct it|B| Enter the account number and tran amount same as in Wrong transaction, |C| Enter the report code as "REVRS", |D| Click on Submit.
2.       Enter new Transaction : As the wrong transaction has been reversed in the first step, new transaction can be created as per the requirement.

1.7.21.   PPF account closure issues

The screenshots shows that the PPF account closure cannot be verified as the balance amount is zero for the account.


Solution: The closure Transaction needs to be posted

1.       Post the closure transaction and verify the acccount closure in HCAAC menu.
2.       If the closure transaction is in deleted state, then cancel the account closure and close the same account in HCAAC menu, ensure the closure is in posted state.

1.7.22.   Procedure for Nomination Details Modification

Whenever existing Nomination detail need to be modified, please do the following.
1. If user want to delete an existing Nomination, then click on "Del" flag check box for the same record.
2.If there are any other nomination records already available, user need to make sure that the sum of nomination percentage should be hundred for all undeleted records.

1.7.23.   PPF A/c.s cannot be transferred from one SOL to another SOL if the status of the account is Discontinued or Invalid

The below screenshot has been taken from the HACXFSOL menu at the time of getting error for PPF account transfer from one sol to another CBS sol.

Solution : PPF A/c.s cannot be transferred from one SOL to another SOL if the status of the account is Discontinued or Invalid. The same account can be made active if it is discontinued, then transferred . If the account is invalid the account needs to be closed and new account can be opened.

1.7.24.   Default fee paid for PPF accounts has not been shown in HACLI inquiry of PPF A/c

The Default fee  collected from Operative/Cash account, the same will be deposited into       Office account. Hence the same can be seen from operative account's inquiry, and will not be shown in PPF account inquiry

1.7.25.   PPF Withdrawal -CASH Limit Error

The screenshots shows that the PPF Withdrawal and cash limit error  : EA3





Solution:  In TRANSFER MODE the transaction needs to be entered, insead of CASH mode.

1.       As per the requirement withdrawal for >=20,000/- by CASH is not allowed, it should be of TRANSFER mode to customer's operative account.

1.7.26.   PPF deposit not allowed as total deposits will exceed the maximum limit


Solution:  In  this case the sum of deposit amount of both of the minor,  guardian account, if the current transaction makes the sum exceed the limit it will be blocked.

1.7.27.   Debit /Credit Account ID entered is not a PPF account

The below screenshot has been tacken from Loan related transaction in PPF transaction menu. If the entered account number is other than PPF account the error " Debit /Credit Account ID entered is not a PPF account" will be shown


Solution :  For Loan related transactions in PPF transaction menus, PPF account number to be entered in the appropriate field, (ref screenshot : in the field, where the user tried with loan account number)

1.7.28.   CTUPLD menu : File does not exist in path

The below screenshot shows the case where the file name entered wrongly in the menu

Solution :  The file name should be entered completely like TRFRINDET-<A/c Number>.TXT (eg : TRFRINDET-3000365919.TXT  not as TRFRINDET-3000365919, TRFRINDET, 3000365919.TXT, or DOP )

1.7.29.   PPF account Debit /Credit transaction missed before migration

5.8.1.1.                This case needs to be handled manually, To make a missed history transaction,
5.8.1.2.                [01] a new transaction to be created  in PPF transaction menu : with the transaction amount as on BOD (inclusive of interest amount) . Report code should be "EXCPN" (as it is exceptional transaction) [02] If it is history credit transaction, then amount would have already been collected from the customer, hence the Dr. account can be filled with Office account number.
5.8.1.3.                [03] Else, If it is history debit transaction, then amount would have already been paid to the customer, hence the Cr. account can be filled with Office account number

1.7.30.   LNPPF acount cannot be opened if the loan eligibility start date not reached or loan eligibility end date reached(in other words withdrawal start date started)


The screenshots shows that the PPF Loan not allowed to open as the loan eligibility start date not reached or loan eligibility end date reached(in other words withdrawal start date started).
Solution : There are two cases in this.                                                             
[01] If Loan Eligibility start date has not arrived, then the customer can avail the loan after the loan eligibility start date.
[02] If the withdrawal start date already started, the customers can able to do a "Normal Withdrawal", instead of taking a loan.

1.7.31.     Account Discontinuity/ Default Fee is not applicable for extended PPF accounts.


Issue Description : The account’s Default Fee not calculated and shown for extended PPF account.

Solution : The concept of Discontinuity is applicable for PPF accounts which are in lock in period.
[01] The extended PPF accounts have already completed the PPF lock in period and hence the arrears is not applicable.
[02] Late fee amount is also not applicable for extended PPF accounts.

1.7.32.   Freezed account cannot be transferred from one SOL to another SOL.

[01] In HAFSM menu the account needs to be inquired and the current freeze status to be noted down. [02] In HAFSM menu the account needs to be un-freezed and verified.
[03] Through HACXFER menu the account can be transferred from one sol to another.
[04] 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].



No comments :

Post a Comment