While researching a problem, I found that there are missing records (a gap in TranNum’s) in our PartTran table
Below is a snapshot of the query of the PartTran table. Notice how the TranNum’s jump from 208704 to 208707.
And the original issue I was researching was that Packer 25566 had two STK-CUS lines, but we can’t find any transactions for the one line.
I didn’t think any process ever deleted PartTran records.
Hi,
Didn’t get some transactions done with a date in the future did you?
This has happened to me before
Regards,
John
I though about that. But my query above only limits the TranNum >= 208700. So it should have shown anyway. (Unlike the Part Transaction History Tracker - which uses a cutoff date).
Also Tran 208707 was actuall line 2 of the Packer. So the missing trans (208705 and 06) would have been from the same packer and created at the same time.
It is sad but true, you may find their are unused and duplicated transaction numbers. I know this through analysis of my company’s PartTran table entries. I believe these transaction numbering errors are related to either App Server hangs or crashes. Carl