Search Results get_item_num

Overview

APPS.GME_ERES_PKG is a Process Manufacturing (OPM) PL/SQL package body that supports Electronic Records and Electronic Signatures (ERES) processing within Oracle E-Business Suite 12.1.1 and 12.2.2. ERES functionality is used in regulated manufacturing environments (for example, FDA 21 CFR Part 11 compliance) where changes to production records must be captured, routed for approval, and signed electronically. The package acts as the backend engine that stages ERES events generated from OPM forms and converts them into structured XML payloads suitable for Oracle Workflow event processing. The package header comment specifies that its procedures insert ERES events into the GME_ERES_GTMP staging table for ERES processing initiated from a form. This package therefore serves as the bridge between form-level user actions (such as adding, removing, or updating resources on a batch) and the workflow-driven signature and audit trail infrastructure. Its classification as an "OTHER" API indicates it is an internal, non-public API intended for use within the OPM ERES framework rather than for general customer extension.

Key Procedures and Functions

The ETRM metadata documents four procedures and functions within this package body:

• INSERT_EVENT — The central staging procedure. It inserts an ERES event into the GME_ERES_GTMP table for subsequent ERES processing. The source excerpt shows it accepts identifiers for the event name, event key, user key label and value, a post-operation API, and parent event context, and returns a status value. It performs duplicate detection against GME_ERES_GTMP, and contains special handling for resource-related events (resource added, removed, and updated), including deletion of superseded "resource added" rows when a resource is removed.
• GET_ITEM_NUMBER — Retrieves the item number associated with an ERES event context. This is the object matching the user's search term "get_item_num." It is used to resolve the inventory item identity that an ERES event pertains to, so the event payload and approval routing can reference the correct item.
• GET_OPRN_NO — Retrieves the operation number for the manufacturing context associated with an ERES event. It supports OPM routing and batch step identification, referencing the GMD_OPERATIONS_B table.
• GET_EVENT_XML — Generates the XML representation of an ERES event. This XML is the payload delivered to Oracle Workflow via the event subscription framework, enabling notification, approval, and signature capture.

Tables Accessed

• GME_ERES_GTMP — The ERES global temporary/staging table. INSERT_EVENT writes event rows here and queries it for duplicate detection and resource event reconciliation.
• GMD_OPERATIONS_B — The OPM operations base table, used by GET_OPRN_NO to resolve operation numbers for event payloads.
• WF_EVENT_SUBSCRIPTIONS — The Oracle Workflow event subscription table, consulted to determine how raised ERES events are routed to workflow processes.

Usage Notes

GME_ERES_PKG is invoked internally by OPM ERES-enabled forms (such as resource, activity, and batch step maintenance forms) whenever a regulated change occurs. The form calls INSERT_EVENT, which stages the event; GET_ITEM_NUMBER, GET_OPRN_NO, and GET_EVENT_XML are then used to enrich and serialize the event before it is raised to Oracle Workflow. The package is referenced by one other package, indicating it is a dependency within the OPM ERES stack rather than a standalone entry point. Customizations should avoid direct calls to these procedures unless replicating the standard staging pattern, as the signature semantics and GME_ERES_GTMP lifecycle are tightly coupled to ERES workflow processing.