Results for “resource_units”

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

Overview

MSC_ST_BOR_REQUIREMENTS is a staging (interface) table in the MSC schema owned by Oracle Advanced Supply Chain Planning. Its documented purpose is to hold inbound data that the collection program validates and processes before transferring it into the base planning table MSC_BOR_REQUIREMENTS. It is not a transactional or user-facing object; it is a transient landing area through which bill-of-resources resource requirement records flow during a data collection run, after which successfully validated rows are promoted into the production planning repository.

The ETRM metadata labels this object's heuristic Data Vault classification as standalone, meaning that structurally it is mined as neither a hub, link, nor satellite because no foreign-key relationships to other staging objects are defined. From a modeling perspective, this is best treated as a raw staging entity—effectively a load buffer—rather than a durable hub or satellite. The single documented foreign-key relationship is DEPARTMENT_ID referencing BOM_DEPARTMENTS, which is an outbound reference to a base EBS table rather than an intra-vault relationship.

Key Information Stored

The table carries 29 documented columns in the 12.2.2 schema. The most operationally significant are:

• BILL_OF_RESOURCES – the bill-of-resources identifier tying the requirement row to a BOM definition.
• ORGANIZATION_ID – the inventory/planning organization in which the resource requirement applies.
• ASSEMBLY_ITEM_ID and SOURCE_ITEM_ID – the parent assembly and the source item driving the requirement.
• RESOURCE_ID – the resource for which the requirement is defined.
• DEPARTMENT_ID – the department responsible; this is the column that carries the documented FK to BOM_DEPARTMENTS.
• OPERATION_SEQUENCE_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM – the operation and resource sequencing that positions the requirement within the routing.
• RESOURCE_UNITS, RESOURCE_DEPARTMENT_HOURS, BASIS – the quantity demanded, its department-hours equivalent, and the basis on which the requirement is expressed.
• ASSEMBLY_USAGE, SETBACK_DAYS, ORIGINATION_TYPE, LINE_ID – usage quantity, lead-time offset, origin of the record, and line identifier.
• DELETED_FLAG – soft-delete indicator used by the collection program.
• Interface/audit columns: SR_TRANSACTION_ID, SR_INSTANCE_ID, REFRESH_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and the standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN).

No surrogate primary-key column is documented in the supplied metadata; SR_TRANSACTION_ID plus SR_INSTANCE_ID and REFRESH_ID function as the practical business-key candidates for identifying a staged row within a collection cycle.

Common Use Cases and Queries

Typical usage centers on diagnosing collection failures or reconciling staged volumes against the target planning table. A common pattern counts rows awaiting processing by refresh:

• Identify stale or failed loads: SELECT REFRESH_ID, COUNT(*) FROM MSC.MSC_ST_BOR_REQUIREMENTS GROUP BY REFRESH_ID;
• Trace a requirement back to its department: SELECT r.BILL_OF_RESOURCES, r.RESOURCE_ID, d.DEPARTMENT_CODE FROM MSC.MSC_ST_BOR_REQUIREMENTS r JOIN BOM.BOM_DEPARTMENTS d ON r.DEPARTMENT_ID = d.DEPARTMENT_ID;
• Find soft-deleted rows still present after a run using DELETED_FLAG.
• Compare staged versus final counts against MSC_BOR_REQUIREMENTS for the same REFRESH_ID to confirm the collection program promoted all valid records.

Related Objects

• MSC_BOR_REQUIREMENTS – the target table this staging object feeds; records are validated and promoted into it.
• BOM_DEPARTMENTS – referenced via MSC_ST_BOR_REQUIREMENTS.DEPARTMENT_ID → BOM_DEPARTMENTS.DEPARTMENT_ID, the only documented FK.
• MSC_ST_* staging tables – sibling interface tables populated by the same collection program.
• MSC collection program / MSC_COLLECT package – the process that reads and validates these rows.
• Standard WHO and planning collection views used for monitoring refresh runs in Advanced Supply Chain Planning.