Search Results igi_du_type_headers_pk

Overview

IGI_EXP_DU_TYPE_HEADERS_ALL is a Public Sector Financials International (IGI) table that stores the header-level information for the DU (Document Unit) type definition. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this object sits at the center of the expenditure tracking model used by government and public sector organizations to classify, validate, and process expenditure documents against defined document unit types.

Each row represents a single DU type definition, capturing its name, description, effective dates, organization context, and straight-through processing (STP) flags. The table functions as the parent of detail-level definitions and DU instances. Based on the foreign key topology—where three dependent tables reference this header via DU_TYPE_HEADER_ID—a Data Vault modeling exercise would classify this object as hub-leaning, since it holds the durable business key from which dependent satellites and links derive their context.

Key Information Stored

The table contains 14 documented columns. The most significant are:

• DU_TYPE_HEADER_ID — the surrogate primary key, enforced by index IGI_EXP_DU_TYPE_HEADERS_U1. This is the value carried as a foreign key into all dependent tables.
• DU_TYPE_NAME and ORG_ID — together forming the unique business key enforced by index IGI_EXP_DU_TYPE_HEADERS_U2. DU_TYPE_NAME is the user-facing identifier of the DU type; ORG_ID provides the multi-org (operating unit) partition so that the same type name can exist in separate organizations.
• DU_TYPE_DESC — the descriptive text explaining the purpose of the DU type.
• START_DATE and END_DATE — the effective dating range that governs when the DU type definition is active and eligible for use in transaction processing.
• APPLICATION_ID — identifies the owning application, allowing the type definition to be scoped to a particular Oracle application context.
• STP_ONLY and STP_SITE_ONLY — straight-through processing flags that control whether the DU type is restricted to automated processing, and whether that restriction applies at the site level only.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit lineage.

Common Use Cases and Queries

This table is typically queried to resolve the active DU type definitions available within an operating unit, or to join header attributes (name, description, STP flags) onto detail-level and transaction-level records.

• Listing active DU types for an organization:

  SELECT du_type_header_id, du_type_name, du_type_desc
  FROM   igi.igi_exp_du_type_headers_all
  WHERE  org_id = :org_id
  AND    TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE+1);

• Reporting the STP configuration across DU types:

  SELECT du_type_name, stp_only, stp_site_only
  FROM   igi.igi_exp_du_type_headers_all
  WHERE  application_id = :application_id;

• Joining headers to details to produce a full definition report:

  SELECT h.du_type_name, d.*
  FROM   igi.igi_exp_du_type_headers_all h,
         igi.igi_exp_du_type_details_all d
  WHERE  h.du_type_header_id = d.du_type_header_id;

• Auditing recently modified definitions using LAST_UPDATE_DATE as the driver for incremental extracts.

Related Objects

The following objects reference or depend on IGI_EXP_DU_TYPE_HEADERS_ALL through the documented foreign key DU_TYPE_HEADER_ID:

• IGI_EXP_DUS_ALL — joins on DU_TYPE_HEADER_ID; stores the individual DU (document unit) instances that instantiate a defined DU type.
• IGI_EXP_DU_TYPE_DETAILS_ALL — joins on DU_TYPE_HEADER_ID; holds the detail-level definition lines that belong to each DU type header.
• IGI_EXP_TU_TYPE_DETAILS_ALL — joins on DU_TYPE_HEADER_ID; associates TU (Transaction Unit) type details with the DU type header, linking the expenditure document model across both unit dimensions.

Together these three dependent tables form the core schema for IGI expenditure document unit configuration and processing.