Results for “ahl_approval_rules_vl”

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

Overview

The AHL_APPROVAL_RULES_VL view is a public, language-sensitive (VL) database view owned by the APPS schema within the Oracle E-Business Suite. It belongs to the AHL product family, Complex Maintenance Repair and Overhaul, a module used extensively in aerospace, defense, and heavy-asset maintenance environments. The view exposes approval rule configuration data that governs how maintenance, repair, and overhaul transactions and related business objects are routed for approval inside the AHL approval engine.

As a VL view, AHL_APPROVAL_RULES_VL joins a base table to its translated (_TL) counterpart and restricts the returned translation row to the session language via USERENV('LANG'). This design makes the view suitable for reporting, concurrent programs, Forms-based LOVs, and integration interfaces that must return approval rule definitions in the language of the logged-in user. Because the view is defined in APPS and marked VALID, it can be referenced directly by custom reports and extensions without requiring additional grants beyond the standard APPS synonym access.

Underlying Base Objects

• AHL_APPROVAL_RULES_B — the base (non-translated) table that stores the operational attributes of each approval rule, including key, status, priority, operating unit, effective dates, and the descriptive flexfield attribute columns.
• AHL_APPROVAL_RULES_TL — the translation table supplying APPROVAL_RULE_NAME, DESCRIPTION, and LANGUAGE.
• HR_ALL_ORGANIZATION_UNITS_TL (referenced in the documented join through HOU) — used to resolve the operating unit name into the OPERATING_NAME column.

The join predicate is AARB.APPROVAL_RULE_ID = AART.APPROVAL_RULE_ID, with AART.LANGUAGE = USERENV('LANG'). The outer condition on OPERATING_UNIT_ID allows the view to return global (null operating unit) rules alongside organization-specific rules, since it evaluates AARB.OPERATING_UNIT_ID IS NULL OR AARB.OPERATING_UNIT_ID = HOU.ORGANIZATION_ID. The ROW_ID value surfaced by the view is derived from AARB.ROWID.

Key Columns

• APPROVAL_RULE_ID — primary identifier of the approval rule; the join key across the _B, _TL, and related setup tables.
• APPROVAL_RULE_NAME / DESCRIPTION — the translated name and description, returned in the session language.
• APPROVAL_OBJECT_CODE — identifies the business object type the rule applies to.
• APPROVAL_TYPE_CODE / APPROVAL_PRIORITY_CODE — classify the approval mechanism and the precedence of the rule.
• APPLICATION_USG_CODE — indicates the application or usage context in which the rule is active.
• OPERATING_UNIT_ID / OPERATING_NAME — the operating unit the rule is scoped to; OPERATING_NAME is blank when the rule is not organization-specific.
• STATUS_CODE / SEEDED_FLAG — indicate whether the rule is enabled and whether it is Oracle-seeded (protected) rather than user-defined.
• ACTIVE_START_DATE / ACTIVE_END_DATE — the effective date range for which the rule is valid.
• OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent update control.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield (DFF) segments for customer-specific rule attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID — standard audit columns.

Common Use Cases and Queries

The view is typically consumed to enumerate approval rules configured for a given operating unit, to build selection lists in custom forms, or to validate which rules are active for a specific object type on a given date. A typical query returns all currently active rules for the user's language:

• List active rules by object type — SELECT approval_rule_id, approval_rule_name, approval_type_code, operating_name FROM ahl_approval_rules_vl WHERE approval_object_code = :p_object AND status_code = 'ACTIVE' AND SYSDATE BETWEEN active_start_date AND NVL(active_end_date, SYSDATE + 1);
• Operating-unit scoped rules — filter on operating_unit_id or operating_name to isolate rules that apply to a specific organization.
• Seeded versus user-defined rules — query on seeded_flag to distinguish Oracle-supplied rules from custom configurations when troubleshooting upgrade impacts.
• Language-aware reporting — because translation is resolved automatically, the view is preferred over direct _B/_TL joins in multilingual deployments.

Because the view applies the language and operating unit predicates internally, it should be favored for read-only reporting, integration extracts, and validation logic, while DML against approval rules must target the underlying AHL_APPROVAL_RULES_B and AHL_APPROVAL_RULES_TL tables.