Results for “xla_fv_pya_gl_v”

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

Overview

APPS.XLA_FV_PYA_GL_V is a Subledger Accounting (XLA) view that exposes general ledger journal entry data for a subledger application in a form compatible with the standard XLA accounting line interface. Its name follows the XLA "FV" (Functional View) naming convention, where FV denotes a view over the final accounting representation, PYA refers to the source product or subledger family, and GL denotes that the payload represents general ledger journal entries rather than subledger accounting lines. The view is owned by the APPS schema and has a VALID status within the E-Business Suite 12.1.1 and 12.2.2 environments.

The principal role of this view is to present GL-side journal data through the column contract expected by XLA reporting and integration layers. Rather than exposing a full set of subledger attributes, it returns a fixed projection in which GL-specific columns (journal header and line identifiers, entered and accounted amounts, accounting completeness, and set of books) are populated, while subledger-only attributes are emitted as typed NULL placeholders. This makes the view a conforming producer in union queries that consolidate GL and subledger accounting output.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over two referenced base objects:

• FV_PYA_GL_V (VIEW) — the immediate source of the journal and accounting columns projected by XLA_FV_PYA_GL_V.
• FND_GLOBAL (PACKAGE) — the standard EBS global-value package, referenced to supply runtime context (such as the current user and application/session identifiers) used in the view definition.

Because FV_PYA_GL_V is itself a view, XLA_FV_PYA_GL_V functions as a presentation layer that reshapes the underlying GL functional view into the XLA column layout. The entire definition is a single SELECT over FV_PYA_GL_V, meaning no base tables are directly joined; all physical data access occurs through the referenced view.

Key Columns

The view projects a substantial column set. The columns populated from FV_PYA_GL_V carry meaningful GL data:

• JE_HEADER_ID and JE_LINE_NUM — the GL journal header identifier and journal line number identifying the accounting entry.
• ENTERED_DR / ENTERED_CR — entered debit and credit amounts in the transaction currency.
• ACCOUNTED_DR / ACCOUNTED_CR — accounted debit and credit amounts in the ledger currency.
• CURRENCY_CODE, SET_OF_BOOKS_ID, CODE_COMBINATION_ID, and APPLICATION_ID — the currency, ledger, accounting flexfield combination, and source application.
• ACCOUNTING_COMPLETE — the accounting completion status flag.

The remaining columns — including AE_HEADER_ID, AE_LINE_REFERENCE, ACCOUNTING_DATE, GL_TRANSFER_STATUS, TRX_NUMBER_C, TRX_DATE, THIRD_PARTY_ID, and the tax columns such as TAXABLE_ENTERED_DR and TAX_CODE — are cast as typed NULL values. They exist solely to satisfy the common XLA interface shape and are not sourced from GL.

Common Use Cases and Queries

This view is typically consumed by XLA and GL reconciliation reports, subledger-to-GL transfer diagnostics, and custom integration extracts that expect a uniform journal-line structure. A simple query retrieving core journal amounts for a given ledger might read:

• SELECT je_header_id, je_line_num, currency_code, entered_dr, entered_cr, accounted_dr, accounted_cr FROM xla_fv_pya_gl_v WHERE set_of_books_id = :ledger_id;
• SELECT COUNT(*), SUM(accounted_dr - accounted_cr) FROM xla_fv_pya_gl_v WHERE accounting_complete = 'Y' GROUP BY set_of_books_id;
• Union with a subledger-side XLA view to build a consolidated journal listing across sources.

Because all data flows through FV_PYA_GL_V, queries should be reviewed against that view's own performance profile, and access should be granted consistently with the APPS schema privileges on both views and FND_GLOBAL.