Search Results user_releaseable_flag




Overview
Explore in AI Chat

Overview

AP_HOLDS_HOLD_NAME_V is an Oracle Application Object Library view owned by the APPS schema in Oracle E-Business Suite, classified under the AP - Payables product. ETRM metadata documents the object as VALID and originating from Release 10SC. The view serves as a presentation and lookup layer over the Payables hold code definitions, combining the hold code configuration held in AP_HOLD_CODES with the descriptive lookup text held in AP_LOOKUP_CODES. Its purpose is to expose human-readable hold names and reasons alongside the technical hold lookup codes, and to carry the USER_RELEASEABLE_FLAG attribute that indicates whether a given hold can be released by an end user rather than only by a system or administrative process.

Because the view is read-oriented and resolves lookup descriptions into displayed fields, it is commonly referenced for reporting, validation, and integration purposes where callers require the descriptive hold text without having to join AP_HOLD_CODES and AP_LOOKUP_CODES manually. This makes it useful for both functional reporting and technical processing that must interpret hold semantics.

Underlying Base Objects

The view text is defined as a join between AP_HOLD_CODES (referenced in ETRM 12.2.2 metadata as a SYNONYM resolving to the underlying AP table) and AP_LOOKUP_CODES (referenced as a VIEW). A filter restricts the result set to hold types of 'INVOICE HOLD REASON', 'VARIANCE HOLD REASON', 'MATCHING HOLD REASON', and 'INSUFFICIENT FUNDS'. Additional join predicates require L.LOOKUP_TYPE = 'HOLD CODE', an equality between L.LOOKUP_CODE and C.HOLD_LOOKUP_CODE, and the condition NVL(C.INACTIVE_DATE, SYSDATE + 1) > SYSDATE, which excludes hold codes that have been inactivated on or before the current date. FND_GLOBAL is also referenced, providing session context such as the effective date and org-related values used during evaluation.

Key Columns

  • HOLD_LOOKUP_CODE — the hold lookup code from AP_HOLD_CODES, functioning as the join key to the lookup definition.
  • HOLD — the displayed hold name (L.DISPLAYED_FIELD), the user-facing label for the hold.
  • REASON — the descriptive reason text (L.DESCRIPTION) associated with the lookup code.
  • LOOKUP_TYPE — the hold type sourced from C.HOLD_TYPE, constrained to the four hold reason categories.
  • USER_RELEASEABLE_FLAG — the flag from AP_HOLD_CODES that specifies whether the hold can be released by a user. The spelling "RELEASEABLE" reflects the historical column name, and this column is the attribute most often queried when applications or reports must determine which holds are user-releasable.

Common Use Cases and Queries

The view is typically used to list active, user-releasable holds, to translate hold codes into display names for reports, or to drive validation logic during hold application and release. A representative query listing user-releasable holds is:

  • SELECT hold_lookup_code, hold, reason, lookup_type FROM ap_holds_hold_name_v WHERE user_releaseable_flag = 'Y';
  • SELECT hold, reason FROM ap_holds_hold_name_v WHERE hold_lookup_code = :hold_code;
  • SELECT lookup_type, COUNT(*) FROM ap_holds_hold_name_v GROUP BY lookup_type;

Because the view already enforces the active-date and hold-type filters, queries against it return only currently valid hold reason codes, simplifying downstream logic and eliminating redundant invalidation checks in custom reports and integrations.