Results for “ap_wfapproval_context”

8 results




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

Overview

APPS.AP_WFAPPROVAL_HISTORY_V is a reporting view in the Oracle Payables module of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). It consolidates the approval history of invoices processed through the Oracle Workflow-based Invoice Approval workflow and presents a human-readable iteration of that history. Specifically, the view joins the raw approval history stored in AP_INV_APRVL_HIST_ALL to two lookup configurations — AP_WFAPPROVAL_STATUS and AP_WFAPPROVAL_CONTEXT — so that codes such as the response value and the history type are translated into their displayed (translatable) text. Because it exposes both the raw codes and the displayed fields, the view serves as the canonical source for displaying, auditing, and extracting invoice approval routing and action history.

Underlying Base Objects

The view is defined as a UNION ALL of two queries. The first reads AP_INV_APRVL_HIST_ALL (the persistent approval history table) and outer-joins it to two rows drawn from AP_LOOKUP_CODES (itself a view over the lookup tables), one filtered on LOOKUP_TYPE = 'AP_WFAPPROVAL_STATUS' and the other on LOOKUP_TYPE = 'AP_WFAPPROVAL_CONTEXT'. The second branch reads AP_APPROVERS_LIST_GT (a global temporary table holding the pending approvers list) and produces a synthetic "future approver" row for invoices whose workflow status is INITIATED and that have not yet been sent. This branch is filtered against AP_INVOICES_ALL and excludes approvers for whom a SENT history row already exists, using the AP_WFAPPROVAL_CONTEXT lookup type to derive the correct context from the approver's item class (header or line). The FND_GLOBAL package is referenced by the ETRM metadata as part of the object's dependency footprint.

Key Columns

  • INVOICE_ID — The invoice identifier linking the row to AP_INVOICES_ALL.
  • LINE_NUMBER — The invoice line the approver acted on, for line-level approvals.
  • RESPONSE / DISPLAYED_FIELD — The workflow response code (for example SENT, APPROVED, REJECTED) and its translated display value from AP_WFAPPROVAL_STATUS.
  • APPROVER_ID and APPROVER_NAME — The approver's person identifier and display name.
  • AMOUNT_APPROVED and APPROVER_COMMENTS — The approved amount and any comment captured at the approval action.
  • LAST_UPDATE_DATE — The timestamp of the history row; for pending approvers this is populated with SYSDATE.
  • ITERATION — The workflow iteration count, distinguishing re-runs of the approval process.
  • HISTORY_TYPE / DISPLAYED_FIELD — The context of the action (for example DOCUMENTAPPROVAL or LINESAPPROVAL) and its translated text from AP_WFAPPROVAL_CONTEXT.

Common Use Cases and Queries

Typical applications include approval audit reports, tracking who approved what and when, and reconciling pending approvers against completed approvals. The view is readily queried for a single invoice's complete approval trail:

SELECT invoice_id, line_number, approver_name, response,
       history_type, amount_approved, approver_comments, last_update_date
FROM   apps.ap_wfapproval_history_v
WHERE  invoice_id = :p_invoice_id
ORDER  BY iteration, last_update_date;

It is equally useful for identifying invoices still awaiting action, by selecting rows whose RESPONSE or displayed status indicates a pending approver returned from the second UNION ALL branch. Because it exposes both codes and translated values, the view supports both localized reporting and programmatic integration that matches on stable lookup codes.