Search Results criteria_set_desc




Overview
Explore in AI Chat

Overview

GL_AUTOREV_CRITERIA_SETS is a General Ledger configuration table that stores named journal reversal criteria sets in Oracle E-Business Suite Release 12.1.1 and 12.2.2. A criteria set is a reusable definition that determines how journal entries are automatically reversed, governing attributes such as reversal method, reversal period, and reversal date logic. Because criteria sets are defined once and attached to ledgers, this table functions as a central reference object within the GL reversal framework, allowing organizations to standardize reversal behavior across multiple ledgers without redefining the rules repeatedly.

The object resides in the GL schema and is classified as VALID in the ETRM repository. Based on its foreign key structure — where GL_LEDGERS references GL_AUTOREV_CRITERIA_SETS but the table itself references no parent — the heuristic Data Vault classification is hub-leaning. In a Data Vault model this table would be modeled as a hub, with CRITERIA_SET_ID serving as the business key that anchors the set's descriptive attributes.

Key Information Stored

The documented physical schema contains 25 columns. The most significant are:

The presence of 15 attribute columns and a context column indicates the table is flexfield-enabled, allowing implementers to capture additional reversal parameters without schema changes. Note that the physical columns documented here do not include the reversal method or period values themselves; those semantics are typically derived through related reversal criteria lines or the ledger-level assignment.

Common Use Cases and Queries

The primary use case is administrative: identifying which criteria sets exist, which ledgers consume them, and whether they are secured. A typical lookup query is:

  • SELECT criteria_set_id, criteria_set_name, criteria_set_desc, security_flag FROM gl_autorev_criteria_sets ORDER BY criteria_set_name;
  • To find ledgers assigned to a given set, join to GL_LEDGERS: SELECT l.name, c.criteria_set_name FROM gl_ledgers l, gl_autorev_criteria_sets c WHERE l.criteria_set_id = c.criteria_set_id;
  • To locate unassigned sets, use an outer join or a NOT EXISTS subquery against GL_LEDGERS.CRITERIA_SET_ID.
  • Audit reporting leverages LAST_UPDATE_DATE and LAST_UPDATED_BY to track configuration changes over time.
  • Flexfield extraction queries select CONTEXT and ATTRIBUTE1–ATTRIBUTE15 for downstream reporting or migration.

Because the table is small and highly referenced, it is well suited to value-set or lookup-based validation in custom concurrent programs and forms.

Related Objects

The most significant dependent object is GL_LEDGERS, which references this table through GL_LEDGERS.CRITERIA_SET_ID. This relationship is the core integration point: every ledger may point to one criteria set, and the set therefore drives reversal behavior for all journals posted to that ledger. Related objects also include the AutoReverse criteria form and the General Ledger AutoReverse program, which read this configuration when generating reversal entries. Descriptive flexfield definitions attached to CONTEXT and ATTRIBUTE1–15, along with the definition access set security framework that interprets SECURITY_FLAG, are additional dependencies. Reporting views and concurrent programs that query reversal configuration should be reviewed to confirm they honor the security flag when exposing criteria set data.