Search Results g_default_control_rec




Overview
Explore in AI Chat

Overview

APPS.BOM_RTG_PUB is the public PL/SQL routing API in Oracle E-Business Suite, declared with AUTHID CURRENT_USER so that it executes under the privileges of the calling schema. Its business purpose is to provide a programmatic interface for creating, updating, and deleting routings and all associated child entities—routing header, routing revisions, operations, operation resources, substitute operation resources, and operation networks—without requiring users to manipulate the underlying base tables directly.

The package supports processing of single or multiple business entities per call, with the constraint that all entities supplied in one invocation must belong to the same routing. In addition to its transactional APIs, BOM_RTG_PUB exposes a set of utility conversion procedures that translate routing child entities to and from their Bill of Materials equivalents. This bridges the routing and BOM domains and allows BOM structure records to be leveraged where routing constructs are expected, and vice versa. The package is a foundational interface in the manufacturing module: ETRM metadata records that it is referenced by 51 other packages, indicating it is embedded in a wide web of dependent application logic. The current source baseline ($Header: BOMBRTGS.pls 120.6.12020000.2) is consistent with EBS 12.1.1 and 12.2.2.

The user search term g_default_control_rec refers to a package-level default control record variable that governs processing behavior on API calls. It represents the standard EBS pattern of supplying a global control structure and an error-handler so that callers can direct batch processing, control commit behavior, and retrieve diagnostics.

Key Procedures and Functions

ETRM documents nine public program units in BOM_RTG_PUB, all with PUB classification:

  • PROCESS_RTG — The core transactional driver. It accepts caller-populated record types for the routing header and child entities and processes them according to each record's transaction_type (for example, 'CREATE'). It registers errors in the PL/SQL error table so that callers can extract them after execution.
  • CONVERT_RTGOP_TO_COMOP — Converts a routing operation into the corresponding common (BOM) operation representation.
  • CONVERT_COMOP_TO_RTGOP — Performs the reverse mapping, deriving a routing operation from a common operation.
  • CONVERT_ECOOP_TO_COMOP — Converts an ECO (engineering change order) operation into a common operation.
  • CONVERT_COMOP_TO_ECOOP — Converts a common operation back into an ECO operation.
  • CONVERT_RTGRES_TO_ECORES — Maps a routing operation resource to an ECO resource.
  • CONVERT_ECORES_TO_RTGRES — Maps an ECO resource back to a routing operation resource.
  • CONVERT_RTGSUBRES_TO_ECOSUBRES — Maps a substitute routing operation resource to an ECO substitute resource.
  • CONVERT_ECOSUBRES_TO_RTGSUBRES — Maps an ECO substitute resource back to a substitute routing operation resource.

Tables Accessed

ETRM metadata lists a single directly referenced object for this package via APPS synonyms: PLITBLM, the PL/SQL error and message table. PROCESS_RTG uses this table to log validation and processing errors raised while creating, updating, or deleting routings and their children; callers query it afterward to obtain error text and diagnostic context. Although the conversion procedures logically operate against routing and BOM table structures, only PLITBLM is documented as referenced in the available metadata.

Usage Notes

BOM_RTG_PUB is typically invoked from three sources. First, Oracle Manufacturing forms may call the API to persist routing changes made interactively. Second, concurrent programs that mass-create or mass-maintain routings, or that load routing data through interfaces, call PROCESS_RTG in batch mode. Third, custom PL/SQL code and other application packages call the API directly; this is consistent with the documented fact that 51 packages reference it.

The documented calling convention requires the caller to initialize the error handler, populate record types (including the control record, such as g_default_control_rec, which carries processing options) for each entity, then invoke PROCESS_RTG. Because the package is AUTHID CURRENT_USER, the invoking session must have appropriate privileges on the referenced synonyms and underlying objects. Callers should always inspect the PL/SQL error table (PLITBLM) after execution rather than relying on exceptions, since errors are registered there by design.