Search Results get_primary_prior_line_ops




Overview
Explore in AI Chat

Overview

APPS.BOM_RTG_NETWORK_API is a public PL/SQL API in Oracle E-Business Suite that provides programmatic navigation of the operation network defined within Oracle Bills of Material and Routing. Manufacturing routings are not strictly linear; an operation may be reached through a primary path, an alternate path, a rework path, or a feeder line, and the sequence that a user sees on a routing form does not necessarily reflect the true precedence relationships stored in the network. This package resolves those relationships for a given routing sequence and assembly, allowing callers to determine which operations precede or follow a given line operation.

The package is classified as an API under the APPS schema and is documented for both release 12.1.1 and 12.2.2. It exposes a strongly typed PL/SQL collection interface built on an Op_Record_Type record containing operation sequence number and operation sequence identifier, with the corresponding Op_Tbl_Type table passed to callers as an IN OUT NOCOPY parameter. This design permits a single call to return an ordered set of operations without repeated round trips to the database. The package is referenced by four other packages within the E-Business Suite, indicating that it functions as a shared infrastructure component for routing-related processing rather than an end-user facing feature.

Key Procedures and Functions

  • GET_ALL_PRIOR_LINE_OPS — Returns every line operation that precedes the current line operation, including operations on primary and alternate paths. Operations on rework paths and standalone line operations are deliberately excluded.
  • GET_PRIMARY_PRIOR_LINE_OPS — Returns only prior line operations on the primary path, including feeder line operations. When the current operation lies on an alternate path, the procedure collects prior operations along that alternate path until it reaches the primary path, then continues with primary path operations only.
  • GET_ALL_LINE_OPS — Retrieves the complete set of line operations associated with the routing context, providing the full population from which prior and next operation logic is derived.
  • GET_ALL_PRIMARY_LINE_OPS — Retrieves all line operations restricted to the primary path, omitting alternate path operations.
  • GET_ALL_NEXT_LINE_OPS — Returns all line operations that follow the current line operation, mirroring the forward direction of the prior-operations logic.
  • GET_NEXT_LINE_OPERATION — Returns the immediate successor line operation rather than the complete downstream set.
  • CHECK_LAST_LINE_OP — Validates whether a given line operation is the final operation in the routing network, a common gate for completion and close-out logic.

Tables Accessed

The package operates against the core routing and network tables through APPS synonyms. BOM_OPERATIONAL_ROUTINGS supplies the routing header identified by routing sequence; GET_PRIMARY_PRIOR_LINE_OPS falls back to assembly item, organization, and alternate routing designator to derive the routing sequence identifier when the sequence ID is not supplied. BOM_OPERATION_NETWORKS holds the from-to precedence relationships that define which operations precede or follow another, and is the principal source for prior and next operation resolution. BOM_OPERATION_SEQUENCES provides the operation sequence identifiers and sequence numbers returned in the Op_Tbl_Type collection. DUAL is used for expression evaluation and single-row queries. PLITBLM supports PL/SQL table handling within the package internals.

Usage Notes

The package is typically invoked from Oracle Forms, concurrent programs, and custom PL/SQL that must reason about routing precedence without walking the network manually. A caller supplies the routing sequence identifier and current line operation, declaring an Op_Tbl_Type variable and passing it as the IN OUT NOCOPY parameter to receive results. Because NORCOPY semantics are used, the collection is passed by reference and callers should not assume the input contents are preserved unchanged.

Two behavioural constraints are important. First, the same operation may be reachable through multiple paths; callers requiring de-duplication should account for this. Second, when p_rtg_sequence_id is null, GET_PRIMARY_PRIOR_LINE_OPS resolves the routing through assembly item, organization, and alternate routing designator, so all three must be valid. These APIs are best used where network-aware sequencing is required, such as shop floor dispatch, operation completion validation, and cost roll-up routines.