Search Results ies_lookups_pvt

Overview

IES_LOOKUPS_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It forms part of the Oracle iSupplier Portal (IES) application family and provides the low-level implementation routines that manage lookup-code data used throughout the supplier-facing self-service modules. As indicated by the PVT suffix, the package is classified as private within the Oracle ETRM taxonomy and is not intended to be called directly by customer extensions, forms, or concurrent programs. It exposes two documented program units, INSERT_LOOKUP and UPDATE_LOOKUP, which together encapsulate the maintainable operations for adding and modifying lookup entries held in the application's lookup repository.

The package resides in a VALID state in both Oracle EBS 12.1.1 and 12.2.2 and is documented in ETRM as depending only on SYS and the STANDARD package at the schema level. This narrow dependency footprint is characteristic of a lightweight utility package that performs straightforward DML rather than orchestrating a broad business transaction.

Key Procedures and Functions

• INSERT_LOOKUP — Creates a new lookup record within the supplier portal lookup tables. It is the entry point used when a new lookup code or lookup value must be registered so that it becomes available for validation and display in iSupplier Portal and related EBS pages.
• UPDATE_LOOKUP — Modifies an existing lookup record. It is invoked when the description, enabled flag, or other maintained attributes of a lookup entry require change without creating a new row.

Both routines are procedural building blocks only; they do not constitute a public API. Their complete parameter signatures are intentionally not reproduced here, and the ETRM documentation does not publish them. Callers should treat these units as internal implementation detail of the IES layer.

Tables Accessed

The ETRM extraction for this object lists no tables accessed through APPS synonyms. The package's only recorded dependencies are SYS and STANDARD. In practice, lookup-maintenance routines of this type operate against the EBS lookup tables — typically FND_LOOKUP_TYPES and FND_LOOKUP_VALUES — or against an IES-specific staging or extension table, but the metadata provided does not confirm any specific base table. Any statement about the precise physical tables should therefore be verified against the package body in the target instance rather than assumed.

Usage Notes

IES_LOOKUPS_PVT is referenced by zero other packages in the documented dependency graph and, in turn, lists no inbound references beyond itself, indicating that it is not a widely shared utility. It is most plausibly invoked from within the iSupplier Portal Java or PL/SQL layer — for example, from a page or controller responsible for presenting and administering supplier-visible lookup lists — or from other private IES packages that have not been separately catalogued. Because the ETRM classification is PVT, Oracle support and documentation do not treat these procedures as a supported integration surface.

For Oracle EBS 12.1.1 and 12.2.2 the practical guidance is consistent: custom code should not call INSERT_LOOKUP or UPDATE_LOOKUP directly. Direct invocation bypasses validation, auditing, and cache-refresh logic that the IES layer or the standard FND lookup APIs would otherwise enforce. Where lookup creation or amendment is genuinely required, the supported approach is to use the standard Oracle Application Object Library lookup maintenance forms or the corresponding FND public APIs. If inspection of this package is necessary for troubleshooting, the package body should be reviewed in the target instance and the actual base tables confirmed from the source, since the published ETRM metadata does not enumerate them.