Search Results glex_view




Overview
Explore in AI Chat

Overview

GLEX_VIEW is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMF – Process Manufacturing Financials product family. It exposes summarized subledger accounting activity drawn from the Process Manufacturing general ledger staging and master tables, presenting aggregated transaction amounts alongside descriptive attributes for the accounting unit and account. Because the object is defined as a view rather than a table, it carries no independent storage; it is a pre-joined, pre-aggregated projection of the underlying GMF accounting tables, which makes it suitable for downstream reporting, reconciliation extracts, and integration with external systems that need a flattened accounting representation without reconstructing the joins themselves.

The metadata confirms the object status as VALID on the APPS schema, indicating that the view compiles cleanly against its referenced synonyms in both Release 12.1.1 and 12.2.2. The description in the ETRM repository (“Glex view”) is deliberately terse, so the functional meaning must be inferred from the view definition and its column list, which is consistent with a general-ledger-style (GL-ex) transaction extract for process manufacturing.

Underlying Base Objects

The documented base objects referenced by the view are all synonyms pointing to the underlying GMF tables:

  • GL_SUBR_LED — the subledger transaction line source, aliased S; provides amounts, quantities, currency, period, and identifiers.
  • GL_SEVT_MST — the sub-event master, aliased V; supplies SUB_EVENT_CODE and links on SUB_EVENT_TYPE.
  • GL_SRCE_MST — the transaction source master, aliased R; supplies TRANS_SOURCE_CODE and links on TRANS_SOURCE_TYPE.
  • GL_ACCU_MST — the accounting unit master, aliased U; supplies the accounting unit number and description.
  • GL_ACCT_MST — the account master, aliased A; supplies the account number, description, and company code.
  • GL_PLCY_MST — the accounting policy master, aliased P; supplies the segment delimiter used to concatenate the accounting unit and account segment.

The joins are key-based on the sub-event type, transaction source type, accounting unit ID, account ID, and company code, and the result is grouped to aggregate amounts, quantities, and base amounts per accounting unit, account, voucher, and period.

Key Columns

  • DEBIT_CREDIT_SIGN, AMOUNT_TRANS, AMOUNT_BASE — the sign indicator and summed transaction and base currency amounts.
  • QUANTITY, QUANTITY_UM — summed quantity and its unit of measure.
  • CURRENCY_TRANS, CURRENCY_BASE, EXCHANGE_RATE — transaction and base currencies with the applied rate.
  • DOC_TYPE, DOC_ID, VOUCHER_ID — document classification and identifiers for drill-back.
  • TRANS_SOURCE_CODE, SUB_EVENT_CODE, SUB_EVENT_TYPE, TRANS_SOURCE_TYPE — descriptive attributes resolved from the master tables.
  • ACCTG_UNIT_ID, ACCT_ID, LEDGER_CODE, CO_CODE, FISCAL_YEAR, PERIOD, GL_TRANS_DATE — accounting and period context.
  • PROJECT_NO — the project number associated with the accounting line; this is the column users search for most often, since it links GMF subledger activity to project costing and capital or expense project reporting.
  • SEGMENT, DESCRIPTION — the concatenated accounting unit and account segment (built with the policy segment delimiter) and its concatenated description.

Common Use Cases and Queries

The view is typically queried for period-end reconciliation, project cost analysis, and interface extracts. A representative query filters on the project number and accounting period:

  • SELECT project_no, acct_id, period, fiscal_year, SUM(amount_base) FROM apps.glex_view WHERE project_no = :project_no AND period = :period GROUP BY project_no, acct_id, period, fiscal_year;
  • Reconciliation of subledger activity to the general ledger by ledger_code, period, and acct_id, comparing amount_trans against amount_base.
  • Project-level cost roll-ups using project_no joined to project reporting tables, with quantity and quantity_um for process yield analysis.
  • Drill-back reporting using doc_id, voucher_id, sub_event_code, and trans_source_code to trace summarized amounts to source documents.

Because GLEX_VIEW aggregates at the accounting-unit, account, voucher, and period level, queries should not expect line-level detail; finer granularity requires querying the base GMF tables directly.