Search Results get_activity_desc
Overview
APPS.GMD_ERES_UTILS is a utility package body in the Oracle E-Business Suite Process Manufacturing (Oracle Process Manufacturing / OPM) schema. Its principal responsibility is to provide reusable, low-level lookup and status-update services for formulation, recipe, routing, and operation data used by Oracle E-Records and electronic signature (ERES) processing. The package was evidently designed to support ERES-related business flows, where an electronic record must capture human-readable descriptions of the process entities (formulas, recipes, routings, operations, resources, and parameters) that were created, modified, or approved. Rather than embedding individual SELECT statements and status transitions inside forms or workflow code, the application centralizes them in GMD_ERES_UTILS.
The package also contains an internal diagnostic helper, SET_DEBUG_FLAG, which inspects FND_LOG runtime levels to determine whether debug logging is active. The package header timestamp (120.11.12020000.2, dated 2012/07/17) indicates it is maintained as a shipped OPM/ERES file and is compatible with both the 12.1.1 and 12.2.2 release levels of EBS.
Key Procedures and Functions
The documented interface exposes over forty procedures and functions, which fall into several functional groups:
- Formula lookups: GET_FORMULA_NO, GET_FORMULA_VERS, and GET_FORMULA_DESC return the formula number, version, and description for a given formula identifier, allowing ERES records to reference formulas in business terms rather than internal IDs.
- Recipe and routing lookups: GET_RECIPE_NO, GET_RECIPE_VERSION, GET_ROUTING_NO, and GET_ROUTING_VERS perform the equivalent retrieval for recipes and routings.
- Operation lookups: GET_OPERATION_NO and GET_OPERATION_VERS retrieve the operation number and version for an operation ID from GMD_OPERATIONS.
- Descriptive attribute lookups: GET_LINE_TYPE_DESC, GET_STATUS_MEANING, GET_PROCESS_QTY_UM, GET_ACTIVITY_DESC, GET_RESOURCE_DESC, GET_PROC_PARAM_DESC, and GET_PROC_PARAM_UNITS resolve codes into user-facing descriptions, units of measure, or status meanings. GET_ACTIVITY_DESC, the object of the user search, returns the descriptive text for an activity, drawing on FM_ACTV_MST.
- Status update procedures: SET_FORMULA_STATUS, SET_OPERATION_STATUS, SET_ROUTING_STATUS, and SET_RECIPE_STATUS change the status of the respective entities, supporting approval, release, or obsoletion steps within ERES-controlled workflows.
Each routine is a thin, single-purpose wrapper. The documented source shows a typical pattern: declare a cursor against the base table, fetch into an OUT NOCOPY parameter, and close. The NOCOPY hint indicates the intent to avoid parameter copying overhead for large values.
Tables Accessed
The package reads and writes the following OPM base tables through APPS synonyms:
- Formula and activity: FM_FORM_MST, FM_FORM_MST_B, FM_ACTV_MST, FM_MATL_DTL, GMD_FORMULATION_SPECS, GMD_FORMULA_SUBSTITUTION.
- Recipe and item substitution: GMD_RECIPES_B, GMD_RECIPE_GENERATION, GMD_RECIPE_VALIDITY_RULES, GMD_ITEM_SUBSTITUTION_HDR, GMD_ITEM_SUBSTITUTION_HDR_B.
- Routing and operations: GMD_ROUTINGS_B, GMD_OPERATIONS, GMD_OPERATIONS_B.
- Resource master: CR_RSRC_MST.
The lookups drive descriptive translation; the _B tables (base, language-independent) and master tables (FM_FORM_MST, FM_ACTV_MST, CR_RSRC_MST) supply the human-readable descriptions. The SET_* procedures update status columns on the formula, recipe, routing, and operation tables.
Usage Notes
GMD_ERES_UTILS is referenced by six other packages in the OPM schema, making it a shared utility layer rather than an entry-point API. It is normally invoked from process manufacturing forms (formula, recipe, routing, and operation maintenance), from ERES electronic signature and electronic record routines, and from concurrent programs that need to translate internal IDs into descriptions when building audit output. Customizations should call the documented procedures rather than issuing direct SQL against the underlying tables to preserve the descriptive logic. Because the package only fetches and updates narrow columns, it should be treated as a helper API; callers remain responsible for transaction control, validation, and any additional business rules in the ERES flow. The SET_DEBUG_FLAG helper can be enabled through FND logging to diagnose issues without changing the package.