A Migration Job set up to insert rows directly into `INVENTORY_PART_UNIT_COST` fails on every row with `ORA-01003: no statement parsed` and no further error detail, even though the field mapping looks correct.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This points to migrating into a container that isn't meant to be populated by direct migration at all — Inventory Part unit cost values are meant to be determined by the application's own cost roll-up calculation process, not set directly via a migration job into the unit-cost container; if you hit this specific error migrating into unit-cost data, treat it as a signal to run the proper cost roll-up calculation through the application instead of continuing to debug the migration job's configuration.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions