Search Results insert_routing_steps

Overview

GMD_ROUTING_STEPS_PVT is a private PL/SQL package in the Oracle E-Business Suite Process Manufacturing (OPM) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. It encapsulates the low-level transactional logic that manages routing steps and their inter-step dependencies within process routings. A routing defines the sequence of operations performed to manufacture a product, and each routing step represents an individual operation complete with its resources, materials, and predecessor/successor relationships. This package provides the DML primitives that create, modify, and remove those routing step records and their dependency links.

The private ("_PVT") designation indicates the package is intended as an internal implementation layer. It is not the supported public entry point for external integrations; the corresponding public API surface is provided by GMD_ROUTINGS_PUB, whose PL/SQL types (such as the step dependency table and the update table type) are referenced directly in this package's signatures. GMD_ROUTING_STEPS_PVT is referenced by three other packages, confirming its role as a shared internal service consumed by higher-level routing maintenance logic. The header carries a version marker of 115.2 and an API version constant of 1, reflecting its long-standing stability in the OPM data model.

Key Procedures and Functions

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

• INSERT_ROUTING_STEPS — Creates a new routing step for a given routing. It accepts the parent routing identifier and a routing detail record (modeled on the FM_ROUT_DTL%ROWTYPE), and returns a status indicator.
• INSERT_STEP_DEPENDENCIES — Establishes predecessor relationships for a routing step. It takes the routing identifier, the step number, and a collection of step dependencies, returning a status.
• UPDATE_ROUTING_STEPS — Modifies an existing routing step identified by its step identifier, applying changes from an update table, and returns a status.
• UPDATE_STEP_DEPENDENCIES — Revises the dependency relationship between a step and its dependent step within a routing, using the update table convention and returning a status.
• DELETE_ROUTING_STEP — Removes a routing step by its step identifier, optionally scoped to a routing, and returns a status.
• DELETE_STEP_DEPENDENCIES — Removes one or all dependency links for a step, optionally filtered by dependent step and routing, and returns a status.

Every procedure uses the standard OPM x_return_status OUT parameter to communicate success or failure to the caller.

Tables Accessed

The package reads and writes several core OPM routing tables through APPS synonyms:

• FM_ROUT_DTL — the routing step detail table, the primary target of inserts, updates, and deletes.
• FM_ROUT_DEP — stores the dependency relationships between routing steps.
• GMD_ROUTINGS — the routing header, providing the parent routing context.
• GEM5_ROUTINGSTEP_ID_S — the sequence used to generate routing step identifiers.
• GMD_RECIPE_ROUTING_STEPS, GMD_RECIPE_ORGN_ACTIVITIES, GMD_RECIPE_ORGN_RESOURCES, GMD_RECIPE_STEP_MATERIALS — recipe-related tables that associate steps with activities, resources, and materials.
• PLITBLM — the OPM temporary/interface table used during processing.

Usage Notes

As a private package, GMD_ROUTING_STEPS_PVT is not the recommended integration point for custom development. It is typically invoked indirectly through the public routing APIs in GMD_ROUTINGS_PUB, or by the OPM routing maintenance forms and related concurrent programs that orchestrate step creation and dependency management. Custom code should prefer the public API, reserving direct calls to this package for scenarios where no public equivalent exists. Because the procedures return status through x_return_status, callers must check this value after each invocation and handle failures appropriately. Direct DML against the underlying tables is discouraged, since the package encapsulates identifier generation and dependency consistency logic that manual inserts would bypass.