Search Results process_rtg_header




Overview
Explore in AI Chat

Overview

BOM_RTG_OI_UTIL is a utility package in the Oracle E-Business Suite Applications (APPS) schema that supports the open interface processing of manufacturing routing and operation data. Its name reflects its role: "RTG" denotes routing, "OI" denotes open interface, and "UTIL" identifies it as a helper package. The package provides the procedural backbone for loading routing headers, operation sequences, operation resources, sub-operation resources, operation networks, and routing revisions from the interface staging tables into the base manufacturing tables.

Unlike a public API such as BOM_RTG_PUB, this package is classified in ETRM as a UTIL object. It is not designed to be called directly by end users or by general custom code. Instead it is invoked by the routing open interface concurrent program and by higher-level processing packages that orchestrate the validation, defaulting, and insertion of routing records. The package is declared AUTHID CURRENT_USER, so its unqualified object references resolve against the calling schema's privileges rather than a fixed definer context.

The documented source header, BOMUROIS.pls (version 120.1), shows initial creation on 13-DEC-2002 and a revision on 15-JUN-05 that added a batch identifier parameter. That batch identifier is significant because it allows a single logical interface run to be grouped and tracked, and because it enables selective cleanup of interface rows after processing. The package is referenced by one other package in the documented metadata, confirming its role as a supporting component rather than an entry-point API.

Key Procedures and Functions

The documented interface exposes six functions, all of which return an INTEGER status and accept a common set of context parameters: org_id and all_org for organization scoping, user_id and login_id for audit attribution, prog_appid, prog_id and req_id for concurrent request context, an IN OUT NOCOPY err_text for error messaging, and p_batch_id for batch identification. The parameter lists are not reproduced here; only purposes are described.

  • PROCESS_RTG_HEADER — Processes routing header records. This is the function associated with the user's search term "process_rtg_header". It reads routing header interface rows and creates or updates the corresponding routing header definitions, applying organization and batch context and returning status with error text.
  • PROCESS_OP_SEQS — Processes operation sequence records, building the sequence of operations that make up a routing.
  • PROCESS_OP_RESOURCES — Processes operation resource assignments, attaching resources to operation sequences.
  • PROCESS_SUB_OP_RESOURCES — Processes sub-operation resource assignments, handling resources attached at the sub-operation level.
  • PROCESS_OP_NWKS — Processes operation network records, loading the operation network interface data.
  • PROCESS_RTG_REVISIONS — Processes routing revision records, loading item revision information associated with routings.

Tables Accessed

The package reads and writes the base manufacturing routing tables BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_RESOURCES, BOM_STANDARD_OPERATIONS, BOM_DEPARTMENTS, and MTL_SYSTEM_ITEMS, and MTL_PARAMETERS for organization-level defaults. It consumes staged data from the interface tables 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. Errors are recorded in MTL_INTERFACE_ERRORS, and batch lifecycle management uses BOM_INTERFACE_DELETE_GROUPS, which supports the batch identifier concept and post-run cleanup of processed rows.

Usage Notes

BOM_RTG_OI_UTIL is normally invoked through the Manufacturing routing open interface concurrent program rather than from forms. Custom integrations typically insert rows into the BOM_OP_*_INTERFACE tables and submit that concurrent program, allowing the program to call these functions internally. Direct invocation from custom PL/SQL is possible but unsupported in practice, since the functions assume concurrent request context and consistent interface staging. When troubleshooting, MTL_INTERFACE_ERRORS is the primary diagnostic source, and the p_batch_id value links all records processed in a single run.