Search Results approver_sequence

Overview

ASO_APPROVER_DETAILS_V is a seeded, read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ASO (Order Capture) product family. It exposes approver-level detail rows associated with the approval infrastructure used by Oracle Order Management and related Order Capture flows in both EBS 12.1.1 and 12.2.2. In the ETRM metadata the object is registered as object type VIEW with a status of VALID.

The view serves as a denormalized reporting and integration surface over the approval detail table. Rather than requiring callers to join approver identifiers to the person or resource tables manually, it resolves the approver's display name and translates the internal approver status code into a user-facing meaning. This makes it well suited for approval-status inquiries, workflow-driven lookups, and inbound/outbound integrations that need to present approver identity and state in a single row.

The search fragment provided ("'approver_user_id':approver.get('approver_user_id'),'approver_name':approver.get('approver_name'),") reflects a typical consumer pattern: application code (often JavaScript or a middleware mapping layer) reading the APPROVER_USER_ID and APPROVER_NAME attributes from an approval record and re-keying them into a JSON-style payload. ASO_APPROVER_DETAILS_V is the natural source of exactly those two fields, since it surfaces both the numeric user identifier and the resolved display name on the same row.

Underlying Base Objects

The view text is defined over the following documented base objects:

• ASO_APR_APPROVAL_DETAILS (referenced through a synonym) — the primary detail table supplying approval rows, audit columns, sequence, status code, comments, and send/receive dates. Aliased as AAD.
• ASO_LOOKUPS (a view) — joined on APPROVER_STATUS to translate the stored lookup code into its MEANING, restricted to LOOKUP_TYPE = 'ASO_APPROVER_STATUS'. Aliased as AL.
• PER_ALL_PEOPLE_F (synonym) — used in a scalar subquery to derive the approver's FULL_NAME from PERSON_ID where the effective-dating range covers SYSDATE.
• JTF_RS_RESOURCE_EXTNS (synonym) — used as a fallback name source keyed on USER_ID, filtered by the resource's active date range.

The name resolution strategy is an NVL: the person name is preferred, and the resource source name is substituted when no person match exists. The APPROVER_STATUS equals MEANING join makes the status column directly readable.

Key Columns

• APPROVAL_DET_ID — primary detail identifier for the approval row; extended into APPROVAL_DET_WF_ITEM_KEY as APPROVAL_DET_ID||'DET', the workflow item key used to correlate the row to Oracle Workflow.
• OBJECT_APPROVAL_ID — links the detail row to its parent approval object.
• APPROVER_NAME — resolved display name (person full name, or resource source name as fallback).
• APPROVER_PERSON_ID — HR person identifier, when the approver is an employee.
• APPROVER_USER_ID — FND user identifier, the key commonly mapped into integration payloads.
• APPROVER_SEQUENCE — ordering of the approver within the approval hierarchy.
• APPROVER_STATUS — decoded status meaning from ASO_LOOKUPS.
• APPROVER_COMMENTS — free-text remarks recorded by the approver.
• DATE_SENT / DATE_RECEIVED — timestamps for notification dispatch and response.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical usages include approval-status reporting, workflow reconciliation, and interface extracts that publish approver identity and outcome.

• List approvers and status for a given approval object.
• Retrieve APPROVER_USER_ID and APPROVER_NAME for integration mapping.
• Identify pending approvals by DATE_SENT with no DATE_RECEIVED.
• Reconcile workflow item keys back to approval details.

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

SELECT approver_user_id, approver_name
FROM   apps.aso_approver_details_v
WHERE  approver_status = 'PENDING';

Because the view performs correlated scalar subqueries and effective-dated lookups, heavy ad hoc reporting should be filtered by OBJECT_APPROVAL_ID or APPROVER_USER_ID to keep plan costs predictable.