Results for “ahl_approver_type”

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

Overview

APPS.AHL_APPROVERS_V is a reporting and integration view in the Oracle E-Business Suite Advanced Product Catalog (AHL) module. It exposes the approval approver assignments defined in the AHL_APPROVERS base table, resolving the technical approver type code into a user-facing meaning and resolving the approver identifier into a display name. The view is a UNION of two branches: one branch handles approvers whose APPROVER_TYPE_CODE is 'USER', and the other branch handles approvers whose APPROVER_TYPE_CODE is 'ROLE'. Because it joins to FND lookup views and JTF resource views, the view presents denormalized, display-ready data suitable for concurrent programs, Oracle Reports, OAF pages, and outbound integration extracts without requiring the caller to reproduce the lookup and resource resolution logic. The view is owned by the APPS schema and is typically granted to application users via the standard AHL grant set.

Underlying Base Objects

The view is defined over the following documented objects:

• AHL_APPROVERS (referenced through a synonym) — the primary transactional table holding approval approver rows. It supplies ROWID (aliased ROW_ID), APPROVAL_APPROVER_ID, APPROVAL_RULE_ID, OBJECT_VERSION_NUMBER, APPROVER_TYPE_CODE, APPROVER_ID, and APPROVER_SEQUENCE.
• FND_LOOKUP_VALUES_VL — the multilingual lookup view, filtered on LOOKUP_TYPE = 'AHL_APPROVER_TYPE' and joined on LOOKUP_CODE = APPROVER_TYPE_CODE, supplying the translated MEANING as APPROVER_TYPE_NAME. This is the object directly associated with the user's search term ahl_approver_type.
• AHL_JTF_RS_EMP_V — a resource/employee view used in the USER branch to resolve APPROVER_ID to USER_NAME as APPROVER_NAME.
• JTF_RS_ROLE_RELATIONS_VL — the role view used in the ROLE branch to resolve APPROVER_ID to ROLE_NAME; the branch also permits APPROVER_ID IS NULL, allowing role rows with no specific resource binding.
• FND_GLOBAL — the standard EBS package referenced by the view definition, typically for session context such as USER_ID or responsibility-dependent filtering.

Key Columns

• ROW_ID — the ROWID of the underlying AHL_APPROVERS row; useful for direct DML targeting.
• APPROVAL_APPROVER_ID — primary identifier of the approver assignment row.
• APPROVAL_RULE_ID — the parent approval rule to which the approver belongs.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the AHL framework.
• APPROVER_TYPE_CODE — the stored type code (USER or ROLE), the value domain linked to the AHL_APPROVER_TYPE lookup.
• APPROVER_TYPE_NAME — the translated lookup meaning for the type code.
• APPROVER_ID — the resource identifier (user or role), resolved in conjunction with the type code.
• APPROVER_NAME — the display name; user name or role name depending on the branch.
• APPROVER_SEQUENCE — ordering of the approver within the rule.

Common Use Cases and Queries

A typical query lists approvers for a given approval rule with resolved names:

• SELECT approval_rule_id, approver_sequence, approver_type_name, approver_name FROM apps.ahl_approvers_v WHERE approval_rule_id = :p_rule_id ORDER BY approver_sequence;
• Reporting on approver type distribution: SELECT approver_type_name, COUNT(*) FROM apps.ahl_approvers_v GROUP BY approver_type_name;
• Integration extracts requiring stable identifiers: select ROW_ID and OBJECT_VERSION_NUMBER alongside display columns when feeding external approval engines.
• Lookup validation and troubleshooting of the ahl_approver_type domain by comparing APPROVER_TYPE_CODE to APPROVER_TYPE_NAME.

Because the view uses a UNION of two filtered branches, queries returning all rows should not assume a single source table; DISTINCT is applied within each branch to suppress duplicates arising from the role relation join.