Search Results qa_ss_notify_workflow_s

Overview

QA_INSPECTION_WF is a workflow integration package in the Oracle E-Business Suite Quality Management module. Its business purpose is to bridge the Oracle Quality inspection planning and skip-lot functionality to the Oracle Workflow notification engine. Specifically, the package raises workflow events when the conditions governing an inspection plan change, so that the appropriate supervisory personnel receive notification and can act on the change. Two categories of inspection-related change are supported: frequency changes within a skip-lot inspection environment, and reduced inspection events. The package does not perform inspection calculations itself; rather, it packages context data — process codes, descriptions, inspection plan identifiers, frequency values, criteria text, and recipient roles — into a workflow parameter list and raises a named business event through the Workflow API. The item type and process name are hard-coded as QASKPFRQ, identifying this as the skip-lot frequency change workflow used by Oracle Quality. The package body header indicates a last source revision dated November 2002, making it a legacy component that has been carried forward into the 12.1.1 and 12.2.2 application releases with minimal change.

Key Procedures and Functions

The package exposes two documented public functions, both of which return a NUMBER. That return value is the workflow item key generated for the correlated workflow instance.

• RAISE_FREQUENCY_CHANGE_EVENT — Raises the event named "QA SKIPLOT FREQUENCY CHANGE" against item type QASKPFRQ. It accepts caller-supplied context describing the process code, description, inspection plan, the previous frequency, the new frequency, the criteria that triggered the change, and the role name of the supervisor to be notified. Internally it obtains a unique item key from the sequence QA_SS_NOTIFY_WORKFLOW_S, appends each value to a Workflow parameter list using WF_EVENT.ADDPARAMETERTOLIST, then invokes WF_EVENT.RAISE. The function returns the item key to the caller.
• RAISE_REDUCED_INSPECTION_EVENT — Raises a workflow event notifying recipients that a lot has been moved to reduced inspection. Its documented inputs include lot information, the inspection date, and inspection plan context. As with the frequency change function, it builds a parameter list and raises the corresponding event, returning the workflow item key.

No private helper procedures are documented in the available metadata; all logic is contained within the two public functions and the package-wide declarations.

Tables Accessed

The documented object references are limited and are exposed through APPS synonyms.

• QA_SS_NOTIFY_WORKFLOW_S — An Oracle sequence, not a table, used to generate unique numeric workflow item keys via SELECT ... FROM DUAL. It ensures each raised notification event has a distinct correlation key.
• WF_PARAMETER_LIST_T — The Oracle Workflow PL/SQL collection type used to accumulate name/value pairs that are passed into WF_EVENT.RAISE. It is not a physical table but a workflow infrastructure type.
• DUAL — Used solely to fetch the next sequence value.

Notably, the documented package sample reads no Quality inspection tables directly; inspection context is supplied by the calling program, and persistence of the resulting notification state is handled by the Oracle Workflow runtime tables.

Usage Notes

QA_INSPECTION_WF is an internal integration point rather than an end-user API. It is most commonly invoked from Oracle Quality skip-lot processing logic — for example, when an inspection plan's sampling frequency is adjusted automatically by skip-lot rules, or when a lot is downgraded to reduced inspection — to generate a workflow notification to the responsible supervisor or quality role. The ETRM metadata records that two other packages reference QA_INSPECTION_WF, indicating it is called programmatically rather than from a form or concurrent program directly. Customers typically extend or subscribe to the raised events (QASKPFRQ) through Oracle Workflow Builder to route notifications, rather than calling the package's functions themselves. Because the return value is the workflow item key, callers can use it to reconcile the generated notification with the originating inspection transaction. Any customization should preserve the expected parameter names, since the workflow process definition depends on them.