Results for “pricing_quantity_uom”

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

Overview

OEBV_ORDER_LINES is an APPS-owned database view within the Oracle E-Business Suite Order Management (ONT) module. It exposes a denormalized, report-friendly projection of sales order line data, drawing from the underlying OE_ORDER_LINES entity. The view is registered as VALID in both EBS 12.1.1 and 12.2.2, and is widely used as a read-only interface for reporting, ad hoc querying, and integration extracts where full access to the transactional order line table is either unnecessary or undesirable.

The view is particularly valuable because it resolves several coded attributes into their display meanings at the view layer. Lookup-based columns such as SOURCE_TYPE_CODE, FREIGHT_TERMS_CODE, BOOKED_FLAG, CANCELLED_FLAG, OPEN_FLAG, SHIPPABLE_FLAG, and FULFILLED_FLAG are presented through embedded OE_LOOKUPS join directives (the "_LA:" prefixes in the view text), producing human-readable MEANING values rather than raw codes. The view also embeds a "_DF:" descriptor for OE_LINE_PRICING_ATTRIBUTE, enabling pricing-attribute access against each line. For the searched term pricing_quantity_uom, the view exposes the PRICING_QUANTITY_UOM column alongside PRICING_QUANTITY and PRICING_DATE, making it a natural access point for pricing UOM analysis without navigating the full pricing attribute model.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: OE_ORDER_LINES, accessed through a SYNONYM in the APPS schema. The view text aliases this source as LINE, and every projected column originates from that alias. OEBV_ORDER_LINES therefore behaves as a thin, mostly column-selective layer over OE_ORDER_LINES, with the primary transformation being the resolution of lookup MEANING values and the inclusion of descriptive attribute references in place of raw foreign keys.

Because the view is defined over OE_ORDER_LINES through a synonym, it inherits that table's partitioning, indexing, and Multi-Org (ORG_ID) characteristics. No additional base tables are documented for this view; joins needed for lookup meanings are implied by the view text construct rather than being listed as separate referenced objects.

Key Columns

• LINE_ID / HEADER_ID / ORG_ID — Primary line, parent order header, and operating unit identifiers, essential for any join back to OE_ORDER_HEADERS_ALL or Multi-Org filtering.
• LINE_NUMBER, ORDERED_QUANTITY, ORDER_QUANTITY_UOM — The transactional quantity and its unit of measure.
• PRICING_QUANTITY, PRICING_QUANTITY_UOM, PRICING_DATE — The pricing basis quantity, its UOM, and the effective pricing date, directly relevant to searches on pricing_quantity_uom.
• UNIT_SELLING_PRICE, UNIT_LIST_PRICE, ORIGINAL_LIST_PRICE, PRICE_LIST_ID, AGREEMENT_ID — Pricing amounts and the pricing/list sources applied to the line.
• INVENTORY_ITEM_ID, SHIP_FROM_ORG_ID, ITEM_TYPE_CODE, LINE_CATEGORY_CODE — Item and fulfillment context.
• SCHEDULE_STATUS_CODE, SCHEDULE_SHIP_DATE, PROMISE_DATE, REQUEST_DATE, ACTUAL_SHIPMENT_DATE, FULFILLMENT_DATE — Scheduling and fulfillment milestones.
• SHIPPED_QUANTITY, FULFILLED_QUANTITY, ACCEPTED_QUANTITY, CANCELLED_QUANTITY, INVOICED_QUANTITY — Quantity lifecycle measures spanning shipment, fulfillment, receipt, cancellation, and billing.
• FLAG MEANING COLUMNS — BOOKED, CANCELLED, OPEN, SHIPPABLE, and FULFILLED flags resolved to their lookup meanings.
• AUDIT COLUMNS — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY for change tracking.

Common Use Cases and Queries

The view supports pricing audits, order-line extracts, and fulfillment reporting. A typical query isolating pricing UOM mismatches follows:

• SELECT line_id, ordered_quantity, order_quantity_uom, pricing_quantity, pricing_quantity_uom, pricing_date FROM apps.oebv_order_lines WHERE org_id = :p_org AND order_quantity_uom <> pricing_quantity_uom;
• SELECT header_id, line_number, unit_selling_price, unit_list_price FROM apps.oebv_order_lines WHERE price_list_id = :p_price_list AND booked_flag = 'Yes';
• SELECT line_id, shipped_quantity, fulfilled_quantity, invoiced_quantity FROM apps.oebv_order_lines WHERE schedule_status_code = 'SHIPPED';

Because flag columns from the view may already carry resolved meanings, predicates on those columns should use the lookup meaning text rather than the underlying Y/N code. All access should reside in a reporting or read-only responsibility, with ORG_ID always supplied to respect Multi-Org security.