Search Results invoice_amount_remaining




Overview

JG_ZZ_AP_IR_REP_ITF_V is an Oracle E-Business Suite internal reporting interface view owned by the APPS schema. It is registered under FND Design Data as JG.JG_ZZ_AP_IR_REP_ITF_V and carries a VALID status in both 12.1.1 and 12.2.2 environments. The view is classified as Oracle Internal Use Only; Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Any custom reporting or integration that reads from it is therefore performed at the customer's own risk and is not covered by Oracle support.

The object is a denormalized presentation layer over Accounts Payable invoice data, exposing invoice header, supplier, batch, line, distribution, tax, and payment-method attributes in a single flattened row structure. Its name follows the Globalization (JG) naming convention, indicating it originated within the regional/localization reporting stack, specifically as an Accounts Payable Invoice Register reporting interface. The _ITF suffix denotes an interface object, and the underlying base synonym JG_ZZ_AP_IR_REP_ITF suggests a reporting interface table populated by a concurrent program or data-pump process and subsequently read by this view. The presence of REQUEST_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN gives the view the standard multi-org/WHO audit signature expected of interface-style data. The column INVOICE_AMOUNT_REMAINING, the search term of interest, exposes the unpaid balance on an invoice and is the principal reason users query this view.

Underlying Base Objects

Per documented ETRM metadata, JG_ZZ_AP_IR_REP_ITF_V is defined over the following referenced objects:

The view therefore joins the staged interface data to master AP and supplier tables plus EBTax and document sequencing, producing a self-contained invoice register extract.

Key Columns

Common Use Cases and Queries

The view is typically used for invoice register reporting, open-liability aging, and reconciliation extracts, particularly where the remaining balance is required. A representative query filtering on the requested column is:

  • SELECT invoice_num, supplier_name, invoice_date, invoice_amount, invoice_amount_remaining, invoice_currency_code, organization_name FROM apps.jg_zz_ap_ir_rep_itf_v WHERE request_id = :p_request_id AND invoice_amount_remaining > 0 ORDER BY supplier_name, invoice_date;
  • Aggregate open exposure by supplier: SELECT supplier_name, SUM(invoice_amount_remaining) open_balance FROM apps.jg_zz_ap_ir_rep_itf_v WHERE posted_flag = 'Y' GROUP BY supplier_name;
  • Distribution-level reconciliation: SELECT invoice_num, distribution_line_number, distribution_account, distribution_line_amount, invoice_amount_remaining FROM apps.jg_zz_ap_ir_rep_itf_v WHERE liability_ccid = :p_ccid;

Because the object is Oracle Internal Use Only, it should be invoked from standard Oracle programs rather than embedded in supported custom code. Any custom query should pin REQUEST_ID to isolate a specific run and treat the view as read-only.