Search Results g_update

Overview

APPS.BOM_ROUTINGINTERFACE_PUB is a public PL/SQL package body within the Oracle E-Business Suite Bills of Material module. Its purpose is to import routing and routing-related interface data from the open interface tables into the production routing tables. The package serves as the programmatic engine behind the routing open interface import process, transforming staged interface records (routings, operations, resources, and item revisions) into valid manufacturing routing definitions tied to assemblies and organizations.

The header metadata identifies the package as a PUB (public) API owned by APPS, with a single exposed entry point. Internally the package operates against a set of package-level globals that govern import behavior, including g_CommitRows, g_Commit, g_OrgId, g_OrgCode, g_AllOrgs, g_DeleteRows, g_UserId, g_LoginId, g_RequestId, g_ProgramId, and g_ApplicationId. A notable internal cursor, l_interface_csr, drives the header import by selecting rows from bom_op_routings_interface where process_flag = 1, filtered by organization depending on the g_AllOrgs setting. The source comment on line 68 indicates the table is scanned twice so that common routings can reference newly created routings.

Key Procedures and Functions

• IMPORTROUTING — The single documented procedure of the package. It performs the routing import, driving the header scan against the interface table and coordinating the population of routing records. Although the ETRM metadata lists only IMPORTROUTING as a documented callable, the package body excerpt shows internal logic for header import (ImportHeader) and delete-group processing via the l_RtgDeleteGroup_csr cursor against bom_interface_delete_groups, which supports removal of existing routings identified by delete group names before re-import. Parameter lists are not reproduced here since the documentation does not specify them; callers should treat IMPORTROUTING as the primary public interface and rely on EBS-standard x_return_status-style conventions when invoking it.

Tables Accessed

• BOM_OP_ROUTINGS_INTERFACE — The primary staging table for routing headers; read by the main import cursor.
• BOM_OP_SEQUENCES_INTERFACE — Staging table for routing operation sequences associated with each routing.
• BOM_OP_RESOURCES_INTERFACE — Staging table for operation resources tied to routing operations.
• MTL_RTG_ITEM_REVS_INTERFACE — Interface table for routing item revisions.
• BOM_INTERFACE_DELETE_GROUPS — Read to obtain delete group names and descriptions for clearing existing routings prior to import.
• MTL_SYSTEM_ITEMS_INTERFACE_S — Interface for item validation and association during import.
• MTL_PARAMETERS — Organization-level setup parameters consulted during validation and processing.
• DUAL — Used for scalar lookups and PL/SQL control-flow queries.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, BOM_ROUTINGINTERFACE_PUB is typically invoked indirectly through the Routing Open Interface concurrent program, which populates the package-level globals (organization, commit size, delete flags, request context) before calling the import logic. Forms-based entry through the routing interface windows ultimately feeds the same interface tables. Because the package is classified as a public API, custom integrations may call it directly, but the documented single procedure and the package's reliance on session globals mean callers should replicate the concurrent program's setup (organization scope, process flag, request identifiers) for reliable results. A common search term associated with this object, g_update, refers to the package-level update flag convention; applications should confirm whether a given g_update state permits insert versus update semantics before relying on it from custom code. Always validate that staged interface rows have process_flag = 1 and correct organization values, since the import cursor silently excludes rows that fail these filters.