Search Results pricing_method_code

Overview

The AS_DOSSIER_PRODUCT_LINES_V view belongs to the Oracle E-Business Suite AS – Sales Foundation product family. Its documented description is "Order history product lines view," indicating that it exposes line-level order history data for consumption by Order Management, sales dossier, and downstream reporting or integration processes. The object serves as a presentation-layer abstraction over the transactional order line tables, flattening hierarchical and configured-item relationships into columns suitable for tabular reporting, BI Publisher extracts, and interface programs.

Because the view is described as "Not implemented in this database" in the supplied ETRM implementation/DBA metadata, it is important to note that the object is a seeded, dictionary-defined view delivered by the application rather than a customer-created database object. It becomes instantiated when the relevant AS/ONT product components are installed. Inventory against the specific search term transaction_type_svrid returned no matching column in this view, so the dossier view does not appear to carry the TRANSACTION_TYPE_SVRID attribute; that column is typically associated with service/transaction-type reference data elsewhere in the AS schema.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents no referenced base objects, and the view text excerpt does not include the FROM clause. From the visible select list, however, the defining query clearly joins the order line entity (aliased LN, likely OE_ORDER_LINES_ALL) and the master item table (MSI, i.e., MTL_SYSTEM_ITEMS_B).

• LN – the primary order line source, supplying LINE_ID, HEADER_ID, quantities, prices, flags, and the DFF ATTRIBUTE1–15 and CONTEXT columns.
• LN2 – a self-join back to the same line source, used to resolve the parent line number for class, standard, and kit item types.
• MSI – MTL_SYSTEM_ITEMS_B, providing ITEM_DESCRIPTION.

The DISTINCT keyword and the self-join on parent lines indicate the query is designed to de-duplicate and present a parent/child hierarchy for configured and kit items.

Key Columns

• LINE_ID, HEADER_ID – primary keys linking the row to its order line and order header.
• LINE_NUMBER / PARENT_LINE_NUMBER – a DECODE-derived display number; child lines are rendered as parent.number, producing a dotted hierarchical representation. SHIPMENT_NUMBER mirrors LINE_NUMBER.
• QUANTITY – computed as ORDERED_QUANTITY minus CANCELLED_QUANTITY, with zero substitution for nulls.
• LIST_PRICE, SELLING_PRICE, SELLING_PERCENT – pricing metrics defaulted to zero when null.
• ITEM_TYPE_CODE, LINE_TYPE_CODE, ITEM_DESCRIPTION – classification and descriptive attributes.
• Configuration flags – OPTION_FLAG, OPEN_FLAG, ATO_FLAG, SHIP_MODEL_COMPLETE_FLAG, COMPONENT_CODE, COMPONENT_SEQUENCE_ID.
• ATTRIBUTE1–15, CONTEXT – descriptive flexfield columns.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used to report historical order lines with parent/child configuration context and pricing. A representative query:

SELECT header_id, line_number, parent_line_number, item_description, quantity, selling_price FROM as_dossier_product_lines_v WHERE header_id = :p_header_id ORDER BY line_number;

Other scenarios include reconciliation of ordered versus shipped quantities, pricing analysis for configured kits, and extraction feeds. Because no base objects are formally documented, always validate the underlying definition in the target instance before relying on column semantics.