Results for “approval_date”

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

Overview

POR_APPROVAL_STATUS_LINES_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and delivered as part of the ICX (Oracle iProcurement) product module. In EBS 12.1.1 and 12.2.2 it provides a consolidated, read-only projection of requisition approval activity, fusing two distinct sources of approval state into a single result set: historical approval actions already taken (PO_ACTION_HISTORY) and approval list lines that are still pending action (PO_APPROVAL_LIST_LINES joined through PO_APPROVAL_LIST_HEADERS). The view's purpose is to present the full approval lifecycle of a purchasing requisition — who approved, in what sequence, the status of each step, and the timestamp of the action — in a display-ready format.

Because it is defined in APPS and references only packaged functions and synonyms accessible to that schema, it is intended for querying rather than for DML. It underlies approval status inquiries surfaced in the iProcurement requisition workflow and is frequently queried directly by technical consultants building custom reports, BI Publisher extracts, and integration interfaces that need approval audit information across both Oracle Purchasing and iProcurement.

Underlying Base Objects

The documented base objects referenced by the view are:

• PO_ACTION_HISTORY (synonym) — supplies records of approval actions already performed against requisitions.
• PO_APPROVAL_LIST_HEADERS / PO_APPROVAL_LIST_LINES (synonyms) — supply the approval list structure, including approvers not yet acted upon (lines beyond the current sequence).
• PO_LOOKUP_CODES (view) — decodes action codes into a displayed label via lookup types 'APPROVER ACTIONS' and 'CONTROL ACTIONS'.
• PO_REQUISITION_HEADERS_ALL (synonym) — the requisition header source context for purchasing-type requisitions.
• POR_VIEW_REQS_PKG, FND_GLOBAL (packages) — supply approver names, business group names, and profile-driven date formatting.

The view is a UNION ALL of two branches. The first selects from PO_ACTION_HISTORY for requisition objects (OBJECT_TYPE_CODE = 'REQUISITION', OBJECT_SUB_TYPE_CODE = 'PURCHASE'). The second selects from the approval list tables for the latest revision (LATEST_REVISION = 'Y', DOCUMENT_TYPE = 'REQUISITION', DOCUMENT_SUBTYPE = 'PURCHASE') where SEQUENCE_NUM is greater than CURRENT_SEQUENCE_NUM, i.e. steps still pending.

Key Columns

• DOCUMENT_ID — the requisition identifier associated with the approval record.
• APPROVER — resolved approver name, returned by POR_VIEW_REQS_PKG.GET_APPROVER_NAME.
• SEQUENCE_NUM — ordering position of the approval step in the approval list.
• APPROVAL_STATUS — the raw action code from PO_ACTION_HISTORY, or the literal 'NULL' for the pending branch.
• APPROVAL_STATUS_LABEL — the decoded displayed field from PO_LOOKUP_CODES, defaulting to 'PENDING' where no action code exists.
• APPROVAL_DATE — formatted action or response date, using FND_PROFILE.VALUE_WNPS('ICX_DATE_FORMAT_MASK').
• NOTES — approval note or approver comment text.
• BUSINESS_GROUP_NAME — business group resolved for the approver.

Common Use Cases and Queries

Typical applications include approval audit reports, aging of pending approvals, and reconciliation of iProcurement requisition status against purchasing records. A simple retrieval for a single requisition:

• SELECT approver, sequence_num, approval_status_label, approval_date, notes FROM por_approval_status_lines_v WHERE document_id = :requisition_id ORDER BY sequence_num;
• SELECT document_id, approver, approval_status_label FROM por_approval_status_lines_v WHERE approval_status_label = 'PENDING';

Because the view resolves approver and business group names through PL/SQL package calls, large unfiltered queries can be performance-sensitive; filtering on DOCUMENT_ID or STATUS is recommended.