Results for “market_segment_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIC_MARKET_SEGMENT_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the BIC – Customer Intelligence product family, a module now classified as obsolete within the EBS application stack. The view exposes market segment definitions that originate from the Oracle Marketing (AMS) data model, presenting them in a simplified, denormalized form suitable for lookup, list-of-values, and reporting consumption.

The primary functional role of BIC_MARKET_SEGMENT_V is to translate the internal cell-based representation used by Oracle Marketing into an externally meaningful market segment structure. Each qualifying record is published with a stable identifier derived from the CELL_ID, a display value derived from the CELL_NAME, and a synthetic foreign-key placeholder. Because the view is defined WITH READ ONLY, it cannot be used as the target of DML statements; it serves exclusively as a query and integration surface.

Underlying Base Objects

The view text is documented as follows:

• Source object: AMS_CELLS_VL — the multi-language, translated view over the Oracle Marketing cells entity.
• Filter predicate 1: MARKET_SEGMENT_FLAG = 'Y' — restricts output to cells that are explicitly designated as market segments. Non-segment cells used for other marketing constructs are excluded.
• Filter predicate 2: ENABLED_FLAG = 'Y' — restricts output to active, enabled segments, excluding soft-disabled records.
• Read-only clause: WITH READ ONLY — enforces non-updatable behavior regardless of the underlying view's own capabilities.

Because AMS_CELLS_VL is a translated (VL) view, CELL_NAME resolves according to the session language or the base language fallback, so the same physical segment can present a localized MARKET_SEGMENT_NAME depending on the runtime NLS environment. No other base tables are documented as referenced by this view in the ETRM 12.2.2 metadata.

Key Columns

• ID — TO_CHAR(CELL_ID). The segment identifier rendered as a character string. The conversion to character is deliberate, since BIC lookup consumers commonly expect string-based keys in flexfield and LOV contexts.
• VALUE — CELL_NAME. The human-readable display value presented to end users in lists of values and pickers.
• ALL_FK — A literal 'ALL' constant. This is a synthetic placeholder used by dependent lookup views to represent an unfiltered or "all segments" option in concatenated foreign-key constructs.
• MARKET_SEGMENT_ID — CELL_ID. The numeric primary identifier of the market segment, exposed under a business-friendly column name.
• MARKET_SEGMENT_CODE — CELL_CODE. The internal code assigned to the cell; useful for programmatic matching where display names may vary by language.
• MARKET_SEGMENT_NAME — CELL_NAME. The descriptive name of the segment, mirrored from VALUE to provide an explicit semantic label alongside the generic lookup columns.

Common Use Cases and Queries

The view is typically consumed by reporting extracts, lookup validation, and legacy BIC integrations that require a flat list of enabled market segments. A representative query returning all active segments is:

SELECT MARKET_SEGMENT_ID, MARKET_SEGMENT_CODE, MARKET_SEGMENT_NAME FROM APPS.BIC_MARKET_SEGMENT_V ORDER BY MARKET_SEGMENT_NAME;

Resolving a specific segment by code, common in interface staging tables, follows the pattern:

SELECT MARKET_SEGMENT_NAME FROM APPS.BIC_MARKET_SEGMENT_V WHERE MARKET_SEGMENT_CODE = :p_code;

Because the view is read-only, it may be joined freely against staging or reporting tables without risk of accidental update through the view. Note that the parent BIC product is obsolete in 12.2.2; organizations still referencing this object should confirm downstream dependencies before retiring it, but the view remains VALID and queryable in both 12.1.1 and 12.2.2 environments.