Search Results geography_fk

Overview

BIC_CUSTOMER_SUMMARY_V is a reporting view that belongs to the BIC — Customer Intelligence product family within Oracle E-Business Suite. In the ETRM metadata for release 12.2.2, the BIC product line is flagged as obsolete, and the view itself is documented as "Not implemented in this database." Consequently, BIC_CUSTOMER_SUMMARY_V will not resolve in a standard 12.1.1 or 12.2.2 instance unless a legacy Customer Intelligence installation or a custom object of the same name was created independently. The view is not a maintained, shipped database object; it is a historical artifact preserved for reference.

The view was designed to present customer scoring and measurement data in a denormalized, report-ready form. It joins customer master records from HZ_PARTIES to period-based measure results held in BIC_CUSTOMER_SUMMARY_ALL, enriches them with market segment assignments from AMS_PARTY_MARKET_SEGMENTS, and aligns each row to a fiscal or accounting period through BIC_DIMV_TIME. The result is a single wide row per customer, period, and measure combination, suitable for direct consumption by BI Publisher reports, Discoverer workbooks, or downstream extracts.

Underlying Base Objects

The view text references four physical base objects, though the ETRM "Referenced base objects" field documents none:

• BIC_CUSTOMER_SUMMARY_ALL — the fact-style table holding PERIOD_START_DATE, VALUE, SCORE, CUSTOMER_ID, BUCKET_ID, MEASURE_ID, and MEASURE_CODE. This is the primary driver of the join.
• HZ_PARTIES — supplies party-level attributes: PARTY_NAME, PARTY_ID, CREATION_DATE, the ADDRESS1–ADDRESS4 fields, CITY, POSTAL_CODE, STATE, COUNTRY, PROVINCE, COUNTY, and EMAIL_ADDRESS.
• AMS_PARTY_MARKET_SEGMENTS — outer-joined (indicated by the (+) operator) on PARTY_ID, supplying MARKET_SEGMENT_ID and, through the join, CUSTOMER_CATEGORY_FK. Only rows where MARKET_SEGMENT_FLAG = 'Y' are matched.
• BIC_DIMV_TIME — the time dimension, keyed on PERIOD_START_DATE = START_DATE, providing accounting period labels and calendar rollups.

The joins are equi-joins between summary, party, and time, with an outer join to market segments to preserve customers lacking a segment assignment.

Key Columns

The view exposes a broad column list. Core identity and measure columns are CUSTOMER_FK (aliased from S.CUSTOMER_ID), CUSTOMER_ID and PARTY_ID (both from P.PARTY_ID), VALUE, SCORE, BUCKET_ID, MEASURE_ID, and MEASURE_CODE. Organization context is provided through ORG_FK and ORG_ID, both mapped to S.ORG_ID. Time attributes include PERIOD_START_DATE, START_DATE, ACT_PERIOD_NAME, ACT_PERIOD_START_DATE, ACT_PERIOD_END_DATE, ACT_YEAR, ACT_PERIOD_NUM, ACT_QUARTER, ACT_HALF_YEAR, ACT_YEAR_START_DATE, and ACT_QUARTER_START_DATE.

The column geography_fk — the term the user searched for — is present in the view's column list but is defined as a literal NULL in the SELECT text, alongside NULL REGION and NULL AREA. This reflects the age of the object: geographic attribution was intended to be populated but was never wired to a source column in this definition. Report authors should therefore treat geography_fk, region, and area as unpopulated placeholders. Other NULL placeholders include ORG_NAME, MEASURE_NAME, MEASURE_DESCRIPTION, MEASURE_WEIGHT, MEASURE_TIME_CODE, ACCOUNT_NUMBER, CUST_ORG_ID, ACQUIRED_DATE, and ACCOUNT_NAME. Customer demographic columns (address, city, postal code, country) come from HZ_PARTIES directly.

Common Use Cases and Queries

Where the view exists, its intended use is customer scoring analysis across periods. A typical query selects customer identity, measure, and score for a given accounting period:

• SELECT party_name, customer_id, measure_code, score, value, act_period_name FROM bic_customer_summary_v WHERE act_period_name = :period_name ORDER BY score DESC;
• Aggregating scores by market segment: SELECT market_segment_fk, COUNT(DISTINCT customer_id), AVG(score) FROM bic_customer_summary_v GROUP BY market_segment_fk;
• Trend reporting by joining act_year and act_quarter to compare period-over-period movement.

Because geography_fk and its companion REGION and AREA columns always return NULL, any query attempting geographic segmentation through this view will yield no usable results. Reporting against geography requires alternate sources such as HZ_LOCATIONS and HZ_PARTY_SITES. Given the obsolete status of the BIC module and the "not implemented" notation in 12.2.2 metadata, this view should be regarded as reference-only; organizations on 12.1.1 or 12.2.2 requiring customer intelligence functionality should rely on supported objects or custom implementations.