Search Results exec_priority

Overview

AMS_IBA_PS_RULEGRPS_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is delivered by the Oracle Marketing (AMS) product family, specifically within the Oracle Marketing rule engine functionality. Per the documented ETRM metadata, the view exists to "display Rules rule overview screen" — that is, it is the data access layer behind the Rules workbench/list page in the Marketing responsibility, where users review and manage rule groups that drive campaign automation, message execution and targeted marketing behavior.

The _VL suffix indicates a "value list" or translation-aware view. The view joins the translatable columns (name, description) from a _TL table with the operational columns from the base ("_B") table, restricted to the session's language. This pattern allows Oracle Marketing to support multi-language deployments of the rule group name and description without exposing language joins to reporting tools or the application UI. For the technical user searching on exec_priority, the view is the single most convenient place to read the execution ordering applied to rule groups because it surfaces column EXEC_PRIORITY directly.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS through synonyms:

• AMS_IBA_PS_RULEGRPS_B — the base table holding language-independent attributes of each rule group, including identifiers, strategy type, execution priority, posting information and standard who-columns.
• AMS_IBA_PS_RULEGRPS_TL — the translation table holding the language-dependent RULEGROUP_NAME and RULEGROUP_DESCRIPTION.

The join is performed on RULEGROUP_ID and is filtered by T.LANGUAGE = USERENV('LANG'), meaning the view returns only the row whose translation language matches the current application session language. The view text selects aliased columns from both tables; it does not aggregate, so one row in the view corresponds to one rule group in the current language. Because the _B table is the driving table, all rule groups will appear even if a translation row is absent (depending on translation completeness), which is standard behavior for _VL constructs.

Key Columns

• ROW_ID — the base table ROWID, exposed for tooling such as Oracle Forms.
• RULEGROUP_ID — primary identifier of the rule group; the join key to AMS_IBA_PS_RULEGRPS_TL.
• POSTING_ID — identifier linking the rule group to its posting/definition context.
• STRATEGY_TYPE — classifies the rule group strategy being applied.
• EXEC_PRIORITY — the execution priority value. This is the column referenced by the exec_priority search term; it controls the sequence in which competing rule groups are evaluated by the Oracle Marketing rule engine. Lower (or numerically ordered) values determine precedence when multiple rule groups match the same condition.
• LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY — standard EBS audit/who columns.
• SECURITY_GROUP_ID — supports multi-organization / security-group filtering within the EBS security model.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/Forms layer.
• RULEGROUP_NAME, RULEGROUP_DESCRIPTION — language-specific text from _TL.

Common Use Cases and Queries

Typical usage is diagnostics or reporting on rule group configuration, particularly around execution ordering. Examples:

List rule groups and their execution priorities:

SELECT rulegroup_id, rulegroup_name, strategy_type, exec_priority
FROM   apps.ams_iba_ps_rulegrps_vl
ORDER  BY exec_priority, rulegroup_id;

Find a specific rule group and its priority:

SELECT rulegroup_name, exec_priority, last_update_date, last_updated_by
FROM   apps.ams_iba_ps_rulegrps_vl
WHERE  rulegroup_id = :p_rulegroup_id;

Identify duplicate or conflicting priorities before tuning the rule engine:

SELECT exec_priority, COUNT(*)
FROM   apps.ams_iba_ps_rulegrps_vl
GROUP  BY exec_priority
HAVING COUNT(*) > 1;

Because the view enforces the session-language join, consistent results require the query session's USERENV('LANG') to match the intended translation language; in multi-language environments, use of the view is preferable to ad hoc joins against the _B and _TL tables. Reporting and integration developers should treat the view as read-only and rely on the Oracle Marketing application APIs for any updates to rule group priority.