Search Results update_last_updated_by

Overview

APPS.BOM_COPY_ROUTING is a private PL/SQL package within the Oracle E-Business Suite Bills of Material product (BOM). It provides the programmatic infrastructure for copying manufacturing routing definitions between items, organizations, and routing revisions, and for managing the promotion and validation of routing primary/alternate designations. The package is classified as an OTHER API under the BOM product and carries the display name Routing Copy. Its lifecycle status is recorded as active, and it is scoped to the business entity BOM_MFG_ROUTING. The header information identifies the original source file as BOMCPYRS.pls, with copyright dating to 1995 and the most recent documented revision at version 120.10 (17-May-2006). A note in the header records that an overloaded procedure was added on 30-Jun-2005 to support routing copy in the context of an ECO (Engineering Change Order).

Functionally, the package encapsulates the copying logic used when a routing must be reproduced from a source item/organization to a destination, including copy-mode selection (current, current plus future, or all), directional copy between BOM and engineering contexts, and alternate designator handling. It also exposes routines for switching a routing to primary status and validating that switch.

Key Procedures and Functions

The documented interface exposes thirteen callable units. The principal routine is COPY_ROUTING, which copies a routing from a specified source sequence, item, and organization to a destination, honoring copy display options, direction of copy, destination alternate, and revision date, and returning error code and message outputs. An overload added in 2005 supports the same operation within an ECO context.

• COPY_ROUTING — copies a routing between items, organizations, or revisions; the core routine of the package.
• COPY_ROUTING_FOR_REVISED_ITEM — variant that copies routing data for an item revision, typically invoked during engineering change processing.
• SWITCH_TO_PRIMARY_RTG — promotes the currently designated routing to primary status.
• SWITCH_RTG_VALIDATE — validates preconditions before a routing may be switched, returning any error condition.
• SWITCH_COMMON_TO_PRIMARY_RTG — performs the switch of a common routing to primary.
• SWITCH_COMMON_TO_ALTERNATE_RTG — switches a common routing to an alternate designator.
• COPY_ATTACHMENTS — copies attached documents associated with the routing.
• GET_MESSAGE — retrieves the message text corresponding to a returned error code.
• UPDATE_LAST_UPDATED_BY — maintains the audit LAST_UPDATED_BY column on affected records.

Parameter signatures are not reproduced here; callers should obtain the exact specification from the installed package header.

Tables Accessed

The package reads and writes the core BOM routing tables through APPS synonyms. BOM_OPERATIONAL_ROUTINGS holds the routing header, while BOM_OPERATION_SEQUENCES and its _S (shadow) companion store operation sequence lines. BOM_OPERATION_RESOURCES, BOM_OPERATION_SKILLS, BOM_SUB_OPERATION_RESOURCES, and BOM_RESOURCE_SETUPS carry resource, skill, and setup requirements. BOM_COMPONENT_OPERATIONS and BOM_OPERATION_NETWORKS link components and operation dependencies. BOM_DEPARTMENTS, BOM_RESOURCES, and BOM_SETUP_TYPES supply reference definitions, and CST_ACTIVITIES links routing operations to cost activities. FND_ATTACHED_DOCUMENTS supports attachment copying, and MTL_INTERFACE_ERRORS is used to record interface-level errors raised during processing.

Usage Notes

Because the package is marked @rep:scope private, it is not intended as a published, supported public API; nevertheless, the Oracle BOM forms and concurrent programs invoke it directly. Typical invocation points include the Routings form when a user copies a routing to another item or organization, engineering change workflows that must propagate routing to a revised item, and the switch-to-primary action. Custom code that calls these routines should treat the interface as subject to change between releases, wrap calls in exception handling, and inspect the returned error code and message rather than assuming silent success. Two other packages reference this package, confirming its role as a shared utility for routing maintenance within BOM.