Results for “acctd_amount_due_remaining”

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

Overview

OZF_X_INVOICES_V is a Trade Management (OZF) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a filtered projection of accounts receivable payment schedule data, presenting invoice header and balance information drawn from the Receivables module in a form suitable for Trade Management reporting and integration. The view is documented as VALID in the ETRM metadata for release 12.2.2. Its principal purpose is to give Trade Management consumers a denormalized, currency-aware invoice picture — transaction number, customer transaction identifier, currency, original and remaining amounts due, transaction date, status, operating unit, transaction class, and customer transaction type — without requiring direct joins against Receivables tables.

The view is particularly relevant to searches involving the column ACCTD_AMOUNT_DUE_REMAINING, since it surfaces the accounted (functional currency) remaining balance alongside the entered-currency equivalent, AMOUNT_DUE_REMAINING.

Underlying Base Objects

The view text is a single-source SELECT over one documented base object: AR_PAYMENT_SCHEDULES_ALL, accessed through its APPS synonym. AR_PAYMENT_SCHEDULES_ALL holds the payment schedules for transactions in Oracle Receivables, including invoice balances, due dates, status flags, and operating unit identifiers, and it is partitioned by operating unit.

The WHERE clause is a multi-org security predicate. It compares ORG_ID to a value derived from the USERENV('CLIENT_INFO') context, decoding the first ten characters of client information and mapping a leading blank to NULL, with a fallback sentinel of -99. Before comparison, both sides are wrapped in NVL(..., -99), so the effective filter is:

• When client information is not populated, ORG_ID is compared against the sentinel -99.
• When an operating unit context is present, only rows for that ORG_ID are returned.
• Rows whose ORG_ID is NULL are normalized to -99 and therefore remain visible when no operating unit context applies.

This construction means the view inherits the standard multi-org access behavior of the underlying table rather than applying an independent, application-level security model.

Key Columns

The view exposes eleven columns, each inherited directly from the base table with no expression or alias transformations:

• TRX_NUMBER — the transaction number of the invoice, used as the user-facing invoice reference.
• CUSTOMER_TRX_ID — the surrogate key of the Receivables transaction, used to join back to AR_CUSTOMER_TRX_ALL and related objects.
• INVOICE_CURRENCY_CODE — the entered currency of the transaction, indicating the currency in which AMOUNT_DUE_ORIGINAL and AMOUNT_DUE_REMAINING are denominated.
• AMOUNT_DUE_ORIGINAL — the original amount due on the transaction in entered currency.
• AMOUNT_DUE_REMAINING — the outstanding balance in entered currency; this is the column most commonly used to determine what remains uncollected.
• ACCTD_AMOUNT_DUE_REMAINING — the remaining balance converted to the ledger's functional currency. When functional and entered currencies differ, this value reflects the accounted amount and is the appropriate basis for accounting and consolidation reporting.
• TRX_DATE — the transaction date of the invoice, supporting period, aging, and trend analysis.
• STATUS — the payment schedule status for the transaction, distinguishing open, closed, and related balance states.
• ORG_ID — the operating unit identifier of the transaction, and the column governed by the multi-org predicate.
• CLASS — the transaction class, for example invoice, credit memo, debit memo, or chargeback.
• CUST_TRX_TYPE_ID — the customer transaction type identifier, allowing a lookup to the transaction type name and category.

Common Use Cases and Queries

Typical scenarios include Trade Management accrual and settlement reporting, outstanding invoice and deduction analysis, and integration extracts that feed accrual or promotion settlement processes. Because the view is currency-aware, it supports both entered-currency reconciliation and functional-currency reporting through ACCTD_AMOUNT_DUE_REMAINING.

A representative query listing open invoices with remaining balances:

• SELECT trx_number, customer_trx_id, invoice_currency_code, amount_due_remaining, acctd_amount_due_remaining, trx_date, status, org_id FROM ozf_x_invoices_v WHERE status = 'OP' ORDER BY trx_date DESC;

A query aggregating functional-currency exposure by operating unit:

• SELECT org_id, COUNT(*) invoice_count, SUM(acctd_amount_due_remaining) accounted_balance FROM ozf_x_invoices_v GROUP BY org_id;

A query joining back to Receivables for transaction type detail:

• SELECT v.trx_number, v.amount_due_remaining, v.acctd_amount_due_remaining, t.name, t.type FROM ozf_x_invoices_v v, ra_cust_trx_types_all t WHERE v.cust_trx_type_id = t.cust_trx_type_id AND v.org_id = t.org_id;

Because the view applies the multi-org predicate internally, queries should be executed with the desired operating unit context set, or with the appropriate MO initialization, to avoid unexpectedly empty result sets.