Search Results bom_rtg_network_validate_api




Overview
Explore in AI Chat

Overview

The APPS.BOM_RTG_NETWORK_VALIDATE_API package body provides server-side validation logic for Oracle E-Business Suite routing networks within the Bills of Material (BOM) module. Its core business purpose is to verify the structural and referential integrity of routing networks — the directed graph of operations that defines how a manufactured assembly flows through the shop floor. The package supports both Oracle EBS 12.1.1 and 12.2.2 environments.

Routing networks comprise operation sequences connected by defined transitions (network links). Before such networks are committed to the database, the application must confirm that referenced routing sequences exist, that network definitions are internally consistent, and that alternate key identifiers can be resolved to their primary keys. This API encapsulates those checks so that multiple calling programs — forms, concurrent programs, and custom extensions — share a single, consistent validation code path.

The package is classified as an API in the ETRM repository, and its ownership resides with APPS. The single documented public entry point is VALIDATE_ROUTING_NETWORK, supported internally by several private helper functions.

Key Procedures and Functions

  • VALIDATE_ROUTING_NETWORK — The sole documented public procedure. It performs the primary validation of a routing network, checking that the network definition is complete and consistent before it is used or persisted. Callers rely on this routine to return an indication of validity rather than querying the base tables directly.
  • get_routing_sequence_id (private helper) — Resolves the surrogate routing_sequence_id from the alternate key supplied by the caller: assembly item, organization, and an optional alternate routing designator. It treats a NULL alternate routing designator as the literal 'NONE', returning NULL when no matching routing is found.
  • check_network_exists (private helper) — Determines whether any network of a given operation_type exists for a specified routing_sequence_id. It returns TRUE when a matching row is present in the network view and FALSE otherwise.
  • ref_pos (private helper) — Supports positional or referential lookups used during the broader validation sequence.

Tables Accessed

  • BOM_OPERATIONAL_ROUTINGS — The header table for routing definitions; queried to translate assembly, organization, and alternate designator into a routing_sequence_id.
  • BOM_OPERATION_NETWORKS (accessed via the view BOM_OPERATION_NETWORKS_V) — Stores the network links between operations; used to confirm that a network exists for a routing sequence and operation type.
  • BOM_OPERATION_SEQUENCES — The operation sequence detail table, referenced during network consistency checks.
  • DUAL — Used in the EXISTS-based existence check within check_network_exists.
  • PLITBLM — An internal APPS table used by the BOM module.

Usage Notes

The package is invoked whenever a routing network must be validated prior to save or use. Typical callers include the Routing form within Oracle Manufacturing, concurrent programs that validate or migrate routing data, and custom PL/SQL extensions that manipulate routing networks programmatically. The ETRM metadata records b_counter, the user's search term, alongside related identifiers such as p_alt_rtg_desig and routing_sequence_id.

Because only one public procedure is exposed, custom code should call VALIDATE_ROUTING_NETWORK rather than the private helpers. The referenced-by count of zero indicates that no other shipped package depends on this API, so its interface is stable but not widely reused internally. Developers extending routing functionality should treat this package as the authoritative validation gate and avoid bypassing it with direct table access.