Search Results igi_exp_du_type_headers_u1

Overview

IGI.IGI_EXP_DU_TYPE_HEADERS_ALL is the header-level definition table for Dialog Unit (DU) types within the Oracle E-Business Suite Procurement and Spend family, owned by the IGI (Oracle Contracts / Procurement) schema. It stores the master definition of each Dialog Unit type as configured through the form IGIPDUTP. A Dialog Unit represents a logical grouping used in third-party and supplier-facing transactions; the header table captures the descriptive, effective-dating, and organizational attributes that govern how a DU type may be used. The table resides in the APPS_TS_TX_DATA tablespace with an index tablespace of APPS_TS_TX_IDX, and it forms the parent (master) side of several detail relationships.

From a data-modeling perspective, the metadata carries a heuristic Data Vault classification of hub-leaning. Treated as a modeling suggestion, this reflects that the table behaves as a durable, business-keyed master entity — a central reference point from which detail tables hang — rather than as a transactional link or a rapidly changing satellite. The single-column surrogate primary key and the stable business key reinforce this hub-like character.

Key Information Stored

The table contains fourteen documented columns. The most significant are listed below, distinguishing the surrogate key from the business-key candidates.

• DU_TYPE_HEADER_ID — NUMBER surrogate primary key, sequence-generated, forming the physical primary key IGI_DU_TYPE_HEADERS_PK and the unique index IGI_EXP_DU_TYPE_HEADERS_U1.
• DU_TYPE_NAME — VARCHAR2(30) business name of the Dialog Unit Type. Uniqueness must be functionally enforced; it participates with ORG_ID in unique index IGI_EXP_DU_TYPE_HEADERS_U2.
• ORG_ID — NUMBER organization identifier; combined with DU_TYPE_NAME it forms the second unique business-key candidate, enabling multi-org, multi-tenant-style scoping.
• DU_TYPE_DESC — VARCHAR2(100) descriptive text for the Dialog Unit.
• APPLICATION_ID — NUMBER identifying the owning application.
• STP_ONLY — VARCHAR2 Yes/No flag indicating whether the DU type is restricted to use with a single third-party site.
• STP_SITE_ONLY — VARCHAR2 Yes/No flag indicating whether the DU type is restricted to a single third-party site.
• START_DATE / END_DATE — DATE effective-dating pair defining the window during which the DU type is valid and usable.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking row creation and modification.

Common Use Cases and Queries

Typical usage centers on validating or reporting DU type configurations. A common pattern joins header to detail and restrict by effective date.

• Active DU type listing: SELECT du_type_header_id, du_type_name, du_type_desc FROM igi.igi_exp_du_type_headers_all WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE) AND org_id = :p_org_id ORDER BY du_type_name;
• Lookup by business key: querying by DU_TYPE_NAME and ORG_ID leverages the IGI_EXP_DU_TYPE_HEADERS_U2 index for fast retrieval.
• Single third-party restriction reporting: filtering on STP_ONLY = 'Y' OR STP_SITE_ONLY = 'Y' to identify types constrained to specific sites.
• Corporate vs. local scoping: examining ORG_ID values to separate global DU type definitions from organization-specific ones.

Because the table is the header for the DU hierarchy, it is frequently the driving table when extracting full DU definitions for integration with downstream procurement flows.

Related Objects

The header table is referenced by several detail tables through the DU_TYPE_HEADER_ID foreign key:

• IGI_EXP_DUS_ALL — joins on DU_TYPE_HEADER_ID; stores the Dialog Units belonging to each type.
• IGI_EXP_DU_TYPE_DETAILS_ALL — joins on DU_TYPE_HEADER_ID; holds per-type detail attributes.
• IGI_EXP_TU_TYPE_DETAILS_ALL — joins on DU_TYPE_HEADER_ID; holds related third-party unit type details.

These dependent objects establish IGI_EXP_DU_TYPE_HEADERS_ALL as the master hub from which the DU definition tree radiates, confirming its role as the authoritative registry for Dialog Unit types in the Oracle EBS 12.1.1 and 12.2.2 IGI schema.