BusinessRejectReason

Tag 380

BusinessRejectReason

Abbreviation:
Typeint
Tag380
AddedFIX.4.2
Used in1 messages

Description

Code to identify reason for a Business Message Reject message.

Wire Format & Usage Example

Single field (key=value)
380=3 (UnsupportedMessageType)
In a FIX message (BusinessMessageReject)
8=FIX.4.4 | 9=... | 35=j | 49=SENDER | 56=TARGET | 34=1 | 52=20240101-09:30:00.000 |  | 380=3 (UnsupportedMessageType) |  | 10=...

Fields are delimited by SOH (ASCII 0x01), shown here as " | ". The highlighted field 380=3 (UnsupportedMessageType) is this field's position in the message.

All valid values
WireNameDescription
380=3UnsupportedMessageTypeUnsupported Message Type
380=7DeliverToFirmNotAvailableAtThisTimeDeliverTo firm not available at this time
380=4ApplicationNotAvailableApplication not available
380=6NotAuthorizedNot authorized
380=0OtherOther
380=5ConditionallyRequiredFieldMissingConditionally Required Field Missing
380=1UnknownIDUnkown ID
380=2UnknownSecurityUnknown Security

Enumerated Values

8
ValueSymbolic NameDescriptionAdded
3UnsupportedMessageTypeUnsupported Message TypeFIX.4.2
7DeliverToFirmNotAvailableAtThisTimeDeliverTo firm not available at this timeFIX.4.3
4ApplicationNotAvailableApplication not availableFIX.4.2
6NotAuthorizedNot authorizedFIX.4.3
0OtherOtherFIX.4.2
5ConditionallyRequiredFieldMissingConditionally Required Field MissingFIX.4.2
1UnknownIDUnkown IDFIX.4.2
2UnknownSecurityUnknown SecurityFIX.4.2

Used in Messages

1