Search Results igi_exp_ar_trans_all




Overview
Explore in AI Chat

Overview

IGI_EXP_AR_TRANS_ALL is a transactional table in the IGI — Public Sector Financials International product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM metadata, it stores the receivables transactions that are held within a DU (Document/Disbursing Unit). In practice, this table acts as the intersection register that records which Oracle Receivables customer transactions have been claimed into a given expenditure or disbursing construct managed by the IGI public-sector extensions.

The table is owned by the IGI schema, has a status of VALID, and is documented in ETRM 12.2.2 with 25 columns. The primary key is IGI_EXP_AR_TRANS_PK, defined on the surrogate column AR_TRAN_ID. A unique index, IGI_EXP_AR_TRANS_U1, is also documented on AR_TRAN_ID, making it the principal business-key candidate. Based on the foreign-key topology supplied in the metadata — references outward to RA_CUSTOMER_TRX_ALL and IGI_EXP_DUS_ALL, with no dependent tables — a Data Vault modeling heuristic classifies this object as a link table, i.e., an associative relationship between receivable transactions and DUs. This classification is a modeling suggestion only; the physical table is a standard EBS transactional entity.

Key Information Stored

The most operationally significant columns are:

  • AR_TRAN_ID — surrogate primary key (IGI_EXP_AR_TRANS_PK and unique index IGI_EXP_AR_TRANS_U1). Uniquely identifies each row in the table.
  • CUSTOMER_TRX_ID — foreign key to RA_CUSTOMER_TRX_ALL, identifying the Oracle Receivables transaction held by the DU.
  • DU_ID — foreign key to IGI_EXP_DUS_ALL, identifying the DU that owns or holds the transaction.
  • ORG_ID — the operating unit context, essential for multi-org (MOAC) security and reporting.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and who-columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns used to capture client-specific, context-sensitive data.

The design is deliberate: only three columns carry intrinsic business meaning (CUSTOMER_TRX_ID, DU_ID, ORG_ID), while the remainder support auditability and flexfield extensibility. There are no dependent foreign keys documented, so referential integrity flows outward from this table, not inward.

Common Use Cases and Queries

Typical use cases include identifying all Receivables transactions attached to a disbursing or document unit, reconciling DU balances against AR activity, and reporting transactions by operating unit. A representative query joins to the foreign tables:

SELECT t.ar_tran_id, t.customer_trx_id, t.du_id, t.org_id
FROM igi_exp_ar_trans_all t
WHERE t.org_id = :p_org_id;

To view the AR transaction detail alongside the DU name:

SELECT r.trx_number, r.trx_date, d.du_name
FROM igi_exp_ar_trans_all t, ra_customer_trx_all r, igi_exp_dus_all d
WHERE t.customer_trx_id = r.customer_trx_id
AND t.du_id = d.du_id;

Reporting frequently filters on ORG_ID and date ranges using CREATION_DATE or LAST_UPDATE_DATE, and attribute columns are commonly used in custom DFF-driven analysis.

Related Objects

The most significant related objects, based on the documented foreign-key relationships, are:

  • RA_CUSTOMER_TRX_ALL — joined on IGI_EXP_AR_TRANS_ALL.CUSTOMER_TRX_ID = RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID; the core AR transaction header.
  • IGI_EXP_DUS_ALL — joined on IGI_EXP_AR_TRANS_ALL.DU_ID = IGI_EXP_DUS_ALL.DU_ID; the DU master.
  • IGI_EXP_AR_TRANS_PK — the primary-key constraint/index over AR_TRAN_ID.
  • IGI_EXP_AR_TRANS_U1 — the unique index over AR_TRAN_ID.
  • Related AR lines and distributions (RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST) are typically traversed through RA_CUSTOMER_TRX_ALL for reporting.