Results for “igi_exp_ar_trx_amounts_v”

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

Overview

IGI_EXP_AR_TRX_AMOUNTS_V is a reporting view owned by the APPS schema within the IGI – Public Sector Financials International product family. Its documented purpose is to return the total transaction amount for Oracle Receivables transactions. The view serves as a summarized aggregation layer that collapses transaction line detail into a single transaction-level amount, identified by CUSTOMER_TRX_ID. It is referenced by two dependent objects — IGI_EXP_AVAILABLE_TRANSACTIONS_V and IGI_EXP_DU_LINES_V — which consume the aggregated TRX_AMOUNT column in downstream expenditure and drawing-line reporting. Because the object is a view rather than a table, it holds no stored data; instead it derives its result set at query time from the Receivables transaction tables. The view status is documented as VALID in both the 12.1.1 and 12.2.2 releases, and it is treated as Oracle proprietary and confidential information in the ETRM documentation. Its narrow column footprint and single aggregation measure make it a lightweight, read-only construct intended for inquiry and reporting rather than transactional processing.

Underlying Base Objects

The ETRM metadata documents the referenced base objects as RA_CUSTOMER_TRX (SYNONYM) and RA_CUSTOMER_TRX_LINES_ALL (SYNONYM). The view text confirms a join between the transaction header table RA_CUSTOMER_TRX and the transaction line table RA_CUSTOMER_TRX_LINES, matched on CUSTOMER_TRX_ID. The aggregation groups by the header identifier and the standard Oracle audit and multi-org columns, producing one row per Receivables transaction. The ETRM 12.2.2 metadata references RA_CUSTOMER_TRX_LINES_ALL, reflecting the table organization changes introduced in Release 12 where the lines table is partitioned and exposed through the _ALL suffix; the view resolves to the appropriate synonym at runtime. In both releases, the underlying objects are standard Oracle Receivables entities, meaning the view is subject to Receivables security, MOAC operating unit filtering through ORG_ID, and any row-level access controls applied to the base tables. Because the view inherits column attributes from its base tables, the transaction amount is sourced exclusively from RA_CUSTOMER_TRX_LINES.EXTENDED_AMOUNT, and no foreign exchange or functional-currency conversion is applied within the view itself.

Key Columns

• CUSTOMER_TRX_ID — The primary identifier of the Receivables transaction. It is the driving grouping key and the join column to all dependent views.
• TRX_AMOUNT — The sum of EXTENDED_AMOUNT across all lines of the transaction. This is the core aggregated measure returned by the view and the reason the object exists.
• CREATION_DATE — The date the transaction header record was created; useful for period and date-range filtering.
• CREATED_BY — The application user ID that created the transaction record.
• LAST_UPDATE_DATE — The most recent modification timestamp of the transaction header.
• LAST_UPDATED_BY — The user ID responsible for the last update.
• LAST_UPDATE_LOGIN — The login ID associated with the last update; supports audit tracing.
• ORG_ID — The operating unit identifier, enabling Multi-Org Access Control filtering in R12 environments.

No transaction number, currency, or customer identifier is exposed; consumers must join back to RA_CUSTOMER_TRX when those attributes are required.

Common Use Cases and Queries

The view is most commonly queried to obtain the aggregate value of a transaction without scanning line-level data. A typical retrieval for a single transaction is:

SELECT customer_trx_id, trx_amount
FROM   apps.igi_exp_ar_trx_amounts_v
WHERE  customer_trx_id = :p_trx_id;

Reporting queries frequently restrict by operating unit and creation date to support period-end expenditure analysis:

SELECT customer_trx_id, trx_amount, creation_date
FROM   apps.igi_exp_ar_trx_amounts_v
WHERE  org_id = :p_org_id
AND    creation_date >= :p_start_date;

Because IGI_EXP_AVAILABLE_TRANSACTIONS_V and IGI_EXP_DU_LINES_V depend on this view, its principal integration role is supplying the transaction value that those views present for available-transaction selection and drawing-unit line reporting. When reconciling expenditure figures, the view provides the transaction-level amount that must tie back to the sum of Receivables lines, and it can be joined to RA_CUSTOMER_TRX on CUSTOMER_TRX_ID to expose transaction number, currency, and customer context. Performance is generally favorable because the aggregation is a straightforward grouped join on indexed columns; in high-volume environments, filtering on ORG_ID or CUSTOMER_TRX_ID is recommended to limit the rows grouped by the underlying query.