Search Results gmd_eres_post_operation

Overview

GMD_ERES_POST_OPERATION is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Process Manufacturing (GMD) product family. The name and API classification indicate that it serves as a post-operation status management utility within the Oracle Process Manufacturing and Enterprise Resource Planning integration layer, specifically supporting e-records and electronic signature (ERES) related processing that occurs after a primary business operation completes. In regulated manufacturing environments, operations such as formula approval, recipe release, routing changes, and specification updates must be tracked and their lifecycle status transitions recorded in a controlled manner. This package provides the centralized, programmatic mechanism for effecting those status changes against the GMD_STATUS repository.

The package is documented as VALID with both a package specification and package body present in the APPS schema. It depends on the SYS.STANDARD package only, confirming that the documented dependency footprint is minimal and that the package relies primarily on internal object references rather than a broad chain of other application APIs. It is not referenced by any other documented packages, which suggests it functions as a terminal or leaf-level utility invoked directly by forms, concurrent programs, or external integration code rather than being nested inside other PL/SQL APIs.

Key Procedures and Functions

The documented package exposes eight status-setting procedures. Each is named for the business entity whose lifecycle status it manages:

• SET_FORMULA_STATUS — Updates the status of a formula record, governing whether a formula is active, pending, or otherwise unavailable for use in downstream production processes.
• SET_FORMULATION_SPEC_STATUS — Manages the status of the specification associated with a formulation, controlling the validity of specification data linked to a formula.
• SET_OPERATION_STATUS — Sets the status of a manufacturing operation definition, determining whether the operation may be used in routing and production execution.
• SET_ROUTING_STATUS — Controls the status of a routing, affecting whether the routing is available for work order and batch generation.
• SET_RECIPE_STATUS — Updates recipe status, governing the usability of the recipe in the production environment.
• SET_VALIDITY_STATUS — Manages validity status, typically relating to the effective-date or approval validity of a process entity.
• SET_AUTO_RECIPE_STATUS — Sets the status of automatically generated recipes, distinguishing system-created recipes from manually authored ones.
• SET_SUBSTITUTION_STATUS — Controls the status of ingredient or item substitutions defined against a formula or recipe.

All eight procedures share a common design intent: they centralize the write logic that transitions a GMD entity between defined status values, ensuring consistency and auditability.

Tables Accessed

The package references a single documented table via APPS synonym: GMD_STATUS. This table is the central status repository for Process Manufacturing entities. Each of the eight procedures writes to GMD_STATUS, recording the new status value against the appropriate entity identifier and entity type. Because the package reads and writes this table directly, any status change executed through these procedures becomes immediately visible to forms and reports that query GMD_STATUS. The absence of additional documented table dependencies indicates that the package performs a focused, single-table update role rather than orchestrating multi-table transactions.

Usage Notes

GMD_ERES_POST_OPERATION is typically invoked in one of three ways. First, from Oracle Forms user interfaces, where a user action such as approving a formula or releasing a recipe triggers the corresponding status-setting procedure. Second, from concurrent programs or batch processes that perform bulk status transitions across many entities. Third, from custom PL/SQL code or integration interfaces that need to programmatically change the status of a GMD entity while preserving the same validation and update semantics used by the standard application.

Because the package is not referenced by any other documented package, callers must invoke it directly; there is no wrapper API that routes through it. When extending or integrating with this package in Oracle EBS 12.1.1 or 12.2.2, developers should treat the SET_* procedures as the supported entry points for status changes and avoid direct DML against GMD_STATUS, so that any auditing or ERES electronic-signature hooks associated with the package remain effective.