# Trade Capture Report \<-\> TCR Ack ExecType requirement inconsistency? **URL:** \ **Category:** General Q&A\ **Tags:** imported, 44-changes, xid\_165365\ **Created:** [July 21, 2011, 8:02am UTC](https://forum.fixtrading.org/t/trade-capture-report-tcr-ack-exectype-requirement-inconsistency/12821 "2011-07-21T08:02:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![michaelhufer\_x](https://avatars.discourse-cdn.com/v4/letter/m/a88e4f/32.png) [@michaelhufer\_x](https://forum.fixtrading.org/u/michaelhufer_x)\ **Post date:** [July 21, 2011, 8:02am UTC](https://forum.fixtrading.org/t/trade-capture-report-tcr-ack-exectype-requirement-inconsistency/12821/1 "2011-07-21T08:02:01Z")
Imported from previous forum ---
**Author:** ![michaelhufer\_x](https://avatars.discourse-cdn.com/v4/letter/m/a88e4f/32.png) [@michaelhufer\_x](https://forum.fixtrading.org/u/michaelhufer_x)\ **Post date:** [July 21, 2011, 8:02am UTC](https://forum.fixtrading.org/t/trade-capture-report-tcr-ack-exectype-requirement-inconsistency/12821/2 "2011-07-21T08:02:01Z")
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](http://www.fixprotocol.org/discuss/read/cfc7b925) ---
**Author:** ![hanno.klein](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/hanno.klein/32/38_2.png) [@hanno.klein](https://forum.fixtrading.org/u/hanno.klein)\ **Post date:** [July 21, 2011, 9:40am UTC](https://forum.fixtrading.org/t/trade-capture-report-tcr-ack-exectype-requirement-inconsistency/12821/3 "2011-07-21T09:40:02Z")
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](http://www.fixprotocol.org/discuss/read/cfc7b925) ---
**Author:** ![michaelhufer\_x](https://avatars.discourse-cdn.com/v4/letter/m/a88e4f/32.png) [@michaelhufer\_x](https://forum.fixtrading.org/u/michaelhufer_x)\ **Post date:** [July 21, 2011, 10:03am UTC](https://forum.fixtrading.org/t/trade-capture-report-tcr-ack-exectype-requirement-inconsistency/12821/4 "2011-07-21T10:03:28Z")
Ok, thank you. Since we are not using FIX 5.0, yet I didn’t look there to see if it has been changed there. I will change the ExecType field also as optional in the FIX.4.4 TCR Ack of our local FIX msg dictionary then. > 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](http://www.fixprotocol.org/discuss/read/cfc7b925)