Results for “oe_as_order_headers_v”
48 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.OE_AS_ORDER_HEADERS_V is a reporting and integration view in the Oracle Order Management (ONT) module. It exposes a denormalized, human-readable projection of sales order header information drawn from OE_ORDER_HEADERS_ALL and a set of related reference and party objects. Its documented purpose is to "provide details of all existing orders in the Order Management," which makes it a convenient single-source query point for dashboards, extracts, interfaces, and downstream integration routines that need order-level attributes without joining the full transactional schema directly.
The view is owned by the APPS schema and is marked VALID in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it introduces no storage of its own and reflects the current state of the underlying base objects at query time. This behavior is important in EBS environments where orders are frequently updated: any committed change to the header or its related lookups is immediately visible through the view.
Underlying Base Objects
The documented dependency list for OE_AS_ORDER_HEADERS_V comprises the following objects:
OE_ORDER_HEADERS_ALL(synonym) — the primary transactional source, supplying header identifiers, order number, flow status, currency, sold-to identifiers, salesrep, and sales channel.OE_ORDER_SOURCES(synonym) — resolved to the order source name.OE_TRANSACTION_TYPES_TL(synonym) — supplies the translated order type name, joined onUSERENV('LANG').HZ_CUST_ACCOUNTS,HZ_CUST_ACCOUNT_ROLES,HZ_PARTIES,HZ_RELATIONSHIPS(synonyms) — resolve the customer account number, sold-to contact, party identifiers, and contact title.RA_SALESREPS_ALL(synonym) andJTF_RS_RESOURCE_EXTNS_VL(view) — supply the sales representative name.HR_OPERATING_UNITS(view) — resolves the operating unit name fromORG_ID.AR_LOOKUPS,OE_LOOKUPS(views) — decode flow status, sales channel, and contact title meanings.OE_OE_TOTALS_SUMMARY(package) — supplies theORDER_TOTAL_NUMERICcolumn through the functionPRT_ORDER_TOTAL.
Most joins to the customer and lookup objects are outer joins, so a header is not suppressed when contact, source, or lookup data is missing.
Key Columns
HEADER_ID— primary key of the order header; used for joins back to transactional tables.ORG_ID,ORG_NAME— operating unit identifier and its resolved name.ORDER_NUMBER— user-facing order number.FLOW_STATUS_CODE,FLOW_STATUS— internal flow status code and its decoded meaning.ORDER_TYPE_ID,ORDER_TYPE— transaction type identifier and translated name.ORDER_SOURCE_ID,ORDER_SOURCE— order source and its name.CREATION_DATE,TRANSACTIONAL_CURR_CODE— creation timestamp and transaction currency.SOLD_TO_ORG_ID,SOLD_TO_CONTACT_ID,SOLD_TO_CONTACT,ACCOUNT_NUMBER,PARTY_ID— sold-to customer, contact, and account identifiers.SALESREP_ID,SALESREP_NAME,SALES_CHANNEL_CODE,SALES_CHANNEL— sales representative and channel information.ORDER_TOTAL— defined asNULLin the view text.ORDER_TOTAL_NUMERIC— returned by theOE_OE_TOTALS_SUMMARY.PRT_ORDER_TOTALfunction, calling it per header row.
Common Use Cases and Queries
The view is typically used for order status reporting, operating-unit extracts, and lightweight integration feeds, particularly where readable lookup meanings are preferred over raw codes. The following examples illustrate typical access patterns.
List orders for a given operating unit with decoded status:
SELECT order_number, org_name, order_type, flow_status, order_total_numeric FROM oe_as_order_headers_v WHERE org_id = :p_org_id AND flow_status = 'BOOKED' ORDER BY creation_date DESC;
Retrieve a single order with customer and salesrep detail:
SELECT order_number, account_number, sold_to_contact, salesrep_name, sales_channel FROM oe_as_order_headers_v WHERE order_number = :p_order_number;
Produce a daily order count by source and type:
SELECT TRUNC(creation_date) order_date, order_source, order_type, COUNT(*) total FROM oe_as_order_headers_v WHERE creation_date >= TRUNC(SYSDATE) GROUP BY TRUNC(creation_date), order_source, order_type;
Because ORDER_TOTAL_NUMERIC is computed through a PL/SQL function invoked once per row, queries returning large result sets should apply selective predicates before aggregating totals. Joins back to OE_ORDER_HEADERS_ALL using HEADER_ID remain the standard approach when additional line-level or attribute-level detail is required.
-
View: OE_AS_ORDER_HEADERS_V 12.1.1
View to provide details of all existing orders in the Order Management.
APPS.OE_AS_ORDER_HEADERS_V·↳ AR_LOOKUPS·↳ HR_OPERATING_UNITS·↳ HZ_CUST_ACCOUNTS·Explore ONT module →
-
View: OE_AS_ORDER_HEADERS_V 12.2.2
View to provide details of all existing orders in the Order Management.
APPS.OE_AS_ORDER_HEADERS_V·↳ AR_LOOKUPS·↳ HR_OPERATING_UNITS·↳ HZ_CUST_ACCOUNTS·Explore ONT module →
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
VIEW: APPS.OE_LOOKUPS 12.1.1
-
VIEW: APPS.OE_LOOKUPS 12.2.2
-
VIEW: APPS.AR_LOOKUPS 12.1.1
-
VIEW: APPS.AR_LOOKUPS 12.2.2
-
SYNONYM: APPS.HZ_PARTIES 12.2.2
-
SYNONYM: APPS.HZ_PARTIES 12.1.1
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
eTRM - AR Tables and Views 12.2.2
Territory information
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - AR Tables and Views 12.1.1
Territory information
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - AR Tables and Views 12.2.2
Territory information
-
eTRM - AR Tables and Views 12.1.1
Territory information