Imported from previous forum
Is there a generally accepted industry definition of “uniqueness” of Allocation ID (AllocID[tag 70]) in Allocation Instruction messages?
Definition from FIXimate: “Unique identifier for this allocation instruction message”
Should this be unique for the day?
Should it be unique forever?
What is the practice right now in the industry?
If it is unique forever - then it seems like the date or datetime should
be part of the AllocID? Thoughts?
Is there a generally accepted industry definition of “uniqueness” of
Allocation ID (AllocID[tag 70]) in Allocation Instruction messages?Definition from FIXimate: “Unique identifier for this allocation
instruction message”Should this be unique for the day?
Should it be unique forever?
What is the practice right now in the industry?
If it is unique forever - then it seems like the date or datetime should
be part of the AllocID? Thoughts?
We set this to our internal allocation id which is unique (forever). Note that it should definitely be > 1 day as sometimes there is a need for next morning cancel/re-book and the cancel needs to be able to reference the original’s AllocID.