|
4.4 Changes
< Previous Next >
Re: Trade Capture Report <-> TCR Ack ExecType requirement inconsistency?
Hanno Klein / Deutsche Börse <>
21 Jul 2011 4:40AM ET First of all, thank you for making the effort and searching the forum for an answer to your question and finding a post from 2005 which (unfortunately) had not been answered. Maybe the reason was that FIX 5.0 was not published until December 2006.
The answer is that the inconsistency is a bug that has been corrected with FIX 5.0 (see its release notes). The TCR was added in FIX 4.3 without a TCRAck. The TCR in FIX 4.3 requires ExecType. This requirement was dropped with FIX 4.4. At the same time the TCRAck was added to FIX 4.4. I can only assume that the FIX 4.3 version of the TCR was taken as a basis and one forgot to align the new TCRAck with the modified TCR at the time.
Regards,
Hanno.
> Hi,
> The ExecType (tag=150) field in the TCR (MsgType=AE) is defined to be optional in FIXimate as well as Volume 5 for FIX 4.4, but it is defined as required in the TCR Ack (MsgType=AR).
>
> So when mapping a TCR Ack from the received TCR I need to "invent" the ExecType if it is not send with the TCR to create a valid TCR Ack.
>
> Has this inconsistency a business requirement or is this a bug in the TCR Ack msg-definition?
>
> Thanks.
>
> Note: There was a similar question ask before but unfortunately no answer was given to that post. See last line in:
> http://www.fixprotocol.org/discuss/read/cfc7b925
Re: Trade Capture Report <-> TCR Ack ExecType requirement inconsistency?
Hanno Klein / Deutsche Börse 21 Jul 2011 4:40AM ET
|
@FIXProtocol
