|
4.2 Changes
< Previous Next >
Re: ExecType in Bust Execution
Greg Wood / Credit Suisse
7 May 2009 4:48PM ET Hi Elton,
Tag 150 should reflect the status of the order once the bust has been taken into account. So if the bust is the only trade of a fully filled order then the message would be 150=0/20=1. A bust on the last fill of an order filled in several clips should go back as 150=1/20=1.
Tag 39 could be different. A busted fill on a partially filled and cancelled order should generate 39=4/150=1/20=1 as per line 7 of example D35 in Appendix D.
The comment below made in an earlier post is interesting, especially since I heard something similar recently -
"One of our FIX partners told me that ExecType would be *always* 150=4 when the Execution Report is busting an execution -- but I'm not sure about that."
- I personally do not understand the logic of this. 150=4 (Cancelled) refers to the order not the fill, and does not follow the logic behind tag 20 in 4.2 to denote the transction type being reported (new, cancel, correct or status). 4.3 and later deprecate tag 20 and put the values into tag 150, but a cancelled order and a trade cancel are still distinct values (150=4 and 150=H respectively).
A question for a wider audience - is there a common deviation from the spec with regards to reporting busts as 150=4 ?
Regards,
- Greg
> Hello,
>
> Thanks, but my question is: when an ExecutionReport is busting an
> execution (20=1), what value should I use in tag 150? Does it have the
> same value of tag 39?
Re: ExecType in Bust Execution
Greg Wood / Credit Suisse 7 May 2009 4:48PM ET
|
@FIXProtocol
