Results for “bom_copy_bill”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.BOM_COPY_BILL is the Bill of Material copy package body responsible for replicating engineering and manufacturing bill structures across items, organizations, and revision levels within Oracle E-Business Suite 12.1.1 and 12.2.2. The package supports the full matrix of copy directions: BOM to BOM, BOM to ENG, ENG to ENG, and ENG to BOM, each governed by the direction argument documented in the header. Copy scope is controlled by the display_option parameter, which distinguishes between copying all components, only the current effective structure, or the current structure plus future-dated changes. The package also implements Transfer To Multiple Orgs (TTM), introduced in Release 12 to allow a bill structured in one source organization to be assigned and copied into multiple destination organizations.

Historically, the package has been extended to handle CTO-relevant attributes and additional operation rows. The header comments document that changes for bug 2740820 introduced new BOM_INVENTORY_COMPONENTS columns and the plan_level attribute into the copy path, and that an overloaded COPY_BILL signature was added in 2003 to permit copying of specific components, reference designators, and substitute components rather than an entire bill.

Key Procedures and Functions

COPY_BILL is the primary entry point, orchestrating the duplication of bill headers, components, operations, reference designators, and substitutes. Supporting functions validate target state before or during the copy: REVISION_EXISTS, GET_REVISION, GET_MAX_MINORREV, and GET_MINOR_REV_CODE resolve revision and minor revision values; GET_ITEM_EXISTS_IN, GET_STRUCTURE_EXISTS_IN, and GET_COMMON_STRUCTURE_EXISTS_IN confirm whether an item or structure already exists in a destination organization or is shared across organizations.

Assignment and TTM processing is handled by ASSIGN_ITEMS_TO_COPY_TO_ORG, GET_ASSIGN_ITEMS_IN, GET_COPY_STRUCTURES_IN, GET_COMMON_STRUCTURES_IN, and GET_ORG_LIST_FOR_HIERARCHY, which together resolve the destination organization list and the structures eligible for copy. PURGE_PROCESSED_COPY_REQUESTS and PURGE_PROCESSED_REQUEST_ERRORS perform housekeeping on the copy request staging tables. Message retrieval is provided by GET_MESSAGE, GET_CNT_MESSAGE, GET_COMP_TYPE_RULE_MESSAGE, and BILL_GET_MSG_INFO, while GET_COMPONENT_PATH resolves component hierarchy paths and UPDATE_CREATED_BY maintains the audit column on staged records.

Tables Accessed

The package reads and writes across the BOM structure schema. BOM_STRUCTURES_B and BOM_COMPONENTS_B hold the bill header and component base rows, with BOM_INVENTORY_COMPONENTS_S storing inventory component detail including the CTO columns added for bug 2740820. BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_COMPONENT_OPERATIONS, and BOM_COMPONENT_OPERATIONS_S carry routing and operation data, including the additional operations supported since the 2001 one-to-many enhancement. BOM_REFERENCE_DESIGNATORS and BOM_SUBSTITUTE_COMPONENTS are maintained by the overloaded copy path. BOM_DEPENDENT_DESC_ELEMENTS stores dependent descriptive element definitions.

The TTM workflow uses BOM_COPY_ORGANIZATION_LIST, BOM_COPY_STRUCTURE_REQUEST, and BOM_COPY_STRUCTURE_ACTIONS to stage destination organizations, pending copy requests, and per-structure actions. EGO_DATA_LEVEL_B and EGO_MINOR_REVISIONS provide the data level and minor revision context required for revision-aware copies.

Usage Notes

BOM_COPY_BILL is not typically called directly by end users; it is invoked by the Bill of Material copy forms (including the Copy Bill and Transfer to Multiple Organizations flows) and by concurrent programs that bulk-process copy requests recorded in BOM_COPY_STRUCTURE_REQUEST. The ETRM record notes the package is referenced by five other packages, confirming its role as a shared service rather than a terminal API.

The option_class search term relates to copy-option classification semantics: callers distinguish whole-structure copies from selective copies of components, reference designators, or substitutes, and the display_option value determines whether future-dated changes are included. Custom code invoking COPY_BILL must supply valid from/to organization, sequence, item, alternate, revision date, user, and direction values, and should call the purge procedures afterward to prevent accumulation of processed request and error rows.