Business Message Reject (MsgType = j, FIXML = BizMsgRej)

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 message should be issued.

See the session-level Reject message

Scenarios for Business Message Reject:

BusinessRejectReason

0 = Other

1 = Unknown ID

2 = Unknown Security

3 = Unsupported Message Type (receive a valid, but unsupported MsgType)

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 SYBMOL: XYZ).

The business message reject format is as follows:

Business Message Reject

Tag	Field Name	FIXML	Req'd	Comments
<Standard Message Header>			Y	MsgType = j
45	RefSeqNum	@RefSeqNum	N	MsgSeqNum of rejected message
372	RefMsgType	@RefMsgTyp	Y	The MsgType (35) of the FIX message being referenced.
379	BusinessRejectRefID	@BizRejRefID	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	@BizRejRsn	Y	Code to identify reason for a Business Message Reject (j) message.
58	Text	@Txt	N	Where possible, message to explain reason for rejection
354	EncodedTextLen	@EncTxtLen	C	Must be set if EncodedText (355) field is specified and must immediately precede it.
355	EncodedText	@EncTxt	C	Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field.
<Standard Message Trailer>			Y

All material contained within the website is copyright of EPAM Systems, Inc. No material contained herein can be copied or otherwise used without the express permission of the copyright holder.