Search Results instance_dp

Overview

EDW_INSTANCE_LTC_IV is a view owned by the APPS schema in Oracle E-Business Suite, delivered under the BIS (Business Intelligence System) product family. It is a VALID database object in both EBS 12.1.1 and 12.2.2. The suffix "_IV" follows Oracle's convention for an interface or integration view — a lightweight projection built on top of a base table, intended for consumption by downstream reporting, extract, or warehouse processes. The view exposes the structure of EDW_INSTANCE_LTC with an added literal column, OPERATION_CODE, which is hard-coded to a single space (' '). This constant placeholder is characteristic of interface views that feed Oracle's Enterprise Data Warehouse / Business Intelligence extract layer, where a uniform column set is required irrespective of whether the source system populates every attribute.

Underlying Base Objects

The view is defined over a single base object: EDW_INSTANCE_LTC. No other referenced objects are documented in the ETRM metadata, and the view definition contains no joins, unions, or subqueries — it is a straight column-level projection with a ROWID alias and a literal. The use of ROWID ROW_ID provides a stable row identifier for the underlying EDW_INSTANCE_LTC record, which is useful in extract processes that need to correlate a warehouse row back to its source. Because the view selects directly from the base table without aggregation or filtering, it inherits the base table's constraints, grants, and indexing behaviour. Any predicate applied against the view is pushed down to EDW_INSTANCE_LTC, so performance is governed entirely by the base table's indexes and the query's filter columns (typically INSTANCE_PK_KEY or ALL_FK_KEY).

Key Columns

• ROW_ID — the ROWID of the underlying EDW_INSTANCE_LTC row, used as a surrogate/technical identifier.
• ALL_FK — the all-purpose foreign key column, holding a denormalised reference value from the source instance row. In the context of a user searching for "all_fk", this is the column of interest: it is the generic FK carrier that links the instance record to its parent entity.
• ALL_FK_KEY — the translated or dimension-key counterpart of ALL_FK, typically populated during ETL so that the FK resolves to a warehouse dimension surrogate key.
• INSTANCE_PK / INSTANCE_PK_KEY — the primary key of the instance row and its corresponding warehouse key.
• INSTANCE_DP — the data-provider / source-system descriptor for the instance.
• NAME, DESCRIPTION — human-readable labels for the instance record.
• USER_ATTRIBUTE1 … USER_ATTRIBUTE5 — the standard Oracle DFF (descriptive flexfield) attribute columns, carrying customer-defined context values.
• CREATION_DATE, LAST_UPDATE_DATE — the standard audit columns used for incremental (delta) extraction.
• OPERATION_CODE — a literal single-space constant, reserved for the extract framework to stamp INSERT/UPDATE/DELETE semantics.

Common Use Cases and Queries

The view is typically consumed by BIS/EDW extraction jobs rather than by end-user forms or concurrent programs. A common requirement is resolving an instance record through its generic foreign key, which is the canonical use of ALL_FK. For example, to list instances belonging to a particular parent entity:

• SELECT instance_pk, name, all_fk, last_update_date FROM apps.edw_instance_ltc_iv WHERE all_fk = :p_all_fk;

For incremental feed extraction, the audit columns drive the predicate, and ROW_ID provides the reconciliation handle:

• SELECT row_id, instance_pk, instance_pk_key, operation_code FROM apps.edw_instance_ltc_iv WHERE last_update_date >= :p_since AND last_update_date < :p_until;

Because OPERATION_CODE is always a blank space, an ETL layer that expects a change indicator must supply that value from its own change-capture mechanism. The DFF attributes are frequently selected alongside ALL_FK to enrich warehouse dimensions with customer-specific context. As with all APPS-owned BIS views, direct DML against EDW_INSTANCE_LTC_IV is not supported; maintenance of the underlying instance rows is performed against EDW_INSTANCE_LTC by the owning BIS processes.