Results for “init_wf”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.GMI_WF_LOT_RETEST package body is an Oracle Process Manufacturing (OPM) component that orchestrates the Lot Retest workflow within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to initiate and manage a Workflow (WF) process that notifies the appropriate personnel when a lot stored in inventory is approaching its retest date. This allows quality and warehouse organizations to schedule and execute retesting activities before the retest deadline elapses, preserving material quality and regulatory compliance.

The package is closely associated with the OPM Quality module (GMI) and the Oracle Workflow engine. It performs two essential duties: launching a retest workflow process (via INIT_WF) and validating whether a retest is warranted (via VERIFY_RETEST). The workflow item type used is GMWLOTEX, and the package deliberately prefixes workflow item keys with the string "RT" to distinguish the retest process from other workflow processes that share the same item type. The package header revision (115.4, dated 2003/10/16) reflects a long-standing, stable code lineage carried forward into the EBS 12.x releases.

Key Procedures and Functions

The package exposes two documented program units:

  • INIT_WF — Initializes and launches the lot retest workflow. It is described as being "called via trigger on ic_lots_mst," meaning it fires in response to an insert or update on the lot master record (typically when a retest date is set or modified). The procedure constructs the workflow item key, determines the notification lead time, and starts the LOT_RETEST_PROC workflow process. Several local variables indicate its behavior: it fetches the retest notification interval from a control table (GMWLOTRT_CTL), defaulting to 7 days if no configured value is found; it forces the workflow to run in the background engine (using the constant threshold value -1) to avoid SAVEPOINT/ROLLBACK errors documented in the Workflow FAQ; and it resolves item, performer, and role information needed to route the notification. The procedure derives the retest notification date and workflow start date before handing the process to the workflow engine.
  • VERIFY_RETEST — Evaluates whether a lot requires retesting. It is the validation counterpart used by the retest workflow to confirm eligibility conditions before progressing the process or generating notifications.

Tables Accessed

The package reads and references the following tables (through APPS synonyms):

  • IC_LOTS_MST — The OPM lot master. Supplies lot_id, lot_no, sublot_no, retest_date, item_id, and created_by, and is the source table for the triggering event.
  • IC_ITEM_MST — Item master, used to retrieve item number, description, unit-of-measure (item_um, item_um2), and dual-UOM indicator for the notification content.
  • FND_USER — Resolves the performer's user name and display description for workflow routing/notification.
  • SY_WF_ITEM_ROLES — Provides the retest role name and display name used to assign the workflow notification recipient.
  • WF_ITEMS — Supplies the workflow item type (GMWLOTEX) and item key metadata.
  • IC_LOCT_INV — Location inventory context, referenced for lot/location qualification.
  • DUAL — Used for single-row SQL evaluations.

Usage Notes

GMI_WF_LOT_RETEST is principally invoked automatically by a database trigger on IC_LOTS_MST; users generally do not call it directly. When a retest date is entered or changed, the trigger calls INIT_WF, which launches the background workflow LOT_RETEST_PROC for item type GMWLOTEX. The workflow engine then issues notifications based on the interval configured in GMWLOTRT_CTL (default seven days). Because the process runs in the background engine, administrators must ensure the Workflow background engine is scheduled and active. A related package references this one, indicating integration within the broader OPM Quality workflow framework. Implementers customizing retest behavior should modify control-table values rather than package logic, as the body is an Oracle-shipped, unsupported-to-modify object.