Search Results gl_je_inclusion_rules




Overview
Explore in AI Chat

Overview

GL_JE_INCLUSION_RULES is a General Ledger configuration table in Oracle E-Business Suite (12.1.1 / 12.2.2) that stores Journal Inclusion Rules. Inclusion rules define which journal sources and journal categories are permitted to be included when a journal rule set is applied — for example, during journal import, consolidation, or the creation of eliminating and suspense entries. Each row represents the mapping between a journal rule set, a journal source, and a journal category, together with flags that determine whether that combination is included and whether the end user may modify the behavior at runtime.

The table is owned by the GL schema and is classified as VALID in the ETRM data model. Applying the heuristic Data Vault classification provided in the metadata, GL_JE_INCLUSION_RULES is best modeled as a standalone reference or configuration object rather than a transactional hub, link, or satellite. In Data Vault terms it behaves most like a reference table that couples two descriptive dimensions (journal source and journal category) to a journal rule set; a formal Data Vault model would typically represent the rule-set-to-source-and-category relationship as a link with descriptive satellites holding the flags and audit columns.

Key Information Stored

The table contains 26 documented columns. The most significant are:

  • JE_RULE_SET_ID — Identifier of the parent journal rule set with which the inclusion rule is associated.
  • JE_SOURCE_NAME — Name of the journal source (for example, Payables, Receivables, or Manual) governed by the rule.
  • JE_CATEGORY_NAME — Name of the journal category (for example, Purchase Invoices or Adjustments) governed by the rule.
  • INCLUDE_FLAG — Indicates whether the specified source and category combination is included when the rule set is processed.
  • USER_UPDATABLE_FLAG — Indicates whether the end user may override the inclusion decision at runtime.
  • CONTEXT — Descriptive flexfield context for the row.
  • ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments available for customer-defined extensions.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns recording who created and last modified each rule.

The surrogate primary key is GL_JE_INCLUSION_RULES_PK, defined on JE_SOURCE_NAME, JE_CATEGORY_NAME, and JE_RULE_SET_ID. A separate unique index, GL_JE_INCLUSION_RULES_U1, is defined on JE_RULE_SET_ID, JE_SOURCE_NAME, and JE_CATEGORY_NAME, representing the business-key candidate. The metadata records no foreign key relationships, consistent with the standalone classification.

Common Use Cases and Queries

Inclusion rules are consulted when General Ledger constructs or validates the set of journals subject to a given rule set, including journal import, consolidation, and revaluation processing. Reporting and validation queries typically join this table to the rule set definition to list the sources and categories enabled for a given rule set:

SELECT r.je_rule_set_id, r.je_source_name, r.je_category_name,
       r.include_flag, r.user_updatable_flag
FROM gl.gl_je_inclusion_rules r
WHERE r.je_rule_set_id = :p_rule_set_id
ORDER BY r.je_source_name, r.je_category_name;

Common scenarios include auditing which sources and categories are excluded from a rule set, verifying that a newly configured source is included before running journal import, and identifying user-updatable rules that can be changed at runtime. The descriptive flexfield columns (CONTEXT and ATTRIBUTE1–15) are useful when client-specific attributes have been defined on the rule.

Related Objects

Because the metadata records no foreign keys, relationships are inferred from the shared business keys:

  • GL_JE_RULE_SETS — The parent rule set table, joined on JE_RULE_SET_ID.
  • GL_JE_SOURCES — Journal source definitions, joined on JE_SOURCE_NAME.
  • GL_JE_CATEGORIES — Journal category definitions, joined on JE_CATEGORY_NAME.
  • GL_JE_HEADERS — Journal headers whose source and category values are tested against the rules.
  • GL_JE_BATCHES — Journal batches processed by rule sets that reference inclusion rules.
  • GL_JE_LINES — Journal lines within included journals.