Search Results aso_approver_status

Overview

ASO_APPROVER_DETAILS_V is a public APPS-owned view within the Oracle E-Business Suite Order Management and Approvals Management schema (ASO). It exposes the approval history associated with sales document approval instances processed through Oracle Workflow. The view is registered in FND Design Data as ASO.ASO_APPROVER_DETAILS_V and is documented as valid in both release 12.1.1 and 12.2.2. Because its type is a public view, Oracle supports its use for custom reporting and integration requirements, though it remains a read-only projection over the underlying approval tables rather than a transactional interface.

At a functional level, the view answers the recurring operational question of who approved a given order, quote, or other ASO-managed document, in what sequence, with what response, and at what point in time. It is the consolidated read model for approval-instance data, joining approval header information to the individual approver detail rows and resolving the approver's display name from either the FND user directory or the HR person record.

Underlying Base Objects

The documented base objects for this view are ASO_APR_APPROVAL_DETAILS, ASO_LOOKUPS, JTF_RS_RESOURCE_EXTNS, and PER_ALL_PEOPLE_F. ASO_APR_APPROVAL_DETAILS is the primary source: it supplies the object approval identifier, approver identifiers, sequence, status, comments, the send and receive timestamps, and the workflow item key. ASO_LOOKUPS is used to translate stored status codes into user-facing lookup meanings. JTF_RS_RESOURCE_EXTNS and PER_ALL_PEOPLE_F are the name-resolution sources, providing the resource and person attributes from which APPROVER_NAME is derived.

Because the view is defined over these joined objects, edits made directly to base tables are visible immediately through the view, but no inserts, updates, or deletes are permitted through the view itself. The relationship to the underlying Workflow tables is indirect: the workflow item key and approver sequence columns are stored on the approval details row and carried forward into the view, rather than being read live from the Workflow runtime tables.

Key Columns

• OBJECT_APPROVAL_ID — Identifier of the approval instance for the parent business object; the natural join key back to the approval header.
• APPROVAL_DET_ID — Primary identifier of the individual approver detail row in ASO_APR_APPROVAL_DETAILS.
• APPROVER_NAME — Display name of the approver, resolved from the FND user or HR person sources; declared length 360.
• APPROVER_PERSON_ID / APPROVER_USER_ID — Foreign references to the HR person and the FND user respectively, enabling joins to PER_ALL_PEOPLE_F and FND_USER.
• APPROVER_SEQUENCE — The approver's position within the routing sequence of the approval instance.
• APPROVER_STATUS — Current disposition of that approver's action (for example approved, rejected, or pending), interpretable through ASO_LOOKUPS.
• APPROVER_COMMENTS — Free-text response entered by the approver; length 4000.
• DATE_SENT / DATE_RECEIVED — Timestamps marking when the notification was dispatched and when the response was captured.
• APPROVAL_DET_WF_ITEM_KEY — The Oracle Workflow item key for the approval detail, length 43, used to correlate the view row to Workflow notification and history records. This is the column most often referenced when tracing approval audit trails.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard who columns for audit and change tracking.

Common Use Cases and Queries

Typical uses include approval audit reporting, aging analysis of pending approvals, and integration feeds that publish approval outcomes to external systems. The workflow item key is frequently used to reconcile view rows with WF_NOTIFICATIONS and notification history during troubleshooting of stuck or re-sent approvals.

SELECT a.object_approval_id,
       a.approval_det_id,
       a.approver_name,
       a.approver_sequence,
       a.approver_status,
       a.date_sent,
       a.date_received,
       a.approval_det_wf_item_key
FROM   apps.aso_approver_details_v a
WHERE  a.object_approval_id = :p_object_approval_id
ORDER  BY a.approver_sequence, a.date_sent;

SELECT a.approver_name,
       a.approver_status,
       a.approver_comments,
       a.date_received
FROM   apps.aso_approver_details_v a
WHERE  a.approval_det_wf_item_key = :p_wf_item_key;

Queries against APPROVER_NAME or APPROVER_COMMENTS should account for the view's name-resolution joins; filtering on APPROVER_USER_ID or APPROVER_PERSON_ID is generally more efficient than filtering on the derived name. All access should observe APPS read-only conventions, and production reports should bind on OBJECT_APPROVAL_ID or the workflow item key to avoid full scans of the approval detail set.