Results for “hold_date”

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

Overview

APFV_AP_HOLDS is a business 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 exists to present invoice hold information in a form suitable for reporting, inquiry, and integration consumption. The view exposes hold records with their descriptive lookup values already resolved, so that downstream tools and reports can display human-readable hold and release reasons without requiring additional joins to the lookup tables.

The object is registered in ETRM with a status of VALID and is classified as a business view rather than a base table. It is defined with a read-only constraint, meaning it is intended strictly for query access. The view is built over the AP_HOLDS data source and applies Oracle Application Object Library (AOL) descriptive flexfield and lookup column aliases so that the underlying coded values are surfaced as descriptive text for consumers.

Underlying Base Objects

The view is defined over AP_HOLDS, accessed via its APPS synonym. The documented base object reference lists AP_HOLDS (SYNONYM) as the sole referenced object. The defining query selects from AP_HOLDS with the alias HO and is created with the WITH READ ONLY clause, which guarantees that no DML can be performed through the view.

AP_HOLDS is the core Payables table that stores every hold placed against an invoice or an invoice line. Because APFV_AP_HOLDS resolves the lookup codes into descriptions, it effectively layers descriptive semantics on top of the raw hold records without altering the underlying data model. All updates and inserts must continue to be performed against AP_HOLDS directly.

Key Columns

The view exposes the following columns, several of which carry AOL descriptive flexfield or lookup aliases:

• HELD_BY_USER_ID — the user who placed the hold, drawn from HO.HELD_BY.
• HOLD_DATE — the date the hold was applied.
• HOLD_REASON — the free-text reason captured when the hold was placed.
• _LA:HOLD_DESCRIPTION — a lookup-derived description of the hold code, resolved from AP_LOOKUP_CODES using the HOLD CODE lookup type and the DESCRIPTION column.
• HOLD_RELEASE_REASON — the reason recorded when the hold was released.
• _LA:RELEASE_DESCRIPTION — the lookup-derived description of the release code.
• INSUFFICIENT_FUNDS_OWNER_ID — the identifier of the owner associated with insufficient funds holds.
• INVOICE_ID — the invoice against which the hold was placed.
• LINE_LOCATION_ID — the invoice line location associated with the hold, when the hold applies at line level.
• HOLD_CODE — the underlying hold lookup code value.
• _DF — the descriptive flexfield reference for the AP_HOLDS entity.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include building invoice hold aging reports, auditing who placed or released holds, and extracting hold data for reconciliation or data-warehouse loads. Because the view resolves lookup descriptions, it is well suited to reporting tools that cannot perform lookup joins themselves.

A representative query listing active holds with descriptions is:

• SELECT invoice_id, hold_code, hold_date, hold_reason FROM apfv_ap_holds WHERE release_reason IS NULL;
• SELECT held_by_user_id, hold_date, hold_reason, hold_release_reason FROM apfv_ap_holds WHERE invoice_id = :invoice_id;

Analysts may join APFV_AP_HOLDS to AP_INVOICES_ALL on INVOICE_ID to combine hold detail with invoice header attributes, and to AP_INVOICE_LINES_ALL via LINE_LOCATION_ID for line-level context. Since the view is read-only, it should be treated purely as a query surface, with all maintenance performed against AP_HOLDS.