Search Results jg_zz_ap_ir_rep_itf_v




Overview
Explore in AI Chat

Overview

JG_ZZ_AP_IR_REP_ITF_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the JG (Regional Localizations) product family. Its documented purpose is to present the Invoice Register — a country-specific localization report that consolidates Payables invoice data for statutory reporting, particularly in jurisdictions where the JG localization layer is deployed. The view is valid in both 12.1.1 and 12.2.2 and is implemented as a join-driven SELECT rather than a stored table, meaning it always reflects current transactional state in the underlying Payables tables.

The view's design centers on the interface table JG_ZZ_AP_IR_REP_ITF, which supplies invoice, line, and distribution identifiers together with accounting flexfield segments and descriptive attributes. The join to AP_INVOICES_ALL, AP_INVOICE_LINES_ALL, and AP_INVOICE_DISTRIBUTIONS_ALL enriches those interface rows with live invoice header, line, and distribution details, while supporting lookups provide vendor, batch, payment method, tax, and document sequence information. This makes the view a single-denormalized source for the Invoice Register layout.

Underlying Base Objects

The view is defined over a mixture of base tables, synonyms, and views. The documented referenced objects are: AP_BATCHES_ALL, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_LINES_ALL, AP_TAX_CODES_ALL, FND_DOCUMENT_SEQUENCES, JG_ZZ_AP_IR_REP_ITF, and ZX_LINES (all accessed via synonyms), together with the views AP_LOOKUP_CODES, IBY_PAYMENT_METHODS_VL, PO_VENDORS, and PO_VENDOR_SITES_ALL, and the FND_GLOBAL package. The principal join is IRT.INVOICE_ID = INV.INVOICE_ID, with outer joins (+) into lines, distributions, batches, and document sequences so that invoices lacking a given subordinate record still appear.

Vendor data flows through PO_VENDORS and PO_VENDOR_SITES_ALL, tax through ZX_LINES, and payment method through the IBY payment methods view. AP_LOOKUP_CODES is joined multiple times (aliased ALC1, ALC3, ALC4, ALC5) to translate coded values such as invoice type and distribution attributes into displayed field text. FND_GLOBAL is referenced for session context, and FND_DOCUMENT_SEQUENCES supplies the legal document sequence value for the invoice.

Key Columns

Common Use Cases and Queries

The view is typically queried by the PG/AP localization report program, but developers and analysts may select from it directly to extract invoice register data, validate localized reporting, or trace description fields. A representative query returning invoice descriptions and related supplier information is:

SELECT invoice_num, invoice_date, vendor_name, description
FROM   apps.jg_zz_ap_ir_rep_itf_v
WHERE  request_id = :p_request_id
ORDER  BY invoice_num;

Because header, line, and distribution descriptions are exposed separately, filters such as WHERE description LIKE '%&keyword%' or WHERE line.description LIKE '%&keyword%' are common when users search for a specific invoice description. Joining on INVOICE_ID, LINE_NUMBER, or INVOICE_DISTRIBUTION_ID allows the view to be correlated with AP_INVOICES_ALL or AP_INVOICE_LINES_ALL for drill-down. Note that the view relies on AP_LOOKUP_CODES and FND_GLOBAL, so querying it outside a properly initialized EBS session may yield incomplete displayed-field values.