Results for “update_step_dependencies”

20 results




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

Overview

GMD_ROUTING_STEPS_PUB is a public PL/SQL API in the Oracle E-Business Suite Process Manufacturing (GMD) product family, classified as a PUB interface and owned by the APPS schema. Its declared purpose, as stated in the package header, is to create or modify routing steps and the dependencies that link those steps into a valid routing network. Routings in Process Manufacturing define the ordered sequence of operations performed to manufacture a product, and each routing step corresponds to a specific operation at a specific point in that sequence. This package encapsulates the business logic required to insert, update, and delete routing step records and their associated step-to-step dependencies, shielding callers from the underlying data model in the FM_ROUT_DTL and FM_ROUT_DEP tables.

The package is declared with AUTHID CURRENT_USER, meaning that privileges are evaluated against the invoking schema rather than the package owner. It exposes an API version constant (m_api_version) set to 1, following the standard Oracle EBS PL/SQL API conventions for versioning and upward compatibility.

Key Procedures and Functions

The package exposes six documented entry points, divided evenly between step-level and dependency-level operations:

  • INSERT_ROUTING_STEPS — Inserts one or more routing step records into the routing details table. It accepts a routing identifier (routing ID, number, and version) together with a row-type record describing the step and a table structure carrying step dependency information, so that a step and its dependencies can be created in a single call.
  • INSERT_STEP_DEPENDENCIES — Inserts dependency records that establish predecessor/successor relationships between routing steps.
  • UPDATE_ROUTING_STEPS — Modifies existing routing step records for a given routing.
  • UPDATE_STEP_DEPENDENCIES — Modifies existing step dependency relationships.
  • DELETE_ROUTING_STEP — Removes a routing step from a routing.
  • DELETE_STEP_DEPENDENCIES — Removes dependency relationships between routing steps.

All procedures follow the standard EBS API parameter convention, including p_api_version, p_init_msg_list, p_commit, and the output parameters x_return_status (with values 'S' for success, 'E' for error, and 'U' for unexpected error), x_message_count, and x_message_list. Callers should always inspect x_return_status before proceeding.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • FM_ROUT_DTL — the routing step detail table, holding the individual steps of a routing; the primary target of insert, update, and delete operations.
  • FM_ROUT_DEP — the step dependency table, recording predecessor/successor links between steps.
  • FM_ROUT_HDR — the routing header table, providing routing-level context and validation.
  • GMD_ROUTINGS, GMD_ROUTINGS_B — the routing entity tables used to validate routing identifiers and versions.
  • GMD_OPERATIONS, GMD_OPERATIONS_B — the operations definition tables, used to validate the operations referenced by routing steps.
  • PLITBLM — the standard EBS message-list table used by the API framework for error and information messaging.

Usage Notes

This package is intended for programmatic manipulation of routing steps and dependencies rather than direct table updates. It is typically invoked from Process Manufacturing routing maintenance forms, from concurrent programs that copy or generate routings, and from custom PL/SQL extensions that need to build or revise routings. Because it is documented as referenced by five other packages, it should be treated as a stable integration point; direct DML against FM_ROUT_DTL and FM_ROUT_DEP bypasses the validation and dependency-consistency logic embedded here. The package is documented as active and compatible in both EBS 12.1.1 and 12.2.2, so custom code written against it remains portable across those releases.