[This message was posted by Hanno Klein of Deutsche Börse Systems <[email protected]> to the "5.0 Feedback" discussion forum at http://fixprotocol.org/discuss/47. You can reply to it on-line at http://fixprotocol.org/discuss/read/8e5169c2 - PLEASE DO NOT REPLY BY MAIL.]
I believe the flow ends with an ER Ack (message BN). You want to continue the flow by saying that you cannot process the ER Ack. As the ER Ack has no response message, you can only resort to a BusinessMessageReject. The ER Ack message is one of the messages which can be referenced via the Business Message Reject message (see FIX 5.0 SP1 Volume 1 page 106) in field RefMsgType. BusinessRejectRefID would contain the unknown ClOrdID value and BusinessRejectReason would be 1 = Unknown ID. You can use Text for further detail. Regards, Hanno. > Guys, > > Would someone happen to know how to reject a BN message. Lets say a > client acks an exec using 35=BN but the clordid provided in the message > is incorrect. Should the reject happen on the application level > 35=8|39=8|150=8 or should it be a business reject 35=j ? > > Please advise. > > Thanks, Arthur [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
