Search Results instance_pk_key

Overview

EDW_INSTANCE_LTC_IV is an Oracle E-Business Suite database view owned by the APPS schema. It belongs to the ETRM (Enterprise Territory and Resource Management) family of database objects and function as a read-only presentation layer over the EDW_INSTANCE_LTC table. The trailing suffix "_IV" follows the EBS naming convention for interface or input views, which are typically created to expose a curated projection of columns from a base table for downstream reporting, data extraction, or integration purposes.

In the context of Oracle EBS 12.1.1 and 12.2.2, this view presents instance-level LTC (likely Location/Territory Configuration or a similar internal designation) data alongside surrogate keys. It is frequently referenced in ETRM-related queries where users search for the instance_dp column, which is one of the named columns exposed directly by this view. The view includes a synthetic OPERATION_CODE column populated with a single blank space, a common EBS pattern used to satisfy interface table structures that expect an operation code column for DML-driven integrations.

Underlying Base Objects

The view is defined over a single base object: EDW_INSTANCE_LTC. No additional base tables or joined objects are documented in the ETRM metadata, confirming that EDW_INSTANCE_LTC_IV is a straightforward projection view rather than a join-based view. The definition selects columns directly from the base table without filters, joins, or aggregation, meaning every row present in EDW_INSTANCE_LTC appears in the view.

The metadata for this object does not document any referenced base objects beyond the immediate parent, and no foreign key or lineage relationships are recorded. From a dependency standpoint, the view inherits the storage and indexing characteristics of EDW_INSTANCE_LTC, so query performance against the view is equivalent to querying the underlying table directly.

Key Columns

The view exposes the following columns:

• ROW_ID — The ROWID of the underlying table row, projected as a stable row identifier for the view.
• ALL_FK and ALL_FK_KEY — Foreign key reference columns, with the _KEY variant typically representing a surrogate or alternate key used in ETRM key-generation logic.
• DESCRIPTION — Descriptive text associated with the instance record.
• INSTANCE_PK and INSTANCE_PK_KEY — The primary key of the instance and its key counterpart, used to uniquely identify an instance record.
• INSTANCE_DP — The instance data point column, which is the column most commonly searched for in this context. It represents a specific data attribute associated with the instance.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — The standard EBS descriptive flexfield (DFF) attribute columns, available for customer-specific extensions.
• NAME — The name of the instance.
• LAST_UPDATE_DATE and CREATION_DATE — Standard EBS audit columns tracking record creation and modification.
• OPERATION_CODE — A literal single-space character, included to conform to interface processing expectations.

Common Use Cases and Queries

The view is primarily used in reporting and integration scenarios where a clean projection of instance LTC data is required. Typical use cases include extracting instance data points for ETRM configuration audits, feeding interface tables, and joining to other ETRM views on INSTANCE_PK or ALL_FK.

A representative query retrieving instance data points and descriptions is:

SELECT instance_pk, instance_dp, name, description, last_update_date
FROM apps.edw_instance_ltc_iv
WHERE instance_dp IS NOT NULL
ORDER BY last_update_date DESC;

For integration scenarios that require the operation code placeholder, a query such as the following is used:

SELECT instance_pk_key, all_fk_key, instance_dp, operation_code
FROM apps.edw_instance_ltc_iv
WHERE all_fk_key = :fk_value;

Because the view applies no filtering or transformation, it is also suitable as a source in ETL mappings and materialized view definitions. When troubleshooting ETRM instance data, querying EDW_INSTANCE_LTC_IV is preferred over the base table when only the exposed columns are needed, as it reduces the surface area of columns to be reviewed and provides a consistent interface contract across EBS releases.