Search Results pmibv_burden_v

Overview

PMIBV_BURDEN_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It is registered as a VALID object and belongs to the PMI product family — Process Manufacturing Intelligence — which Oracle classifies as obsolete in release 12.1.1 and 12.2.2. The view presents burden, or overhead, costing detail records and is intended primarily for reporting, inquiry, and integration scenarios that require a denormalized, read-only projection of burden setup and transaction-level cost data.

The BV suffix follows the conventional Oracle naming pattern denoting a base or business view. Because the view is defined with the WITH READ ONLY clause, it cannot be used as a DML target; inserts, updates, and deletions must be directed against the underlying table. This makes PMIBV_BURDEN_V suitable for SELECT-based extraction, BI Publisher data templates, ad hoc queries, and interface programs that read burden costing information without modifying it.

Underlying Base Objects

The view is defined over a single base object: the table CM_BRDN_DTL, referenced through a synonym. The view text aliases this object as BURDEN and applies a single filter predicate:

• BURDEN.DELETE_MARK = 0 OR BURDEN.DELETE_MARK IS NULL — excludes logically deleted rows, so only active burden detail records are exposed.

The view also carries the read-only clause, reinforcing its role as a query-only artifact. Because the definition is a straightforward single-table projection with no joins, all columns map one-to-one to columns in CM_BRDN_DTL. No foreign key resolution is performed inside the view; the source comments label the ID columns under /* ID */ and the WHO columns separately, but do not resolve them to descriptive values.

Key Columns

The columns fall into four logical groups.

• Burden quantities and usage: BURDEN_QTY, BURDEN_USAGE, BURDEN_UM, BURDEN_FACTOR, ROLLOVER_IND, ITEM_QTY, and ITEM_UM describe the burden amount applied, the usage basis, its unit of measure, any conversion or application factor, the rollover indicator, and the associated item quantity and unit of measure.
• Identifiers: BURDENLINE_ID is the primary key of the underlying burden line and is the column most frequently referenced by users searching for "burdenline_id". ORGN_CODE, WHSE_CODE, ITEM_ID, RESOURCES, CALENDAR_CODE, PERIOD_CODE, COST_MTHD_CODE, COST_CMPNTCLS_ID, CMPNTCOST_ID, and COST_ANALYSIS_CODE identify the organization, warehouse, item, resource, calendar, period, costing method, cost component class, component cost, and cost analysis context for each line.
• WHO columns: LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_DATE, and CREATION_DATE provide audit trail information for each row.
• Filter column: DELETE_MARK is not projected by the view, but it governs which source rows appear.

Common Use Cases and Queries

Typical scenarios include extracting burden detail for a specific organization, period, or item; reconciling burden amounts against cost component classes; and joining burden lines to item or resource master data. The following query retrieves active burden lines for one organization and period:

• SELECT burdenline_id, orgn_code, item_id, resources, period_code, cost_mthd_code, burden_qty, burden_usage, burden_um FROM apps.pmibv_burden_v WHERE orgn_code = :orgn_code AND period_code = :period_code ORDER BY burdenline_id;
• To trace a single burden line by its identifier: SELECT * FROM apps.pmibv_burden_v WHERE burdenline_id = :burdenline_id;
• To aggregate burden by cost component class: SELECT cost_cmpntcls_id, SUM(burden_qty) FROM apps.pmibv_burden_v WHERE orgn_code = :orgn_code GROUP BY cost_cmpntcls_id;

Because PMI is obsolete in 12.1.1 and 12.2.2, usage of this view should be confirmed against current product direction, and any dependency should be documented as a legacy interface. Queries remain valid for as long as the underlying CM_BRDN_DTL table and synonym persist.