Results for “ahl_approval_type”

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

Overview

APPS.AHL_APPROVAL_RULES_V is a reporting view in the Oracle E-Business Suite (12.1.1 and 12.2.2) that presents the approval rules used by Oracle Complex Maintenance, Repair, and Overhaul (CMRO), the product family built on the AHL schema. Approval rules define the routing logic by which records — work orders, execution transactions, and similar CMRO entities — are submitted for review and approved. The view exposes the defining attributes of each rule and, critically, resolves the underlying coded lookup values into their user-facing meanings through outer joins to FND_LOOKUP_VALUES_VL. This makes the view self-describing: a query returns the priority of a rule as a readable name rather than a raw code.

The view is not a base transaction object. It is a denormalized read layer intended for reports, concurrent programs, and integration extracts. Because all lookup joins are outer joins (indicated by the (+) operator), a rule is still returned even when a corresponding lookup row is missing or end-dated, so the view does not silently drop configuration records.

Underlying Base Objects

The view is defined over two documented objects:

• AHL_APPROVAL_RULES_VL — the multi-language (VL) view over the AHL approval rules entity. It supplies all of the rule's own columns, including ROW_ID, APPROVAL_RULE_ID, OBJECT_VERSION_NUMBER, APPROVAL_RULE_NAME, DESCRIPTION, OPERATING_UNIT_ID, and OPERATING_NAME. The VL layer means translated name and description columns are resolved for the current session language.
• FND_LOOKUP_VALUES_VL — the Application Object Library lookup values view, referenced five times in the join under the aliases APROBJ, APPUSG, PRIOTYP, APRTYP, and STATYP. Each instance is filtered on a distinct LOOKUP_TYPE and joined on LOOKUP_CODE to the corresponding code column in the approval rules view.

The five lookup types consumed are AHL_APPR_OBJECT_TYPE, AHL_APPLICATION_USAGE_CODE, AHL_APPR_PRIORITY_TYPE, AHL_APPROVAL_TYPE, and AHL_APPR_STATUS_TYPE. These correspond one-to-one with the code columns exposed by the view.

Key Columns

• ROW_ID / APPROVAL_RULE_ID / OBJECT_VERSION_NUMBER — the primary key and optimistic locking columns for the rule record.
• APPROVAL_OBJECT_CODE / APPROVAL_OBJECT_NAME — the CMRO object the rule applies to (coded value and its lookup meaning, from AHL_APPR_OBJECT_TYPE).
• APPLICATION_USG_CODE / APPLICATION_USG — the application usage context in which the rule applies.
• APPROVAL_PRIORITY_CODE / APPROVAL_PRIORITY_NAME — the priority assigned to the rule, resolved via lookup type AHL_APPR_PRIORITY_TYPE. This is the column pair most commonly searched, since approval_priority_name is the user-facing label for the rule's priority.
• APPROVAL_TYPE_CODE / APPROVAL_TYPE_NAME — the type of approval, resolved via AHL_APPROVAL_TYPE.
• STATUS_CODE / STATUS_NAME — the lifecycle status of the rule, resolved via AHL_APPR_STATUS_TYPE.
• OPERATING_UNIT_ID / OPERATING_NAME — the operating unit scope for the rule.
• ACTIVE_START_DATE / ACTIVE_END_DATE — the effective dating window governing when the rule is valid.
• APPROVAL_RULE_NAME / DESCRIPTION — the translated name and description from the VL layer.

Common Use Cases and Queries

Typical scenarios include auditing which approval rules are active for a given operating unit, verifying that a rule's priority matches configuration intent, and feeding approval rule metadata into external workflow or reporting tools. Because the lookup meanings are already resolved, the view is convenient for direct reporting without additional joins.

Locating rules by priority name (the searched term):

SELECT approval_rule_id,
       approval_rule_name,
       approval_priority_name,
       approval_object_name,
       status_name,
       operating_name
FROM   apps.ahl_approval_rules_v
WHERE  approval_priority_name = :p_priority_name;

Listing currently effective rules for an operating unit:

SELECT approval_rule_name,
       approval_type_name,
       approval_priority_name,
       active_start_date,
       active_end_date
FROM   apps.ahl_approval_rules_v
WHERE  operating_unit_id = :p_org_id
AND    TRUNC(SYSDATE) BETWEEN active_start_date AND NVL(active_end_date, SYSDATE)
ORDER  BY approval_priority_name;

Because the join to FND_LOOKUP_VALUES_VL is outer, the view should not be used as a validation source for lookup configuration; reports that must guarantee a resolved meaning should join the lookup views explicitly and filter on LOOKUP_TYPE and the appropriate language and date criteria.