Search Results igi_exp_dial_unit_def




Overview
Explore in AI Chat

Overview

The IGI_EXP_DIAL_UNIT_DEF view is a Multi-Org secured database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the product IGI — Public Sector Financials International. As its description states, the view presents all information pertaining to dialog unit setup, exposing the configuration and transactional attributes that govern expenditure dialog units used in public sector processing.

The view is defined with the Multi-Org security predicate, which restricts returned rows to the operating unit identified by the session's CLIENT_INFO context. This means it is intended to be queried within an initialized EBS session, automatically filtering records by ORG_ID. It is therefore the standard access point for reporting, concurrent programs, and integration layers that must present organization-specific dialog unit data without hardcoding operating-unit filters.

For users searching on the term mrc_amount, this view is significant because it is one of the objects that exposes multiple reporting currency (MRC) amount columns alongside the primary functional AMOUNT. This supports cross-currency reporting for public sector expenditure.

Underlying Base Objects

The view is defined over the base object IGI_EXP_DIAL_UNIT_DEF_ALL, referenced through a synonym. The _ALL table stores the complete, unrestricted set of dialog unit records across all operating units. The Multi-Org view applies the standard operating-unit filter:

WHERE NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTR(USERENV('CLIENT_INFO'), 1, 10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTR(USERENV('CLIENT_INFO'), 1, 10))), -99)

Because the view is created against the _ALL synonym, it inherits all column definitions and data types directly. No joins, aggregations, or expressions are applied beyond the Multi-Org predicate, so the view is a straightforward row-filtering layer. The -99 default effectively permits records with a null ORG_ID to surface when no operating unit is set.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on dialog unit setup by operating unit, reconciling functional against reporting-currency amounts, and feeding downstream public sector disbursement processes. A representative query retrieving dialog units with their MRC amount is:

SELECT dial_unit_num, org_id, currency_code, amount, mrc_amount, mrc_amount_exchange_rate FROM apps.igi_exp_dial_unit_def WHERE mrc_amount IS NOT NULL;

To review setup for the session's operating unit only, the Multi-Org predicate handles filtering automatically:

SELECT dial_unit_id, act_number, status, main_authorizer FROM apps.igi_exp_dial_unit_def WHERE status = 'APPROVED';

Because the view is not encrypted and exposes no derived logic, it is safe to use directly in custom reports and BI Publisher data templates that require operating-unit-secured dialog unit data.