Search Results edw_source_instances




Overview
Explore in AI Chat

Overview

The BIS.EDW_SOURCE_INSTANCES table is a standalone configuration and metadata repository within the Applications BIS (Business Intelligence System) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the set of source instances from which the Enterprise Data Warehouse (EDW) and related BIS extraction programs draw data. Each row represents one source instance registered for warehouse processing, carrying the instance identifier, enablement state, and linkage to the warehouse-to-instance mapping. Because the table is owned by the BIS schema, it is populated and referenced by BI System Administration and Warehouse Builder-style setup processes rather than by transactional application modules.

Mined foreign-key structure classifies this object heuristically as a standalone entity. Its only documented inbound reference is the self-contained column ROW_ID pointing to CS_SYSTEMS_ALL_B_TEMP. In Data Vault modeling terms, this suggests the table behaves less like a conventional hub surrounded by satellites and more like an isolated reference or control table whose business identity is captured by the unique INSTANCE_CODE. Practitioners building a Data Vault layer should treat INSTANCE_CODE as the natural business key and the surrogate INSTANCE_PK/INSTANCE_PK_KEY as the technical key.

Key Information Stored

The table comprises 35 documented columns. The most operationally significant are listed below; the remaining columns are auditing and descriptive attributes.

Common Use Cases and Queries

Typical usage centres on diagnostics and setup validation for the EDW source-instance configuration. A common query enumerates enabled instances:

  • SELECT instance_code, name, warehouse_to_instance_link FROM bis.edw_source_instances WHERE enabled_flag = 'Y';
  • Join to CS_SYSTEMS_ALL_B_TEMP on ROW_ID to enrich instance records with system definitions.
  • Filter on COLLECTION_STATUS and ERROR_CODE to isolate instances with failed or incomplete collections.

Reporting use cases include auditing which instances are registered versus enabled, reconciling concurrent request history via REQUEST_ID, and validating instance mappings before initiating a warehouse load.

Related Objects

  • CS_SYSTEMS_ALL_B_TEMP — referenced by EDW_SOURCE_INSTANCES.ROW_ID; the primary related table.
  • EDW_SOURCE_INSTANCES_U1 — the unique index on INSTANCE_CODE.
  • BIS warehouse configuration and collection-status tables that consume INSTANCE_PK and WAREHOUSE_TO_INSTANCE_LINK.
  • Concurrent processing tables joined via REQUEST_ID.