Business Message Reject <j> message – FIX 4.2 – FIX Dictionary

FIX 4.2 : Business Message Reject <j> message

Description

The Business Message Reject <j> message can reject an application-level message which fulfills session-level rules and cannot be rejected via any other means. Note if the message fails a session-level rule (e.g. body length is incorrect), a session-level Reject <3> message should be issued.

See the session-level Reject <3> message

It should *NOT* be used in the following situations:

Situation	Appropriate Response
Session-level problem meeting the criteria of the session-level Reject <3> message	Use the session-level Reject <3> message (MsgType <35>=3)
In response to New Order - Single <D> Order Status Request <H> New Order - List <E> List Execute <L>	Use the Execution Report <8> message
In response to: Order Cancel Request <F> Order Cancel/Replace Request <G> List Cancel Request <K>	Use the Order Cancel Reject <9> message
In response to: Execution Report <8>	Use the Don't Know Trade <Q> (DK) message
In response to: Allocation <J>	Use the Allocation ACK <P> message
In response to: List Status Request <M>	Use the List Status <N> message
In response to: Quote Request <R> Quote <S> Mass Quote <i> Quote Cancel <Z> Quote Status Request <a>	Use the Quote Acknowledgement<b> message
In response to: Market Data Request <V>	Use the Market Data Request Reject <Y> message
In response to: Security Definition Request <c>	Use the Security Definition <d> message
In response to: Security Status Request <e>	Use the Security Status <f> message
In response to: Trading Session Status Request <g>	Use the Trading Session Status <h> message

Note the only exception to this rule is in the event a business message is received, fulfills session-level rules, however, the message cannot be communicated to the business-level processing system. In this situation a Business Message Reject <j> with BusinessRejectReason <380> = "Application not available at this time" can be issued if the the system is unable to send the specific "reject" message listed above due to this condition.

Messages which can be referenced via the Business Message Reject <j> message are (the "ID" field BusinessRejectRefID <379> refers to noted in [ ]):

Indication of Interest <6> (IOI) [IOIid <23>]
Advertisement <7> [AdvId <2>]
News [Headline <148>]
Email <C> [EmailThreadID <164>]
Order Cancel Reject <9> [ClOrdID <11>]
Allocation ACK [AllocID <70>]
List Status <N> [ListID <66>]
Don't Know Trade <Q> (DK) - may respond with Order Cancel Reject <9> if attempting to cancel order [ExecID <17>]
Settlement Instructions <T> [SettlInstID <162>]
Market Data-Snapshot/Full Refresh <W> [MDReqID <262>]
Market Data-Incremental Refresh <X> [MDReqID <262>]
Market Data Request Reject <Y> [MDReqID <262>]
Quote Acknowledgement [QuoteID <117>]
Security Definition <d> [SecurityResponseID <322>]
Security Status <f> [SecurityStatusReqID <324>]
Trading Session Status <h> [TradSesReqID <335>]

Scenarios for Business Message Reject <j>:

BusinessRejectReason <380>:

0 = Other
1 = Unknown ID
2 = Unknown Security
3 = Unsupported Message Type (receive a valid, but unsupported MsgType <35>)
4 = Application not available
5 = Conditionally Required Field Missing

Whenever possible, it is strongly recommended that the cause of the failure be described in the Text <58> field (e.g. "UNKNOWN SYMBOL: XYZ").

Structure

Tag	Field Name	Req'd	Comments
<MessageHeader>		Y	MsgType <35> = j
45	RefSeqNum	N	MsgSeqNum <34> of rejected message
372	RefMsgType	Y	The MsgType <35> of the FIX message being referenced.
379	BusinessRejectRefID	N	The value of the business-level 'ID' field on the message being referenced. Required unless the corresponding ID field (see list above) was not specified.
380	BusinessRejectReason	Y	Code to identify reason for a Business Message Reject <j> message.
58	Text	N	Where possible, message to explain reason for rejection
354	EncodedTextLen	N	Must be set if EncodedText <355> field is specified and must immediately precede it.
355	EncodedText	N	Encoded (non-ASCII characters) representation of the Text <58> field in the encoded format specified via the MessageEncoding <347> field.
<MessageTrailer>		Y