Results for “operating_name”

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

Overview

AHL_APPROVAL_RULES_V is an APPS-owned reporting view within the Oracle E-Business Suite (EBS) Complex Maintenance Repair and Overhaul (AHL) module. It exposes the definition of approval rules that govern the routing and authorization of maintenance and repair transactions and documents. Rather than storing raw coded values, the view resolves the descriptive meaning of each rule's attributes by joining the underlying approval-rules base object to several FND_LOOKUP_VALUES_VL lookups. The result is a denormalized, human-readable representation of approval rule configuration that is suitable for reporting, operational diagnostics, and integrations that must interpret approval logic without decoding internal codes.

In Oracle EBS 12.1.1 and 12.2.2, the view is registered in the ETRM metadata with a status of VALID. It is most useful to administrators, business analysts, and developers who need a consolidated listing of the approval rules in effect for a given operating unit, including their object type, application usage, priority, approval type, and current lifecycle status. Because the view performs all lookup resolution internally, consumers avoid the complexity of joining four separate lookup types themselves.

Underlying Base Objects

The view is defined over the following documented objects:

• AHL_APPROVAL_RULES_VL (VIEW) — the primary source of approval rule data, supplying the rule identifiers, codes, dates, and descriptive text.
• FND_LOOKUP_VALUES_VL (VIEW) — referenced repeatedly via outer joins to translate each stored code into its lookup meaning.

All joins to the lookup view are outer joins (designated by the (+) operator). Each lookup uses a specific lookup type: AHL_APPR_OBJECT_TYPE, AHL_APPLICATION_USAGE_CODE, AHL_APPR_PRIORITY_TYPE, AHL_APPROVAL_TYPE, and AHL_APPR_STATUS_TYPE. The outer join construction ensures that a rule row is still returned even when a corresponding lookup value is missing or inactive, in which case the resolved meaning column is null. The view therefore behaves as a single virtual source that flattens one base rule view and four independent lookup relationships into one row set.

Key Columns

• ROW_ID — the unique row identifier for the approval rule record.
• APPROVAL_RULE_ID — the primary business key for the approval rule.
• OBJECT_VERSION_NUMBER — the optimistic locking version counter used for concurrent update control.
• APPROVAL_OBJECT_CODE / APPROVAL_OBJECT_NAME — the coded object type governed by the rule and its decoded meaning from lookup type AHL_APPR_OBJECT_TYPE.
• APPLICATION_USG_CODE / APPLICATION_USG — the application usage context and its decoded meaning from AHL_APPLICATION_USAGE_CODE.
• APPROVAL_PRIORITY_CODE / APPROVAL_PRIORITY_NAME — priority classification and its meaning from AHL_APPR_PRIORITY_TYPE.
• APPROVAL_TYPE_CODE / APPROVAL_TYPE_NAME — approval mechanism type and its meaning from AHL_APPROVAL_TYPE.
• OPERATING_UNIT_ID / OPERATING_NAME — the owning operating unit and its display name.
• STATUS_CODE / STATUS_NAME — the rule's status code and its decoded meaning from lookup type AHL_APPR_STATUS_TYPE. This is the column most commonly targeted by users searching on status_name.
• ACTIVE_START_DATE / ACTIVE_END_DATE — the effective date range during which the rule is active.
• APPROVAL_RULE_NAME / DESCRIPTION — the descriptive name and free-text description of the rule.

Common Use Cases and Queries

A frequent requirement is to list all active approval rules with their readable status, priority, and approval type. The following query restricts results to rules currently within their effective date range:

• SELECT approval_rule_name, status_name, approval_type_name, approval_priority_name, operating_name FROM ahl_approval_rules_v WHERE status_name = 'Active' AND SYSDATE BETWEEN active_start_date AND active_end_date ORDER BY operating_name, approval_rule_name;

To validate lookup configuration integrity, developers can identify rules whose decoded meanings did not resolve, indicating a missing lookup value:

• SELECT approval_rule_id, approval_object_code, status_code FROM ahl_approval_rules_v WHERE status_name IS NULL;

Because the view filters efficiently by operating unit and status, it is also well suited to seed data extracts for integration interfaces and to support audit reviews of approval rule coverage across operating units in both 12.1.1 and 12.2.2 environments.