To create a standard operation:Standard operations are commonly used operations you can define as a template for use in defining future routing operations. If you assign the operation code of standard operation in a routing, the standard operation information is copied into the operation you are currently defining. You can then modify the operation information in your new operation.
You can also create setup standard operations that are used only when setting up machine type resources. When defining resource setup information (see: Defining Resource Setup Information), you have the option of specifying the standard operations used during changeovers.
You must define at least one department before you can define a standard operation. See: Defining a Department.
To create a standard operation:Navigate to the Standard Operations window.
Enter a unique operation code to identify a standard operation.
Note: If Oracle Warehouse Management is installed, the Standard Operations form is used to define which resources of a given department are required in order to perform a warehouse task. Oracle Warehouse Management refers to standard operations as Task Types. The rules engine uses the Code defined for the Standard Operation to reference the Task Type. A bulk picking task may require a forklift machine and a pallet picker manual resource. Oracle Warehouse Management uses a rules based system to determine the task type, or standard operation, each task should be associated with. Tasks of a given type are then dispatched to users associated with the resource definition, who have the qualified equipment for the task available to them. See: Set Up Warehouse Task Types, Oracle Warehouse Management Implementation Guide.
Enter the department where the operation is performed.
Enter the minimum transfer quantity of assemblies to move from this operation to the next.
For operations in ATO model or option class routings only, indicate whether the operation is option dependant, that is, whether the operation is dependant on the choice of an optional component. All mandatory components and their related operations appear on the routing for each configuration. The default is enabled. See: Overview of Configure to Order.
Select your Count Point and Autocharge options. See: Count Point and Autocharge.
Indicate whether to backflush components on shop floor moves at this operation.
A backflush transaction automatically pulls Operation pull components from inventory. Work in Process also pulls all Operation pull components at non-backflush operations preceding this operation (through the previous completed backflush operation.)
Select the Check Skill option to enable check skill.
If the Check Skill option is selected, then you have to capture the requirement for skill check.
Suggestion: The value in this check box is only a default value in routing and can be overridden in the Routing window.
If you are creating operations for a Shop Floor Management enabled organization, see: To create a standard operation for a Shop Floor Management enabled organization. If not, choose the Operation Resources button to assign resources to the standard operation. See: To assign a resource to a standard operation.
To create a standard operation for a Shop Floor Management enabled organization
To enable operation yield in Shop Floor Management, enter the Yield for each operation listed. The valid values range between zero and one. This field is displayed for Shop Floor Management enabled organizations.
Indicate whether this operation yield needs to be considered in the cost rollup, as required by the costing team. This field is displayed for Shop Floor Management enabled organizations.
Select the Shop Floor Transaction tab and select the following fields, if appropriate. See: Oracle Shop Floor Management User's Guide for information about each field. This tab is enabled for Shop Floor Management enabled organizations.
Lowest Acceptable Yield
Use Organization Settings
Queue Mandatory Flag
Run Mandatory Flag
To Move Mandatory Flag
Show Next Operation by Default
Show Lot Attributes
Show Scrap Codes
Optionally, select the Stocking Point tab and enter the default subinventory and locator for the standard operation.
Optionally, choose Codes and Exclusions to enter Bonus Codes, Scrap Codes, and Responsibility Exclusions for a Shop Floor Management enabled organization.
To define operation competencies for standard operations
Use the Operation Competencies window to enter the competencies required for carrying out the operation. You can add the competency for a resource only once and you cannot enter duplicate records in the operation competency set.
For standard operations and routing, the Check Skill option will remain unchecked when imported. For discrete jobs created through the interface, the job operations will have competencies and check Skill values inherited from the routing. While adding standard operations through the interface the values for Check Skill and competencies will be inherited from standard operation.
Competence and Skill Level are related fields. The Skill Level field is enabled if you enter value in the Competence field and tab out and the Skill Level will have the values relevant to that Competence.
The competencies defined in the resource definition are added to the operation by selecting the assigned resources in the list of values and clicking the Add button.
Navigate to the Operation Competencies window by choosing Operation Competencies from the Standard Operations window.
Create a standard operation.
Select the Check Skill check box.
Click on the Operation Competencies button.
Operation Competencies button will be enabled only when you select Check Skill check box.
The Operation Competencies window opens. Based on the Competence selected, the skill level values for the selected competence appear in the drop down menu of the Skill Level field.
Enter the skill level.
Enter the qualification required for the competence.
Save your work and close the Operation Competencies window.
See Also
Moving and Completing Assemblies
To enter codes and exclusions
Use the Codes and Exclusions window to define the bonus and scrap codes available for this operation at manufacturing execution time. See: Bonus and Scrap Codes, Oracle Shop Floor Management User's Guide. This window also enables you to exclude certain job roles from updating this operation at manufacturing execution time. Responsibility exclusions identify job roles that cannot perform this operation. For example, you can exclude users assigned to the Accounting responsibility from updating a grinding machine operation.
If you gain something or lose something at this operation, you assign either a bonus or scrap code to it. At manufacturing execution time, use the bonus or scrap code available for this operation. Use the responsibility to indicate who cannot perform this operation. For example, a foreman shouldn't be able to use the grinding machine.
Navigate to the Codes and Exclusions window by choosing Codes and Exclusions from the Standard Operations window.
Select the Bonus Codes tab and enter the sequences and codes for this operation.
Select the Scrap Codes tab and enter the sequences and codes for this operation.
Select the Responsibility Exclusions tab and enter the responsibilities to exclude from updating this operation.
Save your work and close the Codes and Exclusions window.
To assign a resource to a standard operation
In the Standard Operations window, choose the Operation Resources button to assign resources to the standard operation. See: To assign a resource to a routing operation.
Caution: To assign resources to the standard operation, follow the same steps as you would to assign a resource to a routing operation with one exception. When assigning resources to a standard operation, the Schedule Sequence Number field in the Resources window, Scheduling tab does not exist. If you use the Schedule Sequence Number functionality, you must manually update this field when adding a new operation to a routing using the Standard Operations window.
To create a setup standard operation:Use a setup standard operation only when specifying the standard operation used during a changeover in the Changeover Times window. You cannot use a setup standard operation as a routing operation. See: Defining Resource Setup Information.
Create a setup standard operation the same way you create a standard operation (see: To create a standard operation), omitting the steps used to create standard operations for a Shop Floor Management enabled organization.
Other Sources
Defining Activities and Activity Costs, Oracle Cost Management User's Guide.
Setup Steps (Defining Parameters), Oracle Shop Floor Management User's Guide
