Search Results mtl_system_items_interface_s




Overview
Explore in AI Chat

Overview

APPS.BOM_RTG_OI_UTIL is a utility PL/SQL package in Oracle EBS Release 12.1.1 and 12.2.2 that supports the open interface for importing manufacturing routing and resource information into Oracle Bills of Material. The package body carries the implementation logic behind the routing open interface, translating staged rows held in interface tables into the corresponding production routing entities: operational routings, operation sequences, operation resources, sub-operation resources, operation networks, and routing revisions.

The object is registered in the ETRM repository with VALID status under the APPS schema and is classified as a utility (UTIL) API rather than a public business API. Its design reflects the standard Oracle open-interface pattern, where batch-loaded rows are validated against master data, errors are recorded for correction, and successfully processed rows are migrated into the base tables and optionally purged from the staging tables.

Key Procedures and Functions

Six documented procedures make up the executable surface of the package body, each responsible for one slice of the routing import pipeline:

  • PROCESS_RTG_HEADER — Handles the routing header level. It establishes or validates the operational routing record associated with the item revision being imported, forming the parent context for subsequently processed operation rows.
  • PROCESS_OP_SEQS — Processes operation sequence rows from the operation sequences interface, creating or updating the manufacturing operations that belong to the routing header.
  • PROCESS_OP_RESOURCES — Processes operation resource rows from the op resources interface, attaching resources and their usage to the parent operation sequences.
  • PROCESS_SUB_OP_RESOURCES — Handles sub-operation resource rows, applying resource assignments at the sub-operation tier of the routing structure.
  • PROCESS_OP_NWKS — Processes operation network rows, maintaining the flow and network relationships between operations in the routing.
  • PROCESS_RTG_REVISIONS — Processes routing item revision data, binding routing structures to the correct item revision so that engineering-change-controlled routings remain consistent.

Tables Accessed

The package reads and writes a well-defined set of interface and base tables through APPS synonyms. On the interface side it consumes BOM_OP_ROUTINGS_INTERFACE, BOM_OP_SEQUENCES_INTERFACE, BOM_OP_RESOURCES_INTERFACE, BOM_SUB_OP_RESOURCES_INTERFACE, BOM_OP_NETWORKS_INTERFACE, and MTL_RTG_ITEM_REVS_INTERFACE. These hold the staged import rows supplied by external systems or data conversion programs.

Validation and derivation draw on BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_RESOURCES, BOM_STANDARD_OPERATIONS, BOM_DEPARTMENTS, and MTL_SYSTEM_ITEMS along with the key flexfield views MTL_SYSTEM_ITEMS_KFV and MTL_ITEM_LOCATIONS_KFV. Imported rows that fail validation generate messages through FND_MESSAGE and are logged to MTL_INTERFACE_ERRORS. BOM_INTERFACE_DELETE_GROUPS controls the bulk deletion of successfully processed interface rows. WIP_LINES and MTL_PARAMETERS supply shop-floor and inventory-organization context, and the package references itself recursively for shared internal logic.

Usage Notes

BOM_RTG_OI_UTIL is invoked indirectly rather than called directly by end users. It forms part of the processing engine behind the Bills of Material routing open interface concurrent programs, which submit the interface rows through the standard import cycle: validation, error reporting, and successful migration to base tables. The dependency list confirms it is not referenced by any other database object, so callers are limited to the concurrent program layer and to custom code that deliberately reuses the utility routines.

Typical custom usage follows the same pattern: load the interface tables, supply the relevant delete group, then invoke the processing procedures in dependency order — header, revisions, sequences, resources, sub-operation resources, and networks. Errors must be reviewed in MTL_INTERFACE_ERRORS and corrected before resubmission, since rejected rows remain in the interface tables until successfully processed or purged. Note that the search term MTL_SYSTEM_ITEMS_INTERFACE_S appears only as a referenced object in the dependency metadata; item master validation within routing import is performed against MTL_SYSTEM_ITEMS and its descriptive flexfield views rather than through that interface table in the documented procedure set.