Search Results pa_ael_gl_ei_v




Overview
Explore in AI Chat

Overview

PA_AEL_GL_EI_V is an APPS-owned, VALID database view within the Oracle Projects (PA) module of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. The view presents the Accounting Events Line (AEL) detail for Project expenditures and events together with their associated General Ledger accounting and transfer information. It effectively acts as a unified reporting surface that joins project expenditure/event line data to the subledger accounting lines, the GL journal entries, and the GL import references, exposing both project-side and GL-side attributes in a single row.

Because it spans Projects costing, non-labor resources, customers, suppliers, employees, and GL journals, PA_AEL_GL_EI_V supports cross-module reconciliation of project transactions to their accounting entries. It is a read-only reporting view, not a transactional object, and is typically consumed by reporting tools, extracts, and integration programs that need a flattened, human-readable picture of project accounting activity. Its column list is heavily decorated with descriptive name columns (for example, TRX_CLASS_NAME, GL_TRANSFER_STATUS_NAME, ACCOUNTING_COMPLETE_NAME, CC_TYPE_NAME) so that operational and financial users can interpret codes without additional lookups.

Underlying Base Objects

The view is defined over a broad set of documented base objects. Core Projects tables include PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURE_TYPES, PA_EXPENDITURE_COMMENTS, PA_COST_DISTRIBUTION_LINES_ALL, and PA_CC_DIST_LINES_ALL, which supply the transaction and cost distribution detail. Project and task context comes from PA_PROJECTS_ALL and PA_TASKS, while PA_NON_LABOR_RESOURCES and PA_TRANSACTION_SOURCES provide resource and source classification. PA_SYSTEM_LINKAGES and PA_IMPLEMENTATIONS_ALL contribute system mapping and implementation context.

GL and subledger data are drawn from GL_JE_HEADERS, GL_JE_LINES, GL_IMPORT_REFERENCES, and GL_DAILY_CONVERSION_TYPES. Descriptive lookups are resolved through FND_LOOKUP_VALUES. Party and organization data come from PER_PEOPLE_F, HR_PERSON_NAME, HR_GENERAL, HR_ALL_ORGANIZATION_UNITS_TL, HR_SECURITY, PO_VENDORS, and the PL/SQL packages HR_SECURITY and PA_SECURITY, which enforce organization and project security. XLA_UTIL is referenced for subledger accounting utility logic, and DUAL provides the standard single-row seed for scalar expressions.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling project expenditures to GL, auditing quantity and UOM on accounting event lines, and feeding downstream analytics. The query below illustrates a quantity-focused extract for a given project.

SELECT pa_project_num, pa_task_num, pa_event_num,
       pa_ei_ev_type, pa_quantity, pa_uom,
       pa_period_date, gl_transfer_status_name,
       entered_dr, entered_cr
FROM   apps.pa_ael_gl_ei_v
WHERE  pa_project_num = :project_number
AND    pa_quantity IS NOT NULL
ORDER BY pa_period_date, pa_event_num;

A second pattern summarizes accounting amounts and transfer status for a period.

SELECT gl_transfer_status_name,
       SUM(entered_dr) dr, SUM(entered_cr) cr
FROM   apps.pa_ael_gl_ei_v
WHERE  accounting_date BETWEEN :from_date AND :to_date
GROUP BY gl_transfer_status_name;

Because row-level project and organization security is enforced through PA_SECURITY and HR_SECURITY, queries return only data visible to the requesting user. For performance, filter by PA_PROJECT_NUM or ACCOUNTING_DATE where indexes on the base tables permit.