Search Results je_gr_cutoff_rules




Overview
Explore in AI Chat

Overview

The JE_GR_CUTOFF_RULES table is a Greek localizations object owned by the GL schema and shipped with the JE – European Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores accounting cutoff rules that govern how the Greek statutory ledger enforces period-closing boundaries for specific journal source and category combinations. When a transaction is posted outside an allowed cutoff window, the rule attached to that category determines whether the system raises a warning, blocks the entry, or records an exception. This makes the table a configuration and control object rather than a transactional fact table: it is populated during implementation of the Greek localization and read at runtime by the posting and period-close validation logic.

Mined from the documented foreign-key structure, the Data Vault classification for this object is standalone. In Data Vault modeling terms it behaves most like a satellite that is keyed by its own surrogate rule identifier, with no parent hub or link documented in the ETRM relationship data. Consumers modeling Greek cutoff behavior in a warehouse may therefore treat it as a reference/dimension table rather than as a transactional hub.

Key Information Stored

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

The business-key candidates are documented by two unique indexes. JE_GR_CUTOFF_RULES_U1 enforces uniqueness of RULE_ID alone, while JE_GR_CUTOFF_RULES_U2 enforces uniqueness across SET_OF_BOOKS_ID, CATEGORY_CODE, and CAT_APPLICATION_ID. The second index is the meaningful natural key: it guarantees that only one cutoff rule can exist per ledger, journal category, and owning application.

Common Use Cases and Queries

Typical reporting scenarios include auditing active rules, checking which categories carry the strictest windows, and reconciling rule configuration between environments. A representative query lists all enabled rules for a ledger:

  • SELECT rule_id, category_code, cat_application_id, days, violation_response FROM gl.je_gr_cutoff_rules WHERE set_of_books_id = :ledger_id AND enabled_flag = 'Y' ORDER BY category_code;

To review the effective window for a specific category, filtering on the natural key is efficient because JE_GR_CUTOFF_RULES_U2 supports the predicate:

  • SELECT days, violation_response FROM gl.je_gr_cutoff_rules WHERE set_of_books_id = :ledger_id AND category_code = :category AND cat_application_id = :app_id;

For change tracking, the WHO columns support an audit of recently modified configuration:

  • SELECT rule_id, category_code, last_updated_by, last_update_date FROM gl.je_gr_cutoff_rules WHERE last_update_date > SYSDATE - 30;

Related Objects

The documented relationship model classifies this object as standalone, so no explicit foreign keys to parent tables are listed in the ETRM data. In practice it interacts with the following core EBS objects:

  • GL_SETS_OF_BOOKS – joined on SET_OF_BOOKS_ID to resolve the ledger name and chart of accounts.
  • GL_JE_CATEGORIES – joined on CATEGORY_CODE and APPLICATION_ID to resolve category descriptions.
  • FND_APPLICATION – joined on CAT_APPLICATION_ID to obtain the owning application short name.
  • GL_JE_HEADERS and GL_JE_LINES – the journals whose postings are validated against the cutoff window.
  • FND_FLEX_VALUES – used when the ATTRIBUTE DFF columns are configured with value sets.
  • FND_USER – joined on LAST_UPDATED_BY and CREATED_BY for audit reporting.

Because the table is configuration-oriented, DML is normally performed through the Greek localization setup forms rather than by direct SQL.