Search Results product_status

Overview

The view BIC_INSTALLED_BASE_DETAIL_V belongs to the BIC — Customer Intelligence product family within Oracle E-Business Suite. BIC was an early analytical offering designed to expose customer-installed-base information for downstream reporting, data warehousing, and customer intelligence analytics. In EBS 12.1.1 and 12.2.2 this object is documented as obsolete and, per the ETRM metadata, is not implemented in this database. It therefore exists only as a documented reference rather than an active, queryable object in a standard installation.

Functionally, the view consolidates the installed base — customer products recorded in Oracle Service (CS) — and enriches each record with customer, item, revision, status, unit-of-measure, and original sales order context. Its purpose is to present a single denormalized row per installed customer product, suitable for reporting on what a customer owns, when it was installed, and under what commercial terms it was originally sold.

Underlying Base Objects

The view text joins the following documented base objects:

• CS_CUSTOMER_PRODUCTS_ALL — the primary installed-base table (PRD).
• CS_CP_REVISIONS and CS_CUSTOMER_PRODUCT_STATUSES — revision and lifecycle status of each customer product.
• HZ_CUST_ACCOUNTS, HZ_PARTIES, and BIC_SITE_ADDRESS_V — customer account, party name, and install-site address.
• MTL_SYSTEM_ITEMS (twice), MTL_UNITS_OF_MEASURE — product master, product family, and UOM.
• ASO_I_OE_ORDER_LINES_V, ASO_I_OE_ORDER_HEADERS_V — original sales order line and header.
• CS_CONTACTS — service-request contact association.

Most joins are outer joins, meaning installed-base records are preserved even when the corresponding customer, revision, status, or site data is absent. The item join enforces ORGANIZATION_ID = FND_PROFILE.VALUE_WNPS('ASO_PRODUCT_ORGANIZATION_ID'), so the view is scoped to the product organization defined in that profile option. The WITH READ ONLY clause prevents DML against the view.

Key Columns

The view exposes customer identity (CUSTOMER_ID, CUSTOMER_NAME, CUST_ACCT_NUMBER), product attributes (PRODUCT_NAME, PRODUCT_REVISION, PRODUCT_TYPE, PRODUCT_FAMILY, PRODUCT_STATUS, UNIT_OF_MEASURE), and instance details such as SERIAL_NUMBER, LOT_NUMBER, REFERENCE_NUMBER, QUANTITY, INSTALLATION_DATE, and SHIPPED_DATE. Original order context includes ORIGINAL_ORDER_DATE and ORIGINAL_ORDER_NUMBER.

The column most relevant to the search term ORIGINAL_NET_AMOUNT is derived as ASOL.ORDERED_QUANTITY * ASOL.UNIT_SELLING_PRICE — the extended selling price of the original order line, expressible as quantity multiplied by unit selling price rather than a stored value.

Common Use Cases and Queries

Typical scenarios include installed-base revenue analysis and customer entitlement reporting. A representative query would be:

• SELECT customer_name, product_name, original_order_number, original_net_amount FROM bic_installed_base_detail_v WHERE original_net_amount > 0;
• Aggregating installed-base value by customer or product family for analytics.
• Correlating installation dates with original order dates to measure fulfillment lag.

Because the view is obsolete and not implemented, queries against it will fail on supported 12.1.1 and 12.2.2 environments; equivalent logic must be reconstructed directly from the underlying CS, HZ, and ASO objects.