Results for “ap_hold_codes_hold_name_v”

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

Overview

The AP_HOLD_CODES_HOLD_NAME_V view is a Payables (AP) dictionary object owned by the APPS schema. Its documented description explicitly designates it as "(Release 10SC Only)," indicating that it originated as a compatibility or presentation object in an early release and has been retained in the data dictionary through 12.1.1 and 12.2.2. The view exposes invoice hold reason codes together with their user-facing descriptive text. It joins the operational hold definitions stored in AP_HOLD_CODES to the lookup-based display values of AP_LOOKUP_CODES, thereby resolving the raw HOLD_LOOKUP_CODE into a human-readable hold name and an associated reason.

Because the view filters to active rows only, it is suited to reporting and integration scenarios that require a current, display-ready list of invoice hold reasons. It is not a transactional view: it carries no invoice-hold-assignment data and performs no aggregation against invoice records. Its role is that of a lightweight reference object for validating or presenting hold codes.

Underlying Base Objects

Per the documented view text, the object is defined over two sources:

• AP_HOLD_CODES (referenced in ETRM 12.2.2 as a SYNONYM) — the base table of hold definitions, aliased as C. It supplies the hold lookup code, the hold type, the description, and the inactive date used for the active-record filter.
• AP_LOOKUP_CODES (documented as a VIEW) — the lookup presentation layer, aliased as L. It supplies the displayed field text that becomes the HOLD column.

ETRM additionally records FND_GLOBAL (PACKAGE) among the referenced objects, reflecting the standard Oracle EBS practice of resolving the current application context and session attributes during lookup and view resolution. The join is constrained on L.LOOKUP_CODE = C.HOLD_LOOKUP_CODE, with C.HOLD_TYPE = 'INVOICE HOLD REASON' and L.LOOKUP_TYPE = 'HOLD CODE'. The active-row predicate is NVL(C.INACTIVE_DATE, SYSDATE + 1) > SYSDATE, which treats a null inactive date as open-ended and excludes holds whose inactive date has passed.

Key Columns

• HOLD_LOOKUP_CODE — the code carried from AP_HOLD_CODES.HOLD_LOOKUP_CODE. This is the value most commonly matched against hold_lookup_code in the invoice holds tables during queries and integration mapping.
• HOLD — the display text derived from AP_LOOKUP_CODES.DISPLAYED_FIELD. This is the label intended for user-facing presentation.
• REASON — sourced from AP_HOLD_CODES.DESCRIPTION, carrying the descriptive reason associated with the hold definition.

The three columns together make the view self-sufficient for most reference lookups: a caller can key on the code, display the hold, and echo the reason without touching the base tables directly.

Common Use Cases and Queries

Typical scenarios include LOV population for hold-code selection, decoding hold codes in reports, and validating values received through interfaces. A standard query returning the full active set:

SELECT hold_lookup_code, hold, reason
  FROM apps.ap_hold_codes_hold_name_v
 ORDER BY hold;

To resolve a single code during reporting or validation:

SELECT hold, reason
  FROM apps.ap_hold_codes_hold_name_v
 WHERE hold_lookup_code = :p_hold_lookup_code;

To join the view to invoice hold data, map on the code column:

SELECT h.invoice_id, v.hold, v.reason
  FROM ap_invoice_holds h, apps.ap_hold_codes_hold_name_v v
 WHERE h.hold_lookup_code = v.hold_lookup_code;

Two cautions apply. First, because the view suppresses inactive holds, it must not be used where historical hold definitions are required; AP_HOLD_CODES should be queried directly in that case. Second, since the object is documented as "(Release 10SC Only)," implementations on 12.1.1 and 12.2.2 should treat it as a legacy presentation object and confirm its continued validity in the target environment before embedding it in custom code.