Results for “hold_code”

50+ results




Overview
Explore in AI Chat

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

Overview

APBV_AP_HOLDS is a business (BVI) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Payables (AP) product family and is documented as VALID in the ETRM repository. The view presents invoice hold information in a business-friendly projection of the underlying AP_HOLDS table, allowing reporting tools, concurrent programs, and external integrations to query hold data without directly referencing the base transactional table.

The object is commonly referenced in Payables reporting and in integration scenarios where hold details are required for invoice approval workflows, payment scheduling, and holds analysis. Because it is defined with a WITH READ ONLY clause, the view is strictly query-only; no DML operations are permitted through it, ensuring that hold records can only be created, updated, or released through the standard Payables application logic and APIs.

Underlying Base Objects

APBV_AP_HOLDS is defined over a single base object: the AP_HOLDS table, which is referenced through an APPS-owned synonym. The view text in the ETRM metadata is a straightforward column projection:

The AP_HOLDS table is the core Payables table that stores one row for each hold applied to an invoice or an invoice line. Because APBV_AP_HOLDS is a direct projection with no joins, filtering, or aggregation, it inherits the row-level granularity of AP_HOLDS exactly. No WHO columns are renamed or calculated, and no additional tables are joined in the view definition.

Key Columns

The ETRM metadata lists the view columns with a naming convention that differs slightly from the underlying column names in the SELECT statement. This is significant for developers, because the exposed column names are the ones that must be used in queries against the view.

  • HOLD_CODE — The hold lookup code identifying the type of hold applied to the invoice. In the view text this maps to HOLD_LOOKUP_CODE from AP_HOLDS. This is the column most commonly searched for by users ("hold_code"), and it corresponds to the values defined in the AP_HOLD_CODES lookup.
  • HELD_BY_USER_ID — The user who placed the hold. Maps to HELD_BY in the base table.
  • HOLD_DATE — The date on which the hold was applied.
  • HOLD_REASON — The free-text or descriptive reason entered when the hold was applied.
  • HOLD_RELEASE_REASON — The reason recorded when the hold was released. Maps to RELEASE_REASON.
  • INSUFFICIENT_FUNDS_OWNER_ID — The owner identifier associated with insufficient funds holds. Maps to RESPONSIBILITY_ID.
  • INVOICE_ID — The invoice to which the hold applies; joins to AP_INVOICES_ALL.
  • LINE_LOCATION_ID — The invoice line location, when the hold is line-level rather than header-level.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns.

Common Use Cases and Queries

Typical uses include identifying invoices blocked by specific holds, reporting on hold aging, and driving automated release processes. A representative query retrieving all invoices held by a specific hold code is:

  • SELECT hold_code, invoice_id, hold_date, held_by_user_id FROM apps.apbv_ap_holds WHERE hold_code = 'INSUFFICIENT FUNDS';
  • SELECT hold_code, COUNT(*) FROM apps.apbv_ap_holds GROUP BY hold_code ORDER BY 2 DESC;

Because the view is read-only and unjoined, it is best suited to direct hold-level reporting. For invoice-level context (vendor, amount, status), join to AP_INVOICES_ALL on INVOICE_ID. Note that columns must be referenced using the view's documented names, such as HOLD_CODE rather than HOLD_LOOKUP_CODE.