Results for “gl_je_categories_v”

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

Overview

GL_JE_CATEGORIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, residing in the General Ledger (GL) product module. It exposes journal entry category definitions maintained in the GL_JE_CATEGORIES base table. Journal categories are a foundational classification mechanism in Oracle General Ledger: every journal entry, whether entered manually or imported from subledgers, must be assigned a category such as Adjustment, Accrual, Budget, Purchase Invoices, Payables, Receipts, or Revaluation. The view presents a simplified, read-only projection of the category definitions, allowing reports, concurrent programs, and integration interfaces to validate or display category names without querying the base table directly.

The object is documented as VALID with an owner of APPS in the ETRM metadata for both release 12.1.1 and 12.2.2, indicating it is a supported, seeded database object rather than a customization. Because it is a view rather than a table, it carries no independent storage and inherits the security posture, grants, and synonyms already established for the APPS schema.

Underlying Base Objects

According to the documented view text, GL_JE_CATEGORIES_V is defined over a single source object:

• GL_JE_CATEGORIES — referenced in the ETRM metadata as a SYNONYM, resolving in the APPS schema to the underlying GL_JE_CATEGORIES table. The view text aliases this object as CAT and selects three of its columns with no joins, filters, or aggregation.

Because the view maps directly to the base table without transformation, all rows present in GL_JE_CATEGORIES are visible through the view, including both seeded Oracle categories and any user-defined categories created during implementation. There is no row-level filtering by ledger, set of books, or category status. Values such as JE_CATEGORY_NAME and DESCRIPTION are therefore returned exactly as stored, with the combination of JE_CATEGORY_NAME and USER_JE_CATEGORY_NAME reflecting Oracle's standard dual-naming convention for seeded reference data.

Key Columns

The view exposes the following three columns, all sourced from GL_JE_CATEGORIES:

• JE_CATEGORY_NAME — The internal, Oracle-maintained category name. This is the value stored on journal entry headers (GL_JE_HEADERS.JE_CATEGORY) and on journal entry lines (GL_JE_LINES.JE_CATEGORY). It is the value used by the Journal Import process, by the Create Accounting program, and by most programmatic interfaces. Seeded values are language-independent and should be treated as the authoritative key.
• USER_JE_CATEGORY_NAME — The user-facing, translatable category name displayed on forms, reports, and the Enter Journals window. Oracle seeds this with a value that matches or closely follows the internal name, but implementations may adjust it. This is the appropriate column for presentation-layer output.
• DESCRIPTION — A free-text description of the category, useful for documenting the intended accounting purpose of the category in reports, lookup listings, and user documentation.

Common Use Cases and Queries

The view is typically used to validate category values during journal import or interface table loading, to populate LOV-style listings in custom programs, and to provide a self-documenting reference for journal reports that display both the internal and user-facing names. Because it references a single synonym and applies no predicates, queries against it are inexpensive and can be safely joined to GL_JE_HEADERS or GL_JE_LINES on JE_CATEGORY_NAME without additional indexing concerns.

Listing all categories with their user-facing names and descriptions:

• SELECT JE_CATEGORY_NAME, USER_JE_CATEGORY_NAME, DESCRIPTION FROM APPS.GL_JE_CATEGORIES_V ORDER BY JE_CATEGORY_NAME;

Joining to journal headers to label posted batches with the user-facing category:

• SELECT H.JE_HEADER_ID, H.NAME, H.JE_CATEGORY, C.USER_JE_CATEGORY_NAME FROM APPS.GL_JE_HEADERS H, APPS.GL_JE_CATEGORIES_V C WHERE H.JE_CATEGORY = C.JE_CATEGORY_NAME AND H.STATUS = 'P';

Identifying categories that lack a descriptive definition for data-quality review:

• SELECT JE_CATEGORY_NAME FROM APPS.GL_JE_CATEGORIES_V WHERE DESCRIPTION IS NULL;

These patterns are portable across 12.1.1 and 12.2.2, as the view definition and APPS ownership are consistent in both releases.