Search Results cr_object_version_number

Overview

APPS.AMS_IBA_RULESETS_V is a reporting and integration view in Oracle E-Business Suite that exposes ruleset definitions used by the Interaction Base Application (IBA) engine. In EBS 12.1.1 and 12.2.2, IBA rulesets drive the ordering logic through which marketing and interaction content is presented to users, for example the sequencing of offers, messages, or products shown during a customer interaction. The view consolidates the base definition table with its translation table so that callers receive a single row per ruleset with language-appropriate name and description text.

The view is owned by APPS and is intended for read-only consumption. It is commonly referenced by concurrent programs, Oracle Answers / BI Publisher reports, and custom extensions that need to enumerate available rulesets, confirm their status, or inspect the configured sort behavior without joining the underlying tables directly. Because it exposes the object version number, it is also suitable for integration patterns that perform change detection or optimistic locking checks against ruleset configuration.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through public synonyms:

• JTF_R_RULESETS_B — the base (non-translated) ruleset table holding identity, version, sort, status, and effective-dating attributes.
• JTF_R_RULESETS_TL — the translation table holding language-specific name and description values keyed by ruleset and language.

The two tables are joined on RULESET_ID. The translation table is joined with the outer-join operator (+) on RSTL.LANGUAGE = USERENV('LANG'), so a row is returned even when no translation exists for the session language. The view applies an ORDER BY RULESET_ID and adds a synthetic ROWNUM column aliased as ROW_NUM, providing a stable sequence for display grids.

Key Columns

• ROW_NUM — synthetic sequence generated by ROWNUM over the ordered result set.
• RULESET_ID — primary identifier for the ruleset; join key to the base and translation tables.
• CR_OBJECT_VERSION_NUMBER — the object version number from JTF_R_RULESETS_B, exposed under an application-style column name. This is the column most often located by users searching for cr_object_version_number.
• NAME / DESCRIPTION — language-specific label and text sourced from JTF_R_RULESETS_TL.
• SORT_ORDER — decoded presentation of the IBA sort order: 0 maps to DESCENDING, 1 to ASCENDING, and 2 to RANDOM.
• SORT_CODE — the raw IBA_SORT_BY_CODE value indicating the attribute used for ordering.
• STATUS — ruleset lifecycle state.
• CREATION_DATE — creation timestamp of the ruleset record.
• START_DATE / END_DATE — effective-dating range controlling when the ruleset is active.

Common Use Cases and Queries

A frequent requirement is to confirm that an expected column name exists in the view. The following query is used to verify the CR_OBJECT_VERSION_NUMBER column and inspect rule set configuration:

• SELECT ruleset_id, cr_object_version_number, name, sort_order, status FROM apps.ams_iba_rulesets_v;
• SELECT ruleset_id, name, start_date, end_date FROM apps.ams_iba_rulesets_v WHERE status = 'A' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1); — returns currently active rulesets for reporting or integration selection.
• SELECT column_name, data_type FROM all_tab_columns WHERE table_name = 'AMS_IBA_RULESETS_V' AND owner = 'APPS'; — metadata discovery to confirm the view exposes CR_OBJECT_VERSION_NUMBER.

Typical uses include populating LOVs for ruleset selection, driving BI Publisher layouts that document IBA configuration, and integration extracts that synchronize ruleset definitions with downstream systems while tracking the object version number for change detection.