TT® FIX Order Routing

Business Message Reject (j) Message

Business Message Reject (j) Message

Business Message Reject (j) Message

Purpose

Used to reject an application-level request that cannot be rejected by other means

Message Direction

From TT FIX to FIX client

Tag Directory

Click the links below to navigate to the documentation for that tag.

Supported Tags

Tag # Field Name Req’d Data type Comments
Component: <Standard Header>
Y 35=j (MsgType)
For additional information about this component group, consult the full documentation.
Tag # Field name Req’d Data type Comments
8 BeginString Y String

FIX protocol version

The tag indicates the beginning of a new message. This tag is always the first tag in the message.

The value is either FIX.4.2 or FIX.4.4.
9 BodyLength Y int

Message length (in characters)

The value represents number of characters in the message following this tag up to, and including, the delimiter immediately preceding Tag 10 (CheckSum). This tag must be the second field in a message.
35 MsgType Y String

Type of message contained in the message body

This tag must appear third in the list of header tags.

Possible values include:

  • 0: Heartbeat
  • 1: Test Request
  • 2: Resend Request
  • 3: Reject
  • 4: Sequence Reset
  • 5: Logout
  • 8: Execution Report
  • 9: Order Cancel Reject
  • A: Logon
  • B: News
  • c: Security Definition Request
  • D: Order Single
  • d: Security Definition
  • e: Security Status Request
  • f: Security Status
  • F: Order Cancel Request
  • G: Order Cancel Replace Request
  • H: Order Status Request
  • Q: Don't Know Trade (Inbound Drop Copy only)
  • R: Quote Request
  • V: Market Data Request
  • W: Market Data Snapshot Full Refresh
  • X: Market Data Incremental Refresh
  • Y: Market Data Request Reject
  • AD: Trade Capture Report Request
  • AE: Trade Capture Report
  • AQ: Trade Capture Report Request Ack
49 SenderCompID Y String

ID of the FIX session

The value will be the same value the FIX client sends in tag 56 (TargetCompID) in its requests to TT FIX.
56 TargetCompID Y String

FIX client ID, corresponding to the SenderCompID specified for the user in TT User Setup

The value is the same as sent in tag 49 (SenderCompID) in FIX client requests.
50 SenderSubID C String

Unique ID for the message sender

For CME, the value corresponds to the Operator ID.

Condition: Sent if TT User Setup specifies an exchange operator ID
142 SenderLocationID N string Specific message originator's location (i.e. geographic location and/or desk, trader)
116 OnBehalfOfSubID N Data type: String

Unique Trader ID (can also be provided in Tag 50 (SenderSubID))

The value maps to the Alias field configured for a user in Setup.
129 DeliverToSubID C String

Value of Tag 116 (OnBehalfOfSubID) in the FIX client request.

Condition: Sent in Execution Report (8) and Order Cancel Reject (9) messages.
34 MsgSeqNum Y SeqNum

Message sequence number.
43 PossDupFlag C Boolean

Whether the sequence number for this message is already used

Possible values include:

  • Y: Possible duplicate
  • N: Original transmission

Condition: Sent when TT FIX resends messages
97 PossResend C Boolean

Whether the message might contain information that has been sent under another sequence numbe

Possible values include:

  • Y: Possible resend
  • N: Original transmission

Condition: Sent when TT FIX restarts after encountering a corrupt FIX message cache, and only until it completes the initial download.
122 OrigSendingTime C UTCTimestamp

Original time of message transmission, when transmitting orders as the result of a resend request

Always expressed in UTC.

Condition: Sent when TT FIX resends a message
52

SendingTime

Y UTCTimestamp

Time, in UTC, the message was sent.
45 RefSeqNum Y int

Value of Tag 34 (MsgSeqNum) in the rejected message
372 RefMsgType Y string

Value of Tag 35 (MsgType) in the rejected message
379 BusinessRejectRefID C string

Value of the business-level ID field in the referenced message

Maximum length: 63 characters

Condition: Sent when the rejected message contains an ID
380 BusinessRejectReason Y int

Reason for the rejecting the message

Possible values include:

  • 0: Other
  • 1: Unknown ID
  • 2: Unknown security
  • 3: Unsupported Message Type
  • 4: Application not available
  • 5: Conditionally Required Field Missing
58 Text N string

Text description of the reason for the rejection
Component: <Standard Trailer>
Y For additional information about this component group, consult the full documentation.
Tag # Field Name Req’d Data type Comments
10 Checksum Y String

Unencrypted three-character checksum

This tag must always be the last field in a message (i.e. it serves, with the trailing <SOH>, as the end-of-message delimiter).

Message Notes

The Business Message Reject (j) message is used by the TT FIX whenever it rejects an application-level message that fulfills session-level rules but cannot be rejected via any other means (i.e. Order Cancel Reject (9) message).

For example, suppose a FIX client sends an Order Cancel/Replace Request (G) message where Tag 11 (ClOrdID) matches an existing client order ID. When TT FIX receives the message, it verifies the validity of the message. However, business rules require that a client order ID remains unique for the trading session. Therefore, TT FIX responds with a Business Message Reject (j) message.

Related Information

Any application request message