Results for “aso_i_oe_order_headers_v”

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

Overview

CS_CP_ORDERINFO_RG_V is a Service (CS) module reporting view that exposes combined order header and order line information in a flattened, denormalized form. Its documented purpose is simply to "list the order information," making it a convenient read-only source for reports, concurrent programs, and integration extracts that need order number, order date, customer PO reference, and line-level detail in a single query without joining the underlying order tables manually. The view is not a stored table and carries no independent data; it is a runtime projection over the Order Information (OI) interface views in the Advanced Supply Chain / Order Management integration layer.

Because the view is documented as "Not implemented in this database" in the source metadata, it may not be deployed in every environment. In Oracle EBS 12.1.1 and 12.2.2, the presence of the view depends on whether the Service/Order Information patch set that creates it has been applied. Analysts should verify existence against ALL_VIEWS before referencing it in custom code. The view is especially relevant to users who search for aso_i_oe_order_lines_v, since the line-level content of CS_CP_ORDERINFO_RG_V is drawn directly from that object.

Underlying Base Objects

The view text is defined as an outer join between two Order Information views:

• ASO_I_OE_ORDER_HEADERS_V OOH — supplies ORDER_NUMBER, ORDERED_DATE, and CUST_PO_NUMBER (the header-level attributes).
• ASO_I_OE_ORDER_LINES_V OOL — supplies LINE_NUMBER and the link column, with HEADER_ID used as the join key.

The join is written as OOL.HEADER_ID = OOH.HEADER_ID(+), an Oracle-style outer join anchored on the line view. Practically, this preserves order lines even where a matching header row is not returned by the header view, which is significant when the header view applies validation or status filtering. No base tables are documented as directly referenced; the view depends entirely on the two ASO order-information views, which in turn resolve to the Order Management order headers and lines. This layered design means CS_CP_ORDERINFO_RG_V inherits any filtering, security, or profile-based behavior applied inside ASO_I_OE_ORDER_LINES_V and ASO_I_OE_ORDER_HEADERS_V.

Key Columns

• ORDER_NUMBER — the user-visible order number from the header, the primary identifier for reporting and cross-referencing to Order Management.
• ORDERED_DATE — the date the order was placed or entered, used for period-based reporting and aging.
• CUST_PO_NUMBER — the customer's purchase order reference, essential for B2B reconciliation and customer-facing documents.
• LINE_NUMBER — the order line sequence, enabling line-level reporting.
• LINE_ID (documented alias of LINK_TO_LINE_ID) — the internal line identifier that links back to the order line record, used for drill-down and joins to additional line detail.

Common Use Cases and Queries

Typical scenarios include generating order status extracts, reconciling customer PO references, and feeding downstream service or fulfillment reports. Because the view is a thin projection, filtering is usually performed by order number or date.

A simple listing, for example:

SELECT order_number,
       ordered_date,
       cust_po_number,
       line_number,
       line_id
FROM   cs_cp_orderinfo_rg_v
WHERE  ordered_date >= :p_from_date
ORDER  BY order_number, line_number;

For drill-down, LINE_ID can be joined to the Order Information line view to retrieve item, quantity, and pricing attributes. Analysts should confirm the view is deployed in the target instance and test the outer-join behavior, since header rows may be absent for some lines.