Search Results bom_operation_networks_pkg




Overview
Explore in AI Chat

Overview

The APPS.BOM_OPERATION_NETWORKS_PKG is a server-side PL/SQL package within the Oracle E-Business Suite (EBS) Bills of Material (BOM) application. It serves as the primary data access and business logic layer for maintaining operation network relationships — the directed links that define predecessor/successor sequencing between routing operations on a manufacturing bill of materials. In Oracle EBS 12.1.1 and 12.2.2, operation networks are used to model complex routings where an operation flows into one or more downstream operations, optionally governed by a transition type and a planning percentage. The package encapsulates the insert, update, delete, and concurrency-control logic required to keep the BOM_OPERATION_NETWORKS base table consistent with the operation sequences it references. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is typical of table-handler packages invoked from Oracle Forms and OA Framework pages running in the APPS schema context. The package is classified as OTHER in ETRM, reflecting that it is an internal repository API rather than a public, documented integration interface.

Key Procedures and Functions

  • INSERT_ROW — Creates a new operation network record. It receives the from/to operation sequence identifiers, transition type, planning percentage, WHO columns (creation/update audit fields), and the DFF attribute columns, returning the generated row identifier. It is the entry point used when a user or program adds a new routing link.
  • LOCK_ROW — Acquires an application-level lock on an existing operation network row before modification. It accepts the row identifier, key network attributes, effectivity/disable dates, WHO columns, and DFF attributes, implementing optimistic concurrency control so that concurrent edits do not silently overwrite each other.
  • UPDATE_ROW — Modifies an existing operation network record. Like LOCK_ROW, it takes the row identifier together with the full set of updatable columns (sequence IDs, transition type, planning percentage, effectivity and disable dates, audit fields, and DFF attributes).
  • DELETE_ROW — Removes an operation network relationship, typically invoked after the associated sequence has been purged or when a routing is restructured.
  • CHECK_UNIQUE_LINK — Validates that a proposed from-operation / to-operation pairing does not already exist, preventing duplicate network links. This validation is central to the user search term "check_unique_link" and is usually called prior to INSERT_ROW to enforce integrity before a row is committed.

Tables Accessed

  • BOM_OPERATION_NETWORKS — The base table holding operation network rows (from/to sequence, transition type, planning percent, effectivity dates, audit columns, and DFF attributes). All five procedures read or write this table.
  • BOM_OPERATION_SEQUENCES — Referenced to confirm that the from- and to-operation sequence identifiers exist and belong to the same routing, safeguarding referential integrity.
  • DUAL — Used for singleton validation queries, most notably within CHECK_UNIQUE_LINK to test link existence without touching a physical table.

Usage Notes

BOM_OPERATION_NETWORKS_PKG is an internal repository package and is not intended as a public integration API. It is typically invoked indirectly by the Oracle Bills of Material and Oracle Manufacturing forms and OA Framework pages that maintain routing operation networks, and by concurrent programs that copy or restructure routings. Because ETRM records zero inbound references from other packages, direct calls from custom code are uncommon; where custom PL/SQL must manipulate operation networks, this package is preferred over direct DML on BOM_OPERATION_NETWORKS because it centralizes validation (CHECK_UNIQUE_LINK), concurrency control (LOCK_ROW), audit column population, and DFF handling. Developers should note the AUTHID CURRENT_USER declaration and ensure the invoking schema holds appropriate privileges on the underlying APPS synonyms. The package is present and functionally consistent across both 12.1.1 and 12.2.2, with no documented behavioral divergence between the two releases.