Search Results igi_exp_dial_unit_def_all




Overview

The IGI.IGI_EXP_DIAL_UNIT_DEF_ALL table is a Public Sector Financials International (IGI) object that stores all information pertaining to dialog unit setup within Oracle E-Business Suite 12.1.1 and 12.2.2. Dialog units represent the operational configuration entities used by IGI's expenditure and commitment control functionality, capturing the numbering conventions, document and transaction types, authorization hierarchies, and financial attributes that govern how expenditure documents are grouped and processed. The table is owned by the IGI schema and is marked VALID in the ETRM 12.2.2 documentation set.

From a data modeling perspective, the mined FK structure classifies this object as standalone. This heuristic suggests that the table functions as a self-contained definition entity rather than as a transactional detail dependent on a parent business object. Analysts applying Data Vault conventions may therefore treat it as a reference or hub-like definition table, though the absence of formal foreign keys to other IGI tables should be confirmed against the physical schema before finalizing any modeling decision.

Key Information Stored

The table comprises 34 documented columns. Two unique indexes are defined: IGI_EXP_DIAL_UNIT_DEF_ALL_PK on the surrogate key DIAL_UNIT_ID, and IGI_EXP_DIAL_UNIT_DEF_ALL_U1 on the composite business key (DIAL_UNIT_NUM, DIAL_UNIT_NUM_TYPE, DOC_TYPE_ID, TRX_TYPE_ID). The most significant columns include:

  • DIAL_UNIT_ID — surrogate primary key uniquely identifying each dialog unit definition row.
  • DIAL_UNIT_NUM and DIAL_UNIT_NUM_TYPE — the dialog unit number and its numbering type; together with document and transaction type these form the business key.
  • DOC_TYPE_ID and TRX_TYPE_ID — foreign references to the document type and transaction type that classify the dialog unit.
  • THIRD_PARTY_ID — the third-party (supplier, customer, or partner) associated with the dialog unit.
  • ACT_NUMBER, STATUS, and LEGAL_NUMBER — accounting, lifecycle status, and legal identifiers for the unit.
  • AMOUNT, CURRENCY_CODE, and the MRC columns (MRC_AMOUNT, MRC_EXCHANGE_RATE, MRC_EXCHANGE_RATE_TYPE, MRC_EXCHANGE_DATE) — monetary value and the multiple reporting currency conversions applied to the base transaction.
  • MAIN_AUTHORIZER and ACCOUNT_OFFICER — the individuals responsible for authorizing and administering the dialog unit.
  • DIAL_UNIT_SELECTED_FLAG, DIAL_UNIT_CALL_NUM, TRANS_UNIT_ID, PRINT_DATE, and REQ_REJECT — processing state, selection, print, and rejection indicators.
  • ORG_ID and SITE_ID — multi-org and site partitioning attributes supporting operating unit security.

Common Use Cases and Queries

Typical usage centers on validating dialog unit configuration, tracing numbering sequences, and reporting authorization assignments. A common pattern retrieves active dialog units for a given operating unit:

  • SELECT DIAL_UNIT_ID, DIAL_UNIT_NUM, DIAL_UNIT_NUM_TYPE, DOC_TYPE_ID, TRX_TYPE_ID, STATUS, AMOUNT FROM IGI_EXP_DIAL_UNIT_DEF_ALL WHERE ORG_ID = :org_id AND STATUS = 'ACTIVE';
  • Joining on the business key to locate a specific dialog unit: filter by DIAL_UNIT_NUM, DIAL_UNIT_NUM_TYPE, DOC_TYPE_ID, and TRX_TYPE_ID.
  • Reporting on multi-currency exposure by aggregating AMOUNT versus MRC_AMOUNT grouped by CURRENCY_CODE.
  • Auditing authorizers by querying MAIN_AUTHORIZER, ACCOUNT_OFFICER, and THIRD_PARTY_ID.
  • Tracking data migration progress through the UPGRADE_STATUS column after patch or upgrade cycles.

Related Objects

As a standalone definition table without documented foreign keys, IGI_EXP_DIAL_UNIT_DEF_ALL primarily references other objects by value rather than by FK constraint. The most significant associated objects include:

  • Document type definitions — joined via DOC_TYPE_ID to resolve document classifications.
  • Transaction type definitions — joined via TRX_TYPE_ID.
  • Third party / supplier tables — joined via THIRD_PARTY_ID to identify the counterparty.
  • Organization definitions (HR_ALL_ORGANIZATION_UNITS) — joined via ORG_ID for operating unit context.
  • Currency and exchange rate tables (GL_DAILY_RATES, FND_CURRENCIES) — used to interpret CURRENCY_CODE and the MRC exchange rate columns.
  • Transaction unit definitions — related through TRANS_UNIT_ID.
  • IGI expenditure and commitment control objects — the downstream transaction tables that consume the dialog unit definition during document processing.

Because DIAL_UNIT_ID is the surrogate PK and the composite business key drives most lookups, developers should join on business keys where surrogate values are not available, and observe operating unit partitioning via ORG_ID in all multi-org queries.