Search Results gl_je_categories_vl




Overview
Explore in AI Chat

Overview

GL_JE_CATEGORIES_VL is a valid, language-enabled view owned by the APPS schema in Oracle E-Business Suite General Ledger (GL). It exposes journal entry category definitions in the user's session language by selecting from the translation table GL_JE_CATEGORIES_TL. The "_VL" suffix denotes a "view language" object, which is the standard Oracle EBS pattern for exposing a translated (multi-language) entity as a single view whose rows are automatically filtered to the current runtime language.

The view presents the descriptive and audit attributes of journal entry categories — the classification labels applied to journal entries and journal batches, such as "Accrual," "Adjustment," "Revaluation," or "Payables." Because journal categories drive validation, control totals, and reporting groupings across GL, this view is a common reference point for both reporting queries and integration extracts that need to resolve a category name in the correct language.

Underlying Base Objects

Per the documented ETRM metadata (12.2.2), GL_JE_CATEGORIES_VL is defined over a single referenced base object: the synonym GL_JE_CATEGORIES_TL, which resolves to the underlying translation table in the APPS schema. The "_TL" designation identifies a translation table that stores the user-facing, translatable text for each category, keyed by language.

The view's WHERE clause restricts output using the SQL function USERENV('LANG'), filtering rows to the language of the current user session. This means the view returns one row per category for the active language only; callers do not receive all language variants. The domain entity itself is defined in the base table GL_JE_CATEGORIES_B, with GL_JE_CATEGORIES_TL holding the translated name and description. The view also carries a ROWID-based ROW_ID column, allowing downstream consumers to reference the underlying translation row.

Key Columns

  • ROW_ID — ROWID of the underlying translation-table row, exposed as a stable row identifier.
  • JE_CATEGORY_NAME — Translated journal entry category name; the primary descriptive value filtered by language.
  • LANGUAGE / SOURCE_LANG — Language of the current row and the source language from which the translation derives.
  • USER_JE_CATEGORY_NAME — The user-assigned display name for the category.
  • JE_CATEGORY_KEY — The internal, language-independent key that uniquely identifies the category, useful for joins and integration logic.
  • DESCRIPTION — Optional descriptive text for the category.
  • CONSOLIDATION_FLAG — Indicates whether the category participates in consolidation processing.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
  • ATTRIBUTE1–ATTRIBUTE5, CONTEXT — Descriptive flexfield (DFF) context and attribute segments.

Common Use Cases and Queries

Typical scenarios include a values list / LOV for journal-entry entry screens, reporting that resolves category keys to display names, and integration extracts that must populate category labels in the session language. A standard lookup query is:

SELECT je_category_name, je_category_key, consolidation_flag
FROM   apps.gl_je_categories_vl
ORDER BY je_category_name;

To join categories to journal headers for reporting:

SELECT h.je_header_id, c.je_category_name, h.name, h.status
FROM   apps.gl_je_headers h,
       apps.gl_je_categories_vl c
WHERE  h.je_category = c.je_category_key;

Because the view filters on USERENV('LANG'), callers see only the current session language; where all language variants are required, query GL_JE_CATEGORIES_TL directly with an explicit LANGUAGE predicate instead.