Results for “use_nl”

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

Overview

APPS.JAI_PO_REC_AEL_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that presents localized accounting event data for purchase order receipt transactions within the Oracle Financials Subledger Accounting (SLA) framework. It joins Journal Entry (JE) header, line, and import reference details to receipt transactions captured in the JAI (India Localization) and RCV tables, producing a consolidated, drillable accounting extract for PO receipts.

The view is typically consumed by reconciliation reports, subledger drill-down utilities, and custom extracts that need to trace a general ledger journal entry back to its originating receipt, shipment, and vendor context. Because it pinpoints the GL_IMPORT_REFERENCES_N3 index on the GL_IMPORT_REFERENCES table — as evident from the INDEX(gjr GL_IMPORT_REFERENCES_N3) hint in its definition — the view is optimized to drive off the import reference linkage between SLA journals and source transactions rather than scanning JE headers.

Underlying Base Objects

The view draws on several categories of base objects:

• Accounting/GL tables: GL_JE_HEADERS, GL_JE_LINES, GL_JE_SOURCES, GL_JE_CATEGORIES, GL_DAILY_CONVERSION_TYPES, and GL_IMPORT_REFERENCES.
• Receipt and RGM tables: RCV_SHIPMENT_LINES, JAI_RCV_HEADERS, JAI_RCV_LINES, JAI_RCV_RGM_LINES, JAI_RCV_TRANSACTIONS, JAI_RGM_TRX_RECORDS, and MTL_MATERIAL_TRANSACTIONS.
• Reference/Descriptive objects: PO_VENDORS, PO_VENDOR_SITES_ALL, HR_LOCATIONS, and MTL_UNITS_OF_MEASURE_VL.
• Program units: FND_GLOBAL, HR_GENERAL, and JAI_DRILLDOWN_UTILS_PKG.

The JAI and RCV objects supply source transaction detail, while the GL objects supply the resultant subledger journal lines. GL_IMPORT_REFERENCES serves as the crucial bridge tying SLA-generated journal lines back to their originating receipt transaction.

Key Columns

• Event context: event_type (constant 'PO Receipt'), event_description, trx_class/trx_class_name (both 'JAI PO REC'), trx_type, trx_hdr_id, trx_hdr_table ('jai_rcv_transactions').
• Accounting amounts: Entered_Dr, Entered_Cr, Accounted_Dr, Accounted_Cr, Account_Id, Accounting_Date.
• Journal identification: JE_Header_Id, JE_Line_Num, Je_Category, Je_Source, and user-facing names User_Je_Category_Name and User_Je_Source_Name.
• Currency: Entered_Currency, currency_conversion_rate, currency_conversion_date, currency_conversion_type, currency_user_conversion_type.
• Receipt detail: receipt_num, receipt_date, receipt_line_number, shipment_num, shipped_date, item_id, quantity, sub_inventory, inventory_org_id.
• Tax detail: excise_inv_num, excise_invoice_date, vat_inv_num, vat_invoice_date.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is commonly used to reconcile PO receipt subledger journals, drill from a GL balance to a receipt, and produce India-specific excise/VAT reporting extracts.

• Reconciling journals to receipts by receipt number or date range.
• Drill-down from a journal header/line to the originating receipt transaction.
• Tax reporting using the excise and VAT invoice columns.

A representative query filters on the GL import reference index path:

SELECT receipt_num, receipt_date, JE_Header_Id, JE_Line_Num, Entered_Dr, Entered_Cr, Accounted_Dr, Accounted_Cr FROM APPS.JAI_PO_REC_AEL_V WHERE JE_Header_Id = :p_je_header_id;

Because the view already supplies the link between the JE and its receipt source, it eliminates manual joins across RCV, JAI, and GL tables, making it a practical building block for custom SLA and localization reporting.