Results for “xla_fv_be_gl_v”

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

Overview

XLA_FV_BE_GL_V is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the family of "FV" and "BE" views that present subledger accounting line information in a format compatible with the general ledger journals interface. The name segment "FV" denotes a "flat view" intended for reporting and integration, while "GL" indicates that the output is aligned to the GL_JE_LINES/GL_JE_HEADERS structure. The view exposes a fixed, wide column set that mirrors the columns of the consolidated accounting extract used by the Create Accounting and Transfer to GL programs.

The view is status VALID in ETRM and forms part of the public XLA data model. Its principal reporting role is to make accounting line data—both entered and accounted amounts—queryable using general ledger terminology (JE_HEADER_ID, JE_LINE_NUM, ACCOUNTED_DR, ACCOUNTED_CR, and ACCOUNTING_COMPLETE) rather than the underlying XLA_AE_HEADERS/XLA_AE_LINES identifiers. Because the user search term was "accounting_complete," the ACCOUNTING_COMPLETE column is of particular interest: it is the flag indicating whether the underlying subledger event has been fully accounted and is therefore eligible for transfer to the general ledger.

Underlying Base Objects

ETRM documents a single referenced base object for this view: FV_BE_GL_V (VIEW). This indicates that XLA_FV_BE_GL_V is a wrapper or projecting view defined over FV_BE_GL_V, which in turn is the primary source of the flattened accounting line data. In practice, FV_BE_GL_V and its relatives (for example the FV_BE_XLA_V and FV_BE_GL family) are built by the subledger accounting engine to present accounting event lines in a GL-shaped layout.

The view text is a SELECT that maps source columns such as JE_HEADER_ID, JE_LINE_NUM, ACCOUNTED_CR, ACCOUNTED_DR, ENTERED_CR, ENTERED_DR, APPLICATION_ID, CODE_COMBINATION_ID, CURRENCY_CODE, SET_OF_BOOKS_ID, TRX_DATE, and ACCOUNTING_COMPLETE directly, while forcing many other GL-interface columns to typed NULLs (for example TO_DATE(NULL) ACCOUNTING_DATE, NULL ACCT_LINE_TYPE, NULL COMMENTS, NULL GL_TRANSFER_STATUS, and TO_NUMBER(NULL) ORG_ID). This null-padding technique preserves a uniform column signature across the XLA FV view family so that consumers can reference a common set of column names regardless of the underlying detail available for a given product.

Key Columns

• JE_HEADER_ID / JE_LINE_NUM — Journal header and line identifiers used to correlate the accounting line to its GL journal position.
• ACCOUNTED_DR / ACCOUNTED_CR — Accounted debit and credit amounts in the ledger currency, the values that drive the GL balances.
• ENTERED_DR / ENTERED_CR — Entered debit and credit amounts, before currency conversion.
• ACCOUNTING_COMPLETE — Flag indicating whether the accounting event associated with the line has been completely accounted. This is the column most relevant to the user's search and is central to determining GL-transfer readiness.
• CURRENCY_CODE — Currency of the entered amounts.
• CODE_COMBINATION_ID — Accounting flexfield combination to which the line posts.
• APPLICATION_ID — Identifies the owning subledger application.
• SET_OF_BOOKS_ID — Ledger (set of books) identifier.
• TRX_DATE — Transaction date carried through from the source event.
• ACCOUNTING_DATE, ACCT_LINE_TYPE, GL_TRANSFER_STATUS — Returned as NULL in this view; their populated counterparts reside in the wider XLA accounting line views.

Common Use Cases and Queries

A frequent scenario is verifying which accounting lines are fully accounted before running Transfer to GL. The ACCOUNTING_COMPLETE column is the natural filter for that check:

• Identify lines still awaiting accounting: SELECT je_header_id, je_line_num, accounting_complete FROM apps.xla_fv_be_gl_v WHERE accounting_complete <> 'Y';
• Tie out accounted amounts by currency: SELECT currency_code, SUM(accounted_dr), SUM(accounted_cr) FROM apps.xla_fv_be_gl_v GROUP BY currency_code;
• Reconcile entered versus accounted amounts for a ledger: SELECT set_of_books_id, SUM(entered_dr - accounted_dr), SUM(entered_cr - accounted_cr) FROM apps.xla_fv_be_gl_v GROUP BY set_of_books_id;
• List lines by subledger and application for a period: SELECT application_id, je_header_id, je_line_num, code_combination_id FROM apps.xla_fv_be_gl_v WHERE trx_date BETWEEN :p_start AND :p_end;

Because many columns are null-typed, this view is best used for reporting on the populated GL-oriented columns and for accounting-completion checks; consumers requiring accounting date, line type, or GL transfer status should query the broader XLA accounting line views instead.