Production Ticket(ST) #11527
S@Azhar13 hi, can u help to check CCMN5000012 is missing, as just now doing this collection, the system didn't how the collection No. correctly. and then we download again, check the summary is showed CCMN5000013. checking on web, 0012 is not in the list.
Job Remark:
Ticket Logged Date:
22/04/2024
Ticket No.:
Related Ticket ID:
Type:
Support Request
SLA Initial Response:
22/04/2024
SLA Delivery:
Esclation Time:
Issue Reoccurance#:
Actual Initial Response:
23/02/2024
Resolution:
thsi is due to running number issue in the backed side. Tech team already fix this.
Root cause - Bug
Requester ExpectedDeliveryDate:
Delay Justification:
Priority Seq:
Effort (Hour):
External Ticket #:
None
History
#1 Updated by Muhammed Azhar Mohamed Maideen 5 months ago
select * from txn_mobile_collection_header where col_no like '%CCMN5000012%'-- THER IS NO COLLECTION IN THE PORTAL
select * from txn_mobile_collection_header where col_no like '%CCMN5000013%'-- there is in the DB
select * from txn_mobile_collection_header_at where col_no like '%CCMN5000012%'
#2 Updated by Muhammed Azhar Mohamed Maideen 5 months ago
- Project changed from Datanory to Datanory - SNEKKU
#3 Updated by Muhammed Azhar Mohamed Maideen 5 months ago
- Status changed from Assigned To to Support In Progress
#4 Updated by Muhammed Azhar Mohamed Maideen 5 months ago
- Status changed from Support In Progress to Pending Client Verification
- Resolution updated (diff)
#5 Updated by Muhammed Azhar Mohamed Maideen 5 months ago
- Status changed from Pending Client Verification to Ticket Resolved
- Type set to Support Request
- Actual Initial Response set to 23/02/2024
Rashdan Already tested and it is verified, The issue of Collection number not in sequence has been fixed. You may ask user to update the Datanory apps to our latest version, 3.2.19.4
case closed