Support #4956
[SCP ID :##2491##] : Rentas Trx Not Reflected in Corus & BVMC Report.
| Status: | Work Completed-End life cycle | Start date: | January 07, 2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | January 08, 2015 | |
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | MY CORUS | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
3 successful Rentas transactions performed from CMS but not reflected in Corus Enquiry Screen and in BVMS Report. Details of these 3 transactions are required to be processed by CPO team.
findings.txt 
(20.6 KB)
Related issues
History
#1
Updated by Nor Shuhaida Subri almost 10 years ago
- Status changed from New - Begin Life Cycle to Pending Review
- Assignee changed from Nor Shuhaida Subri to Norhaidah Md Dasuki
Data of the transaction is not log into DB.
Check on table
BIB_INTER_TRANSFER
BIB_BULKPAYMENT_DETAIL
RENTAS_DETAIL
& logs provided also not much help.
Already recommend to IT (Syikin) to deploy Patch 1
As we all know, Penril had provide solutions to enhance the Logger and exception handling to deal with issues like this.
#2
Updated by Zahir Abd Latif over 9 years ago
Dear Kak Haida,
Last email from customer : Re: [Request ID :##2491##] : Rentas Trx Not Reflected in Corus & BVMC Report
From Norashikin, Hi Penril support; As last discussion with user and Penril team, this issue is not related to the logger enhancement. As what i understood from the discussion, the issue for this is that the complete transaction of impacted Rentas transaction is not stored in the database , whereas the enhancement is more to capture the information for the stored transaction. Sara / Chooi; Correct me if i'm wrong.
Can we proceed to close it?
Please advise.
Thanks.
#3
Updated by Norhaidah Md Dasuki over 9 years ago
- Due date set to January 08, 2015
- Status changed from Pending Review to Development / Work In Progress
- Assignee changed from Norhaidah Md Dasuki to Hafizudin MD
- Start date changed from November 26, 2014 to January 07, 2015
Hafiz,
Kindly check on this issue.
#4
Updated by Yap Kah Yan over 9 years ago
IT to confirm if the the transactions is logged into IBG_ENTRY table.
If got logged in IBG_ENTRY, then this issue is related to logger enhancement (not implemented).
#5
Updated by Yap Kah Yan over 9 years ago
- File findings.txt added
Upon checking the logs, we found that the error is cause by inserting null value in OID column.
This issue happened after DR activity and was solved at 26/12/2014.
Similar issue will not occur again as all the missing triggers are created in production after the DR activity.
Caused by: java.sql.BatchUpdateException: ORA-01400: cannot insert NULL into ("BIB"."BIB_COMPANY_TRANSACTION"."OID")
#6
Updated by Ngoh Chee Ping over 9 years ago
- Status changed from Development / Work In Progress to Work Completed-End life cycle
- Assignee changed from Hafizudin MD to Zahir Abd Latif
#7
Updated by Zahir Abd Latif over 9 years ago
- % Done changed from 0 to 100