Results for “gl_je_categories_tl_u2”

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

Overview

GL_JE_CATEGORIES_TL is the translation-enabled (TL) table that stores the language-specific definitions of journal entry categories within Oracle E-Business Suite General Ledger. Journal entry categories classify every journal entry posted to the ledger, determining the origin, purpose, and accounting behavior of each transaction—for example, "Adjustment," "Accrual," "Revaluation," "Purchase Invoices," or "Payroll." The physical table resides in the GL schema and is documented as VALID across EBS 12.1.1 and 12.2.2.

Because the object is a translated table, each category carries one or more rows keyed by language, allowing the category description and user-facing name to appear in the session language while the underlying category key remains language-independent. From a Data Vault modeling perspective, the heuristic classification of this object is hub: it holds the durable, unique business identities (journal entry categories) around which descriptive and transactional satellites would ordinarily be modelled. The 19 documented columns and three unique indexes support the hub conclusion, with the category identity replicated per language and per edition.

Key Information Stored

The table’s documented primary key is GL_JE_CATEGORIES_PK, defined on the business columns JE_CATEGORY_NAME and LANGUAGE. The most significant columns are:

• JE_CATEGORY_NAME — the internal, language-independent identifier for the category; one of the composite primary key columns and a business-key candidate.
• LANGUAGE — the language code of the translation row; the second component of the primary key.
• SOURCE_LANG — language of the source (base) row from which the translation was derived.
• USER_JE_CATEGORY_NAME — the user-visible category name displayed in forms and reports; uniquely indexed by GL_JE_CATEGORIES_TL_U2.
• JE_CATEGORY_KEY — the language-independent surrogate/business key used for cross-language joins; uniquely indexed by GL_JE_CATEGORIES_TL_U3.
• DESCRIPTION — free-text description of the category’s purpose.
• CONSOLIDATION_FLAG — indicates whether the category is eligible for consolidation processing.
• ZD_EDITION_NAME — the edition discriminator appended to all three unique indexes (U1, U2, U3); in the non-editioned base table it resolves to a constant, but in 12.2.2 it supports edition-based redefinition.
• Dated audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Descriptive flexfield columns: ATTRIBUTE1 through ATTRIBUTE5, plus CONTEXT.

The three documented unique indexes—GL_JE_CATEGORIES_TL_U1 (JE_CATEGORY_NAME, LANGUAGE, ZD_EDITION_NAME), U2 (USER_JE_CATEGORY_NAME, LANGUAGE, ZD_EDITION_NAME), and U3 (JE_CATEGORY_KEY, LANGUAGE, ZD_EDITION_NAME)—define the business-key candidates. The true surrogate is not exposed; the composite of JE_CATEGORY_NAME, LANGUAGE, and ZD_EDITION_NAME functions as the persistent identity.

Common Use Cases and Queries

The table is typically joined to transactional journal tables such as GL_JE_HEADERS and GL_JE_LINES to resolve a human-readable category description, and to FA_BOOK_CONTROLS to display the category names configured for each asset-book transaction type. A representative query filters to the session language and resolves the user-facing label:

SELECT jh.je_header_id, jh.name, c.USER_JE_CATEGORY_NAME
FROM   gl_je_headers jh,
       gl_je_categories_tl c
WHERE  jh.je_category_name = c.je_category_name
AND    c.language = USERENV('LANG');

Reporting use cases include: listing all journal sources and categories used in a period, validating that every category referenced by an interface has a translation row, and populating LOVs in custom concurrent programs. Because the table is a hub, ETL into a data warehouse should extract distinct category keys into a hub table and keep the translated names in a satellite keyed by category and language.

Related Objects

The documented foreign-key relationships identify the principal dependents of this object:

• FA_BOOK_CONTROLS — references GL_JE_CATEGORIES_TL through multiple columns (JE_RETIREMENT_CATEGORY, JE_DEPRECIATION_CATEGORY, JE_RECLASS_CATEGORY, JE_ADDITION_CATEGORY, JE_ADJUSTMENT_CATEGORY, JE_TRANSFER_CATEGORY, JE_DEFERRED_DEPRN_CATEGORY, JE_REVAL_CATEGORY, JE_DEPRN_ADJUSTMENT_CATEGORY, and the CIP variants JE_CIP_ADDITION_CATEGORY, JE_CIP_ADJUSTMENT_CATEGORY, JE_CIP_RECLASS_CATEGORY, JE_CIP_RETIREMENT_CATEGORY, JE_CIP_REVAL_CATEGORY, JE_CIP_TRANSFER_CATEGORY). Each maps an asset transaction to the journal category the depreciation engine will use.
• GL_BC_OPTION_DETAILS — references JE_CATEGORY_NAME to link balance-checking option sets to specific categories.
• GL_BC_PACKETS — references JE_CATEGORY_NAME to define the journal categories included in a balance-check packet.

In practice these are complemented by GL_JE_HEADERS/GL_JE_LINES (transactional joins) and the GL journal import/interface tables, all of which resolve category names against this TL table during posting and reporting. Any change to a category’s user name or description should be reviewed against these dependents before update, since the FK columns enforce referential integrity.