Results for “ael_id”

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

Overview

The APPS.PN_AEL_BILL_GL_V view is a Property Manager (PN) reporting and integration object that consolidates subledger accounting information for billing and payment transactions. The name follows the Oracle Subledger Accounting (SLA) naming convention, where "AEL" denotes Accounting Event Lines. The prefix "PN" confines the view to the Property Manager module, while "BILL_GL" indicates that the view bridges PN billing activity with General Ledger postings. The view draws its driving rows from the PN_AE_HEADERS and PN_AE_LINES tables, which hold the accounting events and accounting lines generated by SLA for Property Manager transactions.

The object is most commonly consumed in the context of Oracle E-Business Suite 12.1.1 and 12.2.2 by the Account Analysis and Create Accounting reconciliation reports. By joining SLA accounting lines back to their originating source transactions through GL_IMPORT_REFERENCES, the view presents a complete audit trail from the subledger accounting entry to the corresponding General Ledger journal and source document.

Underlying Base Objects

The view is defined over a mixture of transactional, accounting, and reference tables. The documented base objects include: PN_AE_HEADERS and PN_AE_LINES (SLA accounting headers and lines for Property Manager), GL_IMPORT_REFERENCES (the linking table between subledger lines and GL journal lines), GL_JE_CATEGORIES (journal category descriptions), GL_DAILY_CONVERSION_TYPES (currency conversion rate types), FND_LOOKUPS (lookup meanings for payment purpose, line type, and transaction type), PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_TERMS_ALL, PN_LEASES_ALL, and the HZ customer model tables HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, and HZ_CUST_SITE_USES. FND_GLOBAL supplies session and environment context at runtime.

The primary join path connects the GL_IMPORT_REFERENCES row (R.JE_HEADER_ID, R.JE_LINE_NUM) to the SLA accounting line and header, then drives the source transaction through PN_AE_LINES.SOURCE_ID and SOURCE_TABLE. This structure is characteristic of SLA reconciliation views in EBS 12.x.

Key Columns

• ACCOUNTING_RULE_NAME — mapped to AEH.PERIOD_NAME; in this view it exposes the accounting period rather than a rule name as such.
• JE_HEADER_ID / JE_LINE_NUM — the General Ledger journal header and line identifiers retrieved from GL_IMPORT_REFERENCES.
• SET_OF_BOOKS_ID, ORG_ID, ACCOUNTING_DATE — ledger, operating unit, and accounting date of the subledger entry.
• ACCOUNTED_DR / ACCOUNTED_CR, ENTERED_DR / ENTERED_CR — ledger-currency and entered-currency debit and credit amounts.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, CURRENCY_USER_CONVERSION_TYPE — currency and rate information associated with the accounting line.
• ACCT_LINE_TYPE / ACCT_LINE_TYPE_NAME — SLA accounting line type code and its lookup meaning.
• JE_CATEGORY / USER_JE_CATEGORY_NAME — journal category code and its user-facing name from GL_JE_CATEGORIES.
• THIRD_PARTY_ID, THIRD_PARTY_NAME, THIRD_PARTY_SUB_NAME — customer party, account name, and site derived from the HZ tables.
• TRX_NUMBER_DISPLAYED, TRX_LINE_TYPE, TRX_LINE_TYPE_NAME — the source transaction reference and its line type.
• CODE_COMBINATION_ID, SOURCE_ID, SOURCE_TABLE, REQUEST_ID — the accounting flexfield, originating transaction key, and concurrent request that created the entry.

Common Use Cases and Queries

Typical uses include subledger-to-GL reconciliation, account analysis by customer or property, and drilling from the GL journal back to the originating Property Manager transaction. The query below lists accounting lines for a given ledger and period:

• SELECT je_header_id, je_line_num, accounting_rule_name, gl_category_name...

A representative statement is:

SELECT je_header_id, je_line_num, accounting_rule_name,
       je_category, user_je_category_name,
       third_party_name, accounted_dr, accounted_credit...

Filters are normally applied on set_of_books_id, accounting_rule_name (period), org_id, and third_party_id to constrain the result set. Because the view is defined in the APPS schema and is a read-only reporting object, it should be queried directly rather than modified, and large extracts should be limited by ledger and accounting period to avoid full scans across the SLA and HZ join chain. The view is especially relevant when reconciling Property Manager billing events that have been transferred to General Ledger.