Results for “gl_je_category_names_v”

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

Overview

The GL_JE_CATEGORY_NAMES_V view is a General Ledger (GL) dictionary object owned by the APPS schema and marked VALID in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes the descriptive identity of journal entry categories, which are the classification codes used to group and control journal entries throughout the accounting cycle. In EBS, journal categories such as Adjustment, Accrual, Revaluation, Payables, and Receivables determine default balancing behavior, posting controls, and the source of an entry.

The ETRM documentation classifies this object as 10SC ONLY, indicating it is a compatibility or legacy-oriented view rather than a primary, fully supported interface. Its principal role is to present the category name columns in a simplified projection, allowing reports, conversions, and integrations to resolve a journal category name without querying the full category definition. Because the view contains no validation logic and no joining to journal headers or lines, it functions purely as a lightweight lookup of category metadata.

Underlying Base Objects

The view is defined over a single base object: GL_JE_CATEGORIES, referenced through the synonym resolved in the APPS schema. No other tables, views, or PL/SQL functions participate in its definition. The documented view text is:

• SELECT JES.USER_JE_CATEGORY_NAME USER_JE_CATEGORY_NAME, JES.JE_CATEGORY_NAME JE_CATEGORY_NAME, JES.DESCRIPTION DESCRIPTION FROM GL_JE_CATEGORIES JES

This one-to-one projection means every row in the view corresponds to exactly one row in GL_JE_CATEGORIES. There is no aggregation, filtering, or outer join, so row counts and key uniqueness are inherited directly from the base table. Consequently, any category that is enabled or disabled in the underlying setup is reflected identically in the view, and the view cannot be used to infer posting status, which resides in the base table's control columns.

Key Columns

The view exposes exactly three columns, each aliased directly from the base table:

• USER_JE_CATEGORY_NAME — The user-defined, display-facing name of the journal category. This is the value typically seen on entry screens and printed on journals, and it is the attribute reporting layers normally present to end users.
• JE_CATEGORY_NAME — The internal, language-independent category identifier. This is the value stored on journal headers and referenced by application logic, making it the appropriate join key when linking category metadata to transactional data.
• DESCRIPTION — The free-text description attached to the category, used for documentation and reporting clarity.

Because the view omits the remaining columns of GL_JE_CATEGORIES, it should not be treated as a substitute for the base table when control attributes such as the category type, balancing requirements, or enabled flag are required.

Common Use Cases and Queries

The view is most useful where only the category name and description are required. Typical applications include reference-data extracts for conversions, simple list-of-values validation in custom reports, and joins that translate the JE_CATEGORY_NAME stored on journal headers into a user-readable label.

A representative query returning all category names is:

• SELECT user_je_category_name, je_category_name, description FROM apps.gl_je_category_names_v ORDER BY user_je_category_name;

A common integration pattern joins the view to journal header data, for example:

• SELECT h.je_header_id, v.user_je_category_name, h.name, h.status FROM apps.gl_je_headers h, apps.gl_je_category_names_v v WHERE h.je_category_name = v.je_category_name;

Because the view is documented as 10SC ONLY, implementations migrating from earlier releases should verify current support before adopting it in new customizations. Where additional category attributes are needed, querying GL_JE_CATEGORIES directly is the recommended alternative.