Position of ApplVerID (1128) ?

, ,
1

Imported from previous forum

2

There is an ambiguous positional requirement for field 1128 (ApplVerID). The FIXT.1.1 specification shows in one table (p. 17) that 1128 is following MsgType and thus it looks like the 4th field whereas in FIXT Header Mapping Table (p. 33) it is stated that it must be the 6th field following 49 and 56. However, the 4th and 5th fields (SenderCompID and TargetCompID) have no positional requirements.
Does anybody know the correct position (if any) of 1128 (ApplVerID)?

3

You are right, the positional requirement for field 1128 (ApplVerID) is indeed ambiguous looking at the two different places in the document, thanks for bringing this error to our notice.

My recommendation to the GTC FIX 5.0 Usage Subcommittee would be to go with the order given in FIXT Header Mapping table Page 31 of 66, ie ApplVerID [1128] be the 6th field after SenderCompID [49] and TargetCompID [56]. The reason I prefer this appraoch is because SenderCompID [49] and TargetCompID [56] will be present in every message.

There is an ambiguous positional requirement for field 1128 (ApplVerID).
The FIXT.1.1 specification shows in one table (p. 17) that 1128 is
following MsgType and thus it looks like the 4th field whereas in FIXT
Header Mapping Table (p. 33) it is stated that it must be the 6th field
following 49 and 56. However, the 4th and 5th fields (SenderCompID and
TargetCompID) have no positional requirements. Does anybody know the
correct position (if any) of 1128 (ApplVerID)?

4

The FIXT Header Mapping Table is the correct one. An errata to the documentation and repository to correct the table for the Standard Header will be issued in the near future.

To summarize, with FIXT the following Standard Header fields must be ordered as:
BeingString (8) - 1st position
BodyLength (9) - 2nd position
MsyType (35) - 3rd position
SenderCompID (49) - 4th position
TargetCompID (56) - 5th position
ApplVerID (1128) - must be 6th position if used

There is an ambiguous positional requirement for field 1128 (ApplVerID).
The FIXT.1.1 specification shows in one table (p. 17) that 1128 is
following MsgType and thus it looks like the 4th field whereas in FIXT
Header Mapping Table (p. 33) it is stated that it must be the 6th field
following 49 and 56. However, the 4th and 5th fields (SenderCompID and
TargetCompID) have no positional requirements. Does anybody know the
correct position (if any) of 1128 (ApplVerID)?

5

Thanks Lisa. Will this be the errata for SP1?

The FIXT Header Mapping Table is the correct one. An errata to the
documentation and repository to correct the table for the Standard
Header will be issued in the near future.

To summarize, with FIXT the following Standard Header fields must be
ordered as: BeingString (8) - 1st position BodyLength (9) - 2nd
position MsyType (35) - 3rd position SenderCompID (49) - 4th position
TargetCompID (56) - 5th position ApplVerID (1128) - must be 6th
position if used

There is an ambiguous positional requirement for field 1128
(ApplVerID). The FIXT.1.1 specification shows in one table (p. 17)
that 1128 is following MsgType and thus it looks like the 4th field
whereas in FIXT Header Mapping Table (p. 33) it is stated that it must
be the 6th field following 49 and 56. However, the 4th and 5th fields
(SenderCompID and TargetCompID) have no positional requirements. Does
anybody know the correct position (if any) of 1128 (ApplVerID)?

6

This will be an errata to FIXT.1.1.

Thanks Lisa. Will this be the errata for SP1?

The FIXT Header Mapping Table is the correct one. An errata to the
documentation and repository to correct the table for the Standard
Header will be issued in the near future.

To summarize, with FIXT the following Standard Header fields must be
ordered as: BeingString (8) - 1st position BodyLength (9) - 2nd
position MsyType (35) - 3rd position SenderCompID (49) - 4th position
TargetCompID (56) - 5th position ApplVerID (1128) - must be 6th
position if used

There is an ambiguous positional requirement for field 1128
(ApplVerID). The FIXT.1.1 specification shows in one table (p. 17)
that 1128 is following MsgType and thus it looks like the 4th field
whereas in FIXT Header Mapping Table (p. 33) it is stated that it
must be the 6th field following 49 and 56. However, the 4th and 5th
fields (SenderCompID and TargetCompID) have no positional
requirements. Does anybody know the correct position (if any) of
1128 (ApplVerID)?