You can create discrete jobs in the following ways:
- manually (both standard and non–standard discrete jobs).
- manually from a simulation (standard discrete jobs only).
- automatically using Oracle Master Scheduling/MRP and Oracle Supply Chain Planning to plan your standard discrete production, then using the Planner Workbench to implement your planned orders. automatically using Advanced Planning and Scheduling’s High Level Scheduling Engine to schedule jobs and import them into Work in Process.
- automatically (standard discrete jobs only) from final assembly orders for specific customer configurations and/or standard assemble–to–order (ATO)/configure–to–order items.
- using the Work Order Interface to import planned orders and updated planned order recommendations.
Planned Discrete Jobs
You can create planned orders and reschedule recommendations using the Planner Workbench in Oracle Master Scheduling/MRP and Oracle Supply Chain Planning. You can modify the due dates and quantities of planned orders, and also firm plan these orders. You can create new discrete jobs by implementing all or some planned orders.
When you create jobs using the Planner Workbench, you can specify the WIP accounting class. Accounting classes can be defaulted. If the job being created is for a lot controlled assembly, the WIP Default Lot Number Type parameter is used to determine whether lot numbers are assigned based on the job name or based on the Oracle Inventory lot number rules.
Discrete jobs created from planned orders use the planned order quantity as the default job quantity. The primary bill of materials and primary routings for the assemblies are used to create work in process bills and routings. Jobs created from planned orders are backward scheduled from the required completion date. The calculated start date is used to determine the bill and routing revisions and revision dates.
Planning takes shrinkage rate, component yield, and safety stock into consideration in the planning process. Once you define the standard job, supply is calculated using the following formula:
available supply quantity = (MRP net quantity – quantity
completed – quantity scrapped) x 1 – item shrinkage rate)
You can also use the Planner Workbench to reschedule existing jobs.
For example, you can reschedule every assembly in the plan or you can reschedule only certain specific assemblies.
When you implement planned orders and create discrete jobs, Planning does not take into account the WIP:View Only Released ECOs profile option in the Personal Profile Values window. Oracle Advanced Planning provides a profile option enabling you to align Work in Process production with engineering changes for planning .
In a pull–based system, inventory items for a particular part or assembly area are replenished as soon as they are needed. When the items are needed, kanban cards in Oracle Inventory change their Supply Status to Empty, and Inventory generates production kanban replenishment request automatically.
- If the source type of the kanban card is Production, as opposed to Supplier or Inter–Org, the type of Work in Process Entity that is created is determined based on the assembly referenced by the kanban card per the following rules:
- If the lowest priority or primary routing of the assembly is a Flow routing, a Flow schedule is created. This is true even if the items Repetitive Planning attribute is set
- If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is set, then a repetitive schedule is created.
- If the lowest priority or primary routing of the item is not a Flow routing, and the Repetitive Planning attribute is NOT set, then a discrete job is created Signals to create discrete jobs and repetitive schedules are processed by the WIP Mass Load program.
When discrete jobs and repetitive schedules are created in response to kanban replenishment signals, they are automatically loaded into the Work Order Interface and automatically processed. If the replenishment signal creates a discrete job, the kanban card is referenced on that job; however, if the replenishment signal creates a repetitive schedule, the kanban card is not referenced. Once the discrete job or repetitive schedule has been successfully loaded, the status of the kanban card is updated to In process.
When kanban replenishment jobs and schedules fail validation and processing, they are automatically deleted from the interface table. The reason for their failure is noted on the Job and Schedule Interface report, which is automatically printed each time the Mass Load program is run. When imported, non–kanban job and schedule information that fails validation or processing is marked. You can use the Pending Jobs and Schedules window to view, update, and resubmit this information.
Final Assembly Orders
You can automatically create final assembly orders for Assemble to Order (ATO) items entered in Oracle Order Management. These discrete job orders are created on a single job to single sales order delivery basis.
On the Sales Order window (which you open from the Discrete Jobs window in Work in Process), you also can associate discrete jobs for both standard items and ATO items with sales orders and thereby allocate production to specific customers. To determine the job start date, you schedule jobs created from final assembly orders backwards from the order due date. The calculated start date is used to determine the bill and routing revisions and revision dates.
Work Order Interface
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.
WIP Accounting Class Defaults
You can set up default WIP accounting classes at several levels:
- at the category account level for discrete jobs and repetitive line/assembly associations
- at the Default Discrete Class parameter class level for standard discrete jobs
- at the project cost group level for project jobs