Search Results igi_exp_dial_unit_def_all_pk

Overview

The table IGI.IGI_EXP_DIAL_UNIT_DEF_ALL is a transaction data table within the Oracle E-Business Suite IGI schema (the former Oracle Public Sector / Financials "Expenditures" product line, which houses the Dialog Unit functionality used by government and public-sector customers). It stores all setup and operational information pertaining to dialog units — a grouping construct that batches invoices and documents together before they are authorized, requisitioned, or transmitted through an external payment or government interface. The object is stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and it is registered in FND Design Data as IGI.IGI_EXP_DIAL_UNIT_DEF_ALL.

In Data Vault modeling heuristic terms, this object classifies as a satellite (or a standalone hub-satellite composite). It carries a synthetic surrogate key (DIAL_UNIT_ID) plus descriptive, state, financial, and who-column attributes that change over the dialog unit's lifecycle. No foreign key relationships were mined to external parent tables, so it currently behaves as an independent entity anchored by its own primary key rather than as a pure link resolving other hubs.

Key Information Stored

The physical schema documents 34 columns. The most significant are:

• DIAL_UNIT_ID — the system-generated numeric surrogate primary key backed by the unique index IGI_EXP_DIAL_UNIT_DEF_ALL_PK.
• DIAL_UNIT_NUM — the human-facing dialog unit number (VARCHAR2 30).
• DIAL_UNIT_NUM_TYPE — indicates whether the number is Actual or Legal.
• DOC_TYPE_ID and TRX_TYPE_ID — document type and transaction type identifiers, which scope the dialog unit.
• THIRD_PARTY_ID and SITE_ID — the third-party (supplier/payee) and site identifiers associated with the unit.
• ORG_ID — the operating unit/organization identifier supporting multi-org access control.
• CURRENCY_CODE — introduced specifically to prevent documents of differing currencies from being combined in the same dialog unit.
• AMOUNT — the monetary value of the dialog unit.
• STATUS — the lifecycle state, one of: Selected, Rejected, Put in transmission unit, Point of acceptance, Requisitioned, or Transmitted.
• DIAL_UNIT_SELECTED_FLAG — selection indicator used during unit assembly.
• TRANS_UNIT_ID — linkage to the transmission unit.
• MRC_EXCHANGE_RATE and related MRC columns — multi-reporting-currency conversion values for foreign-currency documents.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

The business-key candidate is captured by the second unique index, IGI_EXP_DIAL_UNIT_DEF_ALL_U1, defined across DIAL_UNIT_NUM, DIAL_UNIT_NUM_TYPE, DOC_TYPE_ID, TRX_TYPE_ID — meaning a dialog unit number is unique only within the combination of its number type and document/transaction types. This is distinct from the surrogate DIAL_UNIT_ID primary key.

Common Use Cases and Queries

Typical reporting and integration scenarios include tracking dialog units by status, reconciling currency-specific batches, and listing units pending transmission. A representative query retrieving active dialog units for an operating unit is:

• SELECT dial_unit_id, dial_unit_num, status, currency_code, amount FROM igi.igi_exp_dial_unit_def_all WHERE org_id = :p_org AND status = 'Selected';
• Business-key lookup: filter on dial_unit_num combined with dial_unit_num_type, doc_type_id, and trx_type_id to resolve a unit without knowing its surrogate ID.
• Status-based reporting: group counts and amounts by STATUS to monitor the pipeline from Selected through Transmitted.
• Currency validation: identify records where mixed CURRENCY_CODE values risk contaminating a transmission unit.

Related Objects

Based on the documented key structure, the most significant associated objects are the unique indexes and the columns that act as candidate external references. The primary index IGI_EXP_DIAL_UNIT_DEF_ALL_PK enforces uniqueness on DIAL_UNIT_ID, while IGI_EXP_DIAL_UNIT_DEF_ALL_U1 enforces the business key on DIAL_UNIT_NUM, DIAL_UNIT_NUM_TYPE, DOC_TYPE_ID, and TRX_TYPE_ID. Downstream objects logically reference this table via TRANS_UNIT_ID (transmission unit tables), ORG_ID (organization/operating unit definitions), THIRD_PARTY_ID and SITE_ID (supplier/site master data), and the standard WHO columns resolving to FND_USER.USER_ID and FND_LOGINS.LOGIN_ID. Because the Data Vault classification is standalone, no hard foreign keys were mined; relationships are maintained at the application layer rather than through enforced database constraints.