Results for “edw_instance_m_iv”

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

Overview

EDW_INSTANCE_M_IV is an Oracle E-Business Suite (EBS) view owned by the APPS schema and registered under the BIS (Business Intelligence System / Applications BIS) product family. It exposes instance-level dimension data from the Enterprise Data Warehouse (EDW) layer, presenting a controlled, read-oriented projection of the EDW_INSTANCE_M structure. In EBS 12.1.1 and 12.2.2, EDW views of this type act as the integration surface between the transactional applications and the BIS/EDW reporting and analytical stack. Rather than exposing the raw staging entity directly to downstream consumers, EDW_INSTANCE_M_IV exposes a curated column list and appends a synthetic OPERATION_CODE attribute, which is a characteristic pattern for EDW interface views that feed change-data-capture or extract pipelines.

The user search term "inst_name" maps directly to the INST_NAME column in this view, which is one of its primary descriptive attributes. This view is therefore the appropriate access point when instance names must be reported or joined to other EDW dimension or fact objects.

Underlying Base Objects

The documented definition of the view is a straightforward projection over a single base object:

• EDW_INSTANCE_M — the sole documented source object; the view SELECTs its columns without joins, unions, or aggregation.

The view text selects ROWID as ROW_ID and carries the instance identifiers and descriptive attributes forward unchanged, with OPERATION_CODE supplied as a literal blank string (' '). This indicates the view is intended as a presentation or interface layer where the operation code is populated or interpreted by the consuming extract process rather than by the database view itself. No additional documented base tables, synonyms, or joins are recorded for this object in the ETRM 12.2.2 metadata; where an EBS instance has been patched or extended, the base table definition should be verified directly against the APPS.EDW_INSTANCE_M DDL.

Key Columns

• ROW_ID — the physical ROWID of the underlying EDW_INSTANCE_M row, useful for high-performance lookups and for identifying duplicate or changed rows.
• INSA_ALL_PK / INSA_ALL_PK_KEY — the source primary key and its surrogate key form for the instance-all association record.
• INSA_NAME — the descriptive name associated with the INSA_ALL_PK relationship.
• INST_DESCRIPTION — the textual description of the instance.
• INST_INSTANCE_DP / INST_INSTANCE_PK / INST_INSTANCE_PK_KEY — the instance data-processing flag, source primary key, and surrogate primary key identifying the instance record.
• INST_NAME — the instance name; this is the attribute most commonly searched and reported on.
• INST_USER_ATTRIBUTE1 through INST_USER_ATTRIBUTE5 — five user-defined descriptive flexfield-style attribute columns available for customer-specific extensions.
• OPERATION_CODE — a constant blank marker column reserved for downstream extract logic; it does not carry data in the view definition.

Common Use Cases and Queries

Typical uses include validating instance dimension membership before loading EDW fact tables, resolving INST_NAME to its surrogate key for star-schema joins, and supplying instance reference data to custom BIS reports or OBIEE/DAC extracts. A basic listing of named instances follows.

• SELECT inst_name, inst_description FROM apps.edw_instance_m_iv ORDER BY inst_name;
• SELECT inst_instance_pk_key, inst_name, inst_user_attribute1 FROM apps.edw_instance_m_iv WHERE inst_name LIKE :p_name;
• SELECT i.inst_name, i.inst_instance_pk_key, f.* FROM apps.edw_instance_m_iv i, apps.edw_fact f WHERE f.instance_pk = i.inst_instance_pk_key;

Because OPERATION_CODE is returned as a blank literal, consumers should not filter on it within the database; instead, treat the view as the read-consistent source of instance attributes and apply change detection at the integration layer. Access is granted through the APPS schema, so grants and synonyms for reporting users should be confirmed before deployment.