Results for “resource_usage”

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

Overview

GMF_LOT_COST_BURDENS is a Process Manufacturing Financials (GMF) transaction table that stores burden detail associated with lot-costed items. In Oracle EBS 12.1.1 and 12.2.2, process manufacturing operations frequently apply burden — overhead, resource absorption, or additional cost components — to inventory lots after the primary lot cost has been established. This table captures those burden components at a granular level, allowing costs to be analyzed, adjusted, and reconciled independently of the base lot cost record.

The table resides in the GMF schema, holds 67 documented columns, and is classified VALID in the ETRM 12.2.2 physical schema. Its heuristic Data Vault classification is standalone, meaning the mined foreign-key structure does not clearly identify it as a hub, link, or satellite in a conventional dimensional model. From a modeling standpoint, it is best treated as a satellite-like detail table: it carries descriptive burden attributes tied to a transaction context (organization, item, lot, cost method) rather than defining an independent business entity. The only documented foreign key is COST_TYPE_ID, which references CST_COST_TYPES.

Key Information Stored

The single documented unique index, GMF_LOT_COST_BURDENS_U1, is defined on LOT_BURDEN_LINE_ID, making that column the surrogate primary key and the strongest business-key candidate. The remaining columns supply the operational context and burden measurements:

• LOT_BURDEN_LINE_ID — surrogate primary key for each burden line.
• ORGN_CODE / ORGANIZATION_ID — organization context for the burden record.
• ITEM_ID / INVENTORY_ITEM_ID — the burdened item, in both legacy and inventory-referenced forms.
• LOT_ID / LOT_NUMBER — the specific lot against which burden is applied.
• WHSE_CODE — warehouse in which the lot resides.
• COST_MTHD_CODE — costing method governing how burden is calculated.
• COST_TYPE_ID — foreign key to CST_COST_TYPES, identifying the burden cost type.
• COST_CMPNTCLS_ID — cost component class to which the burden is assigned.
• START_DATE / END_DATE — effective period of the burden.
• RESOURCES / RESOURCE_USAGE / RESOURCE_UM / RESOURCE_COUNT — resource consumed and its quantity/UOM.
• BURDEN_FACTOR — rate or multiplier applied to derive the burden amount.
• APPLIED_IND — flag indicating whether the burden has been applied.
• LOT_COST_DETAIL_ID — linkage to the underlying lot cost detail.
• DELETE_MARK — soft-delete indicator used by Oracle's concurrent processing.

Common Use Cases and Queries

Typical scenarios include burden cost analysis by lot, reconciliation of applied versus pending burdens, and reporting on resource absorption by organization or warehouse.

• Identify unapplied burdens: SELECT LOT_BURDEN_LINE_ID, LOT_ID, COST_TYPE_ID FROM GMF_LOT_COST_BURDENS WHERE APPLIED_IND = 'N' AND DELETE_MARK = 0;
• Burden by organization and period: filter on ORGN_CODE plus START_DATE/END_DATE ranges.
• Join to CST_COST_TYPES on COST_TYPE_ID to resolve cost type descriptions.
• Aggregate BURDEN_FACTOR or RESOURCE_USAGE by ITEM_ID and LOT_ID for cost rollup reporting.
• Reconcile against LOT_COST_DETAIL_ID to trace burden back to its source lot cost.

Related Objects

• CST_COST_TYPES — referenced via COST_TYPE_ID.
• GMF_LOT_COST_DETAIL — linked through LOT_COST_DETAIL_ID.
• MTL_SYSTEM_ITEMS_B — resolves ITEM_ID / INVENTORY_ITEM_ID.
• MTL_LOT_NUMBERS — resolves LOT_ID / LOT_NUMBER.
• ORG_ORGANIZATION_DEFINITIONS — maps ORGN_CODE / ORGANIZATION_ID.