Search Results get_oprn_no




Overview
Explore in AI Chat

Overview

APPS.GME_ERES_PKG is a Process Manufacturing (OPM) PL/SQL package that supports the E-Records and E-Signatures (ERES) framework in Oracle E-Business Suite. ERES provides electronically signed, auditable event records for regulated manufacturing environments, particularly those subject to 21 CFR Part 11 requirements. The package acts as the integration layer between discrete business events occurring in production and quality processes and the electronic record store that documents them.

Its primary role is event registration and event data retrieval. When a qualifying transaction occurs — a batch step completion, a resource consumption entry, or another signable activity — the package constructs the corresponding electronic record, associates it with its parent context, and optionally dispatches a post-operation API call. The package additionally exposes helper functions that resolve raw identifiers into human-readable values for inclusion in the event payload, and a CLOB-returning function that assembles the full XML representation of a stored event. The GET_EVENT_XML function, which the searching user referenced, is the principal interface for retrieving that serialized event record.

The header comment indicates the package has been stable since a 2005 revision, which is consistent with its role as an established ERES infrastructure component carried forward into 12.1.1 and 12.2.2.

Key Procedures and Functions

  • INSERT_EVENT — The core registration procedure. It creates an electronic event record keyed by event name and event key, captures a user-defined key label and value, optionally names a post-operation API to invoke after insertion, and links the record to a parent event through the parent event name, parent event key, and parent e-record identifier. It returns a status indicator to the caller.
  • GET_ITEM_NUMBER — A lookup function that resolves a combination of organization identifier and inventory item identifier into the corresponding item number string. This supports readable rendering of event details where only internal IDs are otherwise available.
  • GET_OPRN_NO — A lookup function that returns the operation number associated with a given operation identifier, used to populate event content with the recognizable routing operation reference.
  • GET_EVENT_XML — Accepts an event name and event key and returns the assembled event record as a CLOB containing XML. This is the primary retrieval interface for consumers that need the structured, serialized form of an electronic record for display, export, or downstream audit processing.

Tables Accessed

  • GME_ERES_GTMP — The ERES event staging/template table. This is the primary storage underlying event creation and XML assembly, holding the event attributes written by INSERT_EVENT and read by GET_EVENT_XML.
  • GMD_OPERATIONS_B — The operations base table, read to resolve operation identifiers into operation numbers for GET_OPRN_NO.
  • WF_EVENT_SUBSCRIPTIONS — The Oracle Workflow event subscription table, consulted in connection with event dispatch and subscription handling during event registration.

Usage Notes

GME_ERES_PKG is an infrastructure package rather than an end-user entry point. It is normally invoked indirectly by OPM ERES-enabled forms and by the business logic that detects signable events, or directly by custom extensions that need to register a manufacturing event or retrieve its XML. The referenced-by metadata confirms that at least one other package in the APPS schema depends on it, so changes should be evaluated against dependent callers.

Because GET_EVENT_XML returns a CLOB, calling code should manage temporary LOB resources appropriately. The package is documented in the ETRM repository for both 12.1.1 and 12.2.2 with an API classification of OTHER, indicating it is not a formally published public API but is nonetheless available to APPS-schema code. Customizations should avoid altering the signature or behavior of INSERT_EVENT and GET_EVENT_XML, since ERES audit records depend on consistent event construction and serialization.