# FIX Standard Errors and Omissions 2022

**URL:** <https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385>\
**Category:** General Q&A\
**Tags:** errors, fixlatest\
**Created:** [February 18, 2022, 11:12am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385 "2022-02-18T11:12:19Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [February 18, 2022, 11:12am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/1 "2022-02-18T11:12:20Z")

</div>

This thread is intended to capture errors and omissions discovered in the FIX Standard during 2022, e.g. misspellings or gaffes in the description. These will eventually be reviewed by the Global Technical Committee and be corrected with a standard Gap Analysis and a FIX Extension Pack.

---

<div class="post-metadata">

**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:** [February 23, 2022, 2:41pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/2 "2022-02-23T14:41:19Z")

</div>

Related post [FIX Orchestra/Repository Errors and Omissions](http://forum.fixtrading.org/t/fix-orchestra-repository-errors-and-omissions/16359/3) that has been closed to consolidate all issues raised during 2022 into this thread.

---

<div class="post-metadata">

**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:** [April 2, 2022, 9:17am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/3 "2022-04-02T09:17:29Z")

</div>

TriggerTradingSessionID(1113) and TriggerTradingSessionSubID(1114) of the [TriggeringInstruction](https://fiximate.fixtrading.org/en/FIX.Latest/cmp1030.html) component do not use the same code sets as [TradingSessionID(336)](https://fiximate.fixtrading.org/en/FIX.Latest/tag336.html) and [TradingSessionSubID(625)](https://fiximate.fixtrading.org/en/FIX.Latest/tag625.html) respectively. They do not use any code set and are also missing the union datatype Reserved100Plus to permit user-defined values.

---

<div class="post-metadata">

**Author:** ![jorgthonnes](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/jorgthonnes/32/196_2.png) [@jorgthonnes](https://forum.fixtrading.org/u/jorgthonnes)\
**Post date:** [April 14, 2022, 3:26pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/4 "2022-04-14T15:26:37Z")

</div>

Typo in description of `538/NestedPartyRole` (`PartyRoleCodeSet`):

> 81 = Broker cient ID

Should be

> 81 = Broker Clearing ID

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [April 15, 2022, 1:46pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/5 "2022-04-15T13:46:16Z")

</div>

Thank you, @jorgthonnes. This issue has already been covered by EP271 in Chapter 2.6.28. The issue is in [PartyRoleCodeSet](https://fiximate.fixtrading.org/en/FIX.Latest/cds452.html) that is also used by NestedPartyRole(538). EP271 has been implemented and is currently in its QA phase.

---

<div class="post-metadata">

**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:** [April 15, 2022, 3:32pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/6 "2022-04-15T15:32:03Z")

</div>

Error in sort order of [TradeConditionCodeSet](https://fiximate.fixtrading.org/en/FIX.Latest/cds277.html) in FIXimate. Value 0=Cancel shows up between values AK and AL but should instead show up between values BE and 1=Implied Trade.

---

<div class="post-metadata">

**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:** [April 15, 2022, 4:42pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/7 "2022-04-15T16:42:40Z")

</div>

Orchestra.XML currently has 11 occurrences of “`..`” at the end of a sentence that should only be “`.`”

---

<div class="post-metadata">

**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:** [April 16, 2022, 12:52pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/8 "2022-04-16T12:52:37Z")

</div>

Typo “relevent” instead of “relevant” in group usage comment of

1. UnderlyingProvisionOptionRelevantUnderlyingDateBusinessCenterGrp in [UnderlyingProvisionOptionRelevantUnderlyingDate](https://fiximate4.technical-fixprotocol.org/en/FIX.Latest/cmp4305.html)
2. ProvisionOptionRelevantUnderlyingDateBusinessCenterGrp in [ProvisionOptionRelevantUnderlyingDate](https://fiximate4.technical-fixprotocol.org/en/FIX.Latest/cmp4016.html)

---

<div class="post-metadata">

**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:** [April 29, 2022, 10:10am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/9 "2022-04-29T10:10:39Z")

</div>

Typo in tag reference of [UnderlyingCurrency(318)](https://fiximate.fixtrading.org/en/FIX.Latest/tag318.html): Currency(5) should be Currency(15)

---

<div class="post-metadata">

**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:** [May 13, 2022, 7:19am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/10 "2022-05-13T07:19:21Z")

</div>

[DerivativeSettleOnOpenFlag(1254)](https://fiximate4.technical-fixprotocol.org/en/FIX.Latest/tag1254.html) has the wrong abbreviation. It uses `OpenCloseSettlFlag` instead of `SettlOnOpenFlag` like the related field [SettleOnOpenFlag(966)](https://fiximate4.technical-fixprotocol.org/en/FIX.Latest/tag996.html) does.

The **abbreviation** `OpenCloseSettlFlag` can easily be confused with `OpenClsSettlFlag` used by the **field** [OpenCloseSettlFlag(286)](https://fiximate4.technical-fixprotocol.org/en/FIX.Latest/tag286.html).

---

<div class="post-metadata">

**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:** [May 13, 2022, 7:28am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/11 "2022-05-13T07:28:10Z")

</div>

Field name of [DerivativeOptPayAmount(1225)](https://fiximate4.technical-fixprotocol.org/en/FIX.Latest/tag1225.html) should be DerivativeOptPay **out** Amount to align with the other XXXOptPayoutAmount fields.

> OptPayoutAmount(1195)  
> LegOptPayoutAmount(2194)  
> UnderlyingOptPayoutAmount(2029)  
> ComplexOptPayoutAmount(1485)  
> LegComplexOptPayoutAmount(2223)  
> UnderlyingComplexOptPayoutAmount(2047)

---

<div class="post-metadata">

**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:** [May 30, 2022, 3:39pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/12 "2022-05-30T15:39:56Z")

</div>

Implementation of EP85 (Mass Action Filters) created errors and inconsistencies in terms of naming (no change to enum values):

- [MassCancelRequestType(530)](https://fiximate.fixtrading.org/en/FIX.Latest/tag530.html) does not use lowercase for all values and values B/C should be “Cancel orders for…”
- [MassCancelResponseType(531)](https://fiximate.fixtrading.org/en/FIX.Latest/tag530.html) does not use lowercase for all values
- [MassStatusRequestType(585)](https://fiximate.fixtrading.org/en/FIX.Latest/tag585.html) does not use lowercase for all values and values 9/10 should be “Status for orders for a …”
- [MassActionScope(1374)](https://fiximate.fixtrading.org/en/FIX.Latest/tag1374.html) does not use lowercase for all values and values 11/12 should be “All orders for…”
- [MassActionRejectReason(1376)](https://fiximate.fixtrading.org/en/FIX.Latest/tag1376.html) does not use lowercase for all values
- [QuoteCancelType(298)](https://fiximate.fixtrading.org/en/FIX.Latest/tag298.html) does not use lowercase for all values and values 1-3,7-8 should be “Cancel quotes for…”

---

<div class="post-metadata">

**Author:** ![davidgibbs](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@davidgibbs](https://forum.fixtrading.org/u/davidgibbs)\
**Post date:** [June 8, 2022, 8:40am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/13 "2022-06-08T08:40:32Z")

</div>

In the standard FIX Orchestration version 1.5.1 there is no MarketDepthCodeSet.  
Here is the definition of the MarketDepth field.

```
	<fixr:field added="FIX.4.2" id="264" name="MarketDepth" type="int" abbrName="MktDepth">
		<fixr:annotation>
			<fixr:documentation purpose="SYNOPSIS">
     Depth of market for Book Snapshot / Incremental updates
     0 - full book depth
     1 - top of book
     2 and above - book depth (number of levels)
  </fixr:documentation>
		</fixr:annotation>
	</fixr:field>
```

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [June 8, 2022, 9:50am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/14 "2022-06-08T09:50:12Z")

</div>

> [@davidgibbs](#):
>
> In the standard FIX Orchestration version 1.5.1 there is no MarketDepthCodeSet.

@davidgibbs, there is a reason for this. Only the values 0 and 1 have a special meaning (actually only value 0 as 1 means just one level is shown and this depth has a special name “top of book”). The datatype of this field is “int” and the value represents the number of price levels provided, 0 simply meaning that all price levels are shown. A code set would require to list all supported values. Admittedly, the description looks like a list of values but that is not intended.

Where does the “version 1.5.1” come from that you are referencing above?

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [June 13, 2022, 6:16pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/15 "2022-06-13T18:16:11Z")

</div>

SettlPriceDeterminationMethod(2451) is missing its standard values. The field was added with [EP190](https://www.fixtrading.org/packages/ep190/) and was supposed to have the following values:

> 0 = Unknown (Symbolic name: [Unknown])  
> 1 = Last trade price (Symbolic name: [LastTradePrice])  
> 2 = Last bid price (Symbolic name: [LastBidPrice])  
> 3 = Last offer price (Symbolic name: [LastOfferPrice])  
> 4 = Mid price [Elaboration] The price at the mid-point between last bid and last offer price (Symbolic name: [MidPrice])  
> 5 = Average of last trade prices [Elaboration] The average price across a bi-laterally agreed number of trades, e.g. last five trades. (Symbolic name: [AverageLastTradePrice])  
> 6 = Average of last trade period [Elaboration] Average price across bi-laterally agreed time period, e.g. last minute of trading (Symbolic name: [AverageLastTradePeriod])  
> 7 = Underlying price [Elaboration] Based on price of underlying instrument (Symbolic name: [UnderlyingPrice])  
> 8 = Calculated price [Elaboration]Other calculation method, e.g. theoretical price (Symbolic name: [CalculatedPrice])  
> 9 = Manual price [Elaboration]Manually entered price (Symbolic name: [ManualPrice])

---

<div class="post-metadata">

**Author:** ![davidgibbs](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@davidgibbs](https://forum.fixtrading.org/u/davidgibbs)\
**Post date:** [June 15, 2022, 12:10pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/16 "2022-06-15T12:10:01Z")

</div>

Yes thanks, I see that now. So I would put 5 if the depth was 5.  
The “version 1.5.1” is the versioned release in nexus for the orchestra repo artefact.

io.fixprotocol.orchestrations  
fix-standard

---

<div class="post-metadata">

**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:** [June 19, 2022, 3:48pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/17 "2022-06-19T15:48:55Z")

</div>

[AvgPxIndicator](https://fiximate.fixtrading.org/en/FIX.Latest/tag819.html) and [SideAvgPxIndicator](https://fiximate.fixtrading.org/en/FIX.Latest/tag1853.html) have their own code sets and do not share a single one. [AvgPxIndicator](https://fiximate.fixtrading.org/en/FIX.Latest/tag819.html) has two additional values (3=NVAP, 4=Trade is average priced) that the side-level field does not have. I believe there is no reason for this separation and that both fields should use the same code set.

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [July 15, 2022, 4:47pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/18 "2022-07-15T16:47:11Z")

</div>

FIXimate for legacy version FIX 4.2 shows the FIX 4.4 name for the acknowledgement message of an allocation (AllocationInstructionAck) instead of the FIX 4.2 name (AllocationAck): [https://fiximate.fixtrading.org/legacy/en/FIX.4.2/body\_505280.html](https://fiximate.fixtrading.org/legacy/en/FIX.4.2/body_505280.html)

---

<div class="post-metadata">

**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 27, 2022, 2:37pm UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/19 "2022-07-27T14:37:30Z")

</div>

Typo in elaboration of value 0=Manual of [ExecMethod(2405)](https://fiximate.fixtrading.org/en/FIX.Latest/tag2405.html).

> _Also used to identify MTT code M “Off Book Non-Automated”._

Acronym should be “MMT” (Market Model Topology)

---

<div class="post-metadata">

**Author:** ![gtcpm](https://avatars.discourse-cdn.com/v4/letter/g/b2d939/32.png) [@gtcpm](https://forum.fixtrading.org/u/gtcpm)\
**Post date:** [August 25, 2022, 10:18am UTC](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385/20 "2022-08-25T10:18:03Z")

</div>

**Omission** : information related to the replacements for deprecated fields [TargetStrategyParameters(848)](https://fiximate.fixtrading.org/en/FIX.Latest/tag848.html) and [ParticipationRate(849)](https://fiximate.fixtrading.org/en/FIX.Latest/tag849.html) (add elaboration to fields in data dictionary). See forum post [Replacement fields for the deprecated ones](http://forum.fixtrading.org/t/replacement-fields-for-the-deprecated-ones/16737) for details.

[Next page](https://forum.fixtrading.org/t/fix-standard-errors-and-omissions-2022/16385.md?page=2)
