Search Results igi_exp_trx_type_pk




Overview
Explore in AI Chat

Overview

The IGI_EXP_TRX_TYPE table resides in the IGI schema and belongs to the IGI - Public Sector Financials International product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store details of the standard applications transaction types used by the exchange protocol. In practical terms, it acts as a reference and classification table that identifies the transaction types exchanged between public-sector financial systems and the receiving applications, providing the linkage between an exchange document type and the transaction type definition consumed by downstream processing.

From a Data Vault modeling perspective, the metadata's heuristic classification describes this object as satellite-leaning. A satellite classification is a modeling suggestion only: the table carries descriptive attributes (such as transaction name, application, and description) anchored to a business key, with a single outbound foreign key (DOC_TYPE_ID) to a parent reference table. This structure is consistent with a reference or lookup satellite rather than a transactional hub or a link.

Key Information Stored

The table is documented with ten columns. The most significant of these are:

  • TRX_TYPE_ID — the surrogate primary key, defined by the unique index IGI_EXP_TRX_TYPE_PK. This is the column referenced by every downstream foreign key.
  • DOC_TYPE_ID — the foreign key to IGI_EXP_DOC_TYPE, tying each transaction type to its parent exchange document type.
  • TRX_NAME — the descriptive name of the standard application transaction type, the primary business label for reporting.
  • APPLICATION — identifies the standard application (such as Payables, Receivables, or Purchasing) that owns or originates the transaction type.
  • DESCRIPTION — free-text detail describing the transaction type.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard EBS WHO columns recording audit trail information.

Note that TRX_TYPE_ID is the sole documented unique-key candidate. No separate business-key unique index on TRX_NAME or APPLICATION is recorded in the ETRM metadata, so the surrogate key serves as the definitive identifier.

Common Use Cases and Queries

Because this table is a reference source for transaction-type definitions, it is most often used to resolve a transaction type ID into a human-readable name or to filter records by originating application. A typical join resolves descriptive attributes for downstream fact rows:

  • Resolve transaction type names: join IGI_EXP_TRX_TYPE to any of its child tables (for example FUN_TRX_TYPES_B or CN_TRX_ALL) on TRX_TYPE_ID to translate surrogate identifiers into TRX_NAME values for reports.
  • Group by application: SELECT APPLICATION, COUNT(*) FROM IGI_EXP_TRX_TYPE GROUP BY APPLICATION to inventory which standard applications contribute transaction types to the exchange protocol.
  • Resolve the document-type relationship: join to IGI_EXP_DOC_TYPE on DOC_TYPE_ID to report each transaction type alongside its parent exchange document type.
  • Audit monitoring: query on LAST_UPDATE_DATE to identify recently maintained transaction-type definitions.

Related Objects

The table participates in a well-defined web of relationships. Its outbound dependence is on IGI_EXP_DOC_TYPE via DOC_TYPE_ID. Numerous tables reference it through TRX_TYPE_ID, including FUN_TRX_TYPES_B, FUN_TRX_TYPES_TL, FUN_TRX_TYPE_AR_MAPS, FUN_TRX_BATCHES, FUN_PERIOD_STATUSES, FUN_INTERFACE_BATCHES, CN_TRX_ALL, CN_TRX_FACTORS_ALL, ZX_REP_TRX_DETAIL_T, JE_IT_LIST_LINES_ALL, and JG_ZZ_VAT_TRX_DETAILS. These relationships confirm the table's role as a central reference point for transaction-type classification across the IGI exchange protocol and related subledger modules.