Results for “jtf_r_rulesets_v”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.JTF_R_RULESETS_V is a reporting and integration artifact belonging to the JTF – CRM Foundation product family within Oracle E-Business Suite. It presents a consolidated, denormalized representation of ruleset definitions maintained by the CRM Foundation rules engine. The underlying ruleset data model follows the standard Oracle EBS multilanguage (MLS) pattern, in which a "base" table stores transactional and translatable-independent attributes while a separate "_VL" view supplies language-specific descriptive text. JTF_R_RULESETS_V joins these two sources so that a single query returns both the functional attributes of a ruleset and its display name and description in the session's language.
Because it is a view rather than a table, no data is stored in it; all values are derived at runtime from the underlying objects. This makes it suitable for read-only reporting, concurrent program queries, and integration extract logic, but it cannot be used for direct DML. The view is owned by the APPS schema, is documented as VALID, and is listed for Oracle EBS 12.1.1 and 12.2.2.
Underlying Base Objects
The view text is defined over two documented base objects:
- JTF_R_RULESETS_B (referenced as a synonym) — the base table holding non-translatable ruleset attributes, including surrogate key, audit columns, application and status flags, effective dates, class and serial identifiers, and the
OBJECT_TYPEandMAX_OBJECTScolumns. - JTF_R_RULESETS_VL (a view) — the translatable layer providing
NAME,DESCRIPTION, andSOURCE_LANGfor each ruleset, resolving the appropriate language row for the current session.
The join condition is JRSB.RULESET_ID = JRST.RULESET_ID, meaning every row in the composite view corresponds to exactly one ruleset identified by RULESET_ID. The join is an equi-join on the primary key, so cardinality is preserved from the base table and the view effectively augments each base row with translated text.
Key Columns
RULESET_ID— primary identifier of the ruleset; the key used to relate rulesets to rules and rule elements.APPLICATION_ID— the owning application (product) that registered the ruleset.STATUS,START_DATE,END_DATE— lifecycle and effective-dating controls that determine whether a ruleset is usable at a given point in time.RULESET_CLASSandRULESET_SER— classify the ruleset and carry its serial/sequence reference within the class.OBJECT_TYPE— the business object type to which the ruleset applies.MAX_OBJECTS— a functional limit controlling the maximum number of objects the ruleset evaluates or processes; this column is frequently targeted in rules-engine tuning and in queries that audit limit configuration.NAME,DESCRIPTION,SOURCE_LANG— translated text obtained fromJTF_R_RULESETS_VL.CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN— standard WHO audit columns inherited from the base table.
Common Use Cases and Queries
Typical usage includes: listing active rulesets for a given application; auditing rulesets that enforce an object limit via MAX_OBJECTS; and supplying values to integration or diagnostic reports that require both code and translated description.
- Active rulesets for an application:
SELECT ruleset_id, name, ruleset_class, status FROM jtf_r_rulesets_v WHERE application_id = :app_id AND status = 'Y' AND SYSDATE BETWEEN start_date AND end_date; - Reviewing configured object limits:
SELECT ruleset_id, name, object_type, max_objects FROM jtf_r_rulesets_v WHERE max_objects IS NOT NULL ORDER BY object_type, ruleset_id; - Audit of recent changes:
SELECT ruleset_id, name, last_updated_by, last_update_date FROM jtf_r_rulesets_v ORDER BY last_update_date DESC;
Because the view is read-only and language-sensitive, reports should be run with the correct session language to obtain the intended NAME and DESCRIPTION values.
-
View: JTF_R_RULESETS_V 12.1.1
view for ruleset
APPS.JTF_R_RULESETS_V·↳ JTF_R_RULESETS_B·↳ JTF_R_RULESETS_VL·Explore JTF module →
-
View: JTF_R_RULESETS_V 12.2.2
view for ruleset
APPS.JTF_R_RULESETS_V·↳ JTF_R_RULESETS_B·↳ JTF_R_RULESETS_VL·Explore JTF module →
-
VIEW: APPS.JTF_R_RULESETS_V 12.1.1
-
VIEW: APPS.JTF_R_RULESETS_V 12.2.2
-
VIEW: APPS.JTF_R_RULESETS_VL 12.2.2
-
VIEW: APPS.JTF_R_RULESETS_VL 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
12.2.2 DBA Data 12.2.2
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
12.1.1 DBA Data 12.1.1
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel