Search Results bom_rtg_oi_util




Overview
Explore in AI Chat

Overview

APPS.BOM_RTG_OI_UTIL is a utility package within the Oracle E-Business Suite Bills of Material (BOM) module. Its name reflects its role as an Open Interface (OI) utility for routing data: the "RTG" segment denotes routings, while "OI" identifies it as part of the open interface infrastructure that imports and validates manufacturing routing data loaded from external sources. The package is classified as a UTIL object in the ETRM 12.2.2 repository and is owned by the APPS schema, executing with AUTHID CURRENT_USER semantics. Its header comment references the source file BOMUROIS.pls and dates initial creation to 13-DEC-02, with a modification on 15-JUN-05 that added batch ID support. The package orchestrates the validation, transformation, and insertion of routing interface records into the production routing tables, providing the procedural backbone for the Routing Open Interface concurrent programs and the BOM Routing Interface.

Key Procedures and Functions

The package exposes six documented functions, all returning an integer status and accepting a consistent parameter profile that includes organization context (org_id, all_org), session identifiers (user_id, login_id), concurrent program context (prog_appid, prog_id, req_id), an error output buffer (err_text), and a batch identifier (p_batch_id). No parameter lists are invented here beyond what the specification documents.

  • Process_Rtg_Header — Processes routing header interface records, establishing the parent routing definition before detailed operations are loaded.
  • Process_Op_Seqs — The procedure most directly associated with the user's search term "process_op_seqs." It processes operation sequence interface rows, validating and inserting operation steps for a routing.
  • Process_Op_Resources — Handles operation resource assignments, linking resources to the operation sequences established by Process_Op_Seqs.
  • Process_Sub_Op_Resources — Processes subordinate resource records, which capture secondary resource requirements attached to an operation.
  • Process_Op_Nwks — Processes operation network interface data, which defines precedence relationships and flow between operations.
  • Process_Rtg_Revisions — Processes routing revision interface records, managing revision-level versioning of routing definitions.

Tables Accessed

The package reads and writes through APPS synonyms across the routing interface and production schema. Interface staging tables include BOM_OP_SEQUENCES_INTERFACE, BOM_OP_ROUTINGS_INTERFACE, BOM_OP_RESOURCES_INTERFACE, BOM_SUB_OP_RESOURCES_INTERFACE, BOM_OP_NETWORKS_INTERFACE, and MTL_RTG_ITEM_REVS_INTERFACE, which supply the inbound data. Validation and derived data are drawn from BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_RESOURCES, BOM_STANDARD_OPERATIONS, BOM_DEPARTMENTS, MTL_SYSTEM_ITEMS, and MTL_PARAMETERS. Errors encountered during processing are written to MTL_INTERFACE_ERRORS, and batch grouping is managed via BOM_INTERFACE_DELETE_GROUPS, consistent with the batch ID addition noted in the 2005 history entry.

Usage Notes

BOM_RTG_OI_UTIL is typically invoked by the BOM Routing Open Interface concurrent program rather than called directly from forms. It is referenced by one other package in the ETRM repository, indicating layered orchestration within the open interface framework. The p_batch_id parameter allows multiple import runs to be grouped and selectively purged or reprocessed. Custom implementations that load routing data should populate the interface tables and then invoke this package or the standard concurrent program, respecting the err_text output for error handling and the MTL_INTERFACE_ERRORS table for diagnostics. Direct calls require appropriate APPS privileges and should execute within a properly initialized concurrent request context, since the functions depend on prog_appid, prog_id, and req_id for logging and error attribution.