Results for “ams_object_rules_vl”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AMS_OBJECT_RULES_VL is a Marketing (AMS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the definition of object rules — configuration records that describe how the Marketing application should evaluate, approve, or process a given marketing object (for example, a campaign, event, or deliverable). Each row represents one rule definition, including the mechanism by which the rule is executed (PL/SQL package procedure, Java class method, or a stored query), the object the rule applies to, and up to fifteen positional parameters passed to that mechanism.
Because the object name carries the _VL suffix, the view is a "translated" (language) view. It joins the base table to its translation table and filters the translation rows to the session's current language using USERENV('LANG'). This means consumers see the object rule name and description in their own language without needing to write the join themselves, which is the standard pattern for seeded, translatable AMS reference data. The view is read-only and is intended for inquiry, reporting, and integration rather than direct DML; maintenance of the underlying data is performed through the base tables or the Marketing setup UI.
Underlying Base Objects
The view is defined over two documented base objects:
- AMS_OBJECT_RULES_B — the base (non-translated) table holding the technical definition of each rule: identifiers, audit columns, execution metadata, the rule query, the related object, and the parameter columns.
- AMS_OBJECT_RULES_TL — the translation table holding the language-specific
OBJECT_RULE_NAMEandDESCRIPTION, keyed byOBJECT_RULE_IDandLANGUAGE.
The join predicate is B.OBJECT_RULE_ID = T.OBJECT_RULE_ID AND T.LANGUAGE = USERENV('LANG'). Both base objects are referenced through APPS synonyms. Consequently, a row appears in the view only when a translation row exists for the caller's language; the view is effectively an inner join between the base definition and its current-language text.
Key Columns
The view projects all base columns plus the two translated columns. The columns of greatest practical interest are:
- OBJECT_RULE_ID — primary key of the rule; the join key to both base tables.
- OBJECT_RULE_NAME and DESCRIPTION — the translated, user-facing identifiers of the rule.
- RULE_USED_BY and RULE_USED_BY_TYPE — the entity the rule is attached to, and its type, defining the scope in which the rule fires.
- RULE_TYPE — classifies the purpose of the rule (for example, approval or processing behavior).
- API_TYPE together with PACKAGE_NAME, PROCEDURE_NAME, CLASS_NAME, and METHOD_NAME — describe the executable entry point invoked when the rule is run.
- QUERY — the SQL text used by query-based rules.
- RELATED_OBJECT — identifies a secondary object linked to the rule; this is the column most associated with the user's search term "related_object" and is central to rules that operate across two objects.
- PARAM1 through PARAM15 — positional parameters passed to the configured API.
- SEEDED_FLAG — indicates Oracle-seeded versus customer-defined rules.
- APPROVAL_TYPE, SECURITY_GROUP_ID, APPLICATION_ID, and OBJECT_VERSION_NUMBER — control approval behavior, multi-org security, product ownership, and optimistic locking.
- ROW_ID and the standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — support row identification and change tracking.
Common Use Cases and Queries
Typical uses include auditing which rules exist for a given object, verifying the API or query bound to a rule, and extracting rule metadata for migration or documentation. The RELATED_OBJECT column is frequently queried when investigating cross-object rules.
List all rules for one related object in the current language:
SELECT object_rule_id, object_rule_name, rule_type, api_type, related_object FROM ams_object_rules_vl WHERE related_object = '&related_object';
Inspect the executable definition of non-seeded rules:
SELECT object_rule_id, object_rule_name, package_name, procedure_name, class_name, method_name, query FROM ams_object_rules_vl WHERE seeded_flag = 'N';
Join to child setup data by object rule:
SELECT v.object_rule_name, v.rule_used_by, v.rule_used_by_type FROM ams_object_rules_vl v, ams_object_rules_b b WHERE v.object_rule_id = b.object_rule_id AND v.rule_used_by = :object_name;
Note that because the view resolves language dynamically, reports run under different language sessions return different OBJECT_RULE_NAME and DESCRIPTION values for the same OBJECT_RULE_ID. Any code that persists these text columns should therefore be language-aware.
-
View: AMS_OBJECT_RULES_VL 12.2.2
This view returns object rules details.
APPS.AMS_OBJECT_RULES_VL·↳ AMS_OBJECT_RULES_B·↳ AMS_OBJECT_RULES_TL·Explore AMS module →
-
View: AMS_OBJECT_RULES_VL 12.1.1
This view returns object rules details.
APPS.AMS_OBJECT_RULES_VL·↳ AMS_OBJECT_RULES_B·↳ AMS_OBJECT_RULES_TL·Explore AMS module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - AMS Tables and Views 12.2.2
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AMS Tables and Views 12.1.1
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AMS Tables and Views 12.2.2
This table is used to store tracking data for web advertisement and offer type schedules
-
eTRM - AMS Tables and Views 12.1.1
This table is used to store tracking data for web advertisement and offer type schedules