Results for “amount_approved”

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

Overview

AP_WFAPPROVAL_HISTORY_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is part of the Oracle Payables (AP) product family and exposes the workflow approval audit trail for invoices submitted through the Oracle Workflow-based invoice approval process. The view consolidates historical approval actions recorded in the approval history table with currently pending or "future" approvers derived from an approval list global temporary table, so that a single query can return both completed and outstanding approval events for an invoice.

The view's principal consumption is in the Invoice Approval History page and in custom reporting or integration logic where users need to reconstruct who approved an invoice, in what order, and with what comments. Because the column APPROVER_COMMENTS is exposed directly from the history table, searches such as approver_comments against this view are common when auditing rejection reasons or free-text approver notes. The view is defined in the ETRM as VALID and is documented as a UNION ALL construct rather than a simple projection, which is important for both performance planning and result interpretation.

Underlying Base Objects

The documented base objects referenced by the view are AP_INV_APRVL_HIST_ALL, AP_APPROVERS_LIST_GT, AP_LOOKUP_CODES, AP_INVOICES_ALL, and the FND_GLOBAL package.

• AP_INV_APRVL_HIST_ALL — the stored approval history for invoices, supplying INVOICE_ID, LINE_NUMBER, RESPONSE, APPROVER_ID, APPROVER_NAME, AMOUNT_APPROVED, APPROVER_COMMENTS, LAST_UPDATE_DATE, ITERATION, and HISTORY_TYPE.
• AP_APPROVERS_LIST_GT — a global temporary table holding the current approver list; the second branch of the UNION ALL reads it to surface approvers whose approval is still pending.
• AP_LOOKUP_CODES — joined twice through outer joins to translate internal codes into displayed values: lookup type AP_WFAPPROVAL_STATUS maps RESPONSE, and AP_WFAPPROVAL_CONTEXT maps HISTORY_TYPE. A third use references the 'NLS TRANSLATION' / 'FUTURE' code for pending rows.
• AP_INVOICES_ALL — used in an EXISTS clause to restrict the pending-approver branch to invoices whose WFAPPROVAL_STATUS is 'INITIATED'.
• FND_GLOBAL — the standard EBS package supplying session context used during resolution of the view.

Key Columns

• INVOICE_ID — identifier of the invoice; in the pending branch this is sourced from AGT.TRANSACTION_ID.
• RESPONSE — the approver's action or the translated status label; populated from lookup AP_WFAPPROVAL_STATUS (RESPONSE_DSP alias).
• PERSON_ID / APPROVER_ID — the approver's person identifier.
• APPROVER_NAME — display name of the approver (DISPLAY_NAME in the pending branch).
• AMOUNT_APPROVED — amount approved at that step; NULL for pending approvers.
• APPROVER_COMMENTS — free-text comments entered by the approver; the column most often searched. It is NULL for rows originating from the pending-approver branch.
• LAST_UPDATE_DATE — timestamp of the approval action; SYSDATE is substituted for pending rows.
• RESPONSE_DSP / DISPLAYED_FIELD — translated display value for the response code.
• ITERATION — iteration counter distinguishing repeated approval cycles.
• HISTORY_TYPE — context of the approval, such as DOCUMENTAPPROVAL or LINESAPPROVAL.

Common Use Cases and Queries

Typical scenarios include auditing rejection comments, building custom approval-history reports, and feeding invoice approval data into downstream systems. A representative query retrieving approver comments for a specific invoice is:

• SELECT invoice_id, approver_name, response_dsp, approver_comments, last_update_date FROM apps.ap_wfapproval_history_v WHERE invoice_id = :p_invoice_id ORDER BY last_update_date;
• SELECT invoice_id, approver_name, approver_comments FROM apps.ap_wfapproval_history_v WHERE approver_comments IS NOT NULL AND last_update_date >= :p_from_date;
• SELECT invoice_id, approver_name, response_dsp FROM apps.ap_wfapproval_history_v WHERE response_dsp = 'FUTURE';

Because the view uses a UNION ALL, queries filtering only APPROVER_COMMENTS return only historical rows, since pending-approver rows supply NULL for that column. Analytical queries should anticipate that LAST_UPDATE_DATE may be SYSDATE for pending entries, and joins should account for the ITERATION column when multiple approval cycles exist for a single invoice.