Results for “third_party”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGI_EXP_AVAILABLE_TRX_V is a public APPS-schema view shipped with the IGI (Public Sector Financials International) product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to return details of all Payables and Receivables transactions that are available for inclusion into a Dialog Unit. Dialog Units are the IGI mechanism by which third-party (customer or supplier) transactions are grouped and subsequently matched, netted, or otherwise processed for expenditure tracking.

The view presents a consolidated, union-based result set drawn from both the Receivables transaction model (RA_CUSTOMER_TRX_V and IGI_EXP_AR_TRX_AMOUNTS_V) and the Payables invoice model (AP_INVOICES_V). Because it exposes both AR and AP rows in a single, uniform column layout, it functions as the primary feed for IGI's available-transaction lookup, implemented typically as a value set or LOV on Dialog Unit entry forms. It is a reporting and selection view rather than a transactional base object; no DML should be performed against it.

Underlying Base Objects

Documented dependencies for this view include FND_APPLICATION_VL, RA_CUSTOMER_TRX_V, IGI_EXP_AR_TRX_AMOUNTS_V, IGI_EXP_AR_TRANS, IGI_EXP_AP_TRANS, AP_INVOICES_V, AP_HOLDS, and a broad set of PL/SQL packages: 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.

The Receivables branch joins RA_CUSTOMER_TRX_V to IGI_EXP_AR_TRX_AMOUNTS_V on CUSTOMER_TRX_ID and constrains FND_APPLICATION_VL to APPLICATION_ID 222 (Receivables). Only incomplete transactions (COMPLETE_FLAG = 'N') that do not already exist in IGI_EXP_AR_TRANS are returned, ensuring that already-captured AR transactions are excluded. The Payables branch reads AP_INVOICES_V and, by union, supplies supplier invoices with APPLICATION_ID 200 (Payables). Packages such as HR_SECURITY, FND_GLOBAL, and FND_PROFILE drive organization and MOAC security within the underlying views.

Key Columns

• APPLICATION / APPLICATION_ID – Source application name and identifier; 222 for Receivables rows, 200 for Payables rows.
• TRANSACTION_TYPE_DESC / TRANSACTION_TYPE – Human-readable type (from CTT_TYPE_NAME or INVOICE_TYPE) and its internal code (CTT_CLASS or INVOICE_TYPE_LOOKUP_CODE).
• TRANSACTION_NUMBER – Transaction number (TRX_NUMBER for AR, INVOICE_NUM for AP).
• DESCRIPTION / GL_DATE – Transaction comments/description and the general ledger date.
• THIRD_PARTY / THIRD_PARTY_ID – The customer or supplier name and its internal identifier (BILL_TO_CUSTOMER_ID for AR, VENDOR_ID for AP). The user's search term third_party_id maps directly here.
• THIRD_PARTY_SITE / THIRD_PARTY_SITE_ID – Bill-to site name and site-use identifier (AR) or vendor site code and identifier (AP).
• AMOUNT / CURRENCY_CODE – Transaction amount and invoice currency.
• ORG_ID – Operating unit, supporting multi-org filtering and security.
• INVOICE_ID / CUSTOMER_TRX_ID – Primary identifiers of the source document; the AR branch sets INVOICE_ID to -999 and the AP branch sets CUSTOMER_TRX_ID to -999.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns.

Common Use Cases and Queries

Typical usage is to enumerate transactions eligible for Dialog Unit assignment, filtered by third party. Because the view already excludes transactions captured in IGI_EXP_AR_TRANS and only returns incomplete AR records, a straightforward query yields the candidate set.

List available transactions for a given third party:

SELECT application, transaction_number, transaction_type_desc,
       third_party, amount, gl_date, currency_code
FROM   igi_exp_available_trx_v
WHERE  third_party_id = :p_third_party_id
ORDER  BY gl_date;

Restrict to Payables or Receivables:

SELECT transaction_number, third_party, amount
FROM   igi_exp_available_trx_v
WHERE  application_id = 200;   -- 222 for Receivables

Filter by operating unit and currency:

SELECT transaction_number, third_party, amount
FROM   igi_exp_available_trx_v
WHERE  org_id = :p_org_id
AND    currency_code = 'USD';

These query patterns support Dialog Unit creation, reconciliation reporting, and cross-module extraction of outstanding third-party transactions across both Payables and Receivables.