You can load planned orders, planned order update recommendations, and suggested repetitive schedules from any source - planning systems, order entry systems, finite scheduling packages, production line sequencing programs, spreadsheets, and even custom entry forms - into the Work Order Interface. For example, if your plant directly feeds to your customer's plant, you can take demands directly from your customer rather than waiting for the next MRP run thus reducing response time and eliminating unnecessary overhead.
You then use the Import Jobs and Schedules window to launch the WIP Mass Load program, which validates records in the Work Order Interface table and implements any imported records as new discrete jobs, updated discrete jobs, or pending repetitive schedules.
See: Work Order Interface, Oracle Integration Repository, irep.oracle.com
In Oracle Advanced Planning, the ECO Use-up Date is the date when the on-hand quantity is calculated to be 0. It is calculated from inventory supply and requirement demand. Work in Process detailed scheduling calculations are taken sequentially. Therefore, production order recommendations from planning can result in recommendations that either ignore active ECOs, or assume future ECOs are already active.
Oracle Advanced Planning provides a profile option to align Work in Process production with engineering change orders in planning. This enables you to control if resource and component schedules, calculated by Oracle Advanced Planning, are forwarded to Oracle Work in Process when ECO Revision Date differs from the order Start Date.
The profile option, MSC: Release WIP Details if Order Date Different than BOM Revision Date, has the following settings:
Yes: Work in Process details are release even if the job or schedule Start Date is different than the bill of material Revision Date.
The planning engine updates the ECO Revision Date to the Start Date of the earliest affected job or schedule. Oracle Work in Process ignores the job BOM Revision Date and explodes the bill of material and routing details. It uses the planning recommended new Start Date, instead of the existing order Start date. This eliminates revision conflicts among multiple engineering change orders.
No: Work in process details are not released if the job or schedule Start Date is different than the bill of material Revision Date. Work in Process explodes the details effective as of the Start Date.
Engineering Change Orders Use-Up Effectivity, Oracle Advanced Planning Implementation and User's Guide