Search Results approver_status

Overview

ASO_APR_APPROVAL_DETAILS is a transactional table in the ASO (Order Capture) product family of Oracle E-Business Suite, residing in the ASO schema. It stores detailed approval instance information — specifically, the per-approver, per-action records that make up a single approval cycle for an order capture object. Where header-level approval records track the overall approval transaction, this table persists the granular breakdown: which approver acted, in what sequence, with what status, when the notification was sent and returned, and any comments or authority context attached to the decision. It is populated by the Order Capture approval engine and is tightly coupled to workflow-driven approval routing, making it a primary source for approval audit trails, cycle-time analysis, and approver workload reporting.

The ETRM Data Vault classification is heuristic and derived from the documented foreign key structure: the table is classified as standalone. As a modeling suggestion, this reflects a table whose relationships to the surrounding model are largely expressed through non-enforced or soft joins (for example, the approval instance and approver references), rather than a dense web of hard foreign keys. A Data Vault model could still choose to treat it as a satellite hanging off an approval-instance hub, with approver and item references handled as links or carried as descriptive attributes.

Key Information Stored

The table is documented with 45 columns. The most functionally significant are:

• APPROVAL_DET_ID — the surrogate primary key. It is the sole documented unique index candidate (ASO_APR_APPROVAL_DETAIL_U1) and therefore the only business-key candidate identified in the metadata.
• OBJECT_APPROVAL_ID — the parent approval instance this detail row belongs to, the principal join back to the approval header context.
• APPROVER_PERSON_ID and APPROVER_USER_ID — the person and application user assigned to act on the approval.
• APPROVER_SEQUENCE — the ordering position of this approver within the routing chain.
• APPROVER_STATUS — the disposition of the approval action (approved, rejected, pending, and similar).
• APPROVER_COMMENTS — free-text rationale or notes recorded by the approver.
• DATE_SENT and DATE_RECEIVED — notification dispatch and response timestamps, the basis for cycle-time and aging calculations.
• NAME, ITEM_ID, and ITEM_CLASS — identity of the item or object under approval.
• ACTION_TYPE_ID, GROUP_OR_CHAIN_ID, OCCURRENCE, AUTHORITY, and APPROVER_CATEGORY — approval-routing attributes describing the action taken, the group or chain grouping, re-occurrence count, delegated authority, and approver classification.
• SECURITY_GROUP_ID — the multi-org/security grouping, joining to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the framework for concurrent-update control.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE1–ATTRIBUTE20/CONTEXT descriptive flexfield set.

Common Use Cases and Queries

Typical reporting needs include approval audit trails, approver response-time analysis, and identification of stalled approvals.

• Retrieve all approver actions for a given approval instance and order them by sequence:

  SELECT d.approver_sequence, d.approver_person_id, d.approver_status, d.date_sent, d.date_received FROM aso.aso_apr_approval_details d WHERE d.object_approval_id = :p_object_approval_id ORDER BY d.approver_sequence;

• Measure approval cycle time per approver instance using DATE_RECEIVED minus DATE_SENT, filtered by APPROVER_STATUS for completed actions.
• Report approver workload and category distribution grouped by APPROVER_PERSON_ID and APPROVER_CATEGORY over a date range.
• Identify pending or stalled approvals within a routing chain via GROUP_OR_CHAIN_ID where APPROVER_STATUS is still open and DATE_SENT exceeds a threshold.

Because approvals are frequently driven from the Order Capture UI and workflow, direct queries are best used for read-only reporting; transactional changes should flow through the supported approval APIs to preserve integrity.

Related Objects

• ASO_APR_APPROVALS (approval instance/header) — joined via OBJECT_APPROVAL_ID to obtain the parent approval context and the object being approved.
• FND_SECURITY_GROUPS — referenced directly through SECURITY_GROUP_ID, the sole documented foreign key.
• PER_ALL_PEOPLE_F — joined via APPROVER_PERSON_ID for approver names and assignment attributes.
• FND_USER — joined via APPROVER_USER_ID to resolve the acting application user.
• ASO_ORDER_HEADERS_ALL / ASO_ORDER_LINES_ALL — the order capture objects whose approvals these detail rows ultimately represent.
• ASO_APR_APPROVAL_HISTORIES (where present in the ASO approval schema) — historical approval snapshots for audit continuity.
• Order Capture approval APIs and workflow processes — the supported interfaces that create and update these detail rows.