Details
-
Type: Bug
-
Status: Closed
-
Priority: Default
-
Resolution: Not a bug
-
Affects Version/s: 1.5.2
-
Fix Version/s: None
-
Component/s: Message Generation
-
Environment:Linux, CentOS, Java 1.6.0b22 64-bit JVM
Description
I was comparing what is in the default FIX44.xml data dictionary with what is defined for Tag 139 MiscFeeType. It's defined as follows in the FIX44.xml:
<!-- Changed to string in FIX5.0, overrides this field type -->
<field number="139" name="MiscFeeType" type="CHAR">
<value enum="1" description="REGULATORY"/>
<value enum="2" description="TAX"/>
<value enum="3" description="LOCAL_COMMISSION"/>
<value enum="4" description="EXCHANGE_FEES"/>
<value enum="5" description="STAMP"/>
<value enum="6" description="LEVY"/>
<value enum="7" description="OTHER"/>
<value enum="8" description="MARKUP"/>
<value enum="9" description="CONSUMPTION_TAX"/>
</field>
However, in the FIXimate, I see that an additional 3 values are defined:
10 = Per transaction [PerTransaction]
11 = Conversion [Conversion]
12 = Agent [Agent]
I was using a version of FIX44.xml that I modified in order to communicate with NSCC's new UTC system. They are adhering to the 4.4 spec, but I would need to pick up 10 (Per Transaction) field from their TradeCaptureReport message.
Any reason why these 3 fields are not included in the data dictionary?
Also, data dictionary is defined as char. Since the addition of the 3 fields, is this the reason why it is now defined as String in FIX 5.0?
Attachments
Issue Links
- is duplicated by
-
QFJ-755 FIX44.xml field number 139 'MiscFeeType' should be of type 'STRING'
- Closed