Search Results bim_geography




Overview
Explore in AI Chat

Overview

BIM_GEOGRAPHY is a dimension table in the Oracle E-Business Suite Marketing Intelligence (BIM) module. It stores the dimension values representing geographic locations, providing the hierarchy of country, state, city, and postal code values that Marketing Intelligence uses for segmentation, targeting, and analytical reporting against customer and prospect data. The table is populated by the BIM_GEO_PKG concurrent program rather than through direct user maintenance, meaning its contents are derived and refreshed as part of the standard BIM batch cycle.

In Oracle EBS 12.1.1 and 12.2.2 the object is owned by the BIM schema and is documented as VALID in the ETRM repository. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it functions as a reference or dimension construct without participating in the more complex link-based relationships typical of transactional hubs. This classification is a modeling suggestion rather than a functional restriction: the table carries its own unique business keys and a foreign key to security groups, but it does not act as a junction linking other hubs.

Key Information Stored

The table contains 17 documented columns. The most significant are described below.

Common Use Cases and Queries

The primary scenario is geography-based segmentation of marketing data. Analysts join BIM_GEOGRAPHY to customer, prospect, or campaign fact tables on the location hierarchy code to produce regional breakdowns. A typical pattern retrieves the hierarchy for a secured operating context:

SELECT g.location_hierarchy_code, g.country, g.state, g.city, g.postal_code
FROM bim.bim_geography g
WHERE g.security_group_id = :p_security_group_id
AND SYSDATE BETWEEN g.period_start_date AND g.period_end_date;

A second pattern resolves a location from its natural business key using the composite unique index, which is useful for validation or load routines. Batch lineage reporting uses the concurrent program columns to audit which BIM_GEO_PKG request refreshed which rows, while point-in-time reporting relies on the period start and end dates. Because the table is a maintained dimension, direct DML is discouraged; refresh should be performed through the BIM_GEO_PKG concurrent program so that the security group and effective date values remain consistent.

Related Objects

The most significant objects associated with BIM_GEOGRAPHY are:

  • FND_SECURITY_GROUPS — referenced by BIM_GEOGRAPHY.SECURITY_GROUP_ID; the join enforces row-level security on geography dimension members.
  • BIM_GEO_PKG — the concurrent program package that populates and maintains the table.
  • BIM_GEOGRAPHY_PK — the primary key constraint on LOCATION_HIERARCHY_CODE.
  • BIM_GEOGRAPHY_U1 — the unique index on LOCATION_HIERARCHY_CODE.
  • BIM_GEOGRAPHY_U2 — the composite unique index on COUNTRY, STATE, CITY, POSTAL_CODE.
  • BIM marketing fact and dimension tables — downstream analytical objects that resolve geographic attributes by joining on LOCATION_HIERARCHY_CODE.
  • FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to trace the concurrent run that populated each geography record.