To add or update an operation:You can add operations to discrete jobs with statuses of Unreleased, Released, Complete, or On Hold - and add operations to repetitive schedules with statuses of Unreleased. You can also add operations to jobs and repetitive schedules with or without routings.
You can create a routing for a job or schedule that does not have a routing by adding operations to it. When you add the first operation, the system automatically defaults an operation sequence of 1 for the new operation and assigns job or schedule material requirements to this operation. If the job or schedule is already released, the system also loads the job or schedule quantity into the Queue intraoperation step of the new operation.
Note: If you add an operation to a job or repetitive schedule, reschedule to correctly reflect the start and completion dates.
Operations of discrete jobs can be updated if the status is Unreleased, Released, Complete, or On Hold. You can update the operations of repetitive schedules with statuses of Released, Complete, or On Hold if no other active schedules for the assembly are on the line.
Note: Operation dates for repetitive schedules of any status cannot be changed.
You can attach illustrative or explanatory files - in the form of text, images, word processing documents, spreadsheets, video - to operations. See: About Attachments.
To add or update an operation:Navigate to the Operations window.
Select the Job or Line and Assembly.
If you select a line and assembly, choose the repetitive schedule by selecting the first unit start date of that schedule. If you have selected a discrete job, the system displays the scheduled start date of the job.
Optionally, choose Find n to populate the Operations region.
From the Main tabbed region of the Operations region, select the Operation Sequence number.
Optionally, select the Operation Code of a standard operation.
If you add a standard operation by selecting its Operation Code - the Department, Count Point, Autocharge, Backflush, Minimum Transfer Quantity, Check Skill, and Description are defaulted. Resource requirements associated with the standard operation are also defaulted.
You can update the operation codes of unreleased discrete jobs.
If the Operation Code is blank, you must manually define the operation.
Select the Department.
Departments are used for charging resources at an operation and are required.
If you add a standard operation, the system displays the Department of that operation as the default. If there are resources assigned to the standard operation, resources are not updateable.
Enable the Count Point check box to make the operation a count point operation. See: Count Point and Autocharge Fields.
Operations you must always perform (critical, time-sensitive), should be made count point operations. Operations not always performed should be made non-count point operations.
When you perform move transactions, the system defaults to the next count point operation as the To operation sequence. For example - three operations at sequences 10, 20, and 30 are defined as count point, non-count point, and count point respectively. When you select operation 10 as the From operation, the system automatically defaults operation 30, the next count point operation, as the To operation. You can override this default and choose operation 20, if required.
Non-standard operations added are automatically created as count point operatios. If you add a standard operation, the system displays the count point option of that operation as the default.
Enable the Autocharge check box for charging move transactions. See: Count Point and Autocharge Fields.
The Autocharge flag controls both resource and backflush charging when moving assemblies. It determines whether both resource and material are charged when you skip an operation:
The count point, autocharge, and backflush flags work together. Operations can be:
Count point and autocharge
Non-count point and non-autocharge
Non-count point and autocharge.
Note: They cannot be count point and non-autocharge.
If you add a standard operation, the system displays the autocharge option as the default. If you add an operation that is not a standard operation, the system specifies it as a count point operation.
Operations used to charge resources and material should always be specified as autocharge. See: WIP Move.
It is recommended that rework or optional operations are defined as non-autocharge. If the operation is optional and you do not move quantity into it - resource and material are not charged.
For example, three operations at sequences 10, 20, and 30 are defined respectively as autocharge, non-autocharge, and autocharge operations. When you move assemblies from the Queue intraoperation step of operation 10 to an intraoperation step that completes assemblies at operation 30 (To Move, Scrap, or Reject), resources and material at operations 10 and 30 are charged, but those at operation 20 are not. To charge resources and material to operation 20, you must move assemblies into a completion intraoperation step (To Move, Scrap, or Reject) of that operation. See: Intraoperation Steps.
Enable the Backflush check box for backflush operations.
Operation pull components assigned to backflush operations are automatically backflushed (pulled) from inventory when assemblies are moved and completed at that operation. Operation pull components assigned to non-backflush operations prior to the backflush operation are then backflushed.
If you add an operation that is not a standard operation, the system automatically makes the operation a non-backflush operation.
Note: The last operation in a routing must always be a backflush operation. Otherwise, materials are not backflushed from inventory if the last operation is a non-backflush operation and prior operations are non-backflush with operation pull components.
Enter the Minimum Transfer Quantity.
If adding a standard operation, the value defaults from Bills of Material. If you add an operation that is not a standard operation, the system displays 0 as the default. See: Creating a Standard Operation.
If you attempt to move fewer than the minimum transfer quantity, a warning message displays.
Enable the Check Skill check box if you are validating operator skills for an operation.
The labor skills validation feature is applicable only for operation moves transacted in Manufacturing Execution System for Discrete Manufacturing, and not operation moves transacted in Work in Process windows. If adding a standard operation, the value defaults from Bills of Material. This field enables the Operation Competencies button for navigating to the Operations Competencies window to enter required skill level values. See:
In the Quantities tabbed region, you can enter a value in the Progress % field.
These entries are used to calculate the percent complete for the entire job, based on a weighted average of scheduled hours. Oracle Project Manufacturing uses this value for project tasks, which can then be rolled up to the project level for earned value.
In the Dates tabbed region, you can manually schedule and reschedule a discrete job operation by changing dates. The job must have a status of Unreleased, Released, Complete, or On Hold.
You can change the First Unit Start Date (FUSD), the First Unit Completion Date (FUCD), Last Unit Start Date (LUSD), and the Last Unit Completion Date (LUCD) to any date. Changing the dates of an operation does not affect the dates of the operations that precede or follow.
Note: If you change the LUCD of the last operation to a date that is greater than the job completion date, the job completion date is updated to the LUCD. If you change the FUSD of the first operation to a date earlier than the job start date, the job start date is updated to the FUSD.
In the Description tabbed region, enter the operationdescription.
If you add a standard operation, the system displays the description of that operation as the default.
Save your work.
Select the following to navigate to other windows:
Operation Competencies to enter competencies and skill levels required if using the labor skills validation feature in Manufacturing Execution System for Discrete Manufacturing move transactions. See: Creating a Standard Operation, and Creating a Routing
Reschedule to midpoint reschedule a discrete job, see: Midpoint Rescheduling
Resource to update operation resource requirements, see: Adding and Updating Resource Requirements
