Results for “approval_sequence”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ASO_APR_APPROVAL_DET_VL is a language-dependent (VL) view within the ASO - Order Capture product family of Oracle E-Business Suite. It exposes the approval detail records generated when an order capture object—such as a quote, sales order, or fulfillment document—is routed through the Oracle Approval Management Engine (AME) or the JTF approver framework. Each row represents a discrete approval step, identifying the approver, the approver group, the sequence of the step, its current status, and related notification metadata. The view is not implemented as a standalone database object in every environment; it is a defined view whose usefulness depends on the presence of the underlying ASO approval tables. Reporting and integration layers use it to consolidate approver assignment data across language-specific and base tables, making it suitable for order-to-cash dashboards, approval audit trails, and workflow integration endpoints that must resolve a human-readable approver comment alongside its technical identifiers.
Underlying Base Objects
The view is defined over two base tables: ASO_APR_APPROVAL_DET_B (the base table holding language-independent approval detail columns) and ASO_APR_APPROVAL_DET_TL (the translation table holding the APPROVER_COMMENTS column). The join is performed on ASO_APR_APPROVAL_DET_ID, with a filter restricting the TL row to the session language via T.LANGUAGE = USERENV('LANG'). The view projects B.ROWID as ROW_ID alongside all B columns and the translation column T.APPROVER_COMMENTS. Because it resolves the language-specific comment dynamically, the same physical approval record returns different text depending on the user's NLS language setting, which makes it a reliable source for multilingual reporting without requiring the report to join the TL table explicitly. No additional base objects are documented in the ETRM metadata beyond these two tables.
Key Columns
- ASO_APR_APPROVAL_DET_ID — Primary key of the approval detail record; the join key to the translation table.
- ASO_APR_OBJ_APPROVAL_ID — Foreign key linking the detail row to its parent approval header for the object.
- JTF_RS_APPROVER_GROUP_ID — Identifier of the approver group (resource group) responsible for the step; this is the column most commonly searched when investigating group-based approval routing, since it resolves to JTF_RS_GROUPS_B and its friends in the JTF Resource Manager schema.
- JTF_RS_APPROVER_ID — Identifier of the individual approver (resource) assigned to the step.
- APPROVAL_SEQUENCE — Ordinal position of the step in the approval chain, supporting ordered routing analysis.
- APPROVAL_STATUS — Current disposition of the step (for example pending, approved, rejected, or cancelled).
- NOTIFICATION_ID — Reference to the notification generated by the workflow/approval engine, enabling correlation with WF_NOTIFICATIONS.
- MANUAL_REQUEST_FLAG — Indicates whether the approval was requested manually rather than by automated routing.
- DATE_SENT / DATE_RECEIVED — Timestamps for dispatch and response of the approval request.
- APPROVER_COMMENTS — Language-resolved free-text remarks captured by the approver.
- ATTRIBUTE1–15, CONTEXT — Descriptive flexfield (DFF) columns and the context segment for extension data.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.
Common Use Cases and Queries
Typical uses include approval audit reporting, aging analysis of pending approvals, and troubleshooting of approver group assignments. The most frequent starting point is a search on JTF_RS_APPROVER_GROUP_ID.
List all approval steps for a given approver group:
- SELECT ASO_APR_APPROVAL_DET_ID, ASO_APR_OBJ_APPROVAL_ID, JTF_RS_APPROVER_ID, APPROVAL_SEQUENCE, APPROVAL_STATUS, DATE_SENT, DATE_RECEIVED FROM ASO_APR_APPROVAL_DET_VL WHERE JTF_RS_APPROVER_GROUP_ID = :group_id ORDER BY ASO_APR_OBJ_APPROVAL_ID, APPROVAL_SEQUENCE;
Identify pending steps by age:
- SELECT ASO_APR_OBJ_APPROVAL_ID, JTF_RS_APPROVER_GROUP_ID, JTF_RS_APPROVER_ID, TRUNC(SYSDATE) - TRUNC(DATE_SENT) days_pending FROM ASO_APR_APPROVAL_DET_VL WHERE APPROVAL_STATUS = 'PENDING' AND DATE_RECEIVED IS NULL ORDER BY days_pending DESC;
Retrieve approval history with comments for an object, joining the header table to resolve the object identifier:
- SELECT d.APPROVAL_SEQUENCE, d.APPROVAL_STATUS, d.JTF_RS_APPROVER_ID, d.APPROVER_COMMENTS, d.DATE_RECEIVED FROM ASO_APR_APPROVAL_DET_VL d, ASO_APR_OBJ_APPROVAL h WHERE d.ASO_APR_OBJ_APPROVAL_ID = h.ASO_APR_OBJ_APPROVAL_ID AND h.OBJECT_ID = :object_id ORDER BY d.APPROVAL_SEQUENCE;
When extending or validating the join to JTF_RS_GROUPS_B, note that the group identifier stored here is the resource group identifier, and the correct join is on JTF_RS_GROUPS_B.GROUP_ID. Because the view resolves language at query time, reports run under different NLS settings should be tested to confirm comment retrieval and to avoid returning null APPROVER_COMMENTS where a translation is absent.
-
Not implemented in this database·Explore ASO module →
-
Not implemented in this database·Explore ASO module →
-
Not implemented in this database·Explore ASO module →
-
Not implemented in this database·Explore ASO module →