Results for “trx_type_name”

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

Overview

The XTR_AR_OPEN_APLD_TRX_V view is a Treasury (XTR) module reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates open (unapplied) Accounts Receivable transactions with their associated payment schedules and party information, presenting a single denormalized record per open transaction/payment-schedule combination. The view joins Receivables transaction tables with Treasury party data (XTR_PARTIES_V) and General Ledger legal-entity/ledger hierarchy information, producing a reconciliation-ready dataset used in treasury integration and financial reporting.

Its design supports Treasury's need to see outstanding customer obligations alongside the legal entity and ledger context required for cash management and exposure reporting. It is not a transactional table; it exposes no DML and is intended for read-only query, extraction, and integration into Treasury dashboards and third-party banking or risk systems.

Underlying Base Objects

The view is defined over the following documented base objects:

• RA_CUSTOMER_TRX_ALL (synonym) — Receivables transaction header; supplies TRX_NUMBER, TRX_DATE, BATCH_SOURCE_ID, CUST_TRX_TYPE_ID, ORG_ID, and completion status.
• AR_PAYMENT_SCHEDULES_ALL (synonym) — Receivables payment schedules; the primary source for AMOUNT_DUE_REMAINING, DUE_DATE, INVOICE_CURRENCY_CODE, and CUSTOMER_ID.
• RA_BATCH_SOURCES_ALL (synonym) — Provides SOURCE_NAME via an outer join on BATCH_SOURCE_ID and ORG_ID.
• RA_CUST_TRX_TYPES_ALL (synonym) — Provides TRX_TYPE_NAME via an outer join.
• HZ_CUST_ACCOUNTS and HZ_PARTIES (synonyms) — Outer-joined to resolve CUSTOMER_ID to CUSTOMER_NAME (HP.PARTY_NAME).
• HR_OPERATING_UNITS (view) — Resolves ORG_ID to ORG_NAME.
• XTR_PARTIES_V (view) — Supplies COMPANY_CODE (PARTY_CODE) and the LEGAL_ENTITY_ID used to derive the primary ledger.
• GL_LEDGER_LE_V (view) — Correlated subquery selecting the LEDGER_ID where LEDGER_CATEGORY_CODE = 'PRIMARY', yielding SET_OF_BOOKS_CURRENCY.
• XTR_USER_ACCESS (package) — Referenced for Treasury access control/security filtering.

Key Columns

• CUSTOMER_TRX_ID / PAYMENT_SCHEDULE_ID — Primary identifiers for the transaction and its payment schedule.
• TRX_NUMBER, TRX_DATE — Invoice/transaction number and date.
• CUSTOMER_ID, CUSTOMER_NAME — Customer account identifier and party name.
• COMPANY_CODE — Treasury party code, aligned to legal entity.
• ORG_ID, ORG_NAME — Operating unit context.
• CURRENCY_CODE, SOB_CURRENCY_CODE — Transaction currency and the primary set-of-books currency for conversion context.
• AMOUNT — NVL(AMOUNT_DUE_REMAINING, 0), the remaining open balance.
• MIN_DUE_DATE — Earliest due date for the schedule.
• APPLIED_TRX — Constant 'Y' flag marking the row as an open/applied transaction record used as a filter indicator.

Common Use Cases and Queries

Typical scenarios include producing an aged open receivables report by legal entity, feeding treasury exposure calculations, and reconciling AR balances to Treasury party codes.

SELECT trx_number, customer_name, company_code,
       currency_code, sob_currency_code, amount, min_due_date
FROM   xtr_ar_open_apld_trx_v
WHERE  org_id = :p_org_id
ORDER BY min_due_date;

To aggregate open exposure per Treasury party and currency:

SELECT company_code, currency_code, SUM(amount) total_open
FROM   xtr_ar_open_apld_trx_v
GROUP BY company_code, currency_code;

Because the view embeds Treasury user access and legal-entity logic, queries executed under an APPS or Treasury responsibility automatically reflect the caller's data security, making it suitable for direct use in concurrent reports, OAF pages, and integration extracts without additional filtering.