Results for “bic_cities_v”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIC_CITIES_V is a reporting view belonging to the BIC – Customer Intelligence module in Oracle E-Business Suite. Customer Intelligence was a marketing and customer analytics application shipped in earlier EBS releases; in both 12.1.1 and 12.2.2 the module is flagged as obsolete, meaning it is no longer actively developed or supported for new implementations. The view itself is a lightweight, denormalized lookup that surfaces city-level values from the geography dimension used by BIC analytics. Its stated purpose in the ETRM documentation is straightforward: it fetches city names from BIC_DIMV_GEOGRAPHY.
The object is significant primarily to users who maintain legacy BIC reports, migrated customizations, or historical data extracts that reference city identifiers. Because the surrounding module is obsolete, the view is preserved largely for backward compatibility rather than for new development.
Underlying Base Objects
The ETRM metadata documents a single referenced base object: BIC_DIMV_GEOGRAPHY, a dimension view in the Customer Intelligence schema that supplies geography hierarchy members. BIC_CITIES_V is defined directly over that object with no documented intermediate tables or joins.
The ETRM record for 12.2.2 lists no owner and no further referenced base objects, and it notes that the view is "Not implemented in this database." This is a key operational caveat: in many EBS instances, particularly later 12.2.x environments where BIC was never installed or was removed, the view does not physically exist. Scripts or reports that query it will fail with an ORA-00942 or ORA-01775 error unless the Customer Intelligence schema and its dimension objects are present.
Key Columns
The view exposes five columns, which the ETRM lists in two places (the view text and the column list). The effective projection is:
- CITY_ID — the city identifier. The metadata is slightly inconsistent here: the column list names it CITY_ID, while the view text aliases the identifier twice (once as "CITY ID" and once as "CITY_ID"). In practice, CITY_ID is the join key back to the geography dimension.
- VALUE — the display value, populated from the city name. This is the column intended for LOVs and report labels.
- CITY_NAME — the city name, exposed for callers that expect an explicit descriptive column rather than the generic VALUE alias.
- GEOGRAPHY_ID — the parent geography dimension identifier, allowing the city to be resolved within the wider geography hierarchy.
- ID — listed in the column inventory; in the view text it corresponds to the identifier alias that maps to CITY_ID.
Because VALUE, CITY_ID, CITY_NAME, and GEOGRAPHY_ID may all derive from the same underlying city attribute, consumers should treat CITY_ID as the technical key and VALUE or CITY_NAME as the descriptive label, avoiding assumptions about uniqueness across the full geography hierarchy.
Common Use Cases and Queries
Typical usage centers on city selection lists and joins from customer or site records to geography. A representative query is:
SELECT city_id, city_name, geography_id FROM bic_cities_v WHERE UPPER(city_name) LIKE 'SAN%' ORDER BY city_name;
For LOV-style retrieval, the VALUE column is normally preferred:
SELECT city_id, value FROM bic_cities_v ORDER BY value;
A common integration pattern joins the view to a customer address table on the city identifier to enrich analytics extracts with readable city names. Before deploying any such query in 12.1.1 or 12.2.2, confirm that the BIC schema exists in the instance, since the ETRM explicitly records the view as not implemented. Where it is absent, the equivalent reference data should be sourced from the standard geography tables rather than from this obsolete BIC view.
-
View: BIC_CITIES_V 12.1.1
This view fetches city names from bic_dimv_geography.
APPS.BIC_CITIES_V·↳ BIC_DIMV_GEOGRAPHY·↳ FND_GLOBAL·Explore BIC module →
-
VIEW: APPS.BIC_CITIES_V 12.1.1
-
View: BIC_CITIES_V 12.2.2
This view fetches city names from bic_dimv_geography.
Not implemented in this database·Explore BIC module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
eTRM - BIC Tables and Views 12.1.1
This table stores industry standard values for satisfaction
-
eTRM - BIC Tables and Views 12.1.1
This table stores industry standard values for satisfaction
-
12.1.1 DBA Data 12.1.1