Why 39=5 is dropped?

, ,
1

Imported from previous forum

2

Hi FIX experts,

Can someone tell me why the replaced ER OrdStatus=Replaced (39=5) is no longer used to confirm an order modification?

Any response will be appreciated. Thanks.

3

OrdStatus and ExecType are the key fields to tell you two things: a)what is the current state of the order? and b) what kind of transaction was applied to the order? Both fields were used almost identical in FIX 4.2 or lower and there was a third field ExecTransType with a transactional focus. The concept was changed with FIX 4.3 to have a clearer semantic distinction. ExecTransType was dropped all together. ExecType values “Partially Filled” and “Filled” were changed to a single value “Trade”. OrdStatus “Replaced” was dropped because the fact that there was a transaction to replace the order is already expressed with the ExecType value “Replaced”. The information that an order was modified during its lifetime is of lesser value. It is more important to know whether it has already been partially filled or not without having to check the quantity fields.
The concept has remained unchanged since FIX 4.3 released in Aug 2001. FPL has started to optimize the concept for high performance trading with FIX 5.0 SP2 (check Volume 7, Order State Change Matrices for Exchanges, starting on page 191). Further optimization is currently being discussed within the FIX High Performance Working Group. The basic idea is to minimize the number of ExecutionReports needed to convey a single business transaction such as an IOC order being partially filled. This requires a single OrdStatus/ExecType set of values that gives you the current order state as well as the last transaction that was applied.
Regards,
Hanno.

Hi FIX experts,

Can someone tell me why the replaced ER OrdStatus=Replaced (39=5) is no longer used to confirm an order modification?

Any response will be appreciated. Thanks.