Search Results bom_copy_routing




Overview

The APPS.BOM_COPY_ROUTING package body provides the core PL/SQL logic used by Oracle E-Business Suite manufacturing applications to duplicate, select, and maintain routing and operation data for manufactured items. Routings define the sequence of operations, resources, departments, and skills required to build an assembly, and this package automates the otherwise labor-intensive task of copying an existing routing onto a new or revised item, or switching which routing version is designated primary or alternate within an organization.

Functionally, the package supports engineering and production workflows in Oracle Bills of Material and Work in Process. It is classified under the ETRM as an "OTHER" API rather than a public open interface, confirming that it is an internal utility package accessed primarily through standard EBS forms such as the Routings form and the Copy Routing form. The package preserves structural relationships across the routing hierarchy — operation sequences, operation networks, resources, resource setups, skills, and component operations — while also propagating descriptive flexfield data and attachments.

Key Procedures and Functions

The documented 13 procedures and functions cover three broad categories: routing copy, primary/alternate routing maintenance, and supporting utilities.

  • COPY_ROUTING — The primary entry point that duplicates a source routing to a target item or organization, transferring operations, resources, and associated detail records.
  • COPY_ROUTING_FOR_REVISED_ITEM — A variant of the copy routine tailored to revised item versions, ensuring the routing aligns with the new revision.
  • SWITCH_TO_PRIMARY_RTG — Designates an alternate routing as the primary routing for an item.
  • SWITCH_RTG_VALIDATE — Performs validation checks before a routing switch is committed, preventing conflicts.
  • SWITCH_COMMON_TO_PRIMARY_RTG and SWITCH_COMMON_TO_ALTERNATE_RTG — Manage transitions between common and primary or alternate routing designations.
  • COPY_ATTACHMENTS — Transfers attached documents associated with the source routing to the destination routing.
  • UPDATE_LAST_UPDATED_BY — Maintains audit columns on the affected routing rows.
  • GET_MESSAGE — Retrieves standardized messages for error reporting and user feedback.

Tables Accessed

The package reads and writes the principal routing tables through APPS synonyms, including BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_OPERATION_SEQUENCES_S, BOM_OPERATION_NETWORKS, and BOM_COMPONENT_OPERATIONS. Supporting master data is drawn from BOM_DEPARTMENTS, BOM_RESOURCES, BOM_RESOURCE_SETUPS, BOM_OPERATION_RESOURCES, BOM_OPERATION_SKILLS, BOM_SUB_OPERATION_RESOURCES, BOM_SETUP_TYPES, and CST_ACTIVITIES. Attachment handling relies on FND_ATTACHED_DOCUMENTS and FND_ATTACHED_DOCUMENTS2_PKG. Error conditions are logged to MTL_INTERFACE_ERRORS, and WIP_DISCRETE_JOBS and WIP_FLOW_SCHEDULES are checked where routing data intersects with active work orders.

Usage Notes

BOM_COPY_ROUTING is invoked principally from the Oracle Bills of Material Copy Routing form and related routing maintenance forms, where the "Copy Routing From" and "Copy Routing To" actions drive COPY_ROUTING. Standard EBS processes such as revised item creation and routing switch operations call the SWITCH_* procedures. Because the package depends on FND_API, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, and APP_EXCEPTION, it should only be called within a properly initialized EBS session where FND_GLOBAL is populated. Custom code referencing this package should treat it as an internal API, respect the calling sequence (validate, then switch or copy), and avoid direct DML on the underlying routing tables.