Search Results get_proc_param_units

Overview

GMD_RECIPE_FETCH_PUB is a public PL/SQL package body owned by the APPS schema that serves as the primary retrieval API for Oracle Process Manufacturing (OPM) recipe, routing, and formula data within Oracle E-Business Suite 12.1.1 and 12.2.2. Its central business function is to expose validated, denormalized access to recipe structure — including routing steps, operation activities, operation resources, process parameters, step materials, and process loss — to calling applications without requiring those callers to navigate the underlying base tables directly. Because the package is classified as a PUB API and is referenced by fifteen other database objects, it functions as a stable integration contract for recipe data consumption across the OPM module boundary. The package status is VALID, indicating it is compiled and operational in the documented environment.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions, each targeting a discrete slice of recipe metadata:

• GET_VALIDITY_RULES — retrieves the validity rule definitions that govern when a recipe is effective.
• GET_ROUTING_ID — resolves and returns the routing identifier associated with a given recipe context.
• GET_ROUT_HDR — fetches routing header information.
• GET_FORMULA_ID — resolves and returns the formula identifier linked to a recipe.
• GET_ROUT_MATERIAL — retrieves material assignments associated with routing detail.
• GET_PROCESS_LOSS — returns process loss percentages or quantities defined on the recipe.
• GET_ROUTING_STEP_DETAILS — returns the step-level detail of a routing.
• GET_RECIPE_STEP_DETAILS — returns step detail at the recipe level.
• GET_STEP_DEPD_DETAILS — retrieves step dependency information (predecessor/successor relationships).
• GET_OPRN_ACT_DETL — returns operation activity detail for a given operation.
• GET_OPRN_RESC_DETL — returns operation resource detail, including resource assignments and consumption.
• GET_RECIPE_PROCESS_PARAM_DETL — returns process parameter detail attached to a recipe.
• GET_PROC_PARAM_DESC — retrieves the description of a process parameter.
• GET_PROC_PARAM_UNITS — retrieves the unit of measure associated with a process parameter.
• FETCH_CONTIGUOUS_IND — returns the contiguous indicator flag, used to signal whether steps execute contiguously.
• FETCH_ENHANCED_PI_IND — returns the enhanced process instruction indicator flag.

Tables Accessed

The package reads from a broad set of OPM recipe and routing base tables through APPS synonyms:

• GMD_RECIPES / GMD_RECIPES_B — core recipe header data.
• GMD_RECIPE_ROUTING_STEPS, GMD_RECIPE_STEP_MATERIALS, GMD_RECIPE_PROCESS_LOSS, GMD_RECIPE_VALIDITY_RULES — recipe-level structural and rule components.
• GMD_RECIPE_ORGN_ACTIVITIES, GMD_RECIPE_ORGN_RESOURCES, GMD_RECIPE_PROCESS_PARAMETERS — organization-scoped recipe activities, resources, and parameters.
• FM_ROUT_HDR, FM_ROUT_DTL, FM_ROUT_DEP, FM_ACTV_MST — routing header, detail, dependency, and activity master data.
• GMD_OPERATIONS_VL, GMD_OPERATIONS_B, GMD_OPERATION_ACTIVITIES, GMD_OPERATION_RESOURCES, GMD_OPRN_PROCESS_PARAMETERS — operation definitions and their activities, resources, and parameters.
• CR_RSRC_MST, CR_RSRC_MST_B, CR_RSRC_DTL — resource master and detail data.
• GMP_PROCESS_PARAMETERS, GMP_PROCESS_PARAMETERS_B, GMP_PROCESS_PARAMETERS_TL, GMP_RESOURCE_PARAMETERS, GMP_PLANT_RSRC_PARAMETERS — process parameter definitions and plant/resource parameter configurations, including translated descriptions.

The package also depends on FND_API, FND_MESSAGE, FND_MSG_PUB, GMDRTVAL_PUB, GMD_AUTO_STEP_CALC, and GMD_COMMON_VAL, indicating that it uses the Oracle Application Object Library error-handling and message stack, delegates validation to GMD rules, and may invoke automatic step calculation logic during retrieval.

Usage Notes

GMD_RECIPE_FETCH_PUB is typically invoked from OPM recipe and routing forms, concurrent programs that explode or report recipe structures, and custom PL/SQL extensions requiring read-only access to validated recipe data. Because it is a PUB API and is referenced by fifteen other packages, it should be treated as a supported entry point rather than a candidate for direct table access by downstream integrations. Callers benefit from centralized validation and consistent message handling through FND_MSG_PUB. Custom code should reference the documented procedures only and rely on the APPS synonyms for any supplementary queries.