Using XMLAPI to update order - avoid using OrderHistID

There are still cases that XMLAPI is used to update orders for various business reasons, basically there are two methods of doing so, using OrderHistID and View, here are the samples
<UpdateOrder.Request xmlns="urn:com:metasolv:oms:xmlapi:1">
<OrderID>1</OrderID>
<OrderHistID>4</OrderHistID>
<Update path="/account_information/first_name">aaaaaabc</Update>
</UpdateOrder.Request>


<UpdateOrder.Request xmlns="urn:com:metasolv:oms:xmlapi:1">
<OrderID>1</OrderID>
<View>GroupView</View>
<Update path="/account_information/first_name">aaaaaabc</Update>
</UpdateOrder.Request>

You should use <View> parameter to update order instead of using OrderHistID, the reason is that OrderHistID could be changed and the request may be failed due to ORA-20012: Order  not found.    error