Results for “get_oprn_resc_detl”

14 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMD_RECIPE_FETCH_PUB is a public PL/SQL package in the Oracle E-Business Suite Process Manufacturing (OPM) modules, owned by APPS and classified as a PUB interface. Its stated purpose, per the embedded header commentary, is to fetch information related to recipes: recipe identifiers, formula identifiers, routing identifiers, routing step details, step dependencies, operation activity and resource details, and process parameters. The package defines and implements the procedures and datatypes required to return this information to callers. It is registered with scope "public", product "GMD", lifecycle "active", display name "Recipe Fetch package", compatibility "S", and business entity "GMD_RECIPE".

In business terms, the package allows external programs, forms, and concurrent processes to read the complete definition of a manufacturing recipe without directly querying the underlying OPM base tables. A recipe in Process Manufacturing combines a formula (materials and quantities) with a routing (operations, steps, and resources). GMD_RECIPE_FETCH_PUB encapsulates the joins across these structures and returns the results through PL/SQL collection types and record types declared in the package specification. Because it is a public API, it is intended as a supported integration point for customizations and extensions.

Key Procedures and Functions

The ETRM metadata documents sixteen public procedures and functions:

  • GET_VALIDITY_RULES — returns the recipe validity rules that govern the effective dates and applicability of a recipe.
  • GET_RECIPE_STEP_DETAILS — returns routing step information for a recipe, including step identifiers, step quantities, release types, and minimum transfer quantities, together with associated operation attributes.
  • GET_ROUTING_STEP_DETAILS — returns details for routing steps, typically at the routing header and detail level.
  • GET_ROUT_HDR — returns routing header information for a given routing.
  • GET_ROUTING_ID — resolves and returns the routing identifier associated with a recipe.
  • GET_FORMULA_ID — resolves and returns the formula identifier associated with a recipe.
  • GET_ROUT_MATERIAL — returns material details attached to routing steps.
  • GET_PROCESS_LOSS — returns process loss information associated with recipe or routing steps.
  • GET_STEP_DEPD_DETAILS — returns step dependency details describing the sequencing relationships between routing steps.
  • GET_OPRN_ACT_DETL — returns operation activity details for operations referenced by the recipe.
  • GET_OPRN_RESC_DETL — returns operation resource details, including resource capacity attributes.
  • GET_RECIPE_PROCESS_PARAM_DETL — returns the process parameter values defined for a recipe.
  • GET_PROC_PARAM_DESC — returns the description of a process parameter.
  • GET_PROC_PARAM_UNITS — returns the units of measure associated with a process parameter.
  • FETCH_CONTIGUOUS_IND — returns the contiguous indicator flag used in recipe processing.
  • FETCH_ENHANCED_PI_IND — returns the enhanced process instruction indicator flag.

The specification also declares collection types such as recipe_validity_tbl, recipe_rout_matl_tbl, recipe_form_matl_tbl, routing_depd_tbl, and recipe_rout_tbl, and a recipe_step_out record type that carries recipe, routing step, operation, capacity, and charge attributes.

Tables Accessed

The package reads the following tables through APPS synonyms:

These accesses are read-oriented, supporting the fetch role of the package.

Usage Notes

GMD_RECIPE_FETCH_PUB is referenced by fifteen other packages, indicating it is a foundational read interface within the OPM recipe architecture. It is typically invoked by OPM forms and concurrent programs that need to display or process recipe structure, and by custom code requiring supported access to recipe, formula, routing, operation, resource, and process parameter data. Because it is classified as public, customizations should call these documented procedures rather than querying the base tables directly. The header version string references a 2008 revision, consistent with the long-standing stability of this interface across EBS 12.1.1 and 12.2.2.