Support #10190
[SCP ID :##5108##] : Invalid SMS TAC at 7510 instance
| Status: | Closed - End of life cycle | Start date: | September 04, 2019 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | MY RIB | Spent time: | - | |
| Target version: | - |
Description
Hi Hafiz,
Kindly attend below request.
Customer not able to proceed with the transaction (with valid TAC entered) due to "TAC not valid for this Transaction" error message. We have tested all the instances, and from our observation, only 7510 instance will hit this issue. Appreciate your prompt action to check on this and feedback us on the root cause soonest possible. Thank you.
History
#1
Updated by Yap Kah Yan almost 5 years ago
- Status changed from New - Begin Life Cycle to Pending Customer Feedback
- Assignee changed from Hafizudin MD to Zahir Abd Latif
Root Cause:
Transaction type and amount in SMS bean different from Hibernate Service bean.
The information stored in database and user execute when verifying TAC do not match
Possible not able to update the value in TAC table.
Solution:
to restart BV services
#2
Updated by Zahir Abd Latif almost 5 years ago
- Status changed from Pending Customer Feedback to Closed - End of life cycle
- % Done changed from 0 to 100
Issue closed in SCP.