Search Results line_charges

Overview

APPS.OE_PRN_ORDER_LINES_V is a denormalized reporting view in the Oracle E-Business Suite Order Management (ONT) schema. It exposes order line information in a flattened, print- and report-oriented structure, permitting query tools, concurrent programs, and custom integrations to read line-level order data without repeatedly navigating the normalized OE_ORDER_LINES_ALL model. The view is registered under the internal FND Design Data name ONT.OE_PRN_ORDER_LINES_V and holds a VALID status.

Because it is flagged as Oracle Internal Use Only and is not part of the supported public interface, access should be restricted to standard Oracle Applications programs or carefully governed custom code. The "PRN" prefix signals that the view was designed to support order printing and document generation routines, where a single row conveys both header context and line detail. In release 12.1.1 and 12.2.2, the ONLINE flag and multi-org (ORG_ID) awareness remain consistent, and the view continues to be referenced by Oracle's seeded printing and confirmation programs.

Underlying Base Objects

The view resolves a broad set of base objects, most of them synonyms owned in other schemas. The primary source is OE_ORDER_LINES_ALL, providing transactional line attributes, joined to OE_ORDER_HEADERS_ALL for order-level context. Supporting joins resolve descriptive and reference data from MTL_SYSTEM_ITEMS_KFV, MTL_SYSTEM_ITEMS_TL, MTL_CUSTOMER_ITEMS, and MTL_CROSS_REFERENCES for item identification, and MTL_UNITS_OF_MEASURE_TL for the unit of measure. Order-type and pricing context come from OE_TRANSACTION_TYPES_ALL, OE_AGREEMENTS_TL, and OE_BLANKET_HEADERS_ALL.

Payment and currency logic is drawn from RA_TERMS_TL, RA_RULES, and FND_CURRENCY. Several calls are made to PL/SQL packages rather than tables: OE_OE_TOTALS_SUMMARY, OE_ORDER_MISC_PUB, OE_SYS_PARAMETERS, and OE_TOTALS_GRP. This mix of synonyms and package references explains why the view is considered internal — its output depends on session and profile context resolved at runtime.

Key Columns

Identity and line hierarchy are exposed through LINE_ID, HEADER_ID, LINE_NUMBER, ORG_ID, and LINK_TO_LINE_ID, with ATO_LINE_ID, TOP_MODEL_LINE_ID, CONFIGURATION_ID, and COMPONENT_SEQUENCE_ID supporting configured-item structures.

• LINE / LINE_NUMBER — the line identifier and its display sequence.
• ITEM_NUMBER, ITEM_DESCRIPTION, INVENTORY_ITEM_ID, ORDERED_ITEM_ID — catalog and ordered item identification.
• ORDERED_QUANTITY, ORDER_QUANTITY_UOM, INVOICED_QUANTITY — ordered and fulfilled quantities with UOM.
• UNIT_LIST_PRICE, UNIT_SELLING_PRICE, DISCOUNT, TAX_VALUE, TAX_CODE — pricing and tax charge attributes. These VARCHAR2 price columns are central to the line-charges concept, since they carry the resolved charge and adjustment amounts used in order printing.
• REQUEST_DATE, PROMISE_DATE, SCHEDULE_SHIP_DATE, SCHEDULE_ARRIVAL_DATE — scheduling milestones.
• SHIP_TO_ORG_ID, SHIP_FROM_ORG_ID, SOLD_TO_ORG_ID, INVOICE_TO_ORG_ID and contact IDs — party and address derivation.
• CUST_PO_NUMBER, TAX_EXEMPT_NUMBER, SALESREP_ID — customer-facing references.

Common Use Cases and Queries

The view is typically queried for order printing, order acknowledgement, and audit extracts where list and selling prices stand in for line charges.

• Retrieve all lines for an order: SELECT line_number, item_number, ordered_quantity, order_quantity_uom, unit_list_price, unit_selling_price, discount FROM apps.oe_prn_order_lines_v WHERE header_id = :p_header_id ORDER BY line_number;
• Reconcile line charges across prices and tax: SELECT line_id, unit_list_price, unit_selling_price, discount, tax_value FROM apps.oe_prn_order_lines_v WHERE org_id = :p_org AND header_id = :p_header;
• Extract pending shipment schedules: SELECT header_id, line_id, schedule_ship_date, ordered_quantity, ship_from_org_id FROM apps.oe_prn_order_lines_v WHERE schedule_ship_date BETWEEN :p_start AND :p_end AND org_id = :p_org;

Consumers should apply ORG_ID predicates to respect multi-org security and treat results as internal data subject to change in future releases.