You won’t be able to change the status of an object using any migration tools or field updates.  You have to use the appropriate API for the status change to perform the transformation.  There can be dozens of checks and additional actions fire in the background on a transition from one state to another.  Use the Debug Tool on an order change from Planned to Release and look at all of the actions that occur as a result.  You have to mimic all of that detail in a coded transaction to move the object status.   Status isn’t just a piece of data, in indicates completion of a series of actions.

@ShawnBerk ,

How is it possible with scrip migration?

Why can't it be possible with FND migration?

If you have a test environment trying changing the status from Planned to Released using the system but switch on debugging first.

You would usually the MODIFY part of the api but by using debugging you would locate the correct one.

Regards

John

Hi Adarsh,

When updating a status or performing most operations in IFS require data validation which is achieved via business logic. So data migration will not allow you to bypass that logic. However, you can achieve your objective via probably a database trigger on insert event to Customer Order table. You can get the relevant database call from the debug console upon performing a Release and write a trigger to perform this operation.