Search Results inventory_organization_code




Overview
Explore in AI Chat

Overview

JAI_PLA_ENTRY_AEL_V is a base view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JA (Asia/Pacific Localizations) product family. Its functional purpose is to expose Post-Ledger Adjustment (PLA) manual entry transactions in the shape required by the Subledger Accounting (SLA) and ETRM event/accounting extract framework. The view consolidates PLA transaction rows held in JAI_CMN_RG_PLA_TRXS with their corresponding General Ledger journal header and line detail, producing an "AEL" (Accounting Event Line) style projection. In releases 12.1.1 and 12.2.2 the object is reported as VALID in ETRM, and it is typically consumed as a source for diagnostic queries, reconciliation reports, and custom accounting extracts rather than being queried directly by end users.

Underlying Base Objects

The documented referenced objects confirm that the view joins the PLA transaction table to the GL journal model and to party/vendor master data. JAI_CMN_RG_PLA_TRXS supplies the core PLA register row (REGISTER_ID, VENDOR_ID, VENDOR_CUST_FLAG, VENDOR_SITE_ID and audit columns). GL_JE_HEADERS, GL_JE_LINES, GL_JE_CATEGORIES, GL_JE_SOURCES and GL_DAILY_CONVERSION_TYPES provide journal header/line context, category and source names, and conversion type descriptions; GL_LOOKUPS resolves the GL transfer status meaning. Third-party name resolution is performed through PO_VENDORS and PO_VENDOR_SITES_ALL for supplier records, and through HZ_PARTIES, HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL for customer records. Organisation context derives from HR_ORGANIZATION_INFORMATION and ORG_ORGANIZATION_DEFINITIONS, with HR_GENERAL, HR_SECURITY and FND_GLOBAL used for operating unit and security resolution. GL_IMPORT_REFERENCES, MTL_SYSTEM_ITEMS_B and HR_LOCATIONS_ALL are also referenced in the dependency list, supporting import reference and location lookup. The view therefore sits one layer above the PLA transaction table and mirrors the joining logic used by the JA PLA accounting extract.

Key Columns

Common Use Cases and Queries

The view is most often used to reconcile PLA manual entries against their GL postings and to resolve the third party sub-name for reporting. A typical query filters by ledger and accounting period:

  • SELECT trx_hdr_id, je_header_id, je_line_num, third_party_name, third_party_sub_name, entered_dr, entered_cr, accounted_dr, accounted_cr FROM jai_pla_entry_ael_v WHERE ledger_id = :p_ledger AND accounting_date BETWEEN :p_from AND :p_to;
  • SELECT third_party_sub_id, third_party_sub_name, COUNT(*) FROM jai_pla_entry_ael_v GROUP BY third_party_sub_id, third_party_sub_name ORDER BY 1;
  • SELECT gl_transfer_status, gl_transfer_status_name, SUM(accounted_dr) FROM jai_pla_entry_ael_v GROUP BY gl_transfer_status, gl_transfer_status_name;

Because THIRD_PARTY_SUB_NAME is derived by correlated scalar subqueries against PO_VENDOR_SITES_ALL and HZ_CUST_SITE_USES_ALL, queries that return large volumes of rows can be costly; adding predicates on LEDGER_ID, ACCOUNTING_DATE, TRX_HDR_ID or THIRD_PARTY_SUB_ID is advisable. Note also that the view exposes ENTERED_DR/ENTERED_CR in reversed orientation relative to GL, so reporting logic copied from GL_JE_LINES should be adjusted accordingly.