Results for “ap_holds_release_name_v”

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

Overview

AP_HOLDS_RELEASE_NAME_V is a read-only reporting view owned by the APPS schema within the Oracle Payables (AP) module. It exposes the set of hold codes that function as release codes, presenting them alongside their user-facing display names and descriptive reasons. The view was originally introduced for the 10SC release, and although it persists in the E-Business Suite data dictionary through 12.1.1 and 12.2.2 with a VALID status, it is no longer tied to the primary hold-and-release workflow used in later releases. Its continued presence is largely a backward-compatibility artifact, but it remains queryable and is occasionally referenced by custom reports, integrations, and legacy extensions that need a denormalised list of release codes joined to hold lookup metadata.

The view serves a narrow but well-defined role: rather than returning all hold codes, it filters the hold code table to those records whose HOLD_TYPE indicates a release, then resolves each code to its populated display value in the lookup repository. This makes it a convenient source when a report must translate an internal release_lookup_code value into a human-readable label without embedding multiple joins.

Underlying Base Objects

The view is defined over three documented base objects:

• AP_HOLD_CODES (synonym) — the primary source of hold code records and their types. Aliased as C, it supplies HOLD_LOOKUP_CODE, HOLD_TYPE and INACTIVE_DATE.
• AP_LOOKUP_CODES (view) — the lookup repository that stores the DISPLAYED_FIELD and DESCRIPTION for each lookup code. Aliased as L, it is joined on LOOKUP_CODE = C.HOLD_LOOKUP_CODE with LOOKUP_TYPE = 'HOLD CODE'.
• FND_GLOBAL (package) — the standard EBS context package, typically used for security and session context resolution during execution.

The defining predicate restricts output to rows where C.HOLD_TYPE LIKE '%RELEASE%' and the record is not inactive, expressed as NVL(C.INACTIVE_DATE, SYSDATE + 1) > SYSDATE. In other words, any hold code with a live (or null) inactivity date whose type contains the token "RELEASE" is surfaced.

Key Columns

• RELEASE_LOOKUP_CODE — derived from C.HOLD_LOOKUP_CODE; the internal code identifying the release.
• RELEASE — derived from L.DISPLAYED_FIELD; the displayed, user-facing name of the release code.
• REASON — derived from L.DESCRIPTION; the descriptive text associated with the lookup code.
• HOLD_TYPE — derived from C.HOLD_TYPE; identifies the classification of the hold, and by the view's filter will contain "RELEASE".

Common Use Cases and Queries

Typical usage centres on lookup translation and validation of release codes in custom reporting. A simple listing query is:

SELECT release_lookup_code,
       release,
       reason,
       hold_type
FROM   apps.ap_holds_release_name_v
ORDER BY release;

To resolve a specific code to its display name:

SELECT release, reason
FROM   apps.ap_holds_release_name_v
WHERE  release_lookup_code = :p_release_code;

Because the view already filters inactive records, it is well suited as a source for LOV-style validation or for driving dropdowns in custom concurrent programs and OAF/Forms extensions. Note, however, that Oracle's mainstream 12.x release functionality does not depend on this view, so any new development should treat it as legacy and confirm availability against the target instance before relying on it.