Search Results get_step_details

Overview

GMO_CBR_GRP is a Process Manufacturing (OPM) package body owned by APPS and classified under the GRP (group) API category. Its central purpose is the administration and execution of CBR — the Content-Based Routing / Business Event subscription layer used by Process Manufacturing to trigger business logic in response to workflow (Workflow Business Events, or WF_EVENT) activity. The package header comment identifies the source file as GMOGCBRB.pls, version 120.21, dated 2006/09/22, indicating a long-standing component of the E-Business Suite Process Manufacturing stack that predates and persists through releases 12.1.1 and 12.2.2.

The package serves two related functions. First, it enables and manages the event subscriptions that connect Oracle Workflow events to Process Manufacturing rule functions such as GMO_CBR_GRP.PROCESS_EVENT and GMO_CBR_GRP.PROCESS_INSTANCE_INSTR_SET. Second, it processes those events at runtime, interpreting batch and material notifications supplied through XML payloads and persisting the resulting routing decisions. In practice, GMO_CBR_GRP is the plumbing that allows batch progression, dispensing, and quality events to drive automated Process Manufacturing responses.

Key Procedures and Functions

• ENABLE_CBR — Enables CBR processing by querying WF_EVENT_SUBSCRIPTIONS for existing GMO subscriptions and activating the associated event definitions, using local cursors against WF_EVENTS_VL and WF_EVENT_SUBSCRIPTIONS.
• UPDATE_EVENT — Updates an existing Workflow event or subscription record, typically to reflect a change in rule function, status, or parameters.
• PROCESS_EVENT — The principal runtime entry point that receives a business event and evaluates the associated rule logic.
• INSERT_EVENT — Inserts a new Workflow event definition or event subscription row used by the CBR mechanism.
• CBR_PREPROCESS — Performs preparatory validation or data staging before an event is fully processed.
• INSERT_BATH_EVENTS — Raises or records batch-level events (the name reflects the legacy spelling of "batch") for consumption by the CBR subscription framework.
• PROCESS_INSTANCE_INSTR_SET — A rule function referenced explicitly in the subscription cursor; it processes instruction sets for a batch or material instance, driven by incoming event payloads.
• DELETE_PROGRESSION_ROW — Removes a row from the batch progression table, supporting rollback or correction of progression state.

The subscription cursors reveal the operating contract: subscriptions filtering on GMO_CBR_GRP.PROCESS_EVENT or GMO_CBR_GRP.PROCESS_INSTANCE_INSTR_SET, and Process Manufacturing subscriptions owned by product teams and identified through EDR_PSIG_RULE.PSIG_RULE with owner tags other than 'GMO'.

Tables Accessed

The package touches Workflow infrastructure and Process Manufacturing execution data. WF_EVENT_T and WF_EVENT_SUBSCRIPTIONS provide event definitions and subscription registrations. GMO_BATCH_PROGRESSION and its sequence GMO_BATCH_PROGRESSION_S track batch progression state; DELETE_PROGRESSION_ROW operates directly on the former. GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, and GME_BATCH_STEP_RESOURCES supply batch structure and routing detail. GME_MATERIAL_DETAILS, GMO_MATERIAL_DISPENSES, and GMO_MATERIAL_UNDISPENSES capture material consumption and its reversal. GMD_SAMPLES and QA_RESULTS relate quality sampling and results to the event stream. GMO_CBR_XML holds the XML payloads that carry event content, and GMO_LABEL_HISTORY stores label printing history associated with batch events.

Usage Notes

GMO_CBR_GRP is not invoked directly by end users. ENABLE_CBR is typically run once during setup or upgrade by an administrator or a concurrent program to register the Process Manufacturing event subscriptions. Once enabled, PROCESS_EVENT and PROCESS_INSTANCE_INSTR_SET are called by the Oracle Workflow Business Event System whenever a matching event is raised; the package is therefore referenced by zero other PL/SQL packages, since the caller is the event framework rather than application code.

For Oracle EBS 12.1.1 and 12.2.2, the package remains in the APPS schema and depends on standard public synonyms for the OPM tables. Customizations should avoid modifying the package body, since it is a seeded object; extensions belong in separate event subscriptions or rule functions. Support maintenance should focus on ensuring WF_EVENT_SUBSCRIPTIONS records are ENABLED and that the GMO_CBR_XML payload structures remain synchronized with the Process Manufacturing schema.