Solution for RD account Runtime error in DOP Finacle

While closing the RD accounts ( or any other accounts) we generally face the error "Runtime error has occured" as mentioned in the below screen shot.

The screen shots for the said error is mentioned below for reference 

When we close the account i.e., when we click on submit then the system will throw the error as mentioned below

One can observe the error "Runtime error has occured" in the above screen.

Solution for the above problem.

In order to solve the above problem the user has to check the following before attempting the closure for RD ( or any other schemes) they are listed below below for reference and kindly follow them

If the user selected the repayment mode as SB account then check whether the SB account is Dormant ?

Solution:- If the repayment SB account is Dormant then invoke CASBAM in the counter PA role and modify the account status to Active submit and verify the modificaiton in the supervisor.

2. If the user selected the repayment account as SB account then check whether any modification exists for the SB account?

Solution:- Use the menu HAFI and enter the SB account number and click on authorised as "Not authorised" and then click on GO then the system will show pending verifications. If the function is M (modification done but not verified ) verify in CASBAM or if the function is Z(closure attempted) then cancel the closure.

3. If the user selected the repayment account as SB account then check whether SB account authorized or not?

Solution:- Check using HAFI as mentioned above and then authorise the account using the menu CASBAV and then proceed.

4. If the user selected the repayment account as SB or 0340 account then check the CIF status of RD account (closing account) 

Solution:- Invoke CMRC and check the DOB of customer for Ex;- if DOB is 15-03-1527 which is invalid then change the DOB to correct vale submit and verify.

5. If the user attempted closure then check whether any previous modification pending for the closing account.

Solution:- Invoke HAFI and then check the pending authorizations and clear them using the respective menus.