Results for “base_price”

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

Overview

OP_CNTR_DTL_VL is a validated Oracle EBS view owned by the APPS schema within the GML (Process Manufacturing Logistics) product family. It is described in the ETRM documentation as a "Control detail view," and it presents contract pricing detail information for items managed in a process manufacturing environment. The view joins item master data to contract detail data, exposing the full set of pricing attributes associated with a contract line together with the descriptive item number. Because it is maintained as a view rather than a table, it provides a read-only, always-current projection of the underlying contract pricing records, suitable for reporting, custom forms, concurrent programs, and integration interfaces that must not modify the base transactional data. The name suffix "VL" denotes a value-list style view, commonly employed in Oracle EBS to support LOV (list of values) definitions and inquiry-only screens where a denormalized, display-friendly result set is required. It is present and valid in both the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms: IC_ITEM_MST, the process manufacturing item master, and OP_CNTR_DTL, the contract detail table holding the pricing records. The driving table in the join is OP_CNTR_DTL, aliased P, with IC_ITEM_MST aliased I joined on ITEM_ID. The join is an outer join toward the item master (P.ITEM_ID = I.ITEM_ID(+)), meaning contract detail rows are retained even where no matching item master record exists. A filter predicate, NVL(I.DELETE_MARK, 0) = 0, excludes items marked for deletion while still permitting rows with a null delete mark. All columns are drawn from the two source objects without expression-based derivation; the view is essentially a straight projection with a single outer join and one filter.

Key Columns

• ITEM_NO — descriptive item number sourced from IC_ITEM_MST for display and lookup purposes.
• ITEM_ID, PRICE_ID, CONTRACT_ID, LINE_NO — keys tying the row to the item, the pricing record, and the parent contract line.
• BREAK_TYPE — identifies the basis on which the pricing line is broken or qualified, relevant to both value-list filtering and contract pricing logic.
• PRICE_TYPE, PRICE_CLASS, PRICE_UM, BASE_PRICE — the pricing classification, unit of measure, and base price for the contract detail.
• WHSE_CODE, QC_GRADE, FRTBILL_MTHD — warehouse, quality grade, and freight billing method qualifiers.
• TEXT_CODE, DELETE_MARK, TRANS_CNT — text reference, soft-delete flag, and transaction counter.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle flexfield attribute columns for descriptive or DFF-driven data.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include contract price inquiry, value-list population for pricing fields, and extraction of contract pricing for downstream reporting.

Retrieve pricing lines for a specific contract:
SELECT contract_id, line_no, item_no, break_type, price_type, base_price, price_um
FROM apps.op_cntr_dtl_vl
WHERE contract_id = :p_contract_id
ORDER BY line_no;

Value-list query filtered by break type:
SELECT item_no, price_id, break_type, base_price
FROM apps.op_cntr_dtl_vl
WHERE break_type = :p_break_type
AND NVL(delete_mark, 0) = 0;

Join to contract detail for reporting on items without a matching item master record (possible due to the outer join) and review audit metadata to detect recent pricing changes.