Search Results burdenline_id

Overview

The CM_BRDN_DTL table is a core transactional data object within Oracle E-Business Suite Process Manufacturing Financials (GMF). It serves as the detailed repository for burden costs, also known as overhead costs, which are applied to manufactured items. The table's primary role is to store the granular, calculated overhead amounts associated with specific cost components, items, warehouses, and accounting periods. This data is fundamental to achieving accurate product costing in process manufacturing environments, enabling the system to roll up total item costs that include both direct material/labor and allocated indirect expenses. Its existence is critical for cost analysis, inventory valuation, and profitability reporting within the GMF module.

Key Information Stored

The table stores burden cost details keyed by several business dimensions. The primary identifier is the BURDENLINE_ID. The table's unique key (CM_BRDN_DTL_U1) highlights the critical combination of attributes that define a specific burden record: organization (ORGN_CODE), warehouse (WHSE_CODE), item (ITEM_ID), resource (RESOURCES), accounting calendar and period (CALENDAR_CODE, PERIOD_CODE), costing method (COST_MTHD_CODE), cost component class (COST_CMPNTCLS_ID), and cost analysis code (COST_ANALYSIS_CODE). Essential data columns include BURDEN_AMOUNT, which holds the calculated monetary value of the overhead, and the associated units of measure for both the burden and the item (BURDEN_UM, ITEM_UM). The table also links to descriptive flexfields via TEXT_CODE for customizable data capture.

Common Use Cases and Queries

A primary use case is the analysis of overhead costs for a specific item in a given period to understand cost drivers. Financial analysts may query this table to reconcile applied burden costs to general ledger accounts or to investigate cost variances between periods. A typical reporting query would join CM_BRDN_DTL to master tables like IC_ITEM_MST for item descriptions and CM_CMPT_MST for component class details. For example, to retrieve the total burden cost for an item in a warehouse for the current period, one might use a SQL pattern such as: SELECT item_id, SUM(burden_amount) FROM gmf.cm_brdn_dtl WHERE orgn_code = :p_org AND whse_code = :p_whse AND period_code = :p_period GROUP BY item_id;. This data is also foundational for standard GMF reports detailing item cost breakdowns.

Related Objects

The CM_BRDN_DTL table maintains extensive foreign key relationships with master and transactional tables across the GMF, Inventory, and Common application foundations. Key documented relationships include:

• Costing Masters: Links to CM_CMPT_MST (Cost Component), CM_MTHD_MST (Costing Method), and CM_ALYS_MST (Cost Analysis Code) to define the costing framework.
• Inventory Masters: References IC_ITEM_MST (Item) and IC_WHSE_MST (Warehouse) to identify the charged entity and location.
• Calendar & Organization: Joins to CM_CLDR_DTL (Accounting Calendar Period) and SY_ORGN_MST (Organization) for the financial and structural context.
• Resources & Units: Connected to CR_RSRC_MST (Resources) for the overhead source and SY_UOMS_MST (Units of Measure) for the burden and item UOMs.
• Component Details: Relates to CM_CMPT_DTL via CMPNTCOST_ID for detailed component cost data.
• Descriptive Flexfields: References CM_TEXT_HDR for flexible attribute data.

These relationships ensure referential integrity and enable comprehensive joins for reporting and system processes.