Results for “igi_exp_trx_type”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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_TYPEto any of its child tables (for exampleFUN_TRX_TYPES_BorCN_TRX_ALL) onTRX_TYPE_IDto translate surrogate identifiers intoTRX_NAMEvalues for reports. - Group by application:
SELECT APPLICATION, COUNT(*) FROM IGI_EXP_TRX_TYPE GROUP BY APPLICATIONto inventory which standard applications contribute transaction types to the exchange protocol. - Resolve the document-type relationship: join to
IGI_EXP_DOC_TYPEonDOC_TYPE_IDto report each transaction type alongside its parent exchange document type. - Audit monitoring: query on
LAST_UPDATE_DATEto 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.
-
Stores details of the standard applications transaction types used by exchange protocol
-
Stores details of the standard applications transaction types used by exchange protocol
-
TABLE: IGI.IGI_EXP_TRX_TYPE 12.2.2
-
TABLE: IGI.IGI_EXP_TRX_TYPE 12.1.1
-
VIEW: IGI.IGI_EXP_TRX_TYPE# 12.2.2
-
View: IGI_EXP_TRAN_UNIT_V 12.1.1
Displays information about Echange Protocol transmission units.
APPS.IGI_EXP_TRAN_UNIT_V·↳ FND_USER·↳ IGI_EXP_TRAN_UNIT_DEF·↳ IGI_EXP_TRX_TYPE·Explore IGI module →
-
View: IGI_EXP_TRAN_UNIT_V 12.2.2
Displays information about Echange Protocol transmission units.
APPS.IGI_EXP_TRAN_UNIT_V·↳ FND_USER·↳ IGI_EXP_TRAN_UNIT_DEF·↳ IGI_EXP_TRX_TYPE·Explore IGI module →
-
VIEW: IGI.IGI_EXP_TRX_TYPE# 12.2.2
-
FUN_TRX_TYPES_TL stores the translatable column details for the Intercompany transaction types.
-
FUN_TRX_TYPES_TL stores the translatable column details for the Intercompany transaction types.
-
JE_IT_LIST_LINES_ALL table contains Italian Annual Supplier and Customer listing extract detail data
-
Revenue class transaction factors
-
Revenue class transaction factors
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
FUN_TRX_TYPES_B stores the Intercompany transaction types defined.
-
FUN_TRX_TYPE_AR_MAPS stores the mapping between the Intercompany transaction type and the Receivables Transaction Type and Receivables Memo Line. This mapping is used to create Receivables invoices when the Intercompany transactions are tra
-
FUN_TRX_TYPE_AR_MAPS stores the mapping between the Intercompany transaction type and the Receivables Transaction Type and Receivables Memo Line. This mapping is used to create Receivables invoices when the Intercompany transactions are tra
-
FUN_TRX_TYPES_B stores the Intercompany transaction types defined.
-
JE_IT_LIST_LINES_ALL table contains Italian Annual Supplier and Customer listing extract detail data
-
FUN_PERIOD_STATUSES stores the Intercompany period statuses if an Intercompany calendar has been defined in system options. Intercompany period statuses are maintained at the Intercompany Transaction Type level i.e. periods can be opened an
-
FUN_PERIOD_STATUSES stores the Intercompany period statuses if an Intercompany calendar has been defined in system options. Intercompany period statuses are maintained at the Intercompany Transaction Type level i.e. periods can be opened an
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
FUN_TRX_BATCHES stores information about the Intercompany transaction batches. The BATCH_NUMBER and INITIATOR_ID together form a unique key. An Intercompany transaction batch can contain many transactions for multiple recipients.
-
FUN_TRX_BATCHES stores information about the Intercompany transaction batches. The BATCH_NUMBER and INITIATOR_ID together form a unique key. An Intercompany transaction batch can contain many transactions for multiple recipients.
-
/*# * Open interface table for Intercompany Batches. * @rep:scope public * @rep:lifecycle active * @rep:displayname Intercompany Batches Interface * @rep:product FUN * @rep:category BUSINESS_ENTITY FUN_INTERCOMPANY_BATCH */
-
/*# * Open interface table for Intercompany Batches. * @rep:scope public * @rep:lifecycle active * @rep:displayname Intercompany Batches Interface * @rep:product FUN * @rep:category BUSINESS_ENTITY FUN_INTERCOMPANY_BATCH */
-
Contains CN transactions picked up in the AR data collection process.
-
Contains CN transactions picked up in the AR data collection process.
-
Contains AP, AR and GL Transactions selected for VAT reporting
-
Contains AP, AR and GL Transactions selected for VAT reporting
-
This table stores the tax lines information from Payables, Receivables and General Ledger.
-
This table stores the tax lines information from Payables, Receivables and General Ledger.
-
eTRM - IGI Tables and Views 12.2.2
This is a temporary table used for GBV migration from 10.7/11.03 to 11i.
-
eTRM - IGI Tables and Views 12.1.1
This is a temporary table used for GBV migration from 10.7/11.03 to 11i.
-
12.2.2 DBA Data 12.2.2
-
eTRM - IGI Tables and Views 12.1.1
This is a temporary table used for GBV migration from 10.7/11.03 to 11i.