Search Results igi_exp_ap_trans




Overview
Explore in AI Chat

Overview

APPS.IGI_EXP_AVAILABLE_TRX_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes transactions eligible for expenditure processing within the Oracle E-Business Suite Advanced Procurement / ETRM (Expenditure Tracking and Reconciliation Management) product family. The view is owned by the APPS schema and is designed to present invoices and customer transactions that have not yet been processed, providing a unified, cross-application read model for downstream ETRM reconciliation and expenditure tracking activities.

The view's architectural significance lies in how it consolidates two distinct transaction streams into a single result set using a UNION. The first branch surfaces Receivables (AR) customer transactions originating from RA_CUSTOMER_TRX_V that satisfy specific eligibility conditions; the second surfaces Payables (AP) invoices from AP_INVOICES_V that carry a particular hold. In both cases, the view also exposes a normalized set of business columns (transaction number, third party, third party site, amount, currency, GL date) so that consumers can treat AR and AP transactions uniformly.

The presence of the "third_party" terminology in the metadata reflects the view's vendor-neutral naming: what upstream is a vendor or a customer is presented here as a generic third party, with corresponding THIRD_PARTY and THIRD_PARTY_SITE columns.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over an extensive set of base objects. The core sources are:

  • RA_CUSTOMER_TRX_V — source of AR customer transaction rows (first UNION branch).
  • AP_INVOICES_V — source of AP invoice rows (second UNION branch).
  • IGI_EXP_AR_TRX_AMOUNTS_V — supplies the transaction amount (TRX_AMOUNT) joined to AR transactions.
  • AP_HOLDS — used to restrict AP invoices to those held with hold lookup code 'AWAIT EXP APP' and no release code.
  • IGI_EXP_AR_TRANS and IGI_EXP_AP_TRANS — referenced in NOT EXISTS subqueries that exclude transactions already processed by ETRM.
  • FND_APPLICATION_VL — supplies the APPLICATION_NAME, joined where the application ID is 222 (Receivables) or 200 (Payables).

Additional documented dependencies are primarily packaged APIs and utilities referenced by the underlying views and columns, including AP_INVOICES_PKG, AP_INVOICES_UTILITY_PKG, AP_PREPAY_UTILS_PKG, ARH_ADDR_PKG, ARPT_SQL_FUNC_UTIL, FND_GLOBAL, FND_PROFILE, FND_USER_AP_PKG, HR_GENERAL, HR_SECURITY, PA_TASK_UTILS and PA_UTILS4. These typically support the security, currency and descriptive-flexfield logic embedded in the source views rather than appearing directly in the outer query text.

Key Columns

The view exposes a harmonized set of columns:

Common Use Cases and Queries

Because the view is a read-only reporting construct, it is most commonly queried directly for reconciliation dashboards, ETRM candidate selection, and third-party expenditure reporting. A representative query is:

  • SELECT APPLICATION, TRANSACTION_NUMBER, THIRD_PARTY, THIRD_PARTY_SITE, AMOUNT, CURRENCY_CODE, GL_DATE FROM APPS.IGI_EXP_AVAILABLE_TRX_V WHERE ORG_ID = :p_org_id;
  • Filtering by source: SELECT * FROM APPS.IGI_EXP_AVAILABLE_TRX_V WHERE APPLICATION_ID = 200; (Payables only) or APPLICATION_ID = 222 (Receivables only).
  • Identifying candidates not yet processed, since the NOT EXISTS clauses already exclude transactions present in IGI_EXP_AR_TRANS and IGI_EXP_AP_TRANS.

When troubleshooting missing rows, examine the AP hold code 'AWAIT EXP APP' and the COMPLETE_FLAG on the AR side, as these are the principal filters imposed by the view definition.