Results for “ap_web_fnd_lookups_pkg”

50+ results




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

Overview

The APPS.AP_WEB_FND_LOOKUPS_PKG package is a small Oracle E-Business Suite PL/SQL utility package owned by the APPS schema. It is used by the Oracle Payables and Oracle iSupplier/Web Expenses family of modules (objects prefixed AP_WEB_) to resolve Oracle Application Object Library lookup codes into their human-readable meanings, with particular focus on the standard Yes/No lookup values used across Payables web-based user interfaces. The package header carries the source control tag $Header: apwlupss.pls 115.1 2002/12/26 10:13:27 srinvenk noship $, indicating it has existed since at least the 11i era and has been carried forward unchanged into the 12.1.1 and 12.2.2 code lines. Because it is declared with AUTHID CURRENT_USER, it executes with the privileges of the calling session rather than as definer rights, which means the caller must already have access to the underlying FND_LOOKUPS data.

The package is classified as an "OTHER" API in the ETRM metadata for 12.2.2, meaning it is not a public, fully supported integration API but rather an internal helper used by other Oracle Payables packages.

Key Procedures and Functions

The documented package body/header specification exposes a single public function:

  • GETYESNOMEANING — Accepts a lookup code value and returns the corresponding lookup meaning from the standard Yes/No lookup type. It is used to translate the stored code (for example, Y or N) into the displayable meaning so that Payables web pages, reports, and internal validation routines render consistent, language-aware labels.

The package also declares global (package-level) variables g_langCode, g_yesMeaning, and g_noMeaning. These are populated to cache the current language code and the resolved Yes/No meanings within a session, thereby avoiding repeated queries against FND_LOOKUPS for the same values during a single user interaction. Two subtypes, lookups_meaning and lookups_code, are anchored to FND_LOOKUPS.MEANING%TYPE and FND_LOOKUPS.LOOKUP_CODE%TYPE respectively to keep parameter and return types aligned with the dictionary columns.

Tables Accessed

Although the ETRM metadata does not list explicit table references via APPS synonyms, the function and subtype declarations make clear that the package reads the Oracle Application Object Library table FND_LOOKUPS. The anchored subtypes reference FND_LOOKUPS.MEANING and FND_LOOKUPS.LOOKUP_CODE, and the purpose of GETYESNOMEANING is to retrieve a MEANING for a supplied LOOKUP_CODE. In an APPS-owned package, this access is normally performed through the APPS.FND_LOOKUPS synonym. The package is read-only with respect to this table; no inserts, updates, or deletes against application data are implied. There is no evidence of any DML against Payables transactional tables.

Usage Notes

This package is not intended for direct customer invocation and should be treated as an internal Oracle Payables utility. It is referenced by three other packages in the EBS code base, which call GETYESNOMEANING to resolve Yes/No prompts, validation logic, and display values in Payables web-based flows. Typical invocations occur from Oracle Forms and OAF-based pages that present conditional Yes/No options, and from concurrent programs or PL/SQL routines that must convert lookup codes to meanings for output. Custom code may call the function when it needs to display the same Yes/No text that standard Payables screens use, but doing so constitutes use of an unsupported internal API. Because the package is AUTHID CURRENT_USER, any custom caller must have the necessary privileges on FND_LOOKUPS. The package has remained stable since its 2002 header revision, so it is safe to assume identical behaviour across 12.1.1 and 12.2.2.