Search Results gem5_routingstep_id_s




Overview
Explore in AI Chat

Overview

GMD_ROUTING_STEPS_PVT is the private implementation package body behind the public routing steps API in Oracle Process Manufacturing (OPM), part of the Oracle E-Business Suite 12.1.1 / 12.2.2 codebase. The package encapsulates the low-level business logic that creates, maintains, and removes the routing step records and the precedence relationships between those steps for a routing defined in GMD_ROUTINGS. Routing steps represent the sequential operations performed during manufacturing, including the activities, resources, and materials consumed or produced at each operation. By isolating this logic in a PVT (private) package, Oracle ensures that direct DML against the routing step base tables is performed only through a controlled, validated code path, while the companion public package GMD_ROUTING_STEPS_PUB exposes the transaction entry points used by callers.

Key Procedures and Functions

The documented package contains six procedures, organized as three paired operations covering the routing step header and its dependency (precedence) records:

  • INSERT_ROUTING_STEPS — Creates new routing step rows, deriving the primary key from the GEM5_ROUTINGSTEP_ID_S sequence and populating the operational attributes of each step.
  • INSERT_STEP_DEPENDENCIES — Inserts the dependency/precedence definitions that link one routing step to its predecessor or successor, establishing the process flow.
  • UPDATE_ROUTING_STEPS — Modifies the attributes of an existing routing step, typically invoked when an operation's definition changes.
  • UPDATE_STEP_DEPENDENCIES — Maintains changes to the precedence relationships between steps.
  • DELETE_ROUTING_STEP — Removes a routing step and coordinates the cleanup of associated detail records.
  • DELETE_STEP_DEPENDENCIES — Removes the dependency relationships associated with a step or routing.

All six follow Oracle's standard API conventions, chaining calls to FND_API, FND_MSG_PUB, and the GRP (group) handle pattern via GMD_API_GRP for error management and transaction consistency.

Tables Accessed

The package reads and writes the core OPM routing tables. GMD_RECIPE_ROUTING_STEPS and GMD_ROUTINGS hold the routing step and routing header data, while GMD_RECIPE_STEP_MATERIALS, GMD_RECIPE_ORGN_ACTIVITIES, and GMD_RECIPE_ORGN_RESOURCES capture the materials, activities, and resources tied to each step. Precedence data resides in FM_ROUT_DTL (routing detail) and FM_ROUT_DEP (routing dependencies). The sequence GEM5_ROUTINGSTEP_ID_S supplies the primary key for new routing step rows. Validation is delegated to GMDRTVAL_PUB, and the PLITBLM package is used for PL/SQL index-by table handling.

Usage Notes

This private body is never called directly by end users. It is invoked exclusively through GMD_ROUTING_STEPS_PUB, which in turn is called by OPM process execution and routing definition forms, by concurrent programs that copy or import routings, and by custom extensions. The dependency listing shows the package is referenced by three other database objects, confirming its role as a shared internal service rather than a standalone entry point. When extending OPM routing functionality, developers should call the public wrapper rather than this package, since the PVT body assumes that group handles, message stacks, and validation have already been initialized by the caller.