Results for “ruleset_class”

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

Overview

JTF_R_RULESETS_B is the base (non-translated) table within the JTF schema of Oracle E-Business Suite that stores rulesets for the CRM Foundation layer. A ruleset is a logical grouping of individual rules into an application unit, allowing the ETRM (or any rules-driven) engine to evaluate, order, and apply collections of rules as a single operational entity rather than as isolated records. The table is defined with a VALID status in both Oracle EBS 12.1.1 and 12.2.2 environments and is owned by the JTF (CRM Foundation) product.

From a data-modeling perspective, the documented foreign-key topology classifies JTF_R_RULESETS_B as hub-leaning. It holds the durable identifier (RULESET_ID) around which translation and rule-member records are grouped, with the translated table JTF_R_RULESETS_TL and the detail table JTF_R_RULES_B both pointing back to it. This suggests the table functions as the central anchor (hub) for ruleset-related descriptive attributes, while the surrounding tables carry language-dependent text and individual rule memberships.

Key Information Stored

The table contains 18 documented columns. The most operationally significant are:

• RULESET_ID — surrogate primary key, defined by constraint JTF_R_RULESETS_B_PK and reinforced by unique index JTF_R_RULESETS_U1.
• APPLICATION_ID — identifies the Oracle application that owns the ruleset, driving the availability of the ruleset across product boundaries.
• RULESET_CLASS — categorizes the ruleset so the engine can select the appropriate evaluation class.
• RULESET_SER — a serial or sequencing attribute distinguishing rulesets with similar configuration.
• OBJECT_TYPE and MAX_OBJECTS — define the object the ruleset operates against and the numeric ceiling for objects the ruleset may process.
• IBA_SORT_ORDER and IBA_SORT_BY_CODE — control how rules within the ruleset are ordered during evaluation (IBA = Intelligent Business Agent context).
• STATUS — lifecycle state of the ruleset (for example active or inactive), which gates execution.
• START_DATE and END_DATE — define the effective window during which the ruleset is valid.
• SECURITY_GROUP_ID — foreign key into FND_SECURITY_GROUPS, enforcing row-level security and multi-organization partitioning.
• OBJECT_VERSION_NUMBER — optimistic-locking counter used by the OA Framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO-audit columns.

Business-key candidates are limited; the unique index JTF_R_RULESETS_U1 covers RULESET_ID, so the table effectively relies on the surrogate key as its distinct identifier.

Common Use Cases and Queries

Rulesets are queried most often to enumerate active rule groupings for a given application, to inspect scheduling and sorting behaviour, and to join rules to their parent grouping for reporting.

A typical active-ruleset listing:

• SELECT r.RULESET_ID, r.APPLICATION_ID, r.RULESET_CLASS, r.STATUS, r.START_DATE, r.END_DATE FROM JTF.JTF_R_RULESETS_B r WHERE r.STATUS = 'Y' AND SYSDATE BETWEEN r.START_DATE AND NVL(r.END_DATE, SYSDATE + 1);

To retrieve the translated name or description, join to JTF_R_RULESETS_TL on RULESET_ID and filter by LANGUAGE. To inventory the rules contained inside a ruleset, join to JTF_R_RULES_B on RULESET_ID. Security-group-scoped reporting adds a join to FND_SECURITY_GROUPS via SECURITY_GROUP_ID. Common reporting outputs include ruleset inventory by application, expiry analysis of rulesets approaching END_DATE, and ruleset-to-rule population counts.

Related Objects

• JTF_R_RULESETS_TL — translated child table; joined on JTF_R_RULESETS_TL.RULESET_ID = JTF_R_RULESETS_B.RULESET_ID.
• JTF_R_RULES_B — the individual rules belonging to each ruleset; joined on JTF_R_RULES_B.RULESET_ID = JTF_R_RULESETS_B.RULESET_ID.
• FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; used for row-level security scoping.
• FND_APPLICATION (referenced via APPLICATION_ID) — resolves the owning product for the ruleset.
• JTF_R_RULESETS_B_PK / JTF_R_RULESETS_U1 — primary key and unique index constraints that enforce identity and integrity.