Search Results insert_step_dependencies

Overview

APPS.GMD_ROUTING_STEPS_PVT is a private PL/SQL package in Oracle E-Business Suite (12.1.1 and 12.2.2) that provides the internal processing layer for maintaining routing steps and their interdependencies within Oracle Process Manufacturing (OPM). A routing defines the sequence of operations required to manufacture a product, and each routing step represents an individual operation in that sequence. Step dependencies establish predecessor/successor relationships between steps, governing the order and conditions under which steps may execute.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking schema rather than the package owner, and it exposes an API version constant (m_api_version) plus a package name constant for diagnostic and error-handling purposes. It is classified as a PVT (private) API, indicating that it is not intended to be called directly by external consumers; instead it is invoked by the public routing API layer and by other OPM packages. The ETRM metadata records that the package is referenced by three other packages, confirming its role as a shared internal component.

Key Procedures and Functions

The package exposes six documented procedures, covering the full lifecycle of routing steps and their dependencies:

• insert_routing_steps — Inserts a routing step into a routing. It accepts a routing identifier and a routing step record, returning a return status to the caller.
• insert_step_dependencies — Inserts dependency relationships for a given routing step. It receives the routing identifier, the routing step number, and a step dependency table, and returns a status. This is the procedure most frequently targeted by developers searching for "insert_step_dependencies," as it is the supported internal entry point for creating routing step dependencies.
• update_routing_steps — Modifies attributes of an existing routing step using an update table type, returning a status.
• update_step_dependencies — Modifies an existing dependency relationship between two routing steps within a routing, driven by the step number, dependent step number, routing identifier, and update table.
• delete_routing_step — Removes a routing step by its step identifier, with an optional routing identifier, returning a status.
• delete_step_dependencies — Removes one or more step dependencies, using the step number, an optional dependent step number, and the routing identifier.

All procedures follow the standard EBS API convention of an x_return_status OUT parameter to communicate success or failure to the calling program.

Tables Accessed

The package operates against several OPM tables accessed through APPS synonyms:

• FM_ROUT_DTL — Stores routing step detail (header-level step definitions); the primary source and target for step insert, update, and delete operations.
• FM_ROUT_DEP — Stores routing step dependency records; the target of insert, update, and delete dependency operations.
• GMD_ROUTINGS — Stores routing header information referenced by routing identifier.
• GMD_RECIPE_ROUTING_STEPS, GMD_RECIPE_STEP_MATERIALS, GMD_RECIPE_ORGN_ACTIVITIES, and GMD_RECIPE_ORGN_RESOURCES — Recipe-related step, material, activity, and resource tables that carry the operational detail attached to routing steps.
• GEM5_ROUTINGSTEP_ID_S — The sequence used to generate routing step identifiers.
• PLITBLM — A PL/SQL index-by table used for internal bulk processing.

Usage Notes

Because GMD_ROUTING_STEPS_PVT is a private API, it should not be invoked directly from custom code. Client-side logic should call the public wrapper procedures in GMD_ROUTINGS_PUB, which pass the appropriate step dependency table structures (such as gmd_routings_pub.gmd_routings_step_dep_tab and gmd_routings_pub.update_tbl_type) into this private package. Typical invocation paths include the OPM routing maintenance forms and any concurrent programs or batch interfaces that create or revise routings. Developers reviewing this package for dependency insertion behavior should treat insert_step_dependencies as the internal implementation behind the published routing API, and should always inspect the x_return_status value after any call. As with all private EBS APIs, direct usage is unsupported and may be affected by patch upgrades across 12.1.1 and 12.2.2.