Results for “cm_brdn_dtl”

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

Overview

CM_BRDN_DTL is the Cost Burden Details table owned by the GMF schema in Oracle Process Manufacturing Financials (OPM Financials). It stores the burden, or overhead, costs that are applied to an item within a specific organization, warehouse, period, and cost method. Each row represents a discrete burden line that ties a resource to a burden usage quantity, a conversion factor, and the cost component class under which the burden is absorbed into the item's cost. In Oracle EBS 12.1.1 and 12.2.2 this table functions as the transactional ledger of applied overhead: it is read by the OPM cost rollup and burden absorption processes and is the source of the overhead element in frozen and perpetual item costs.

The heuristic Data Vault classification mined from the foreign-key structure is link. This is a modeling suggestion only: CM_BRDN_DTL resolves a many-to-many association among items, resources, organizations, warehouses, calendars, periods, and cost methods, and is therefore best treated as a link entity rather than as a hub or satellite.

Key Information Stored

The surrogate primary key is BURDENLINE_ID, enforced by the index CM_BRDN_DTL_PK. A secondary unique index, CM_BRDN_DTL_U1, spans ORGN_CODE, WHSE_CODE, ITEM_ID, RESOURCES, CALENDAR_CODE, PERIOD_CODE, COST_MTHD_CODE, and COST_CMPNTCLS_ID; these columns constitute the documented business-key candidate that guarantees one burden line per item/resource/period/cost method combination. The most operationally significant columns are:

• BURDENLINE_ID — surrogate primary key and parent for downstream references.
• ORGN_CODE, WHSE_CODE, ITEM_ID — the organizational and inventory context of the burdened item.
• RESOURCES — the resource whose usage drives the burden charge.
• CALENDAR_CODE, PERIOD_CODE — the cost period in which the burden is effective.
• COST_MTHD_CODE, COST_CMPNTCLS_ID — the cost method and cost component class that classify the overhead.
• BURDEN_QTY, BURDEN_UM, BURDEN_FACTOR — the burden basis quantity, its unit of measure, and the applied conversion factor.
• ITEM_QTY, ITEM_UM — the item quantity and unit over which the burden is spread.
• ROLLOVER_IND, TRANS_CNT — rollover flag and transaction counter used by the costing processes.
• COST_ANALYSIS_CODE — links the line to a cost analysis definition in CM_ALYS_MST.
• DELETE_MARK, TEXT_CODE — logical deletion flag and the text block reference in CM_TEXT_HDR.
• Standard audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include burden cost analysis by period, reconciliation of absorbed overhead against the cost component class, and extraction of burden rates for external reporting. A representative query joining the business-key columns to the item master is:

• SELECT d.burdenline_id, d.orgn_code, d.whse_code, d.item_id, d.resources, d.period_code, d.burden_qty, d.burden_factor, d.burden_um
• FROM gmf.cm_brdn_dtl d
• WHERE d.delete_mark = 0
• AND d.orgn_code = :orgn
• AND d.period_code = :period;

To surface the item description, join IC_ITEM_MST on ITEM_ID and ORGANIZATION_ID. To report by overhead class, join CM_CMPT_MST on COST_CMPNTCLS_ID. To validate that a burden was posted in the correct accounting window, join CM_CLDR_DTL on CALENDAR_CODE and PERIOD_CODE. Rollup and absorption reports should filter on DELETE_MARK and join CST_COST_TYPES on COST_TYPE_ID when cost-type segregation is required.

Related Objects

CM_BRDN_DTL sits at the intersection of item, resource, organization, and cost configuration data. The most significant related objects are:

• IC_ITEM_MST / IC_ITEM_MST_B — joined on ITEM_ID; the burdened item definition.
• CR_RSRC_MST / CR_RSRC_MST_B — joined on RESOURCES; the resource whose usage incurs the burden.
• CM_ALYS_MST — joined on COST_ANALYSIS_CODE; the cost analysis definition.
• CM_CMPT_MST / CM_CMPT_MST_B — joined on COST_CMPNTCLS_ID; the overhead cost component class.
• CM_MTHD_MST — joined on COST_MTHD_CODE; the cost method in effect.
• CM_CLDR_DTL — joined on CALENDAR_CODE and PERIOD_CODE; the costing calendar period.
• CM_CMPT_DTL — joined on CMPNTCOST_ID; the component cost detail driving the burden.
• CM_TEXT_HDR — joined on TEXT_CODE; the descriptive text block.
• IC_WHSE_MST — joined on WHSE_CODE; the warehouse context.
• SY_ORGN_MST / SY_ORGN_MST_B — joined on ORGN_CODE; the organization definition.

SY_UOMS_MST supplies unit-of-measure validation for both BURDEN_UM and ITEM_UM, and CST_COST_TYPES is referenced through COST_TYPE_ID. Because CM_BRDN_DTL is a child of the item and resource masters, any purge or copy of a burden line must respect the referential constraints defined by these foreign keys.