Search Results burden_factor

Overview

PMIFV_BURDEN_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PMI – Process Manufacturing Intelligence product family. It exposes costing information for burden (overhead) details, presenting the rows stored in the burden detail table alongside resolved descriptive attributes from the process manufacturing calendar tables. The view carries the object status VALID in both Oracle EBS 12.1.1 and 12.2.2 and is defined with a WITH READ ONLY clause, so it supports query and reporting access exclusively. Its principal role is to provide a flattened, security-filtered projection of burden factor data for use in cost analysis, overhead reporting, and downstream integration. Users and integrators searching for the term "burden_factor" will most often encounter this view because the BURDEN_FACTOR column is one of its central regular attributes.

The view does not store data of its own. Every row is derived at runtime from the underlying burden and calendar tables, which means results always reflect the current transactional state of burden definitions rather than a materialized snapshot.

Underlying Base Objects

The view text is defined over the following documented base objects, all referenced through APPS synonyms:

• CM_BRDN_DTL – the burden detail table that supplies the primary burden attributes, including quantity, usage, unit of measure, burden factor, rollover indicator, item quantity, and item unit of measure, together with the identifying and costing keys.
• CM_CLDR_HDR – the calendar header table, outer-joined on CALENDAR_CODE to supply the calendar description.
• CM_CLDR_DTL – the calendar detail table, outer-joined on both CALENDAR_CODE and PERIOD_CODE to supply the period description.
• SY_ORGN_MST – the organization master table, referenced in a subquery that applies organization-level security.
• PMI_SECURITY_PKG – the security package whose SHOW_RECORD function governs which organizations a given user may see.

The joins to CLDRHDR and CLDRDTL use the Oracle outer-join syntax (+), so burden rows are retained even when no matching calendar header or detail record exists. A filter on DELETE_MARK restricts output to active (non-deleted) burden lines. The organization security predicate permits rows where ORGN_CODE is null or where PMI_SECURITY_PKG.SHOW_RECORD returns 'TRUE' for the organization, effectively enforcing row-level access by responsibility or user.

Key Columns

• BURDEN_FACTOR – the overhead burden rate or multiplier applied during costing; the column most directly associated with the "burden_factor" search term.
• BURDEN_QTY, BURDEN_USAGE, BURDEN_UM – the burden quantity, its usage basis, and the unit of measure in which the burden is expressed.
• ROLLOVER_IND – indicator controlling whether unused burden is carried forward to subsequent periods.
• ITEM_QTY, ITEM_UM – the item quantity and unit of measure against which the burden is applied.
• BURDENLINE_ID – the primary identifier for the burden detail line.
• ORGN_CODE, WHSE_CODE, ITEM_ID – organization, warehouse, and item keys that scope the burden record.
• RESOURCES – the resource or resource set to which the burden relates.
• CALENDAR_CODE, CALENDAR_DESCRIPTION, PERIOD_CODE, PERIOD_DESCRIPTION – calendar and period identifiers with their resolved descriptions.
• COST_MTHD_CODE, COST_CMPNTCLS_ID, CMPNTCOST_ID, COST_ANALYSIS_CODE – costing method, cost component class, component cost, and cost analysis identifiers linking the burden to the cost rollup.
• LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_DATE, CREATION_DATE – standard WHO audit columns.

Common Use Cases and Queries

The view is typically used to reconcile burden factors by organization, item, and period, to feed cost analysis extracts, and to verify that overhead rates are correctly defined before a cost rollup. Because security is embedded, reports built on the view automatically respect organization restrictions without additional predicates.

A representative query retrieving active burden factors for a specific organization and calendar period:

• SELECT burdenline_id, orgn_code, item_id, calendar_code, period_code, burden_factor, burden_qty, burden_um, cost_mthd_code FROM apps.pmifv_burden_v WHERE orgn_code = :p_orgn_code AND period_code = :p_period_code ORDER BY item_id;

An aggregate query summarizing burden factors by cost component class:

• SELECT cost_cmpntcls_id, cost_mthd_code, COUNT(*) burden_lines, AVG(burden_factor) avg_factor FROM apps.pmifv_burden_v GROUP BY cost_cmpntcls_id, cost_mthd_code;

A query combining burden attributes with resolved calendar descriptions:

• SELECT b.item_id, b.calendar_code, b.calendar_description, b.period_code, b.period_description, b.burden_factor FROM apps.pmifv_burden_v b WHERE b.rollover_ind = 'Y';

All queries should respect the read-only nature of the view; inserts, updates, and deletes against PMIFV_BURDEN_V are not permitted and must be directed to the base burden tables through standard Oracle EBS APIs.