This topic introduces you to the concept of a workflow process and refers you to the documentation that fully explains Oracle workflows. It presents an understanding of the OPM Quality Management workflows, how to set them up, how to start them, and how to use the Quality windows.
This appendix covers the following topics:
The Quality Management application in Oracle Process Manufacturing (OPM) supports quality inspection on the raw materials, intermediates, or finished goods at any stage during inventory transaction, receiving, production, or sales cycle, from within the corresponding applications.
Using the Quality Management application, you can set up specifications, draw samples, enter test results, and perform stability studies. The following business events are supported:
Oracle Inventory
Process Execution
Quality Management
Sample Creation
Sample Disposition and Sample Group Disposition
Testing Request
Compositing Results
Specification Status Change Approval
Specification Validity Rule Status Change Approval
Customer, Inventory, Supplier, WIP, and Monitoring Validity Rule Status Change Approval
Stability Study
Status Change
Lot Sampling
Batch Creation
Testing
Time Point Testing
Lot Retesting
Item UOM Conversion
OPM Quality Management workflows use two major components:
The design uses the Oracle Workflow Business Event System to define an event and associate it with a subscription to the business event. The subscription initiates a workflow to perform any needed database changes, notifications, or other requirements. Events and subscriptions can be enabled or disabled by the customer as needed using the business event system. A customer can add a new subscription to an event to perform customized functionality or features.
Oracle Workflow lets you automate and continuously improve business processes by routing information according to a set of business rules. You can transmit this information to individuals both inside and outside your enterprise on an individual basis.
Refer to the Oracle Workflow Guide and the Oracle E-Records Implementation Guide for additional information on:
Workflow Business Event System
The Sample Creation Notification workflow sends a notification to draw a material sample as required by the associated sampling plan for the item specification and specification validity rule in effect. This workflow can be triggered by an inventory quantity increase, receiving transaction, batch step release, or lot expiration or retest. The notification lists the sampling plan information and includes a link to the Item Samples window, where information about the sampling event is populated.
The Testing Notification workflow sends a notification to prompt you to perform a test and enter its result against a particular sample. It is initiated by the creation of a sample that is already associated to a specification or selection of the result action for retesting a certain test. Each tester for a given sample in process receives a notification for the expected test result.
The Sample Disposition Notification workflow prompts for assignment of the final disposition for a sample once testing is complete. The sample disposition can be changed to accepted, accepted with variance, or rejected when all tests (if required by the associated specification) have recorded results that have been evaluated and finalized.
The Sample Group Disposition Notification workflow notifies you that the sampling event requires a final disposition, based on the number of samples required by the sampling plan. This workflow is launched when all the samples within a sampling event have a final disposition of accept, accept with variance, reject, or cancel.
The Composite Results Notification workflow asks you whether to composite the results across a set of samples within the same sampling event. This workflow is initiated when testing of all the samples in a sampling event (based on the number of samples required by the sampling plan) is complete and each sample has a final sample disposition. The notification provides a link to the Composite Results window, where information about the sampling event is populated.
The Spec Status Change Approval Notification workflow notifies the contact person when the specification status has changed. The workflow is activated for processing the status change. Typically, workflow approval is activated for status changes to Approved for Lab Use and Approved for General Use. The other statuses can be processed without requiring workflow approval.
The Spec Customer Validity Rule Status Change Approval Notification workflow notifies the contact person when the customer specification validity rule status has changed. The workflow is activated for processing the status change. Typically, workflow approval is activated for status changes to Approved for Lab Use and Approved for General Use. The other statuses can be processed without requiring workflow approval.
The Spec Inventory Validity Rule Status Change Approval Notification workflow notifies the contact person when the inventory specification validity rule status has changed. The workflow is activated for processing the status change. Typically, workflow approval is activated for status changes to Approved for Lab Use and Approved for General Use. The other statuses can be processed without requiring workflow approval.
The Spec Supplier Validity Rule Status Change Approval Notification workflow notifies the contact person when the supplier specification validity rule status has changed. The workflow is activated for processing the status change. Typically, workflow approval is activated for status changes to Approved for Lab Use and Approved for General Use. The other statuses can be processed without requiring workflow approval.
The Spec WIP Validity Rule Status Change Approval Notification workflow notifies the contact person when the WIP specification validity rule status has changed. The workflow is activated for processing the status change. Typically, workflow approval is activated for status changes to Approved for Lab Use and Approved for General Use. The other statuses can be processed without requiring workflow approval.
The Spec Monitoring Validity Rule Status Change Approval Notification workflow notifies the contact person when the monitoring specification validity rule status has changed. The workflow is activated for processing the status change. Typically, workflow approval is activated for status changes to Approved for Lab Use and Approved for General Use. The other statuses can be processed without requiring workflow approval.
The Sample Group Rejection Notification workflow notifies the contact person that either a monitoring sample group, or a stability study time point sample group is rejected.
The Stability Study Change Status Notification workflow notifies the study owner of status changes in the stability study. The process of changing status from New to a status of Completed involves a series of workflow notifications. Oracle E-Records operates with this workflow to enforce the stability study status control business rules. The cancellation of a stability study is also controlled by the workflow.
When the stability study is approved, and specific lots of the item to be tested exist, then the Stability Study Lot Sample Notification workflow notifies the stability study contact person to obtain samples for all required material sources. In the notification, the contact person is designated to draw and store the specified samples, and to update the sample records accordingly.
When the stability study is approved, and specific lots of the item to be tested do not exist, then the Stability Study Batch Creation Notification workflow notifies the stability study contact person to request that a batch be created for the study. The notification is sent only if the batch is a material source.
The Stability Study Testing workflow is a master workflow that governs the Stability Study Time Point Scheduling Notification workflow, and the Stability Study Late Time Point Scheduling Notification workflow. This workflow runs as a background process to monitor for any time point test that requires a workflow notification, or a late workflow notification. The workflow raises the appropriate event for either scheduled or late time point tests.
If the stability study is canceled or the scheduled time point testing date changes, then a workflow API manages the situation. The sample group disposition is changed from a status of retained to a status of pending, and the sample pull dates are updated.
The Stability Study Time Point Scheduling Notification workflow notifies you to pull samples for time point testing. The notification considers the required lead time, and it requests you to change the disposition of a time point sample from Retained to Pending. When the sample disposition is changed to Pending, tests are scheduled. If the test is not performed within the grace period, then the OPM Quality Stability Study Testing master workflow raises a separate event that indicates the test is overdue.
The Stability Study Late Time Point Scheduling Notification workflow notifies you that a test is overdue. The notification considers the required grace period, and uses the OPM Quality Stability Study Testing master workflow to raise a separate event to indicate the test is late.
The Quality UOM Conversion Notification workflow notifies the contact person that a recommended UOM conversion exists. A link to the Item Lot Inter-class Unit of Measure Conversion window in the Oracle Inventory application is provided. This link does not operate unless a lot number is assigned.
For the proper functioning of the workflows, a few administrative steps must be handled. These include setting up notification contacts for the workflow and starting the workflow engine.
In Oracle Applications, choose the Oracle Workflow responsibility and invoke the Workflow Process Activation. Enable the following workflow notifications:
OPM Quality Sample Creation
OPM Quality Test
OPM Quality Sample Disposition
OPM Quality Sample Group Disposition
OPM Quality Composite Results
OPM Quality Spec Status Change Approval
OPM Quality Spec Customer Validity Rule Status Change Approval
OPM Quality Spec Inventory Validity Rule Status Change Approval
OPM Quality Spec Supplier Validity Rule Status Change Approval
OPM Quality Spec WIP Validity Rule Status Change Approval
OPM Quality Spec Monitoring Validity Rule Status Change Approval
OPM Quality Sample Group Rejection
OPM Quality Stability Study Change Status
OPM Quality Stability Study Lot Sample
OPM Quality Stability Study Batch Creation
OPM Quality Stability Study Testing
OPM Quality Stability Study Time Point Scheduling
OPM Quality Stability Study Late Time Point Scheduling
OPM Quality UOM Conversion
Raising an event can be done from PL/SQL code or within a workflow. Raising events must be done before commit statements or when something has occurred. When raising an event, parameters can be sent to the event for use by the workflow. The parameters are defined as a set of name/value pairs. These name/values are used as the attribute name/values of the workflow associated with the subscription for the specific event being raised.
Use the Workflow Administrator to configure the seeded event subscription for the prebuilt inbound message if necessary.
Using the Workflow Administrator, add an event that can be raised from the PL/SQL code. This event can be due to an inventory transaction, item receiving or production, shipment picklot, etc.
Each business event is identified by a short name followed by a description. The event is referenced by the event short name across the framework and outside the framework. You need to know the event short name in order to call the API. The event is defined using the SSWA responsibility Workflow Administrator Web Applications. The owner tag of the business event is the application short name, such as GMD.
Refer to the Oracle Workflow Guide for details on configuring a workflow event.
Use the Workflow Administrator to add a subscription that subscribes to the event as defined earlier. This subscription is associated with a specific workflow. For example, an inventory transaction can raise an event where a subscriber to that event initiates the Sample Creation workflow.
A subscription can be added to a defined local business event. The phase of the subscription determines if the subscription is synchronous or not. Phase values less than 100 are synchronous; all others asynchronous. There can be multiple subscriptions to the same business event with different functionality. A workflow can be associated with a subscription.
The Workflow Quality Manager events should have the second subscriber disabled. This enables the Quality workflow notifications to function as expected with respect to samples and sample dispositions.
Workflows can be associated with a subscription. In the case of OPM Quality Management, a subscription for an event initiates a workflow execution.
Workflows control notifications for sample creation, sample disposition, and sample rejection. Workflows also control notifications for specification status and specification validity rule status. Workflows monitor and execute all aspects of the stability study including notifications for study status change, lot sampling, batch creation, time point testing. If time point testing is not performed within a scheduled grace period, then workflow issues a late time point test notification.
Following are the OPM Quality Management workflows:
OPM Quality Sample Creation
OPM Quality Test
OPM Quality Sample Disposition
OPM Quality Composite Results
OPM Quality Sample Group Disposition
OPM Quality Spec Status Change Approval
OPM Quality Spec Customer Validity Rule Status Change Approval
OPM Quality Spec Inventory Validity Rule Status Change Approval
OPM Quality Spec Supplier Validity Rule Status Change Approval
OPM Quality Spec WIP Validity Rule Status Change Approval
OPM Quality Spec Monitoring Validity Rule Status Change Approval
OPM Quality Sample Group Rejection
OPM Quality Stability Study Change Status
OPM Quality Stability Study Lot Sample
OPM Quality Stability Study Batch Creation
OPM Quality Stability Study Testing
OPM Quality Stability Study Time Point Test
OPM Quality UOM Conversion
The OPM Quality Sample Creation workflow notifies the workflow recipient that a sample or samples need to be taken for the item transaction.
The workflow that notifies a user about creating a sample can be instantiated by multiple applications, each with its own set of attributes and parameters. These applications include Receiving, Inventory, Production, and the resample quality action.
This business event is triggered when adjusting, updating, or creating items.
oracle.apps.gmd.inventory.created
IC_TRANS_CMP.TRANS_ID
Subscriber Workflow:
OPM Quality Sample Creation
Oracle Approval Management Transaction Name:
Process Quality Inventory Transaction Sample Creation
| Parameter | Description |
|---|---|
| ORG | Inventory Organization |
| ITEM_ID | Item ID |
| ITEM_NO | Item |
| TRANS_QTY1 | Quantity1 |
| TRANS_QTY2 | Quantity2 |
| TRANS_QTY_UOM1 | UOM1 |
| TRANS_QTY_UOM2 | UOM2 |
| LOT_ID2 | Lot ID |
| LOT_NO | Lot Number |
| LPN | License Plate Number |
| SUBINVENTORY | Subinventory |
| LOCATOR | Locator |
| GRADE | Grade |
| TRANSACTION_TYPE | Trans Type |
The workflow sends a notification to the contact person, requesting that a sample be taken. The body of the notification for inventory transaction follows:
You have been designated to create a sample or samples based on the inventory transaction described below:
Transaction Details
Document Type: &DOC_TYPE
Document Description: &DOC_DESC Document No: &DOCUMENT_NO Organization Code: &ORGN_CODE
Item: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Parent Lot Number: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
LPN: LPN_No.
Quantity: &TRANS_QTY
UOM: &TRANS_UOM
Dual Quantity: &ITEM_QTY2
Dual UOM: &ITEM_UOM2
Sampling Plan: &SAMPLING_PLAN
Click Forms to launch the Samples window. Enter the sample and save. The Notifications window is displayed again and you can click OK to respond to the notice.
This business event is triggered from the receipt transaction for an item that has the inspection required indicator enabled on the item master. The receiving transaction process flow is:
Receive against a purchase order line.
Receive material into a receiving locator.
Quality Receiving event is raised.
An applicable specification is retrieved.
Send a notification to create a sample.
Sample is created.
Send a notification to perform tests.
Testing is performed and completed.
Sample Disposition is assigned.
Sample Group Disposition is assigned.
Go to the Receiving Transaction window to record accepted or rejected quantities and deliver material to inventory.
oracle.apps.gml.po.receipt.created
rcv_transactions.transaction_id
Subscriber Workflow:
OPM Quality Sample Creation
Oracle Approval Management Transaction Name:
Process Quality Receiving Transaction Sample Creation
| Parameter | Description |
|---|---|
| ORG | Inventory Organization |
| SUB_ORG | Sub inventory |
| ITEM_ID | Item ID |
| ITEM_NO | Item |
| TRANS_QTY1 | Quantity1 |
| TRANS_QTY_UOM1 | UOM1 |
| TRANS_QTY2 | Quantity2 |
| TRANS_QTY_UOM2 | UOM2 |
| LINE_TYPE | Only products and byproducts |
| RECEIPT_ID | Receipt ID |
| RECEIPT_LINE_ID | Receipt Line ID |
| PO_HEADER_ID | PO Header ID |
| PO_LINE_ID | PO Line ID |
| SUPPLIER_ID | Supplier ID |
The workflow sends a notification to the contact person, requesting that a sample be taken. The body of the notification for receiving transaction follows:
You are designated to create a sample or samples based on the receiving transaction described below:
Transaction Details
Organization Code: &ORGN_CODE
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Receipt: &RECEIPT_NO
Purchase Order No: &PURCHASE_NO
Supplier Number: &SUPPLIER_NO
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Parent Lot Number: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
Qty: &TRANS_QTY
UOM: &TRANS_UOM
Sampling Plan: &SAMPLING_PLAN
This business event is triggered from the receipt transaction into a specific lot for an item that has the inspection required indicator enabled on the item master. The receiving transaction process flow is:
Receive against a purchase order line.
Receive material into a lot inventory locator.
Quality Receiving event is raised.
An applicable specification is retrieved.
Send a notification to create a sample.
Sample is created.
Send a notification to perform tests.
Testing is performed and completed.
Sample Disposition is assigned.
Sample Group Disposition is assigned.
Go to the Receiving Transaction window to record accepted or rejected quantities and deliver material to inventory.
oracle.apps.gmi.po.receipt
rcv_transaction_interface.transaction_id
Subscriber Workflow:
OPM Quality Sample Creation
Oracle Approval Management Transaction Name:
Process Quality Receiving into Inventory
| Parameter | Description |
|---|---|
| ORG | Inventory Organization |
| SUB_ORG | Sub inventory |
| ITEM_ID | Item ID |
| ITEM_NO | Item |
| TRANS_QTY1 | Quantity1 |
| TRANS_QTY_UOM1 | UOM1 |
| TRANS_QTY2 | Quantity2 |
| TRANS_QTY_UOM2 | UOM2 |
| LINE_TYPE | Only products and byproducts |
| RECEIPT_ID | Receipt ID |
| RECEIPT_LINE_ID | Receipt Line ID |
| PO_HEADER_ID | PO Header ID |
| PO_LINE_ID | PO Line ID |
| SUPPLIER_ID | Supplier ID |
The workflow sends a notification to the contact person, requesting that a sample be taken. The body of the notification for receiving transaction follows:
You are designated to create a sample for the receiving transaction described below:
Transaction Details
Organization Code: &ORGN_CODE - &ORGN_NAME Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Receipt: &RECEIPT_NO
Purchase Order No: &PO_NUMBER
Supplier Number: &SUPPLIER
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC1
Parent Lot Number: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
Qty: &TRANS_QTY
UOM: &TRANS_UOM
Sampling Plan: &SAMPLING_PLAN
Click Forms to launch the Samples window. Enter the sample and save. The Notifications window is displayed again and you can click OK to respond to the notice.
When a batch or batch step is created, an event is raised to initiate the OPM Quality Sample Creation workflow. This workflow sends a notification to a contact person informing that a new batch or batch step is created and sampling is required. This includes the samples required for the batch or batch step.
At the release of each step (operation), when the batch step quality status is Sample Required, the OPM Quality Sample Creation workflow is initiated to inform the contact person to take a sample of the production item. This notification includes a link to the Samples window.
oracle.apps.gme.batch.created
oracle.apps.gme.batchstep.created
oracle.apps.gme.bstep.rel.wf
GME_BATCH_HEADER.BATCH_ID
GME_BATCH_STEPS.BATCHSTEP_ID
| Type | Subscriber Workflow | Oracle Approval Management Transaction Name |
|---|---|---|
| Batch | OPM Quality Sample Creation | Process Quality Production Transaction Sample Creation |
| Batch Step | OPM Quality Sample Creation | Process Quality Production Transaction Sample Creation |
| Parameter | Description |
|---|---|
| BATCH_ID | Batch ID |
| BATCH_STEP_ID | Batch Step ID |
The workflow sends a notification to the contact person, requesting that a Sample be taken. The body of the notification for the production transaction follows:
You have been designated to create a sample or samples based on the production transaction described below:
Transaction Details
Organization Code: &ORGN_CODE - &ORGN_NAME
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Batch No: &BATCH_ NO
Batch Step: &BATCH_ STEP_NO
Recipe: &RECIPE_ NO
Formula: &FORMULA_ NO
Item: &ITEM_NO
Item Revision: &ITEM_LOCATOR
Item Description: &ITEM_DESC
Sampling Plan: &SAMPLING_PLAN
Click Forms to launch the Samples window. Enter the sample and save. The Notifications window is displayed again and you can click OK to respond to the notice.
This business event is initiated by reaching the expiration date for an item lot.
oracle.apps.gmd.lotexpiry
IC_LOTS_MST.ITEM_ID||'-'||IC_LOTS_MST.LOT_ID
ORGANIZATION_ID - INVENTORY_ITEM_ID - LOT_NUMBER
Subscriber Workflow:
OPM Quality Sample Creation
Oracle Approval Management Transaction Name:
Process Quality Lot Expiry Sample Creation
| Parameter | Description |
|---|---|
| ITEM_ID | Item ID |
| LOT_ID | Lot ID |
| LOT_NO | Lot Number |
| GRADE | Grade |
| EXPIRE_DATE | Expiration Date |
The workflow sends a notification to the contact person, requesting that a Sample be taken. The body of the notification for Lot expiration transaction follows:
You are designated to create a sample for the lot expiry transaction described below Transaction Details:
Transaction Details
Organization: &ORGN_CODE - &ORGN_NAME
Subinventory: &SUBINVENTORY
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC1
Parent Lot Number: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
UOM: &TRANS_UOM
Dual UOM: &ITEM_UOM2
Expiry Date: &EXPIRY_DATE
Sampling Plan: &SAMPLING_PLAN
Run the Inventory Date Notification concurrent program in Oracle Inventory to either send a notification to manually or automatically create samples based on lot retest or lot expiry. The concurrent request can launch the Lot and Serial Date Notification workflow, which raises the business events for reaching the lot retest or expiry date. The Inventory Date Notification concurrent request searches for item lots that are process quality-enabled in a process-enabled inventory organization. Refer to the Oracle Inventory User's Guide for detailed information on the concurrent request parameters.
This business event is initiated by reaching the retest date for an item lot.
oracle.apps.gmd.lotretest
IC_LOTS_MST.ITEM_ID||'-'||IC_LOTS_MST.LOT_ID
Subscriber Workflow:
OPM Quality Sample Creation
Oracle Approval Management Transaction Name:
Process Quality Lot Retest Sample Creation
| Parameter | Description |
|---|---|
| ITEM_ID | Item ID |
| LOT_ID | Lot ID |
| LOT_NO | Lot Number |
| GRADE | Grade |
| RETEST_DATE | Retest Date |
The workflow sends a notification to the contact person, requesting that a Sample be taken. The body of the notification for lot retest transaction follows:
You are designated to create a sample for the lotretest transaction described below Transaction Details:
Transaction Details
Organization Code: &ORG
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC1
Parent Lot Number: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
UOM: &TRANS_UOM
Dual UOM: &ITEM_UOM2
Retest Date: &RETEST_DATE
Sampling Plan: &SAMPLING_PLAN
Click Forms to launch the Samples window. Enter the sample and save. The Notifications window is displayed again and you can click OK to respond to the notice.
Run the Inventory Date Notification concurrent program in Oracle Inventory to either send a notification to manually or automatically create samples based on lot retest or lot expiry. The concurrent request can launch the Lot and Serial Date Notification workflow, which raises the business events for reaching the lot retest or expiry date. The Inventory Date Notification concurrent request searches for item lots that are process quality-enabled in a process-enabled inventory organization. Refer to the Oracle Inventory User's Guide for detailed information on the concurrent request parameters.
There is a fork in the workflow. The notification is sent to the person defined in AME for the workflow's contact. The control parameter list is:
Event Type
Inventory Organization
Inventory Item
Subinventory
Locator
A contact person can be defined using at least one of the control parameters. The workflow resolves the role to at least a single user.
This workflow is initiated by creating a sample or retesting. When a sample is created and associated to a specification, each workflow recipient receives a notification for the scheduled tests. The quality testing process is:
Sample is created.
The tester defined for each test is retrieved from AME.
The tests are grouped by the tester defined in AME.
Sends a notification to each tester with the list of the tests they need to conduct. The notification includes a link to the Forms window where the results can be entered.
The purpose of this workflow is to find the testers and send notification for testing a particular sample. In the case of a sample creation, the sample information is identified. In the retest or additional testing scenarios, the test is known.
oracle.apps.gmd.qm.performtest
GMD_SAMPLES.SAMPLE_ID
Subscriber Workflow:
OPM Perform Quality Test
Oracle Approval Management Transaction Name:
Process Quality Perform Test
| Parameter | Description |
|---|---|
| SAMPLE_ID | Sample ID |
| SAMPLING_NO | Sample Number |
| TEST_ID | Test ID |
This workflow is spawned through the creation of sample and a specific specification for an item. This function finds the notifier associated with the test from AME. The control parameters are:
Lab
Item
Test Class
Test
Test Method
A contact person can be defined using at least one of the control parameters. The role associated with this test is resolved to at least a single user.
The workflow sends a notification soliciting a response about the result of the tests.
You have been designated to perform the following test on the sample.
Sample Details
Laboratory Organization: &QC_LAB_ORGN_CODE
Sample Number: &SAMPLE_NO
Sample Description: &SAMPLE_DESC
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Item UOM: &ITEM_UOM
Parent Lot: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Test Details
------- Test Code: &TEST_CODE
Test Description: &TEST_DESC
Test Class: &TEST_CLASS
Test Method: TEST_METHOD_CODE
Test Method Description: &TEST_METHOD_DESC
Test Replication: &TEST_REPLICATE
Test Equipment: &RESOURCES
Planned Resource: &PLANNED_RESOURCE
Planned Result Date: &PLANNED_RESULT_DATE
Test By Date: &TEST_BY_DATE
Click on the form to launch the Results window and enter the results. After saving the result, in the Notification screen, click OK to respond to the notice.
When sample testing is complete, the OPM Quality Sample Disposition workflow is initiated to prompt for a sample disposition as Accept, Accept with Variance, or Reject.
The basic process for initiating the OPM Quality Sample Disposition workflow is:
All required tests have results.
An event for the sample disposition is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to the contact person as defined in AME, along with the sample information.
oracle.apps.gmd.qm.sample.disposition
GMD_SAMPLES.SAMPLE_ID
Subscriber Workflow:
OPM Sample, Sample Group Disposition, and Composite Results Creation
Oracle Approval Management Transaction Name:
Process Quality Sample Disposition
| Parameter | Description |
|---|---|
| SAMPLE_ID | Sample ID |
| SAMPLING_EVENT_ID | Sampling Event ID |
| RECOMMENDED_DISP | Recommended Target Disposition |
This function finds the approver associated with the sample from AME. The control parameters are:
QC Lab Org
Item
A contact person can be defined using at least one of the control parameters. The role associated with this test is resolved to at least a single user.
You receive a notification soliciting a response about sample approval.
You have been designated to assign a disposition to the sample as described below.
Item Details
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Parent Lot Number: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
LPN: LPN_No
Sample Details
---------------------------------
Sample Number: &SAMPLE_NO
Sample Source: &SAMPLE_SOURCE
Sample Description: &SAMPLE_DESC
Specification: &SPECIFICATION
Sample Plan: &SAMPLE_PLAN
Sample Disposition: &SAMPLE_DISPOSITION
Click Forms to launch the Samples window. After saving the result you will come back to the Notification screen where you may Click the OK button to respond to the notice.
When testing is complete for a sampling event, the OPM Quality Composite Results workflow lets you composite the results across the samples.
The process for initiating the OPM Quality Composite Results workflow is:
All samples of a sampling event have a final sample disposition.
An event for the composite results is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.compositeresults
GMD_SAMPLES.SAMPLE_EVENT_ID
Subscriber Workflow:
OPM Sample, Sample Group Disposition, and Composite Results Creation
Oracle Approval Management Transaction Name:
Process Quality Sample Composite Results
| Parameter | Description |
|---|---|
| SAMPLING_EVENT_ID | Sampling Event ID |
This function finds the notifier associated with the composite result from AME. The control parameters list is:
Org
Item
A contact person can be defined using at least one of the control parameters. The role associated with this test is resolved to at least a single user.
You receive a notification soliciting a response about sample composite.
You have been designated to composite results for the sample described below.
Organization: &ORG
Item: &ITEM_NO
Description: &ITEM_DESC1
Parent Lot: &PARENT_LOT_NUMBER
Lot: &LOT_NO
LPN: LPN_No
Sample Plan Name: &SAMPLE_PLAN
Samples Taken: &SAMPLES_TAKEN
Spec Name: &SPEC_NAME
Click Forms to launch the Composite Results window. After saving the result you will come back to the Notification screen where you may Click the OK button to respond to the notice.
When all the samples in the sampling event have dispositions of accept, reject, accept with variance, or cancel, the OPM Quality Sample Group Disposition workflow is initiated to prompt for a sampling event disposition.
The basic process for initiating the OPM Quality Sample Group Disposition workflow is:
All sample dispositions have been changed from testing to accept, accept with variance, reject, or cancel.
An event for the sampling disposition is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.samplingevent.disposition
GMD_SAMPLES.SAMPLE_EVENT_ID
Subscriber Workflow:
OPM Sample, Sample Group Disposition, and Composite Results Creation
Oracle Approval Management Transaction Name:
Process Quality Sample Group Disposition
| Parameter | Description |
|---|---|
| SAMPLING_EVENT_ID | Sampling Event ID |
| RECOMMENDED_DISP | Recommended Target Disposition |
| CURRENT_DISP | Current Target Disposition |
This function finds the notifier associated with the sampling event approval from AME. The control parameters list is:
Org
Item
A contact person can be defined using at least one of the control parameters. The role associated with this test is resolved to at least a single user.
You receive a notification soliciting a response about sample event disposition.
You have been designated to assign a disposition to the sampling event as described below.
Recommended Disposition:
Item: &ITEM_NO
Description: &ITEM_DESC1
Parent Lot: &PARENT_LOT_NUMBER
Lot: &LOT_NO
LPN: LPN_No
Sample Plan: &SAMPLE_PLAN
Spec Name: &SPEC_NAME
Click Forms to launch the Sample Groups window. After saving the result you will come back to the Notification screen where you may Click the OK button to respond to the notice.
Refer to the "Understanding the Status Approval Workflow" topic for a complete discussion of changing status of specifications. The basic process for initiating the OPM Quality Spec Status Change Approval workflow is:
A specification is status is changed.
An event for the specification status change is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.spec.sts
GMD_SPECIFICATIONS.SPEC_ID
Subscriber Workflow:
OPM Quality Spec Status Change Approval
Oracle Approval Management Transaction Name:
Process Quality Spec Status Change Approval
| Parameter | Description |
|---|---|
| ITEM_NO | Item Name |
| ORGN_CODE | Organization Code |
Request Notification
The workflow sends a notification to the contact person indicating that a specification needs approval.
&REQUESTER has requested a spec status change
Spec Name: &SPEC_NAME
Spec Version: &SPEC_VRS
Spec Description: &DESCRIPTION Spec Status: &SPEC_STATUS
Spec Type: &SPEC_TYPE
Overlay: &OVERLAY Base Spec: &BASE_SPEC
Item: &ITEM_NO Item Revision: &ITEM_REVISION
Item Description: &DESCRIPTION
Grade: &GRADE
Owner Organization: &OWNER_ORGN_CODE
Owner Organization Name: &OWNER_NAME
Current Status: &SPEC_STATUS
Change Status To: &TARGET_STATUS_DESC
Please click Approve to approve or Reject to reject.
Refer to the "Understanding the Status Approval Workflow" topic for a complete discussion of changing status of specification validity rules. The basic process for initiating the OPM Quality Spec Validity Rule Status Change Approval workflow is:
A specification validity rule status is changed.
An event for the specification validity rule status change is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.svr.cus.sts
GMD_CUSTOMER_SPEC_VRS. SPEC_VR_ID
Subscriber Workflow:
OPM Quality Customer Spec Validity Rule Status Change
Oracle Approval Management Transaction Name:
Process Quality Customer Validity Rule Status Change Approval
| Parameter | Description |
|---|---|
| CUST_NAME | Customer Name |
| ITEM_NO | Item |
Request Notification
The workflow sends a notification to the contact person indicating a request to approve a customer validity rule.
&REQUESTER has requested a spec validity rule status change
Spec Name: &SPEC_NAME
Spec Version: &SPEC_VRS
Spec Description: &DESCRIPTION
Spec Status: &SPEC_STATUS
Spec Type: &SPEC_TYPE
Overlay: &OVERLAY
Item No: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Grade: &GRADE
Owner Organization: &OWNER_ORGN_CODE
Owner Organization Name: &OWNER_ORGN_NAME
Spec Validity Rule Status: &SPEC_VR_STATUS
Parent Lot: &PARENT_LOT_NUMBER
Lot: &LOT_NUMBER
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Resource: &RESOURCE
Requestor: &REQUESTOR
Current Status: &START_STATUS_DESC
Change Status To: &TARGET_STATUS_DESC
Please click Approve to approve or click Reject to reject.
Refer to the "Understanding the Status Approval Workflow" topic for a complete discussion of changing status of specification validity rules. The basic process for initiating the OPM Quality Spec Validity Rule Status Change Approval workflow is:
A specification validity rule status is changed.
An event for the specification validity rule status change is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.svr.inv.sts
GMD_INVENTORY_SPEC_VRS. SPEC_VR_ID
Subscriber Workflow:
OPM Quality Inventory Spec Validity Rule Status Change
Oracle Approval Management Transaction Name:
Process Quality Inventory Validity Rule Status Change Approval
| Parameter | Description |
|---|---|
| ITEM_NO | Item |
Request Notification
The workflow sends a notification to the contact person indicating a request to approve an inventory validity rule.
&REQUESTER has requested a spec validity rule status change
Spec Name: &SPEC_NAME
Spec Version: &SPEC_VRS
Spec Status: &SPEC_STATUS
Source Type: &SOURCE_TYPE
Item No: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Grade: &GRADE
Owner Organization: &OWNER_ORGN_CODE
Owner Organization Name: &OWNER_ORGN_NAME
Spec Validity Rule Status: &SPEC_VR_STATUS Parent Lot: &PARENT_LOT_NUMBER Lot: &LOT_NUMBER
Delayed LPN Entry: delayed_lpn_entry (Yes/No).
Subinventory: &SUBINVENTORY
Locator: &LOCATOR Resource: &RESOURCE
Requester: &REQUESTER
Current Status: &START_STATUS_DESC
Change Status To: &TARGET_STATUS_DESC
Please click Approve to approve or click Reject to reject.
Refer to the "Understanding the Status Approval Workflow" topic for a complete discussion of changing status of specification validity rules. The basic process for initiating the OPM Quality Spec Validity Rule Status Change Approval workflow is:
A specification validity rule status is changed.
An event for the specification validity rule status change is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.svr.sup.sts
GMD_SUPPLIER_SPEC_VRS. SPEC_VR_ID
Subscriber Workflow:
OPM Quality Supplier Spec Validity Rule Status Change
Oracle Approval Management Transaction Name:
Process Quality Supplier Validity Rule Status Change Approval
| Parameter | Description |
|---|---|
| SUPP_NAME | Supplier Name |
| ITEM_NO | Item |
Request Notification
The workflow sends a notification to the contact person indicating a request to approve a supplier validity rule.
&REQUESTER has requested a spec validity rule status change
Spec Name: &SPEC_NAME
Spec Version: &SPEC_VRS
Spec Status: &SPEC_STATUS
Source Type: &SOURCE TYPE
Item No: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Grade: &GRADE
Owner Organization: &OWNER_ORGN_CODE
Owner Organization Name: &OWNER_ORGN_NAME
Spec Validity Rule Status: &SPEC_VR_STATUS
Parent Lot: &PARENT_LOT_NUMBER
Lot: &LOT_NUMBER
Delayed LPN Entry: delayed_lpn_entry (Yes/No).
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Resource: &RESOURCE
Requester: &REQUESTER
Current Status: &START_STATUS_DESC
Change Status To: &TARGET_STATUS_DESC
Please click Approve to approve or click Reject to reject.
Refer to the "Understanding the Status Approval Workflow" topic for a complete discussion of changing status of specification validity rules. The basic process for initiating the OPM Quality Spec Validity Rule Status Change Approval workflow is:
A specification validity rule status is changed.
An event for the specification validity rule status change is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.svr.wip.sts
GMD_WIP_SPEC_VRS. SPEC_VR_ID
Subscriber Workflow:
OPM Quality WIP Spec Validity Rule Status Change
Oracle Approval Management Transaction Name:
Process Quality WIP Validity Rule Status Change Approval
| Parameter | Description |
|---|---|
| RECIPE | Recipe |
| ITEM_NO | Item |
Request Notification
The workflow sends a notification to the contact person indicating a request to approve a WIP validity rule.
&REQUESTER has requested a spec validity rule status change
Spec Name: &SPEC_NAME
Spec Version: &SPEC_VRS
Spec Status: &SPEC_STATUS
Source Type: &SOURCE TYPE
Item No: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Grade: &GRADE
Owner Organization: &OWNER_ORGN_CODE
Owner Organization Name: &OWNER_ORGN_NAME
Spec Validity Rule Status: &SPEC_VR_STATUS
Parent Lot: &PARENT_LOT_NUMBER
Lot: &LOT_NUMBER
Delayed LPN Entry: delayed_lpn_entry (Yes/No).
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Resource: &RESOURCE
Requester: &REQUESTER
Current Status: &START_STATUS_DESC
Change Status To: &TARGET_STATUS_DESC
Please click Approve to approve or click Reject to reject.
Refer to the "Understanding the Status Approval Workflow" topic for a complete discussion of changing status of specification validity rules. The basic process for initiating the OPM Quality Spec Validity Rule Status Change Approval workflow is:
A specification validity rule status is changed.
An event for the specification validity rule status change is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
oracle.apps.gmd.qm.svr.mon.sts
GMD_MONITORING_SPEC_VRS. SPEC_VR_ID
Subscriber Workflow:
OPM Quality Monitoring Spec Validity Rule Status Change
Oracle Approval Management Transaction Name:
Process Quality Monitoring Validity Rule Status Change Approval
| Parameter | Description |
|---|---|
| ORG | Organization |
Request Notification
The workflow sends a notification to the contact person indicating a request to approve a WIP validity rule.
&REQUESTER has requested a spec validity rule status change
Spec Name: &SPEC_NAME
Spec Version: &SPEC_VRS
Spec Status: &SPEC_STATUS
Source Type: &SOURCE TYPE
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Grade: &GRADE
Owner Organization: &OWNER_ORGN_CODE
Owner Organization Name: &OWNER_ORGN_NAME
Spec Validity Rule Status: &SPEC_VR_STATUS
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Resource: &RESOURCE
Requestor: &REQUESTOR
Current Status: &START_STATUS_DESC
Change Status To: &TARGET_STATUS_DESC
Please click Approve to approve or click Reject to reject.
The Sample Group Rejection Notification notifies you that either a monitoring sample group, or a stability study time point sample group is rejected.
The basic process for initiating the OPM Quality Sample Group Rejection workflow is:
Sample group dispositions are changed from complete to reject.
An event for the sampling disposition is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the sampling event information.
The Sample Group Rejection Notification notifies the contact person that either a monitoring sample group, or a stability study time point sample group is rejected.
oracle.apps.gmd.qm.smpl.rej
SAMPLING_EVENT_ID
Subscriber Workflow:
OPM Quality Sample Group Rejection Workflow
Oracle Approval Management Transaction Name:
Process Quality Sample Rejection
| Parameter | Description |
|---|---|
| SUBINVENTORY | Subinventory |
| RESOURCE | Resource |
Request Notification
The workflow sends a notification to the contact person indicating that a sample group is rejected.
In the case of Resource/Locator:
The following sample disposition has been rejected
Resource Details
Resource: &RESOURCE
Resource Instance: &RESOURCE_INST
Description: &RESOURCE_DESC
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Click on the form to open the Sample Groups window.
In the case of Stability Studies:
The following sample disposition has been rejected
Study: &STUDY_NAME
Study Description: &STUDY_DESC
Item: &ITEM_NO
Item Description: &ITEM_DESC
Click on the form to open the Sample Groups window.
The Stability Study Change Status Notification notifies the study owner of status changes in the stability study. The process of changing the stability study status from New to a status of Complete involves a series of workflow notifications. This workflow can work in conjunction with Oracle E-Records if it is enabled.
The basic process for initiating the OPM Quality Stability Study Change Status workflow is:
A stability study is created with an initial status of New, depending on the default value assigned to GMA: New for the STBL document type.
An event for change status is raised.
Subscriber for the event initiates the workflow.
Workflow sends notification to contact person as defined in AME, along with the change status event information.
This business event is triggered from the Change Status dialog box accessed from the Actions menu on the Stability Study window.
oracle.apps.gmd.qm.ss.csts
SS_ID
Subscriber Workflow:
Quality Stability Study Change Status
Oracle Approval Management Transaction Name:
GMDQM_STABILITY_CSTS
Process Quality Stability Study Status Change
| Parameter | Description |
|---|---|
| OWNER_ORGN_CODE | Lab Organization Code |
| ITEM_NO | Item |
You receive a notification about the requested change of status for the stability study. The body of that request is:
&REQUESTER has requested a change status for the following Stability Study
Owner Organization: &ORG
Stability Study Name: &SS_NAME
Stability Study Description: &SS_DESC
Start Status Description: &START_STATUS_DESC
Target Status Description: &TARGET_STATUS_DESC
Storage Plan: &STORAGE_PLAN
Item No: &ITEM_NO
Item Description: &ITEM_DESC
Item Revision: &ITEM_REVISION
Base Spec: &BASE_SPEC
Lab Org: &LAB_ORGN
Notification Time: &NOTIFY_TIME
Grace Time: &GRACE_TIME
Sched Start Date: &SCHED_START_DATE
Sched End Date: &SCHED_END_DATE
Revised Start Date: &REVISED_START_DATE
Revised End Date: &REVISED_END_DATE
Actual Start Date: &ACTUAL_START_DATE
Actual End Date: &ACTUAL_END_DATE
Owner: &OWNER
The following table lists each of the preseeded stability study statuses, a description of the status as it appears in the workflow notification process, whether status can be updated, and the listed status type:
| Status | Description | Updateable? | Status Type |
|---|---|---|---|
| 100 | New | Yes | 100 |
| 200 | Request Approval of Stability Study Plan | No | 200 |
| 300 | Revise Stability Study Plan | Yes | 300 |
| 400 | Stability Study Plan Approved | Yes | 400 |
| 500 | Request Approval to Launch | No | 500 |
| 600 | Revise Launch Request | Yes | 600 |
| 700 | Launch Approved | Yes | 700 |
| 800 | In Progress | No | 800 |
| 900 | Request Approval to Cancel | No | 900 |
| 940 | Request Approval to Cancel From Approved Plan | Yes | 940 |
| 970 | Request Approval to Cancel From Approved Launch | No | 970 |
| 980 | Request Approval to Cancel from In Progress | No | 980 |
| 1000 | Canceled | No | 1000 |
| 1100 | Completed | No | 1100 |
The Stability Study Lot Sample Notification notifies a workflow recipient to take samples from the specified lot material source when a stability study is approved.
This business event is triggered by a stability study status change to Stability Study Plan Approved.
oracle.apps.gmd.qm.ss.lot
SOURCE_ID
Subscriber Workflow:
OPM Quality Stability Study Sample Creation
Oracle Approval Management Transaction Name:
GMD_STABILITY_LOT
Process Quality Stability Study Lot Sample
| Parameter | Description |
|---|---|
| OWNER_ORGN_CODE | Lab Organization Code |
| ITEM_NO | Item |
Request Notification
The workflow sends a notification to the contact person designating them to draw and store the listed samples, and to update the sample records accordingly. The body of the notification follows:
The following sample records have been created after the approval of the Sample Source Stability Study. You are designated to take an initial sample to qualify as a material source from this Stability Study:
Study: &STUDY
Study Description: &STUDY_DESC
Status: &STATUS
Organization: &ORG
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Parent Lot: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
Variant Material Source
Batch: &BATCH_ NO
Recipe: &RECIPE_ NO
Recipe Version: &RECIPE VERSION
Variant Storage condition
Storage Spec: &STORAGE_SPEC
Storage Spec Version: &STGE_SPEC_VER
Resource: &RESOURCE
Storage Subinventory: &STORAGE_SUBINVENTORY
Storage Locator: &STORAGE LOCATOR
Variant Package
Package: &PACKAGE
Formula: &FORMULA_ NO
Formula Version: &FORMULA_VERSION
Sample Quantity/UOM: &SAMPLE_QTY/&SAMPLE_UOM
Click Forms to open the Source Variants window. The notification window is displayed again and you can click OK to repsond to the notice.
The Stability Study Batch Creation Notification notifies a workflow recipient to create a batch as a material source when no specific lots are entered as material sources for the stability study. The workflow is triggered when a stability study is approved.
This business event is triggered by a stability study status change to Stability Study Plan Approved.
oracle.apps.gmd.qm.ss.batch.cr
SOURCE_ID
Subscriber Workflow:
OPM Quality Stability Study Sample Creation
Oracle Approval Management Transaction Name:
GMDQM_STABILITY_BATCH
Process Quality Stability Study Batch
| Parameter | Description |
|---|---|
| OWNER_ORGN_CODE | Lab Organization Code |
| ITEM_NO | Item |
Request Notification
The workflow sends a notification to the contact person designating them to create a batch. The body of the notification follows:
You are designated for creation of a batch as material source of a stability study. The details are as follows:
Organization: &ORG
Study: &STUDY
Study Description: &STUDY_DESC
Status: &STATUS
Study Date: &STUDY_DATE
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Plant: &PLANT
Recipe: &RECIPE
Recipe Version: &RECIPE VERSION
Sample Qty: &SAMPLE_QTY
Sample UOM: &SAMPLE_UOM
Please enter the Batch Number in the Material Sources Screen
The OPM Quality Stability Study Testing workflow is the master workflow for two related workflows:
OPM Quality Stability Study Time Point Scheduling Workflow
OPM Quality Stability Study Late Time Point Scheduling Workflow
The workflow is the background process for the stability study, and it checks continuously for any time point test requiring a workflow notification (oracle.apps.gmd.qm.ss.tp) or a late workflow notification (oracle.apps.gmd.qm.ss.tplt). In each instance, it raises an appropriate event.
Schedule the Workflow Background Process concurrent program to run hourly, or at an interval that is compatible with your stability study time point testing design.
Navigate to the Submit Request window.
Enter Name as Workflow Background Process. The Parameters dialog box displays.
Select Item Type as OPM Quality Stability Study Testing.
Select Process Deferred as Yes.
Select Process Timeout as Yes.
Click OK.
Click Schedule... in the At these Times... region. The Schedule dialog box displays.
Select Periodically in the Run the Job... region.
Enter Start At as the date and time to begin the stability study testing. This field defaults to the system date and time.
Leave End At blank to run the process indefinitely, or enter an appropriate time and date to end the workflow background process.
Enter 1 and select Hour(s) to check for time point testing hourly.
Click OK.
Click Submit on the Submit Request window to submit the request.
The time point testing workflow is triggered so that a notification is sent to a user at a time set by the stability study lead time. If the test is not performed within the grace period, then a late notification is raised as a separate event.
If the stability study is canceled or a date changes, then the wf_engine.abort workflow API is called using the combination of item_type, the eight character name of the workflow, and item_key the key used for identifying the workflow.
Sample group disposition is changed from a status of Retained to a status of Pending. Sample pull dates on the are updated.
oracle.apps.gmd.qm.ss.test
SS_ID
Subscriber Workflow:
OPM Quality Stability Study Testing
Oracle Approval Management Transaction Name:
GMDQM_STABILITY_PARENTTEST
| Parameter | Description |
|---|---|
| OWNER_ORGN_CODE | Lab Organization Code |
| ITEM_NO | Item |
The Stability Study Time Point Test notification manages notifications for future testing and for late time point testing.
The Stability Study Time Point Test Notification notifies you that a future test is required. The notification considers the required lead time. If the test is not performed within the grace period, then the OPM Quality Stability Study Testing master workflow raises a separate event that indicates the test is overdue.
oracle.apps.gmd.qm.ss.tp
TIMEPOINT_ID
Subscriber Workflow:
OPM Quality Stability Study Time Point Test
Oracle Approval Management Transaction Name:
GMDQM_STABILITY_TEST
Process Quality Stability Study Testing Timepoint
| Parameter | Description |
|---|---|
| OWNER_ORGN_CODE | Lab Organization Code |
| ITEM_NO | Item |
Request Notification
You are designated to draw and store these samples and update the sample records accordingly:
Organization: &ORG
Study: &STUDY
Study Description: &STUDY_DESC
Status: &STATUS
Study Date: &STUDY_DATE
Time Name: &TIME_NAME
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Variant No: &VARIANT_NO
Storage Spec: &STORAGE_SPEC
Storage Spec Version: &STGE_SPEC_VER
Sample Qty: &SAMPLE_QTY
Resource: &RESOURCE
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Sample Number: &SAMPLE_NO
Sample Qty: &SAMPLE_QTY
Click Forms to launch the MultiRow Samples window. After saving the result you will come back to the Notification screen where you may Click the OK button to respond to the notice.
The Stability Study Late Time Point Test Notification notifies you that a test is overdue. The notification considers the required grace period, and uses the OPM Quality Stability Study Testing master workflow to raise a separate event to indicate the test is late.
oracle.apps.gmd.qm.ss.tplt
TIMEPOINT_ID
Subscriber Workflow:
OPM Quality Stability Study Late Time Point Test
Oracle Approval Management Transaction Name:
GMDQM_STABILITY_LATETEST
Process Quality Stability Study Testing Timepoint Late
| Parameter | Description |
|---|---|
| OWNER_ORGN_CODE | Lab Organization Code |
| ITEM_NO | Item |
Request Notification
Late Time Point Testing of a Stability Study
You have been designated to pull the stability study variant time point testing as described below.
Organization: &ORG
Study: &STUDY
Study Description: &STUDY_DESC
Status: &STATUS
Study Date: &STUDY_DATE
Time Name: &TIME_NAME
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Item Description: &ITEM_DESC
Variant No: &VARIANT_NO
Storage Spec: &STORAGE_SPEC
Storage Spec Version: &STGE_SPEC_VER
Sample Qty: &SAMPLE_QTY
Resource: &RESOURCE
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Sample Number: &SAMPLE_NO
Sample Qty: &SAMPLE_QTY
Click Forms to launch the MultiRow Samples window. After saving the result you will come back to the Notification screen where you may click the OK button to respond to the notice.
The Quality UOM Conversion Notification notifies the workflow recipient of a recommended UOM conversion. One workflow notification is issued for each recommended UOM conversion listed on the Change Disposition window UOM Conversions tab. Click the link to the Oracle Inventory Lot Inter-class Unit of Measure Conversion window. The item, lot, and conversion information displays on that window. The window fields are all protected from update. A lot number must be entered if it is not available for the sample group.
You can keep the workflow notification open, reenter the item lot conversion link, and enter another lot number for the same conversion. When the conversions are established for all the desired item lots, then you can close out the notification.
The basic process for initiating the OPM Quality UOM Conversion workflow is:
Record samples and results for all tests saved on the specification created in setting up for the unit of measure conversion process. Refer to the "Using Lot UOM Conversions Based on Quality Results" topic for a complete discussion of this process.
Change the sample group disposition to Accept, Accept with Variance, or Reject.
An event for change status is raised.
Workflow sends notification to contact person as defined in AME, along with the UOM conversion event information.
Select the UOM Conversion tab on the Change Disposition window. The application enters all data displayed on this tab:
If at least one test on the specification has the Calculate UOM indicator selected
If the Change Disposition To field displays Accept, Accept with Variance, or Reject
If the sample group source is Inventory or Supplier
Data appears on this tab even when test results are out-of-specification.
If a lot UOM conversion already exists for the lot, then the current conversion between the UOM class of the base UOM and the UOM class of the To UOM is displayed below the new proposed conversion.
Select the Recommend indicator next to the desired UOM conversions. If this indicator is not selected, then the proposed conversion is not used in inventory.
Click OK to change the disposition of the sample group.
Subscriber for the event initiates the workflow.
Provide an eSignature for the disposition change if one is required.
Receive the OPM Quality UOM Conversion workflow notification.
Click the UOM Conversion link to the Oracle Inventory Lot Inter-class Unit of Measure Conversion window, and save to create the conversions.
Close the workflow notification.
This business event is triggered from the Change Disposition window.
oracle.apps.gmd.qm.uomconv.csts
EVENT_SPEC_DISP_ID
Subscriber Workflow:
Quality UOM Conversion
Oracle Approval Management Transaction Name:
Process Quality UOM Conversion
| Parameter | Description |
|---|---|
| ORGN_CODE | Organization |
You receive a notification about the UOM conversion. The body of that request is:
There has been a recommendation for Item Lot UOM Conversion.
Source: &SOURCE
Samples Taken: &SAMPLES_TAKEN
Samples Group Disposition: &SAMPLE_GRP_DISP
Item Number: &ITEM_NO
Item Revision: &ITEM_REVISION
Parent Lot: &PARENT_LOT_NUMBER
Lot Number: &LOT_NO
Organization: &ORG
Subinventory: &SUBINVENTORY
Locator: &LOCATOR
Supplier: &SUPPLIER
Supplier Lot: &SUPPLIER_LOT
PO Number: &PO_NUMBER
PO Line Num: &PO_LINE_NO
Receipt Num: &RECEIPT_NO
Receipt Line No: &RECEIPT_LINE_NO
Spec: &SPEC
Spec Version: &SPEC_VERSION
Test Name: &TEST_NAME
Conversion: &CONVERSION
Please open the Lot Inter-class Unit of Measure Conversion window Link in order to approve the Lot UOM Conversions, form Link: ICCNVED
Your responsibility must have access to the Lot Inter-class Unit of Measure Conversion window in order to approve the Lot UOM Conversions.
The Oracle Approval Management framework defines the approval matrix and approval groups. AME lets you define transaction and associate attributes that control the approvers of the transaction. It also lets you define approval groups based on FND users and let these groups be associated to rules. Approval Management production rules represent business rules that determine who must approve a transaction.
The process flow for creating an e-record and e-signature approval matrix is accomplished through the AME responsibility available in Oracle Applications.
Refer to the Oracle Approvals Management Implementation Guide and the Oracle E-Records Implementation Guide for details.
Each business event is associated with a set of control parameter lists. The business event is the transaction in AME while the control parameter list becomes the list of attributes. In the case of the test business event, the attributes are Lab, Item, Test Class, Test, and Test Method.
A transaction type is defined in AME, and corresponds to an Oracle workflow business event. The name of the transaction type is the same as the name of the business event. Attributes are defined for the transaction along with the associated SQL statement, which derives the values of the attributes for a given transaction.
You define approval groups that are associated to the rule in AME.
Define conditions in AME using the attributes. For example, the Lab is OPME.
Define rules in AME using the conditions. For example, the Rule for Plant Code is used with a specific approval list. If the plant code is OPME, then the approval list defined in AME is used.