Search Results held_by_user_id




Overview
Explore in AI Chat

Overview

APPS.APFV_AP_HOLDS is a read-only view in the Oracle E-Business Suite Payables (SQLAP) schema that exposes invoice hold information stored in the AP_HOLDS table. The "APFV" prefix follows the Oracle EBS convention for an Application Object Library (AOL) "flexfield view," a construct that pairs the underlying data columns of a base table with the descriptive and value-set relationships required by Oracle Forms. In this case, the view supplies the display values needed to render the hold name and release name lookups used on Payables hold forms and related screens.

Because the view is defined with the WITH READ ONLY clause, it cannot be used to insert, update, or delete data. It is intended strictly for query and reporting purposes. The view plays a supporting role in the Payables application's flexible field (flexfield) infrastructure, translating stored lookup codes into readable descriptions at runtime, and it may also be referenced by custom reports, integrations, and diagnostic queries that need hold information in a presentation-ready form.

Underlying Base Objects

The view is defined over a single documented base object: the AP_HOLDS synonym, which resolves to the AP_HOLDS table owned by the AP (Payables) schema. ETRM metadata lists AP_HOLDS (SYNONYM) as the only referenced object, so the view is a thin projection layered directly on that table rather than a join of multiple base tables.

All columns in the view text are drawn from the AP_HOLDS alias HO. The special literal expressions embedded in the SELECT list — the '_LA' and '_DF' strings — are AOL flexfield descriptors that Oracle Forms interprets to attach lookup and descriptive flexfield behavior. The '_LA:HO.HOLD_LOOKUP_CODE:AP_LOOKUP_CODES:HOLD CODE:DESCRIPTION' expression links the hold lookup code to the AP_LOOKUP_CODES view to obtain the hold description, and the parallel '_LA' expression on RELEASE_LOOKUP_CODE resolves the release reason description. The '_DF:SQLAP:AP_HOLDS:HO' string identifies the descriptive flexfield context for the AP_HOLDS record. Because it is a synonym-based, single-table view, any data change in AP_HOLDS is immediately reflected when the view is queried.

Key Columns

  • INVOICE_ID — Foreign key identifying the invoice against which the hold is placed.
  • LINE_LOCATION_ID — Identifies the specific invoice line or line location affected by the hold.
  • HOLD_LOOKUP_CODE — The lookup code defining the type of hold applied.
  • HOLD_REASON — Free-text reason supplied when the hold was applied.
  • HELD_BY — The user or process that placed the hold.
  • HOLD_DATE — The date the hold was applied.
  • RELEASE_REASON — Text explaining why the hold was released.
  • RESPONSIBILITY_ID — The responsibility under which the hold was created.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit columns tracking who created and last modified the hold record.

The two '_LA' expressions resolve the hold code and release code into their descriptive names via AP_LOOKUP_CODES, which is what makes the view useful for direct reporting without additional lookups.

Common Use Cases and Queries

This view is commonly used to report active and released holds on invoices, to drive custom hold-management dashboards, and to troubleshoot why an invoice is blocked from payment. Because it returns lookup descriptions alongside codes, it is convenient for end-user-facing extracts.

A typical query lists holds for a given invoice:

SELECT invoice_id, hold_lookup_code, hold_reason, held_by, hold_date, release_reason FROM apps.apfv_ap_holds WHERE invoice_id = :invoice_id;

Another common pattern aggregates holds by code to identify the most frequent hold types affecting a pay run, or joins the view back to AP_INVOICES_ALL on INVOICE_ID to enrich the output with supplier and invoice number. All access is read-only, so the view should be treated purely as a query surface over AP_HOLDS.