Search Results user_attribute5




Overview
Explore in AI Chat

Overview

The view EDW_BIM_LSTA_LEADSTATUS_LTC_IV belongs to the BIM (Marketing Intelligence) product family within Oracle E-Business Suite, and is documented as obsolete in ETRM 12.2.2. It is an interface-oriented (IV suffix) warehouse extraction view that exposes lead status reference data in a denormalized, change-tracking friendly form. The view is defined as a straight projection over EDW_BIM_LSTA_LEADSTATUS_LTC, exposing a stable column contract that downstream ETL, staging, and reporting layers can consume without depending on physical storage details of the base object.

The _IV designation, together with the presence of ROW_ID, ALL_FK_KEY, ALL_FK, and OPERATION_CODE, is characteristic of Oracle Marketing/EDW interface views used to feed incremental loads into an enterprise data warehouse. The ALL_FK_KEY column in particular is the surrogate key construct that supports foreign-key resolution and slowly changing dimension (SCD) processing. Users searching for all_fk_key will typically encounter this view while investigating how marketing lead-status records are keyed and propagated through the warehouse pipeline.

The ETRM record states "Not implemented in this database." This means the view is documented as metadata but is not deployed in the environment being queried. It should therefore be treated as a reference definition rather than a currently queryable object.

Underlying Base Objects

Per the documented ETRM metadata, no base tables are separately listed, and the referenced base objects are recorded as "none documented." The view definition itself, however, unambiguously selects from a single object: EDW_BIM_LSTA_LEADSTATUS_LTC. All columns in the view are derived from that object, with two exceptions: ROW_ID, which is the pseudo-column ROWID aliased as ROW_ID, and OPERATION_CODE, which is an alias of USER_ATTRIBUTE5.

The _LTC suffix on the base object is consistent with Marketing "Lead Target Category" style staging structures. The relationship is strictly one-to-one: no joins, aggregations, filters, or set operations appear in the documented view text. The view is therefore a lightweight column-mapping layer whose principal value is standardization of column names and ordering, plus the addition of a row identifier that ETL tooling can use for change detection.

Key Columns

  • ROW_ID — The ROWID pseudo-column, aliased. Provides a physical row locator usable by ETL change-detection routines.
  • LEAD_STATUS_PK_KEY — Surrogate key for the lead status dimension; the primary join key in warehouse fact loads.
  • ALL_FK_KEY — The consolidated foreign-key key. Central to the "all_fk_key" search term; used for cross-referencing the lead-status record to its parent dimension members in the EDW.
  • ALL_FK — The foreign-key value associated with ALL_FK_KEY; the two columns are used together for key/value resolution.
  • LEAD_STATUS_PK / LEAD_STATUS_DP — Primary key and display value of the lead status.
  • STATUS_CODE, NAME, MEANING, DESCRIPTION — Descriptive attributes of the lead status.
  • USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Descriptive flexfield segments. USER_ATTRIBUTE5 is re-exposed as OPERATION_CODE, indicating that the fifth attribute carries insert/update/delete operation indicators for the ETL load.
  • INSTANCE — Warehouse instance or source-system identifier.
  • LAST_UPDATE_DATE, CREATION_DATE — Audit columns supporting incremental (high-water-mark) extraction.
  • SECURITY_GROUP_ID — Multi-tenant security grouping for row-level data segregation.

Common Use Cases and Queries

In a typical BIM-to-EDW integration, this view is the extraction contract for lead status reference data. Analysts and ETL developers use it to build delta loads based on audit dates, and to resolve foreign keys via ALL_FK_KEY. Because the view is documented as not implemented, queries should be validated against the deployed environment before use.

A representative incremental extraction query:

  • SELECT LEAD_STATUS_PK_KEY, ALL_FK_KEY, ALL_FK, STATUS_CODE, NAME, MEANING, OPERATION_CODE FROM EDW_BIM_LSTA_LEADSTATUS_LTC_IV WHERE LAST_UPDATE_DATE >= :p_high_water_mark;

Filtering by operation type for change-data-capture processing:

  • SELECT ROW_ID, LEAD_STATUS_PK_KEY, OPERATION_CODE FROM EDW_BIM_LSTA_LEADSTATUS_LTC_IV WHERE OPERATION_CODE IN ('I','U','D');

Resolving a specific foreign key to its lead status description:

  • SELECT ALL_FK_KEY, ALL_FK, LEAD_STATUS_PK, NAME, DESCRIPTION FROM EDW_BIM_LSTA_LEADSTATUS_LTC_IV WHERE ALL_FK_KEY = :p_all_fk_key;

Because the view is obsolete in 12.1.1/12.2.2, functional replacements in the current BIM data model should be preferred for new development, with this definition retained only for documentation and migration of legacy interfaces.