Search Results get_line_type_desc

Overview

GMD_ERES_UTILS is a utility package owned by the APPS schema in Oracle E-Business Suite, classified under the Process Manufacturing (GMD) product family. Its name reflects its association with ERES (Electronic Records and Electronic Signatures) functionality in an FDA-regulated environment, though the procedures it exposes are general-purpose lookup and status-transition helpers for process manufacturing entities. The package provides a centralized library of small, single-responsibility routines that retrieve descriptive attributes and version identifiers for formulations, recipes, routings, and operations, and that perform controlled status changes on those entities with optional signature context.

The package is documented as containing 43 procedures and functions, of which twenty are enumerated in the ETRM metadata. It is referenced by six other packages, indicating that it functions as a shared dependency layer rather than as an entry point invoked directly by end users.

Key Procedures and Functions

The documented routines fall into three functional clusters.

• Identifier and version lookups: GET_OPERATION_NO, GET_OPERATION_VERS, GET_FORMULA_NO, GET_FORMULA_VERS, GET_RECIPE_NO, GET_RECIPE_VERSION, GET_ROUTING_NO, and GET_ROUTING_VERS. Each accepts a surrogate primary key and returns the human-readable entity number or version. These allow callers to resolve internal IDs into display values without embedding joins against the master tables.
• Descriptive lookups: GET_FORMULA_DESC, GET_LINE_TYPE_DESC, GET_STATUS_MEANING, GET_PROCESS_QTY_UM, GET_ACTIVITY_DESC, and GET_RESOURCE_DESC. These return descriptive text or unit-of-measure codes for a formulation line, a status code, an operation, an activity, or a resource. GET_PROC_PARAM_DESC and GET_PROC_PARAM_UNITS are the process-parameter variants, taking a parameter identifier and returning its description or its associated units of measure respectively. GET_PROC_PARAM_DESC is the object most commonly targeted by searches against this package.
• Status transitions: SET_FORMULA_STATUS, SET_OPERATION_STATUS, SET_ROUTING_STATUS, and SET_RECIPE_STATUS. These change an entity from a source status to a target status and accept an optional signature status argument, which is the ERES integration point — the signature status records the electronic signature context accompanying a regulated state change.

All output parameters are declared with NOCOPY, a PL/SQL compiler hint that passes OUT parameters by reference rather than by value, avoiding a copy on return. This is consistent with the package's role as a high-frequency utility invoked repeatedly from loops.

Tables Accessed

The package reads and writes a defined set of process manufacturing base tables through APPS synonyms. Master and header data are drawn from FM_FORM_MST and FM_FORM_MST_B (formulation headers), GMD_OPERATIONS and GMD_OPERATIONS_B (operations), GMD_ROUTINGS_B (routings), and GMD_RECIPES_B (recipes). Detail lines are resolved through FM_MATL_DTL. Resource and activity descriptions come from CR_RSRC_MST and FM_ACTV_MST respectively.

Governance and control tables include GMD_FORMULATION_SPECS, GMD_FORMULA_SUBSTITUTION, GMD_ITEM_SUBSTITUTION_HDR and GMD_ITEM_SUBSTITUTION_HDR_B, GMD_RECIPE_GENERATION, and GMD_RECIPE_VALIDITY_RULES. The status-setting procedures necessarily update the status columns of the formula, operation, routing, and recipe header tables, while the specification and validity rules tables support the ERES aspects of the package — documenting which specifications and substitution rules apply when a regulated status change or signature is recorded.

Usage Notes

GMD_ERES_UTILS is a server-side utility layer. It is not exposed as a standalone concurrent program or form; instead it is invoked from Oracle Forms event logic, from other PL/SQL packages (six documented dependents), and from custom extensions that need to resolve process manufacturing IDs, descriptions, or units without duplicating lookup SQL. The status procedures are typically called during approval, release, or signature workflows, where the optional signature status parameter carries the ERES context forward to the audit tables.

Because the package performs DML in its SET_* procedures, callers should treat those routines as transactional participants and manage commit and rollback boundaries explicitly. Lookups should be invoked against the appropriate organization context, since formulation and recipe visibility is often organization-dependent.