Production Ticket(ST) #11698
Hi pls check, invoice and collection number missing INWWX001117-240510 CCWWX001142-240510
1) checked in the datanpry DB
2) checked in the autocount( *CCWWX001142240510
CCWWX001158-240511
CCWWX001159-240511) di dnot flow
3)deleted the duplicated collection done by azhar
4) insert collection that has been stucked in the di_table
Root cause=- support team operational issue
None
Description
Hi pls check, invoice and collection number missing INWWX001117-240510 CCWWX001142-240510
CCWWX001110-240510
CCWWX001111-240510
This 2 collection number on 07/05/24 already use it, how come 10/05/24 collection got show again
Collection number missing
CCWWX001158-240511
CCWWX001159-240511
History
#1 Updated by Muhammad Arif 4 months ago
- Status changed from Assigned To to Support In Progress
#2 Updated by Muhammad Arif 4 months ago
- Assignee changed from Muhammad Arif to Muhammed Azhar Mohamed Maideen
1. Hi pls check, invoice and collection number missing INWWX001117-240510 CCWWX001142-240510
findings:
Collection number missing: CCWWX001142-240510
Root cause: due to duplicate upload (second upload by support team) - mistake by Azhar (CCWWX001110-240510,CCWWX001111-240510)
Solution: need to delete the testing data first (uploaded to goldcrest already), after delete can proceed to insert back the missing collection
2. CCWWX001110-240510
CCWWX001111-240510
This 2 collection number on 07/05/24 already use it, how come 10/05/24 collection got show again
incorrect data: test data uploaded by support team
correct collection number (uploaded by user): CCWWX001110-240507, CCWWX001111-240507
Solution: Need to delete this data at datanory and goldcrest. But how to explain to user?
3. Collection number missing
CCWWX001158-240511 :due to item 2, caused collection in items 3 can be inserted (calculation for invoice will be incorrect)
CCWWX001159-240511 :due to item 2, caused collection in items 3 can be inserted (calculation for invoice will be incorrect)
@~Azhar13 please get advice from Jann regarding about this mistake
how to handle customer and how to request user to delete
my side cant proceed to insert data if the duplication data still there
next time if accidentally uploaded data to production, please inform Afiq or me or Chong Yu. we can help to delete data before the data integrated
#3 Updated by Muhammed Azhar Mohamed Maideen 4 months ago
select * into DMS_EcoSystem_backup_table.dbo.txn_mobile_collection_header_14052024
from DMS_EcoSystem.dbo.txn_mobile_collection_header
select * into DMS_EcoSystem_backup_table.dbo.txn_mobile_collection_detail_14052024
from DMS_EcoSystem.dbo.txn_mobile_collection_detail
select * into DMS_EcoSystem_backup_table.dbo.txn_mobile_collection_invoice_14052024
from DMS_EcoSystem.dbo.txn_mobile_collection_invoice
select * from txn_mobile_collection_header where col_no like '%CCWWX001110-240510'
--delete from txn_mobile_collection_header where col_id ='ef633f8e-fca2-4474-953b-afcaa9e5b8e7'
select * from txn_mobile_collection_detail where col_id = 'ef633f8e-fca2-4474-953b-afcaa9e5b8e7'
--delete from txn_mobile_collection_detail where col_id ='ef633f8e-fca2-4474-953b-afcaa9e5b8e7'
select * from txn_mobile_collection_invoice where col_id= 'ef633f8e-fca2-4474-953b-afcaa9e5b8e7'
--delete from txn_mobile_collection_invoice where col_id ='ef633f8e-fca2-4474-953b-afcaa9e5b8e7'
---------------------------------------------------------------------------------------------------------
select * from txn_mobile_collection_header where col_no like 'CCWWX001111-240510'
delete from txn_mobile_collection_header where col_id ='fc4fc14b-5dd1-4e70-a461-031d0de7511a'
select * from txn_mobile_collection_detail where col_id like 'fc4fc14b-5dd1-4e70-a461-031d0de7511a'
--delete from txn_mobile_collection_detail where col_id ='fc4fc14b-5dd1-4e70-a461-031d0de7511a'
select * from txn_mobile_collection_invoice where col_id= 'fc4fc14b-5dd1-4e70-a461-031d0de7511a'
--delete from txn_mobile_collection_invoice where col_id ='fc4fc14b-5dd1-4e70-a461-031d0de7511a'
already perform deletion
#4 Updated by Muhammed Azhar Mohamed Maideen 4 months ago
- Status changed from Support In Progress to Pending Client Verification
- Resolution updated (diff)
#5 Updated by Muhammed Azhar Mohamed Maideen 4 months ago
- Status changed from Pending Client Verification to Ticket Resolved
- Type set to Support Request
- Actual Initial Response changed from 13/05/2024 to 14/05/2024