Task #1053
IBSCR030 - New Phoenix SP for Branch Code Checking
| Status: | Closed - End of life cycle | Start date: | July 21, 2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Sarinah Darsy | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
New Phoenix Store Procedure to be integrated for “branch numberâ€, “application type†and “account type†retrieval base on account number. The previous logic to handle branch code in IB is not sufficient anymore when branch number grows more than “010†which the old branch number start with “01 & 02â€.
CR As attached
History
#1
Updated by Sarinah Darsy about 13 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
- Assignee set to Sarinah Darsy
- % Done changed from 0 to 20
In process of development.
Checking at Coding, current values to get branch code, acct type and acct appl are from our own method that is cannot be used if branch grows to more than 010. We will use new SP to get Branch code from phoenix that pass to us all info of branch code, acct type & acct appl from the account No.
Projects should be change are:
ESBWebService - create new method that called the new Sp getBranchCode
kfh_consumer - modify setter bean to set info of branch code, acct type and appl type to ESBAccountNumber.java.
kfh_bib - modify setter bean to set info of branch code, acct type and appl type to ESBAccountNumber.java.
kfh_corus - modify setter bean to set info of branch code, acct type and appl type to ESBAccountNumber.java.
IBGCore - modify method that set branch code, acct type and appl type (CreditingEngine.java).
Done on ESBWebService projects. But currently cannot test at development since they doing something on phoenix.
#2
Updated by Sarinah Darsy about 13 years ago
- % Done changed from 20 to 50
Changes done on the coding.
Need to test it on the development environment whether it is successful or not.
pending on user preparation on the Phoenix Development testing environment.
#3
Updated by Sarinah Darsy about 13 years ago
- Status changed from Development / Work In Progress to Pending Customer Feedback
- % Done changed from 50 to 90
Already revert to user on the table column size problem.
Waiting for the user feedback.
#4
Updated by Sarinah Darsy about 13 years ago
Forgot to mention, after changes on table column size made, User need to re-register the user again otherwise the error user will get the error message of "Username already exist." since the user id already stored at DB.
#5
Updated by Sarinah Darsy about 13 years ago
- Status changed from Pending Customer Feedback to Development / Work In Progress
- % Done changed from 90 to 40
Aiyaaa..just noticed, i was wrongly update the redmine case. the past 2 updates is for Case ID: HD00011535 - Approve Corus CMS user which url is http://hub.penril.net/redmine/issues/1064.
Please ignore it.
For this Case KFH IT already given phoenix development testing to us but it is still pending on the new SP for getBranchCode. So, we cannot do any testing for this issue yet.
#6
Updated by Sarinah Darsy about 13 years ago
- % Done changed from 40 to 80
Pending on user to give us the sample Batu Pahat Account No to test on this.
ESBWebService part done and tested successfully.
Now need to test at the kfh_consumer, kfh_bib, kfh_corus and IBG to test on this issue once the account no are ready.
But so far, the existing account no looks ok.
Will need Ayu help to test on IBG OFI and RFI testing.
#7
Updated by Sarinah Darsy about 13 years ago
- % Done changed from 80 to 90
Current status for this UAT:
Tested Successfully today:
1) GIA Placement & Upliftment
2) FTT
Pending:
1) Bulk Payment - Pending Penril to check. Still failed to debit intrabank, rentas and IBG trx as bulk status still remain as "Accepted".
2) IBG OTC (GFS) - Still pending IT (Harmizam) and Penril to recheck the relevant SP to be used & update into env 6001.
1) Bulk payment - error on result set when getting below query:
"select BIB_COMPANY.* from bib_company where bib_company.company_id = (select bib_bulk_payment.customer_id from bib_bulk_payment where bib_bulk_payment.batch_id = ?)"
This query apply on all module (IBG, RENTAS & IBG). But all the module will return the same error.
I didn't touch on this java file to fix this issue. Before this it was ok. right now, running this query on toad it was no problem but when deploy it into Bulkpayment project would return the error of:
INTRABANK
-------------
09 Aug 2011 18:08:50,620 ERROR Intrabank:246 - java.sql.SQLException: Missing IN or OUT parameter at index:: 2
java.sql.SQLException: Missing IN or OUT parameter at index:: 2
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1681)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3280)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3329)
at net.penril.engine.Intrabank.process(Intrabank.java:165)
at net.penril.engine.BulkPayment.main(BulkPayment.java:39)
=============
IBG
------
09 Aug 2011 17:42:30,451 ERROR IBG:243 - java.sql.SQLException: Missing IN or OUT parameter at index:: 2
java.sql.SQLException: Missing IN or OUT parameter at index:: 2
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1681)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3280)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3329)
at net.penril.engine.IBG.processIBG(IBG.java:157)
- Still not yet Fixed, checking. Will ask Wei Cheng too.
2)*IBG OTC (GFS)* - error coz there are no SP for getBranchCode at Phnx 6001. KFH IT team already put the SP into it but user has yet test it.
#8
Updated by Sarinah Darsy about 13 years ago
- Status changed from Development / Work In Progress to Work Completed-End life cycle
- % Done changed from 90 to 100
UAT done successfully.
No more pending issue.
#9
Updated by Sarinah Darsy about 13 years ago
- Status changed from Work Completed-End life cycle to Pending Prod Deployment
#10
Updated by Vincent Devethas almost 13 years ago
- Status changed from Pending Prod Deployment to Work Completed-End life cycle
Completed and moved to production
#11
Updated by Norhaidah Md Dasuki about 10 years ago
- Status changed from Work Completed-End life cycle to Closed - End of life cycle