Results for “order_header”

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

Overview

XNI_LEVEL_3_EXP_V is a reporting view historically shipped with the XNI (Install Base Intelligence) module of Oracle E-Business Suite. XNI was an early analytical layer for Oracle Install Base, intended to expose installed-asset information in a denormalized, presentation-ready form. In release 12.1.1 and 12.2.2 the XNI module is classified as Obsolete, and the ETRM metadata explicitly states that this view is not implemented in this database. The view therefore has no runtime object in a current 12.1.1 or 12.2.2 instance; the definition below is retained only as historical documentation for upgrade assessment and impact analysis.

The view presents installed instances from CSI_ITEM_INSTANCES joined to the originating order line, order header, item master, and sales representative, producing a flattened row per installed instance with an associated order-based amount. Its purpose was to support Installed Base Intelligence reports that tie customer assets back to sales orders and selling representatives.

Underlying Base Objects

Although the ETRM metadata lists no referenced base objects for 12.2.2, the documented view text identifies five sources:

• CSI_ITEM_INSTANCES (A) — the driving table; supplies instance identity, ownership, active dates, quantity, last order line reference, and inventory item.
• OE_ORDER_LINES_ALL (B) — joined via A.LAST_OE_ORDER_LINE_ID = B.LINE_ID; supplies unit selling price used in the amount calculation.
• OE_ORDER_HEADERS_ALL (C) — joined via B.HEADER_ID = C.HEADER_ID; supplies order number, org, salesrep, and transactional currency.
• MTL_SYSTEM_ITEMS_B (D) — joined via A.INVENTORY_ITEM_ID = D.INVENTORY_ITEM_ID and B.INVENTORY_ITEM_ID = D.INVENTORY_ITEM_ID; supplies product number and name segments.
• JTF_RS_SALESREPS (E) — outer-joined on salesrep ID and org; supplies the sales representative name.

The join chain is strictly line-driven: an instance is only reported when its last order line matches an existing order line and header.

Key Columns

• INSTANCE_ID / INSTANCE_NUMBER — unique installed-instance identifier and user-visible instance number.
• OWNER_PARTY_ACCOUNT_ID — party account owning the instance.
• ACTIVE_START_DATE / ACTIVE_END_DATE — instance active period.
• AMOUNT — computed as ROUND((A.QUANTITY * B.UNIT_SELLING_PRICE)/11000000, 2), an order-value measure.
• LAST_OE_ORDER_LINE_ID — the order line that most recently created or updated the instance; the primary key sought by users searching on this term.
• INVENTORY_ITEM_ID, PRODUCT_NUMBER, PRODUCT_NAME, MTL_ORGANIZATION_ID — item identification and master organization.
• ORDER_HEADER, ORDER_NUMBER, ORDER_ORG_ID, ORDER_SALESREP_ID, TRANS_CUR_CODE — order header context and transaction currency.
• SALESREP_NAME — sales representative name, null when no match exists.

Common Use Cases and Queries

Historically the view supported installed-base reports reconciling assets to orders, salesrep performance on installed instances, and item-level asset valuation. On 12.1.1 and 12.2.2 the view is absent, so any dependent custom code must be remediated. A representative historical query follows:

• SELECT instance_number, last_oe_order_line_id, order_number, amount FROM xni_level_3_exp_v;
• SELECT order_number, product_name, salesrep_name, amount FROM xni_level_3_exp_v WHERE owner_party_account_id = :party_id;

Where the data is still required, equivalent reporting can be reconstructed directly from CSI_ITEM_INSTANCES, OE_ORDER_LINES_ALL, OE_ORDER_HEADERS_ALL, MTL_SYSTEM_ITEMS_B, and JTF_RS_SALESREPS using the join conditions documented above.