Search Results save_profile_value

Overview

APPS.GMD_ROUTING_DESIGNER_PKG is the server-side PL/SQL workhorse behind the Oracle Process Manufacturing (OPM) Routing Designer in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented header comment states that the package specification contains the procedures used by the Routing Designer to create, update, and delete routing step dependencies. Routing in OPM describes the sequence of operations and steps a product or batch must follow through production, and the dependencies between those steps define which operations must precede others. Rather than allowing the form to manipulate the underlying tables directly, the Routing Designer delegates all validation and persistence logic to this package.

Beyond step dependencies, the package scope extends to routing headers, routing steps, routing versions, profiles, and routing security. Historical entries in the source header record that a default status build procedure (SET_DEFAULT_STATUS), routing security checking (CHECK_ROUT_ORGN_ACCESS), and contiguous-indicator / enforce-step-dependency logic were added in the 2004–2005 timeframe, confirming the object's long-standing role in OPM manufacturing routing maintenance. The package is owned by APPS and is classified as OTHER in the ETRM API registry.

Key Procedures and Functions

The documented 25 procedures and functions fall into several functional groups.

• Step dependency maintenance: CREATE_STEP_DEPENDENCY, UPDATE_STEP_DEPENDENCY, DELETE_STEP_DEPENDENCY, and GENERATE_STEP_DEPENDENCIES manage the predecessor/successor relationships between routing steps. These are the routines invoked when a user defines, edits, removes, or automatically generates dependencies in the Routing Designer.
• Routing header and structure: CREATE_ROUTING_HEADER, UPDATE_ROUTING_HEADER, INSERT_ROUTING_STEP, UPDATE_ROUTING_STEP, DELETE_ROUTING_STEP, UPDATE_OPERATION_STEP, and COPY_ROUTING handle the construction and cloning of routing definitions.
• Validation and control: VALIDATE_ROUTING_DETAILS, VALIDATE_ROUTING_VR_DATES, CHECK_VERSION_CONTROL, CHECK_FUNCTION, IS_ROUTING_USED_IN_RECIPES, UPDATE_VR_WITH_RT_DATES, GET_ROUTING_MODE, and UPDATE_VR_WITH_RT_DATES enforce business rules, versioning constraints, and recipe usage checks before changes are committed.
• Infrastructure: GET_PROFILE_VALUE and SAVE_PROFILE_VALUE read and persist profile values for the designer session, while CHECK_ROUT_ORGN_ACCESS and SET_DEFAULT_STATUS support routing security and default status builds.

Tables Accessed

The package operates against OPM routing tables through APPS synonyms. FM_ROUT_DTL and FM_ROUT_DEP store routing step details and step dependencies respectively, mirroring the create/update/delete dependency logic. FM_TEXT_TBL and GEM5_TEXT_CODE_S provide text and code lookups. GMD_ROUTINGS and GMD_ROUTINGS_B hold routing header and base data, while GMD_ROUTING_CLASS classifies routings. The sequence GEM5_ROUTING_ID_S and GEM5_ROUTINGSTEP_ID_S supply primary keys for new headers and steps. MTL_UNITS_OF_MEASURE supplies unit-of-measure validation, FND_DUAL is used for dual-table queries typically in validation logic, and PLITBLM is referenced as a PL/SQL table type for in-memory collections.

Usage Notes

This package is invoked principally by the OPM Routing Designer form and related OPM manufacturing forms, not by end users or concurrent programs directly. Custom development should call these procedures rather than writing to FM_ROUT_DEP or FM_ROUT_DTL directly, since the package enforces version control, recipe-usage checks, and routing security that direct DML would bypass. The ETRM registry notes the package is referenced by one other package, indicating a small but real dependency chain within the OPM routing codebase. Users searching for "create_step_dependency" will find that CREATE_STEP_DEPENDENCY is the documented entry point for inserting a new predecessor/successor relationship between routing steps.