Search Results update_in_src_orgs

Overview

CTO_UPDATE_BOM_RTG_PK is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Configure-to-Order (CTO) order fulfillment flow. Its principal business function is the on-demand generation and maintenance of bill of material (BOM) and routing structures for configured models as they are entered on order lines. When a configurator-driven model is booked or changed, the package explodes the model configuration into the specific inventory components and operation sequences required for manufacturing, writing that detail into the BOM interface tables before the standard BOM import programs persist it. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling session rather than the definer, a deliberate choice consistent with its role as an internal engine invoked from within the order management and BOM import flows.

The package carries legacy provenance — the source header reflects a 2004 revision (115.3) — yet it remains documented in the 12.2.2 ETRM repository, indicating continued relevance across the 12.1.1 and 12.2.2 releases. Its debug level is derived from the ONT_DEBUG_LEVEL profile option, and it exposes a batch size constant defaulting to 10 for bulk processing.

Key Procedures and Functions

• UPDATE_BOMS_RTGS — Concurrent-program entry point that drives the update of bills and routings for a given sequence and source delimiter.
• UPDATE_IN_SRC_ORGS — Propagates configuration changes into source organizations for a model line, returning status, message count, and message data.
• WRITETOLOG — Diagnostic logging utility gated by the debug level resolved from the ONT_DEBUG_LEVEL profile.
• UPDATE_BOM_RTG_LOOP — Core per-line worker that creates or updates the bill and routing for a single model/configuration/organization combination, returning bill and routing identifiers plus error detail.
• UPDATE_BOM_RTG_BULK — Bulk wrapper that processes the pending set of lines in batches.
• GET_MODEL_LEAD_TIME — Function that computes the cumulative lead time for a model in a given organization at a specified quantity, returning the lead time through an OUT parameter and an error buffer. This is the routine users locate when searching for "get_model_lead_time"; it is a programmatic interface rather than a user-facing screen.
• INHERIT_OP_SEQ_ML — Function that inherits operation sequence values for a model line using the configuration bill as the reference.
• BMLUPID_UPDATE_ITEM_DESC — Function that updates item descriptions for a given item and organization.
• CHECK_ROUTING and CHECK_BOM — Validation functions that confirm routing and BOM structures exist or are valid before an update proceeds.

Tables Accessed

The package reads and writes across the order management and manufacturing schemas. OE_ORDER_LINES supplies model line context, including ship_from_org_id. BOM structures are sourced and staged through BOM_BILL_OF_MTLS_INTERFACE, BOM_INVENTORY_COMPS_INTERFACE, and BOM_INVENTORY_COMPONENTS_S, which receive the exploded configuration detail. Routing data is handled via BOM_OPERATIONAL_ROUTINGS, BOM_OPERATIONAL_ROUTINGS_S, BOM_OPERATION_SEQUENCES, BOM_OPERATION_NETWORKS, BOM_OPERATION_RESOURCES, and BOM_COMPONENT_OPERATIONS. Supporting reads include BOM_ALTERNATE_DESIGNATORS, BOM_DEPENDENT_DESC_ELEMENTS, BOM_EXPLOSION_TEMP, BOM_CALENDAR_DATES (used in lead-time derivation), and BOM_CTO_ORDER_LINES_UPG.

Usage Notes

CTO_UPDATE_BOM_RTG_PK is not documented as referenced by any other APPS package, which indicates it is invoked either directly by concurrent programs (notably the CTO BOM/routing update program that calls UPDATE_BOMS_RTGS) or from order management processing logic during configuration validation and booking. Customers implementing CTO flows in 12.1.1 or 12.2.2 may call GET_MODEL_LEAD_TIME from custom code to surface lead-time information for configured items; the remaining routines are internal support functions and should be treated as private implementation. Because the package is AUTHID CURRENT_USER and depends on ONT_DEBUG_LEVEL, debugging output should be enabled only in non-production environments.