When does chained orders move to created / reserved status.

Answer

For Procurement Orders:

The chained orders procurement PO's or TO's are created and the status of
the chained order is always reserved.
The reason for the chained order to go to reserved status is to make
that the inventory is reserved to fulfill the SO.

It is the behavior of the application that the procurement orders when
created are always in 'Reserved' Status.
We do not have any configurations currently to modify the status.
However, if you wish to change the status then you can extend 'Reserved'
status and make a changeOrderStatus API call to drop the 'Reserved'
order into a different status.

Out of the box when we create a procurement order, the input for the
createOrder for PO/TO has the attribute ReserveInventoryFlag is passed
as "Y".
Hence when we schedule the sales order , the PO goes to reserved status
as we pass this flag as Y.

OOB while creating a procurement order the reason for passing this
attribute as Y is that reason is to make that the inventory to be
reserved to fulfill the SO.

Drop Ship Orders:

While creating a drop ship order, we provide input for the
createChainedOrder API and we don't pass ReserveInventoryFlag attribute hence the order
goes to created status.
In this case we are manually creating a purchase order for the sales
order .