Search Results shipto_addr

Overview

BIC_INSTALLED_BASE_SUMMARY_V is a reporting view historically delivered with the Oracle E-Business Suite Customer Intelligence (BIC) module. It consolidates the installed base of customer products into a single denormalized result set, joining installed product instances to item master definitions, revision data, status codes, product families, and customer site addresses. The view is documented as obsolete and, according to the ETRM metadata, is not implemented in the current database. In EBS 12.1.1 and 12.2.2 environments where it does exist, its purpose is to supply installed-base analytics — counts, distributions, and listings of customer-owned products by family, revision, and status — for BIC dashboards and for ad hoc reporting in the CRM and service domains.

The column PRODUCT_REVISION is the element most frequently targeted by users searching for revision-level installed base data. It is sourced from CS_CP_REVISIONS and reflects the currently effective revision of an installed customer product.

Underlying Base Objects

The view is defined over the customer products and customer product status tables in the CS (Customer Support / Depot Repair) schema, the item master in MTL, and the Trading Community Architecture (TCA) hierarchy in HZ, with address formatting resolved through BIC_ADDRESS_V. The documented base objects are:

• CS_CUSTOMER_PRODUCTS_ALL (alias PRD) — the driving table of installed product instances.
• MTL_SYSTEM_ITEMS (aliases ITM and ITMF) — the inventory item definition and its product family item.
• CS_CP_REVISIONS (alias REV) — revision records for the customer product.
• CS_CUSTOMER_PRODUCT_STATUSES (alias PS) — status of the installed instance.
• HZ_CUST_SITE_USES_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES — joined three times to resolve bill-to, ship-to, and install-site identifiers.
• BIC_ADDRESS_V — joined three times to format the bill-to, ship-to, and install-site addresses.

All joins to the address and revision objects are outer joins (indicated by the (+) syntax), so a customer product is returned even where revision or site data is incomplete. Notably, the item master join is constrained by FND_PROFILE.VALUE('ASO_PRODUCT_ORGANIZATION_ID'), so the view reflects only the item definitions in the profile-designated product organization. The view is declared WITH READ ONLY.

Key Columns

• CUSTOMER_PRODUCT_ID — primary identifier of the installed instance in CS_CUSTOMER_PRODUCTS_ALL.
• CUSTOMER_ID and ORG_ID — owning customer and operating unit context for multi-org security.
• PRODUCT_NAME — description of the inventory item from MTL_SYSTEM_ITEMS.
• PRODUCT_REVISION — current revision of the installed product, from CS_CP_REVISIONS.
• PRODUCT_TYPE — the type code carried on the customer product record.
• PRODUCT_FAMILY — description of the parent product family item.
• STATUS — the customer product status name (for example, active or terminated).
• INSTALLATION_DATE — date the product was installed.
• SHIPTO_SITE/SHIPTO_ADDR and INSTALL_SITE/INSTALL_ADDR — site identifiers and formatted addresses for shipping and installation.

Common Use Cases and Queries

Typical uses include installed-base population counts by product family and revision analysis for upgrade or service planning. A practical revision-focused query is:

SELECT PRODUCT_NAME, PRODUCT_REVISION, STATUS, COUNT(*) INSTALLED_QTY
FROM   BIC_INSTALLED_BASE_SUMMARY_V
WHERE  ORG_ID = :org_id
GROUP  BY PRODUCT_NAME, PRODUCT_REVISION, STATUS
ORDER  BY PRODUCT_NAME, PRODUCT_REVISION;

Because the view is documented as obsolete and not implemented in current 12.2.2 databases, Oracle does not support it for new development. Teams requiring equivalent installed-base reporting should build queries directly against CS_CUSTOMER_PRODUCTS_ALL, CS_CP_REVISIONS, and the TCA site tables, mirroring the join logic above and applying the ASO_PRODUCT_ORGANIZATION_ID profile constraint explicitly.