Results for “approval_approver_id”

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

Overview

AHL_APPROVERS_V is a seeded Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema and shipped with the AHL – Complex Maintenance Repair and Overhaul product. Its documented status is VALID, and its purpose, per ETRM metadata, is to store the query that relates to approver information for the AHL approval framework. In functional terms, the view provides a unified, presentation-layer result set describing the approvers configured against AHL approval rules, resolving each approver identifier to a human-readable name.

The view is particularly significant for reporting and integration because it is the object typically searched by the column APPROVER_NAME. Downstream consumers — custom reports, BI Publisher data templates, OAF pages, and interfaces — reference this view rather than joining the underlying AHL and JTF tables directly, since the view encapsulates the union logic required to represent both user-type and role-type approvers in a single rowset.

Because the view is a query definition rather than a stored table, it holds no data of its own. All rows are materialized at runtime from the AHL_APPROVERS base and the supporting lookup, employee, and role-relations views.

Underlying Base Objects

ETRM metadata documents the following referenced base objects for AHL_APPROVERS_V:

• AHL_APPROVERS (SYNONYM) — the driving object holding approver assignments, approval rule references, approver type codes, approver IDs, sequences, and object version numbers.
• FND_LOOKUP_VALUES_VL (VIEW) — supplies lookup meanings for the AHL_APPROVER_TYPE lookup type; the view restricts to lookup codes USER and ROLE.
• AHL_JTF_RS_EMP_V (VIEW) — the AHL employee resource view used to resolve user-type approver IDs to user names via RESOURCE_ID.
• JTF_RS_ROLE_RELATIONS_VL (VIEW) — the resource role relations view used to resolve role-type approver IDs to role names via ROLE_ID.
• FND_GLOBAL (PACKAGE) — the standard EBS session context package, referenced for runtime environment/security context.

The view text is constructed as a three-branch UNION: a branch for approvers whose type code is USER, a branch for approvers whose type code is ROLE, and a final branch handling rows where APPROVER_TYPE_CODE = 'ROLE' but APPROVER_ID IS NULL, in which case APPROVER_NAME is returned as an empty string. All branches project DISTINCT rows and share an identical column list.

Key Columns

The view exposes the following documented columns:

• ROW_ID — the ROWID of the underlying AHL_APPROVERS row, useful as a surrogate key in reporting.
• APPROVAL_APPROVER_ID — the unique identifier of the approver assignment record.
• APPROVAL_RULE_ID — the approval rule to which the approver is attached; the join key to the rule definition.
• OBJECT_VERSION_NUMBER — the optimistic locking / concurrency version attribute.
• APPROVER_TYPE_CODE — the raw type discriminator (USER or ROLE).
• APPROVER_TYPE_NAME — the decoded lookup meaning for the type code, sourced from FND_LOOKUP_VALUES_VL.
• APPROVER_ID — the underlying identifier, interpreted as a resource ID for user approvers or a role ID for role approvers.
• APPROVER_NAME — the resolved display name; a user name for user approvers, a role name for role approvers, or an empty string when the role approver ID is null.
• APPROVER_SEQUENCE — the ordering of the approver within its rule's approval chain.

Common Use Cases and Queries

Typical usage centers on listing the approvers belonging to an approval rule, displaying approver names in maintenance work order approval screens, and feeding approver data into notifications and audit reports. The common filter column is APPROVAL_RULE_ID, and results are normally ordered by APPROVER_SEQUENCE.

All approvers for a rule, in sequence:

• SELECT approval_approver_id, approver_type_name, approver_name, approver_sequence FROM ahl_approvers_v WHERE approval_rule_id = :rule_id ORDER BY approver_sequence;

Locating a specific approver by name:

• SELECT approval_rule_id, approver_type_code, approver_id, approver_sequence FROM ahl_approvers_v WHERE approver_name = :approver_name;

Distinguishing user and role approvers:

• SELECT approver_type_name, COUNT(*) FROM ahl_approvers_v GROUP BY approver_type_name;

Because the object is a view, no DML should be issued against it; changes to approver assignments must be performed through the AHL_APPROVERS base object and validated by the AHL application logic so that concurrent access is controlled through OBJECT_VERSION_NUMBER.