Search Results igi_exp_tran_unit_def




Overview
Explore in AI Chat

Overview

The IGI_EXP_TRAN_UNIT_DEF view is a secure, organization-filtered reporting object in the APPS schema belonging to the IGI – Public Sector Financials International product. It exposes information about Exchange Protocol transmission units — the units of data exchanged between a public sector agency and a third party (such as a bank or clearing house) under an exchange protocol agreement. As a "_DEF" (definition) view, it presents the default, user-facing projection of the underlying transaction unit data, applying Multi-Org security so that each operating unit sees only its own rows.

Because the view is defined in APPS and marked VALID in ETRM 12.2.2 metadata, it is intended to be queried directly by reports, concurrent programs, and integrations rather than accessed through its base objects. The presence of MRC_* columns (MRC = Multiple Reporting Currencies) confirms that the view supports MRC-enabled reporting, allowing transactions recorded in a primary set of books to be reported in a reporting set of books using stored exchange rate information.

Underlying Base Objects

The view is defined solely over the synonym IGI_EXP_TRAN_UNIT_DEF_ALL, which resolves to the underlying all-organizations base table storing transmission unit records for every operating unit. The view implements row-level security by restricting rows to the current organization:

  • The WHERE clause filters on ORG_ID, comparing the row's organization against the value derived from USERENV('CLIENT_INFO') for the current session.
  • A non-null ORG_ID match is required; rows with a NULL or unmatched ORG_ID are compared against -99, effectively excluding them from normal operation.
  • All columns are a direct 1:1 projection of the base object — no joins, aggregations, or transformations are applied.

Consequently, the view behaves as a filtered window onto IGI_EXP_TRAN_UNIT_DEF_ALL, and any insert or update must target the base object, not the view.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting MRC-converted transmission unit amounts, reconciling exchange rate usage, and integrating transmission unit data into downstream extracts. A representative query retrieving MRC exchange information is:

  • SELECT trans_unit_num, org_id, amount, mrc_amount, mrc_exchange_rate, mrc_exchange_date, mrc_exchange_rate_type FROM apps.igi_exp_tran_unit_def WHERE mrc_exchange_date IS NOT NULL ORDER BY mrc_exchange_date DESC;
  • SELECT trans_unit_num, trans_unit_status, legal_number, third_party_id FROM apps.igi_exp_tran_unit_def WHERE org_id = :p_org_id AND trans_unit_status = 'A';
  • SELECT mrc_amount_exchange_rate_type, COUNT(*), SUM(mrc_amount) FROM apps.igi_exp_tran_unit_def GROUP BY mrc_amount_exchange_rate_type;

Because organization filtering is enforced by the view definition, these queries automatically return only records for the current operating unit. Reports that need cross-organization visibility must query IGI_EXP_TRAN_UNIT_DEF_ALL directly, subject to the appropriate privileges.