Results for “xtr_ap_source_other”

18 results




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

Overview

APPS.XTR_AP_OPEN_TRX_V is an internal Oracle E-Business Suite view that presents open Accounts Payable transactions exposed through the ETRM (Enterprise Taxation and Regulatory Management) module, the component historically known as eBTax. Within Oracle EBS 12.1.1 and 12.2.2 the view serves as an integration surface between Payables invoice data and the tax determination and reporting infrastructure, allowing open (unpaid or partially applied) supplier invoices to be surfaced with the party, site, organization, and currency context required for regulatory processing. The view is flagged with the standard Oracle warning that it is intended for Oracle Internal Use Only and that Oracle Corporation does not support direct access to applications data through it except from standard Oracle Applications programs. Its view type is Internal, meaning it is not published as a supported public API and its definition may change between releases.

Underlying Base Objects

The view is defined over a combination of AP and shared EBS objects. The primary transactional sources are AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL, which supply invoice header and distribution amounts. Operating unit and ledger context is derived through HR_OPERATING_UNITS and GL_LEDGER_LE_V, while currency conversion behavior is driven by GL_CURRENCY_API. Supplier identity comes from PO_VENDORS, PO_VENDOR_SITES_ALL, and the ETRM party views XTR_PARTIES_V and XTR_USER_ACCESS. Lookup decoding uses AP_LOOKUP_CODES, message formatting uses FND_MESSAGE, and session context is resolved via FND_GLOBAL. The view also references another ETRM view, XTR_AP_OPEN_APLD_TRX_V, which supplies applied-transaction information used to populate the APPLIED_TRX flag. Notably, APPS.XTR_AP_OPEN_TRX_V is not referenced by any other database object, confirming its role as a terminal reporting view rather than a reusable dependency.

Key Columns

The column list provides invoice identifiers and descriptive attributes. INVOICE_ID is the Payables invoice key, and PAYMENT_NUM identifies the associated payment. SOURCE and SOURCE_NAME classify the originating transaction, while TRX_TYPE_ID and TRX_TYPE_NAME describe the transaction type. Organization context is provided by ORG_ID and ORG_NAME. Supplier data is exposed through VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_NAME, and COMPANY_CODE. Transaction details include TRX_DATE, TRX_NUMBER, CURRENCY_CODE, and SOB_CURRENCY_CODE for the ledger currency. Financial measures include AMOUNT together with MAX_DISCOUNTED_AMOUNT, MIN_DISCOUNTED_AMOUNT and the corresponding MAX_DISCOUNTED_DATE and MIN_DISCOUNTED_DATE, which represent discount eligibility windows. MIN_DUE_DATE captures the earliest due date, and APPLIED_TRX (CHAR) indicates whether the transaction has been applied or settled.

Common Use Cases and Queries

Typical usage centers on extracting open invoices for tax reporting, reconciliation, and party-level analysis. A straightforward query retrieves all open transactions for a given operating unit:

  • SELECT INVOICE_ID, TRX_NUMBER, VENDOR_NAME, ORG_NAME, CURRENCY_CODE, AMOUNT, MIN_DUE_DATE FROM APPS.XTR_AP_OPEN_TRX_V WHERE ORG_ID = :p_org_id AND APPLIED_TRX = 'N';
  • Filtering by discount window: SELECT TRX_NUMBER, MAX_DISCOUNTED_AMOUNT, MAX_DISCOUNTED_DATE, MIN_DISCOUNTED_DATE FROM APPS.XTR_AP_OPEN_TRX_V WHERE MIN_DISCOUNTED_DATE >= SYSDATE;
  • Aggregating exposure by supplier: SELECT VENDOR_NAME, SUM(AMOUNT) FROM APPS.XTR_AP_OPEN_TRX_V WHERE APPLIED_TRX = 'N' GROUP BY VENDOR_NAME;

Because the view is internal and unsupported for direct access, these queries should be treated as diagnostic or migration-oriented rather than production interfaces.