[This message was posted by Hanno Klein of Deutsche Börse Systems <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/4c638e6c - PLEASE DO NOT REPLY BY MAIL.]
An unsolicited new order is quite unusual, a rejection of something that the user never submitted as a new order is not ok. A new order starts a new chain of ClOrdID values. The order receiver should stay within the same chain when he modifies the order. He can issue a new OrderID to indicate a new entity from his point of view but has to follow the submitter's chain of events, i.e. to use "Replaced" or "Restated" and not "New". > > Their explanation is that my order was modified by their system. It created > new order for the amount left after partial fills and that new order was > rejected. > > > What is the meaning of the second New in your sequence of events? How can > > the order transition from Partial Fill to New? > > > > Thank you, > > Hanno. > > > > > Hi, > > > > > > Is execution report with OrdStatus Rejected valid after order request was > > > accepted and partially filled? > > > > > > My test order [FIX 4.4, forex, 35=D, 40=1, 59=3] was executed in > > > following sequence execution reports: > > > > > > New -> Partial fill -> Partial fill -> New (2nd time) -> Rejected > > > > > > Last 2 execution report had cumulative quantity and average price fields > > > set to correct values. LeavesQty was set to 0 in the last one. > > > > > > Regards, > > > Adam Szojda [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.
