|
Allocations
< Previous Next >
Re: Allocation Ack against Alloc Report
Sheetal Chainraj <>
28 Nov 2005 4:14PM ET> > I believe there is some confusion on when the Allocation Report
> > message should be used instead of Ack. I understand the ack can only
> > specify the status of the allocation , not its results. My plan was to
> > use Ack as answer to Allocation Instruction, then Alloc Report to
> > specify the results of the allocation instruction. Now , it seems
> > Alloction Report can give the exact same information as Allocation Ack
> > (see tag 87) What is the guideline ? Shall we just get rid off
> > Allocation Ack ?
> >
> > Patrick
>
> The FIX protocol dictates that the "Response to the Allocation message
> is the AllocationACK". So your initial thinking is correct.
>
> Typically the AllocationAck is message is used for two purposes: 1 to
> acknowledge receipt of an allocation instruction (87=3) and 2: to report
> whether the allocation has been accepted or rejected 87=[0,1,2,4,5].
>
> Once an allocation is accepted, the AllocationReport message is used to
> report on the match-status of the allocations which is specified by
> MatchStatus field (573) of the AllocsGroup.
>
> Hope this answers your question
>
> herby
Fix Protocol does suggest that we use the Allocation Instruction Ack message in response to the Allocation Instruction message for 1)Received but not processed 2) Accept, Reject ..
But if you look at the Fix 4.4 Allocations Implementation guide put together by the Allocation Wokring Group ( http://www.fixprotocol.org/working_groups/allocwg/documents ),
you will see that they suggest using one Allocation Instruction Ack to Indicate "received not yet processed" and then the Allocation Report to notify the results.
I would like to know what are the advanatges people see over using an Allocation Report instead of the Allocation Instruction as the second message.
Re: Allocation Ack against Alloc Report
Sheetal Chainraj 28 Nov 2005 4:14PM ET
|
