Results for “bic_invlist_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIC_INVLIST_V is a reporting view historically shipped with the Oracle Customer Intelligence (BIC) product family, a customer analytics offering that is now obsolete in Oracle E-Business Suite. The view presents a consolidated, denormalized list of customer invoices drawn primarily from the Receivables transaction tables, enriched with salesperson, term, remit-to address, party, and customer account attributes. Its purpose was to supply a single flat record per invoice suitable for reporting, extracts, and downstream integration into customer intelligence dashboards, without requiring the consumer to reconstruct the multi-table joins across Receivables and Trading Community Architecture.
The ETRM documentation for the 12.2.2 release records this object but notes that it is "Not implemented in this database," and that no base objects are documented for it. The owner is not recorded, and the view is classified under BIC - Customer Intelligence (Obsolete). This means the definition below should be treated as historical reference rather than as a supported interface in a current 12.1.1 or 12.2.2 installation. Because the user query referenced "ship_date," the SHIP_DATE column, sourced from RA_CUSTOMER_TRX_ALL.SHIP_DATE_ACTUAL, is a principal point of interest.
Underlying Base Objects
The view text joins the following documented sources:
- RA_CUSTOMER_TRX_ALL (aliased CTA) — the primary invoice header table supplying transaction identifiers, dates, currency, purchase order, ship date, ship-via, waybill, and remit-to address reference.
- RA_CUST_TRX_TYPES_ALL (CTT) — transaction type, restricted by the predicate CTT.TYPE = 'INV'.
- RA_TERMS (TRM) — payment term name, outer-joined on TERM_ID.
- RA_SALESREPS_ALL (SR) — salesperson name, outer-joined on PRIMARY_SALESREP_ID.
- BIC_ADDRESS_V (LOC) — the remit-to address, itself a BIC view rather than a base table.
- HZ_PARTIES (PRTY) and HZ_CUST_ACCOUNTS (CUST) — party and customer account identifiers, joined on PARTY_ID and CUST_ACCOUNT_ID.
The join predicates include an ORG_ID match between transaction and transaction type, allowing for null ORG_ID combinations, and an outer-join exclusion filter on the salesperson (SALESREP_ID <> -3).
Key Columns
- CUSTOMER_TRX_ID — Receivables transaction identifier; effectively the primary key of the view.
- CUSTOMER_ID / PARTY_ID / ACCOUNT_NUMBER — billing customer, party, and account number from the TCA tables.
- INVOICE_NUMBER, INVOICE_DATE, DUE_DATE, CURRENCY, REFERENCE — core invoice header attributes.
- SHIP_DATE — derived from CTA.SHIP_DATE_ACTUAL, the actual shipment date recorded on the transaction.
- SHIP_VIA and SHIPPING_REFERENCE — carrier and waybill number.
- ORDER_NUMBER — the customer purchase order reference (CTA.PURCHASE_ORDER).
- SALESPERSON, TERM, REMIT_TO, ORG_ID — ownership, terms, and address context.
- TYPE, STATUS, INVCOM_FLAG, COMPLETE_FLAG — transaction type and completion indicators.
Common Use Cases and Queries
Typical usage involved feeding invoice-level extracts into customer intelligence reporting, often filtered or grouped by shipment date. A representative query follows:
SELECT invoice_number, invoice_date, ship_date, customer_id, order_number, currency, term FROM bic_invlist_v WHERE ship_date >= :p_from_date AND ship_date <= :p_to_date AND org_id = :p_org_id ORDER BY ship_date;SELECT salesperson, COUNT(*) invoice_count FROM bic_invlist_v WHERE ship_date IS NOT NULL GROUP BY salesperson;
Because the view is obsolete and absent from the current database, equivalent reporting should be recreated directly against RA_CUSTOMER_TRX_ALL and its associated tables, or through standard Receivables reporting and the modern BI Publisher data models.
-
View: BIC_INVLIST_V 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_INVLIST_V 12.2.2
Not implemented in this database·Explore BIC module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1