Search Results set_formula_status

Overview

GMD_ERES_POST_OPERATION is a PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite Process Manufacturing (OPM) product family. Its API classification is recorded as OTHER, indicating it is not one of the primary public interfaces of the OPM modules but rather an internal hook consumed by the electronic records and signatures (ERES) approval framework. The package functions as a post-operation callback for the Oracle Process Manufacturing approval workflows, providing the mechanism by which workflow-driven signature events are translated into status transitions on the underlying process entities.

In regulated manufacturing environments, a document such as a formula, recipe, routing, or operation cannot simply be promoted from one lifecycle status to another without an authenticated electronic signature. The ERES subsystem captures that signature through the signature page flow, and once the signature is established the workflow requires a programmatic point at which the target entity status is actually updated. GMD_ERES_POST_OPERATION supplies that point. Each procedure in the package reads the current signature status from the ERES session context and delegates the actual status update to the shared utility package GMD_ERES_UTILS, which performs the validated transition against the process entity.

Key Procedures and Functions

The package body exposes eight documented procedures, each handling a distinct process manufacturing entity type:

• SET_FORMULA_STATUS — sets the formula status to a target status based on the outcome of the signature, as described in the header commentary preserved from the source file.
• SET_FORMULATION_SPEC_STATUS — sets the formulation specification status according to the signature status. This is the procedure matched by the user search term "set_formulation_spec_status".
• SET_OPERATION_STATUS — applies a signature-driven status transition to a routing operation.
• SET_ROUTING_STATUS — applies a signature-driven status transition to a routing header.
• SET_RECIPE_STATUS — applies a signature-driven status transition to a recipe.
• SET_VALIDITY_STATUS — applies a signature-driven status transition to a validity rule.
• SET_AUTO_RECIPE_STATUS — applies a signature-driven status transition to an automatic recipe generation record.
• SET_SUBSTITUTION_STATUS — applies a signature-driven status transition to a substitution record.

Although the procedures are individually named, they share an identical design pattern: each accepts the entity identifier together with a from-status and a to-status, retrieves the signature status from the signature page flow, and hands the request to the corresponding routine in GMD_ERES_UTILS. The header of SET_FORMULA_STATUS, for example, documents a calling convention of the form set_formula_status (100, 400, 700), and the same convention is documented for SET_FORMULATION_SPEC_STATUS. None of the procedures performs the status mutation itself; the package is a thin adapter layer.

Tables Accessed

The only directly documented table reference is GMD_STATUS, accessed through an APPS synonym. GMD_STATUS is the OPM status code repository, holding the valid lifecycle statuses and their associated status codes. The package declares local variables typed against GMD_STATUS.STATUS_CODE, notably placeholders for pending and rework statuses, which are used to interpret the direction of the transition requested by the workflow. Because the actual update is delegated to GMD_ERES_UTILS, any inserts or updates against the entity tables themselves occur outside this package body.

Usage Notes

The package is invoked as a post-operation API from the approval workflow, as stated explicitly in the source commentary. It is not intended for direct invocation by end users, forms, or concurrent programs; no forms or concurrent program registrations are associated with it, and the ETRM metadata records zero packages referencing it. Calls originate from the workflow engine once an electronic signature has been captured, at which point the relevant procedure is selected according to the entity being approved. Because behavior depends on the signature status held in EDR_PSIG_PAGE_FLOW and on logic inside GMD_ERES_UTILS, the package is sensitive to the ERES configuration and the status-code setup in GMD_STATUS. It is available in both Oracle EBS 12.1.1 and 12.2.2, with the source header indicating the last shipped revision of the file. Customizations should not extend this package; the supported extension point is the workflow process definition itself.