Work in Process Actions:There are four types of actions: Message, Alert, User-defined, and Application Specific. These are described below:
Message actions either display a message or post it to the Quality Action Log. They reject input and force the user to enter an acceptable value before the user can continue. You can use Message actions to prompt an operator to take immediate action, such as putting nonconforming parts into a separate holding area or shutting down faulty equipment. Message actions provide immediate feedback and help resolve problems at the source.
Message actions require action details. For example, when you define the Display a message to the operator action, you must enter the message that is to be displayed. Message actions options are as follows:
| Display a message to the operator | Displays the message entered to the operator. |
| Reject the input | Displays the message entered message and rejects the input. Before you can continue with quality data collection, you must enter an acceptable quality results value. |
| Post an entry to the Quality Action Log | Posts the message entered to the Quality Action Log. For example, you can post an entry each time a critical part is found to be defective so that the source of the problem can be determined and eliminated. This creates a quality results audit trail. See: Viewing and Deleting Action Log Entries. |
Quality Alert Actions can launch various processes, as well as send electronic mail notifications to users. They are similar, yet distinctly different from the event alerts that you can define using Oracle Alerts. They share the same underlying database tables and require some of the same setups, however, Quality alerts do not have the full functionality of Oracle Alerts. Quality alert actions include:
Execute an operating system script
Execute a SQL script
Launch a concurrent request
Send an electronic mail notification
User-defined actions are actions that you can set up to meet your specific business needs. The actions can initiate SQL scripts, formulas, programs, or workflow processes that you design. These are Quality's two user-defined actions:
The Assign a Value action enables you to assign a value to a collection plan element based upon your own formula or SQL script. You can only define the Assign a Value action for collection plan elements. For detailed information on this action, see: Defining Actions that Assign a Value: User-Defined Formulas.
The Launch a Workflow action enables you to activate a previously defined workflow process when specified quality results are collected. For example, you could activate a workflow that sends a notification to the maintenance manager and shop floor supervisor when a machine's temperature is recorded as exceeding a specified tolerance.
To use this action, you must first create the workflow in Oracle Workflow (see the Oracle Workflow User's Guide). You also must create a collection plan and collection elements, and select the collection element that will be used as the action trigger. You then define an action rule and associate it with the Launch a Workflow action.
See: Defining Launch a Workflow Actions.
Actions are either specific to an Oracle Applications product and act upon database objects associated with that product, or they are non-product specific. There also are dependencies between some application specific actions and context elements. See: Dependencies Between Context Elements and Actions.
The table below summarizes Oracle Application specific actions, and is followed by their descriptions:
| Oracle Application | Action |
|---|---|
| Work in Process Actions | Assign a shop floor status to the intraoperation step |
| - | Place the job on hold |
| - | Hold all schedules building this assembly on this production line |
| Purchasing Actions | Accept the shipment |
| - | Reject the shipment |
| - | Place the supplier on hold |
| - | Place a document or release on hold |
| - | Assign an ASL status |
| Warehouse Management Actions | Assign a lot status |
| - | Assign a serial status |
| Enterprise Asset Management Actions | Create a work request |
| - | Create a maintenance work order |
Work in Process Actions:These actions are associated with Oracle Work in Process:
| Assign a shop floor status to the intraoperation step | Assigns the shop floor status that you specify in the Action Details region of the Quality Actions window to any intraoperation step of the operation you are moving assemblies into. Shop floor statuses can be used to prevent movement out of a particular job or line/assembly intraoperation step or over an operation step. You can only assign shop floor statuses that are active in Work in Process. See: Shop Floor Statuses. Shop floor statuses assigned by Quality Actions can be changed in Work in Process. See: Assigning and Viewing Shop Floor Statuses. |
| Place the job on hold | Changes the status of the job to On Hold. See: Discrete Job Statuses. The statuses of jobs placed On Hold by Quality Actions can be changed in Work in Process. See: Changing Discrete Job. |
| Hold all schedules building this assembly on this production line | Changes the status of all repetitive schedules on a production line to On Hold. See: Repetitive Schedule Statuses. The statuses of schedules placed On Hold by Quality Actions can be changed in Work in Process. See: Changing Repetitive Schedules . |
Purchasing Actions:Actions associated with Oracle Purchasing or Oracle Supplier Scheduling are as follows:
| Accept the shipment | Accepts an inspected shipment from a supplier. You can correct erroneously accepted shipment information in Oracle Purchasing. See: Entering ReturnsandEntering Corrections. |
| Reject the shipment | Rejects a shipment from a supplier. Shipments that are rejected by Quality can be reinspected. |
Attention: The Accept and Reject the Shipment transaction work in conjunction. You cannot define one without the other.
| Place the supplier on hold | Places the supplier on hold. You can approve new purchase orders for suppliers on hold. You cannot approve payments for suppliers on hold. Suppliers placed on hold by quality actions can be released in Oracle Payables. See: Releasing Holds. |
| Place a document or release on hold | Places the purchase order or release on hold. You cannot print, receive against, invoice, or approve for the future purchase orders or releases that are on hold. |
Attention: This action does not support internal requisition audits. It only supports purchase orders or releases.
| Documents placed on hold by Quality Actions can be released in Oracle Purchasing. See: Controlling Documents. | |
| Assign an ASL Status | Updates the approved supplier's status to the status that you specify. See: Approved Supplier Status. Supplier statuses assigned by quality actions can be changed in Supplier Scheduling. See: Defining the Supplier and Item/Commodity Combination. |
Caution: If you use the Assign an ASL Status action on a plan that has the Supplier but not the Item collection element on it, the ASL status is applied to all supplier and item/commodity combinations for that supplier.
Warehouse Management Actions:Actions associated with Oracle Warehouse Management are as follows:
| Assign a lot status | Assigns a lot status to an inventory lot. See: Overview of Material Status. |
| Assign a serial status | Assigns a status to an inventory serial number. See: Overview of Material Status. |
Enterprise Asset Management Actions:Actions associated with Oracle Enterprise Asset Management are as follows:
| Create a work request | Creates an eAM work request. See: Triggering a Work Request page . Optionally, you can use the collection element Work Request Priority to assign a work priority to the work request. Define the values for Work Request Priority in eAM. See: Work Order and Work Request Priority Codes page . |
| Create a maintenance work order | Creates a released eAM work order See: To manually create a work order. |
