Results for “bom_op_resources_archive”

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

Overview

BOM_OP_RESOURCES_ARCHIVE is a table in the Bills of Material (BOM) schema of Oracle E-Business Suite, documented as the archive of deleted resources on operations. In the manufacturing model, a routing operation may carry one or more resources — labor, machine, or outside-processing resources — that define the capacity and cost consumed during production. When a resource assignment is removed from an operation, the corresponding row is not physically discarded; instead it is preserved in BOM_OP_RESOURCES_ARCHIVE so that historical cost rollups, audit trails, and change-history reporting remain complete. This makes the table a historical companion to BOM_OPERATION_RESOURCES, holding rows that once represented active resource requirements.

Because the archive preserves the full column set of the operational resource record, it retains scheduling attributes, usage rates, charge types, and descriptive flexfields exactly as they existed at deletion time. Under the heuristic Data Vault classification supplied in the metadata, the object is tagged as standalone; from a modeling perspective, this suggests treating it as a satellite-like historical record whose parent hub would be the operation sequence identified by OPERATION_SEQUENCE_ID, with RESOURCE_SEQ_NUM acting as a degenerate sequence attribute rather than a true foreign key to an active entity.

Key Information Stored

The primary key BOM_OP_RESOURCES_ARCHIVE_PK is composed of two columns, OPERATION_SEQUENCE_ID and RESOURCE_SEQ_NUM, which together form the surrogate identifier carried over from the source operation-resource assignment. OPERATION_SEQUENCE_ID identifies the routing operation from which the resource was removed, while RESOURCE_SEQ_NUM provides the ordering of the resource within that operation.

• RESOURCE_ID — references the resource definition that was assigned to the operation.
• ACTIVITY_ID — the activity used for cost or capacity calculation associated with the resource.
• ASSIGNED_UNITS and USAGE_RATE_OR_AMOUNT — the number of resource units assigned and the consumption rate or amount per unit.
• USAGE_RATE_OR_AMOUNT_INVERSE — the reciprocal form of the usage rate, used when the resource is expressed on an inverse basis.
• BASIS_TYPE and STANDARD_RATE_FLAG — control whether the usage is item- or lot-based and whether the standard rate applies.
• SCHEDULE_FLAG and SCHEDULE_SEQ_NUM — determine whether the resource participates in scheduling and its scheduling order.
• RESOURCE_OFFSET_PERCENT — the offset applied when scheduling the resource relative to the operation start.
• AUTOCHARGE_TYPE — governs whether and how the resource is automatically charged during costing.
• SUBSTITUTE_GROUP_NUM — groups substitutable resources so that only one from each group is consumed.
• CHANGE_NOTICE and ACD_TYPE — the engineering change order reference and change type associated with the deletion.
• SETUP_ID — the only documented foreign key, joining to BOM_SETUP_TYPES for setup-related resource definitions.
• ORIGINAL_SYSTEM_REFERENCE — the identifier of the source system record, supporting data migration and interface traceability.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — the concurrent program context that last touched the row.

Common Use Cases and Queries

Cost accountants and manufacturing engineers query this table to reconstruct the resource structure of a routing as it existed before a change. A typical audit query joins the archive to BOM_OPERATION_RESOURCES or BOM_OPERATIONS by OPERATION_SEQUENCE_ID to compare deleted resources against their surviving counterparts. A change-history report filters by CHANGE_NOTICE or ACD_TYPE to list every resource removed under a given engineering change order. Reconciliation queries use ORIGINAL_SYSTEM_REFERENCE to trace migrated records back to a source system, and program-attribution queries use the REQUEST_ID and PROGRAM_ID columns to identify the concurrent process that performed the deletion.

Related Objects

• BOM_SETUP_TYPES — referenced through SETUP_ID, providing the setup-type definition for setup resources.
• BOM_OPERATION_RESOURCES — the active operational table from which archived rows originate; joins on OPERATION_SEQUENCE_ID and RESOURCE_SEQ_NUM.
• BOM_OPERATIONS — supplies operation context through OPERATION_SEQUENCE_ID.
• BOM_DEPARTMENTS — defines the department owning the operation and its resources.
• BOM_RESOURCES — the resource master referenced by RESOURCE_ID.
• BOM_OP_RESOURCES_ARCHIVE_PK — the primary key constraint enforcing uniqueness of OPERATION_SEQUENCE_ID with RESOURCE_SEQ_NUM.