Search Results validate_routing_network




Overview
Explore in AI Chat

Overview

The APPS.BOM_RTG_NETWORK_VALIDATE_API package provides programmatic validation of manufacturing routing networks within Oracle E-Business Suite. A routing network defines the sequence of operations and the flow dependencies between them for a manufactured assembly. As routings grow in complexity, they may contain circular dependencies (loops) or orphaned operations that are not reachable from the primary path (broken links). This package encapsulates the validation logic that detects such structural defects before a routing is released for production use.

The package is classified as an API in the ETRM metadata and is owned by the APPS schema, declaring AUTHID CURRENT_USER so that it executes with the privileges of the calling session. The source header dates to release 11.5 (file BOMRNWVS.pls, version 115.0), and the object remains documented through EBS 12.2.2, indicating its continued role in the manufacturing foundation layer.

Key Procedures and Functions

The package exposes a single documented procedure, VALIDATE_ROUTING_NETWORK. Its purpose, as documented in the source comments, is to validate the routing network by first checking for loops and then checking for broken links.

  • VALIDATE_ROUTING_NETWORK — Performs the complete network validation for a specified routing. It accepts the routing sequence identifier, the assembly item identifier, the organization identifier, and an alternate routing designator, together with an operation type discriminator. It returns a status indicator and a diagnostic message. When a loop or a broken link exists, the returned message identifies the nodes (operations) where the defect occurs.

The package also declares two PL/SQL collection types used internally to pass network node and link data during validation:

  • Lnk_Record_Type / Lnk_Tbl_Type — a record and index-by table representing a directed link between a source operation sequence ID and a target operation sequence ID, with a status flag.
  • Op_Record_Type / Op_Tbl_Type — a record and index-by table representing an operation by its sequence ID and sequence number.

These structures support the graph traversal logic that underlies the validation procedure. The package declares no functions and no additional public procedures beyond the one documented entry point.

Tables Accessed

The package reads from the following application tables via APPS synonyms:

  • BOM_OPERATIONAL_ROUTINGS — the header routing definition, keyed by routing sequence and assembly, used to establish the routing context.
  • BOM_OPERATION_NETWORKS — the network link table, which records the from/to operation dependencies that form the directed graph evaluated for loops and broken links.
  • BOM_OPERATION_SEQUENCES — the individual routing operations referenced by the network links, supplying the operation identifiers and sequence numbers reported in diagnostic messages.
  • DUAL — used for scalar evaluation within the validation logic.
  • PLITBLM — the standard Oracle Applications PL/SQL index-by table utility package (also known as PLITBLM / PLITBLM family) used for collection initialization and manipulation.

The metadata records no references from other packages, indicating the API is a leaf-level utility rather than a shared service consumed by other PL/SQL units.

Usage Notes

This API is typically invoked when a routing must be validated prior to release, or as part of custom extensions that programmatically verify routing integrity. Because it is an APPS-owned API with public execution grants, it can be called from:

  • Oracle Forms-based routing maintenance windows in Oracle Manufacturing, where validation is triggered when the user saves or validates a routing network.
  • Concurrent programs or batch routines that scan large numbers of routings for structural defects.
  • Custom PL/SQL code that must confirm a routing is free of loops and broken links before downstream processing, such as scheduling or capacity planning.

Callers should always inspect the x_status output rather than relying on exceptions; the procedure reports validation failures through its out parameters and returns the offending node identifiers in x_message. Because the procedure is AUTHID CURRENT_USER, the invoking session must have the appropriate privileges on the referenced BOM tables, and the caller must supply a valid organization and assembly context for the routing being examined. The p_operation_type parameter allows the same validation logic to be applied across different classes of routing operations defined in the manufacturing model.