KevinJ of Kansas
10/02/2019, 7:54 PMSirus Badiee
10/02/2019, 7:56 PMSirus Badiee
10/02/2019, 8:08 PMKevinJ of Kansas
10/02/2019, 8:09 PMKevinJ of Kansas
10/02/2019, 8:09 PMSirus Badiee
10/02/2019, 8:15 PMSirus Badiee
10/02/2019, 8:17 PMdbaghdanov
10/02/2019, 8:26 PMSirus Badiee
10/02/2019, 8:27 PMSirus Badiee
10/02/2019, 8:27 PMdbaghdanov
10/02/2019, 8:30 PMItem Fulfillment #IF-12345678
, but the other was IF-12345677
Sirus Badiee
10/02/2019, 8:30 PMSirus Badiee
10/02/2019, 8:30 PMdbaghdanov
10/02/2019, 8:31 PMBased on our engineers, the encountered behavior is as expected since the transaction number and document number are independent numbers. Upon creating a transaction, the transaction number is assigned based on the numbering setup and right after the transactionnumber generation, the same happens with the document number and independent document number sequence.
If there are two transactions created at the same time, there is a possibility that the second transaction gets earlier to the process of assigning the document number.
The suggested workaround is to incorporate some delay into the script to prevent the occurrence of having two transaction generated at the same time but we still cannot guarantee that the numbers will be the same.
dbaghdanov
10/02/2019, 8:31 PMSirus Badiee
10/02/2019, 8:32 PMSirus Badiee
10/02/2019, 8:32 PMdbaghdanov
10/02/2019, 8:33 PMCase: 3114376: Defect 503951 : Item Fulfillment the tranid shows one value, and the transactionnumber an incorrect value
Status Change:
Status changed from Open - Under Investigation to Closed - As Designed
Sirus Badiee
10/02/2019, 8:34 PMdbaghdanov
10/02/2019, 8:35 PMSirus Badiee
10/02/2019, 8:35 PMSirus Badiee
10/02/2019, 8:35 PMSirus Badiee
10/02/2019, 8:36 PMdbaghdanov
10/02/2019, 8:37 PMdbaghdanov
10/02/2019, 8:42 PMwhen creating an Item Fulfillment search, you should not be using the Document Number (like I’ve done before) and instead use the Transaction Number, which returns the tranid , which is the IF-123456789 number.
dbaghdanov
10/02/2019, 8:42 PMSirus Badiee
10/02/2019, 8:44 PMdbaghdanov
10/02/2019, 8:45 PMSirus Badiee
10/02/2019, 8:49 PMSirus Badiee
10/02/2019, 8:49 PMdbaghdanov
10/02/2019, 8:51 PMdbaghdanov
10/02/2019, 8:52 PMKevinJ of Kansas
10/02/2019, 9:02 PMKevinJ of Kansas
10/02/2019, 9:02 PMKevinJ of Kansas
10/02/2019, 9:02 PMKevinJ of Kansas
10/02/2019, 9:03 PMKevinJ of Kansas
10/02/2019, 9:03 PMKevinJ of Kansas
10/02/2019, 9:03 PMKevinJ of Kansas
10/02/2019, 9:03 PMSirus Badiee
10/02/2019, 9:04 PMKevinJ of Kansas
10/02/2019, 9:04 PMSirus Badiee
10/02/2019, 9:04 PMSirus Badiee
10/02/2019, 9:04 PM