Search Results je_gr_cutoff_rules_u1

Overview

GL.JE_GR_CUTOFF_RULES is a General Ledger configuration table in Oracle E-Business Suite (validated against ETRM 12.1.1 and 12.2.2 metadata). It stores the cutoff rules that govern how the Journal Entry General Ledger reconciliation process handles timing differences between goods receipt (GR) and invoice activity. Each row defines, for a given ledger and transaction category, the number of days allowed before a timing difference is considered a violation, together with the response the system should take when that threshold is breached.

The table resides in the APPS_TS_TX_DATA tablespace, is owned by the GL schema, and is catalogued under FND Design Data as JE.JE_GR_CUTOFF_RULES. It is a standalone object: the metadata records no foreign key references to or from other database objects, and referential integrity is therefore enforced at the application layer rather than through database constraints. Using a heuristic Data Vault classification, this object is best modeled as a satellite, since it carries descriptive attributes (days, violation response, enabled flag, and the attribute1–15 descriptive flexfield columns) keyed by the ledger, category, and application context. It could alternatively be represented as a reference hub for the category/business-key combination, but the satellite interpretation aligns more closely with its configuration-style, versioned attribute content.

Key Information Stored

The primary key is defined by JE_GR_CUTOFF_RULES_PK on RULE_ID, a system-generated surrogate identifier. Two unique indexes act as business-key candidates: JE_GR_CUTOFF_RULES_U1 on RULE_ID (which reinforces the primary key) and JE_GR_CUTOFF_RULES_U2 on the composite of SET_OF_BOOKS_ID, CATEGORY_CODE, and CAT_APPLICATION_ID. The U2 index is the meaningful business key and is the object referenced in the user's search; it guarantees that only one cutoff rule exists per ledger, per category, per owning application.

The most significant columns are:

• RULE_ID – surrogate primary key for the rule.
• SET_OF_BOOKS_ID – the ledger (set of books) to which the rule applies.
• CATEGORY_CODE and CAT_APPLICATION_ID – the transaction category and its owning application, completing the unique business key.
• DAYS – the cutoff window, expressed in days, used to evaluate timing differences.
• VIOLATION_RESPONSE – the action taken when a rule is breached.
• ENABLED_FLAG – indicates whether the rule is active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – descriptive flexfield segments for extensibility.

Common Use Cases and Queries

Typical scenarios include auditing which ledgers have cutoff rules enabled, reviewing the number of days permitted before a violation is flagged, and confirming the violation response configured for a category. A representative query pattern is:

• SELECT SET_OF_BOOKS_ID, RULE_ID, CATEGORY_CODE, CAT_APPLICATION_ID, DAYS, VIOLATION_RESPONSE, ENABLED_FLAG FROM GL.JE_GR_CUTOFF_RULES WHERE SET_OF_BOOKS_ID = :ledger_id;
• Filtering on ENABLED_FLAG = 'Y' to list only active rules for reconciliation reporting.
• Joining the rule's DAYS and VIOLATION_RESPONSE to GR/invoice timing-difference data to determine which transactions breach the configured cutoff.

Because the table is standalone and small by design, it is well suited to configuration reporting and to diagnostic queries during period-close investigations of GR/IR timing variances.

Related Objects

The documented metadata lists no database-level dependencies in either direction. According to the ETRM dependency data, GL.JE_GR_CUTOFF_RULES does not reference any database object, and it is referenced only by the APPS synonym JE_GR_CUTOFF_RULES, which exposes the GL table to the application schema. From a functional standpoint, the most significant related objects are those that share its key columns and consume its configuration values, principally:

• APPS.JE_GR_CUTOFF_RULES – the APPS synonym through which the table is queried.
• Ledger definitions keyed by SET_OF_BOOKS_ID (for example GL_SETS_OF_BOOKS), used to resolve the ledger context.
• Category and application reference data resolved through CATEGORY_CODE and CAT_APPLICATION_ID, which supply the descriptive identity behind the unique business key JE_GR_CUTOFF_RULES_U2.

These relationships are enforced through application logic and shared key values rather than declared foreign keys, so integrators should treat the composite U2 key as the authoritative link point when joining to ledger and category reference data.