Search Results oe_prn_order_lines_v




Overview
Explore in AI Chat

Overview

OE_PRN_ORDER_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the ONT (Order Management) product family and is documented in ETRM as VALID. Its stated purpose is to supply line-level details required for printing a sales order — for example, the printed order acknowledgement, pick ticket, or packing slip. The view consolidates order line attributes, item identification, pricing, dates, and shipping information into a single denormalized row set that a report or concurrent program can consume without re-implementing the underlying decode and formatting logic.

Because it is a view and not a table, OE_PRN_ORDER_LINES_V stores no data. It is a read-only projection over the Order Management transaction tables, enriched with lookups, translated descriptions, and calls to several PL/SQL packages that perform currency formatting, line-number concatenation, and discount derivation. This makes it equally suitable for Oracle Reports, BI Publisher, custom concurrent programs, and ad hoc SQL, and it insulates report authors from the physical column changes across the 12.1.3 and 12.2.x code lines.

Underlying Base Objects

The documented referenced objects show that the view is anchored on OE_ORDER_HEADERS_ALL (alias H) and OE_ORDER_LINES_ALL (alias L), which supply the header and line transaction data respectively. Translated and descriptive attributes are resolved through MTL_SYSTEM_ITEMS_TL and MTL_SYSTEM_ITEMS_KFV for item descriptions and concatenated flexfield segments, MTL_CUSTOMER_ITEMS and MTL_CROSS_REFERENCES for customer item numbers, and MTL_UNITS_OF_MEASURE_TL for the unit of measure name. Transaction type context comes from OE_TRANSACTION_TYPES_ALL, while payment and agreement context come from RA_TERMS_TL, RA_RULES, OE_AGREEMENTS_TL, and OE_BLANKET_HEADERS_ALL.

Several package calls are embedded directly in the view definition: OE_ORDER_MISC_PUB.GET_CONCAT_LINE_NUMBER builds the printable line number; FND_CURRENCY.SAFE_GET_FORMAT_MASK supplies the currency format mask for price columns; OE_OE_TOTALS_SUMMARY.GET_DISCOUNT derives the discount amount; and OE_SYS_PARAMETERS and OE_TOTALS_GRP provide system-level and totals-grouping behavior. Each of these base objects is a synonym or package in APPS, so the view resolves entirely within the APPS schema.

Key Columns

The view exposes identifiers and descriptive columns that map directly to printed document fields:

Common Use Cases and Queries

The principal use case is feeding a sales order print report, where the view provides one row per order line already decoded for display. Secondary uses include reconciliation of pricing and discount values, verification of shipped quantities and dates, and data extraction for downstream document generation. A typical query filters by header and organization:

SELECT line, item_number, item_description, ordered_quantity, order_quantity_uom, unit_selling_price, discount, promise_date, ship_to_org_id FROM oe_prn_order_lines_v WHERE header_id = :p_header_id AND org_id = :p_org_id ORDER BY line_number;

For a range of orders, the header identifier can be joined back to OE_ORDER_HEADERS_ALL to obtain the order number and customer name, which the view does not itself expose. When extracting data for BI Publisher, select only the columns required by the template, since the view embeds package function calls whose cost is incurred per row. When filtering by customer, use SOLD_TO_ORG_ID rather than a name column, as no customer name is projected. Because the view performs currency formatting as character data, numeric comparison on the price columns requires casting or the use of the underlying OE_ORDER_LINES_ALL columns instead.