Search Results bill_to_contact




Overview
Explore in AI Chat

Overview

BIC_ORDERS_SUMMARY_V is a reporting view historically shipped within the Oracle Customer Intelligence (BIC) product family in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It presents a consolidated, flattened summary of order header information drawn from the Order Management transactional schema, enriched with customer, address, contact, and order type attributes. The view was intended to feed customer intelligence dashboards, order analytics, and downstream reporting extracts without requiring report authors to reconstruct the complex multi-table joins between order headers, trading partners, and address hierarchies.

In the ETRM metadata for release 12.2.2, this object is documented as part of the BIC – Customer Intelligence module, which is now classified as obsolete. The metadata also records that the view is "not implemented in this database," meaning it is not deployed in the reference environment from which the ETRM content was generated. Consequently, references to this view may appear in legacy customizations, seeded reports, or migration inventories even though the object itself is absent from current installations.

The view is defined with a WITH READ ONLY clause, confirming that it is strictly a query-only construct and cannot be used for DML operations.

Underlying Base Objects

The view text joins several Oracle EBS base objects. The driving source is ASO_I_OE_ORDER_HEADERS_V, an Order Management header view that supplies the core order attributes such as ORDER_NUMBER, ORDERED_DATE, HEADER_ID, and CUST_PO_NUMBER. Customer Intelligence components BIC_ADDRESS_V (aliased twice, for bill-to and ship-to addresses) and standard Trading Community Architecture (TCA) tables — HZ_PARTIES, HZ_CUST_SITE_USES_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES — provide contact and address detail through two parallel hierarchies (invoice-to and ship-to). OE_TRANSACTION_TYPES_TL supplies the translated order type name.

All joins to the TCA and order type objects are outer joins, ensuring that order headers are retained even when customer, address, or order type reference data is incomplete. The ETRM metadata records no documented referenced base objects for the 12.2.2 extraction, so the join relationships above are derived from the supplied view text rather than from a formal object registry.

Key Columns

Common Use Cases and Queries

Typical usage centers on order-level reporting where customer purchase order references, ship-to/bill-to detail, and order type context must be presented together. Because the view is obsolete and may not exist in a given environment, queries should be executed only after confirming object availability in ALL_VIEWS.

SELECT ORDER_NUMBER, ORDERED_DATE, PURCHASE_ORDER, ORDER_TYPE, SHIP_TO
FROM   BIC_ORDERS_SUMMARY_V
WHERE  PURCHASE_ORDER = 'PO-10045'
AND    ORG_ID = 204;

A second common pattern aggregates open orders by customer for intelligence extracts:

SELECT CUSTOMER_ID, COUNT(*) ORDER_COUNT
FROM   BIC_ORDERS_SUMMARY_V
WHERE  OPEN_FLAG = 'Y'
GROUP  BY CUSTOMER_ID;

In 12.1.1 and 12.2.2 environments where BIC is no longer licensed or the view is undeployed, equivalent output should be obtained from ASO_I_OE_ORDER_HEADERS_V joined directly to the TCA tables, replicating the view text supplied in the ETRM metadata.