Documentation for Financial Information eXchange (FIX)
Definition Type: SimpleType
Name: CrossType_enum_t
Namespace: http://www.fixprotocol.org/FIXML-4-4
Containing Schema: fixml-fields-base-4-4.xsd
Documentation:
Type of cross being submitted to a market Valid values: = Cross Trade which is executed completely or not Both sides are treated in the same manner This is equivalent to an All or None 2 = Cross Trade which is executed partially and the rest is cancelled One side is fully executed the other side is partially executed with the remainder being cancelled This is equivalent to an Immediate or Cancel on the other side Note: The CrossPrioritzation 550 field may be used to indicate which side should fully execute in this scenario 3 = Cross trade which is partially executed with the unfilled portions remaining active One side of the cross is fully executed as denoted with the CrossPrioritization field but the unfilled portion remains active 4 = Cross trade is executed with existing orders with the same price In the case other orders exist with the same price the quantity of the Cross is executed against the existing orders and quotes the remainder of the cross is executed against the other side of the cross The two sides potentially have different quantities
Collapse XSD Schema Diagram:
XSD Diagram of CrossType_enum_t in schema fixml-fields-base-4-4_xsd (Financial Information eXchange (FIX))
Collapse XSD Schema Code: 
<xs:simpleType name="CrossType_enum_t">
    <xs:annotation>
        <xs:documentation xml:lang="en">Type of cross being submitted to a market Valid values:  = Cross Trade which is executed completely or not  Both sides are treated in the same manner  This is equivalent to an All or None   2 = Cross Trade which is executed partially and the rest is cancelled  One side is fully executed  the other side is partially executed with the remainder being cancelled  This is equivalent to an Immediate or Cancel on the other side  Note: The CrossPrioritzation  550  field may be used to indicate which side should fully execute in this scenario   3 = Cross trade which is partially executed with the unfilled portions remaining active  One side of the cross is fully executed  as denoted with the CrossPrioritization field   but the unfilled portion remains active   4 = Cross trade is executed with existing orders with the same price  In the case other orders exist with the same price  the quantity of the Cross is executed against the existing orders and quotes  the remainder of the cross is executed against the other side of the cross  The two sides potentially have different quantities  
		</xs:documentation>
        <xs:appinfo xmlns:x="http://www.fixprotocol.org/fixml/metadata.xsd">
            <xs:Xref Protocol="FIX" name="CrossType" tag="549" datatype="int" ComponentType="Field" StdAbbrev="CrssTyp" QualifiedAbbrev="CrssTyp" Category="CrossOrders" CategoryAbbrev="Typ" />
            <xs:Xref Protocol="ISO_15022_XML" />
        </xs:appinfo>
        <xs:appinfo xmlns:x="http://www.fixprotocol.org/fixml/metadata.xsd">
            <x:EnumDoc value="1" desc="CrossAON" />
            <x:EnumDoc value="2" desc="CrossIOC" />
            <x:EnumDoc value="3" desc="CrossOneSide" />
            <x:EnumDoc value="4" desc="CrossSamePrice" />
        </xs:appinfo>
    </xs:annotation>
    <xs:restriction base="xs:string">
        <xs:enumeration value="1" />
        <xs:enumeration value="2" />
        <xs:enumeration value="3" />
        <xs:enumeration value="4" />
    </xs:restriction>
</xs:simpleType>
Collapse Facets:
Facet Value
Enumeration 1
Enumeration 2
Enumeration 3
Enumeration 4
Collapse Derivation Tree:
Collapse References:
nsA:CrossType_t
Documentation for Financial Information eXchange (FIX)

Generated using Liquid Studio - Developer Bundle 21.0.0.0