Search Results update_lookup

Overview

IES_LOOKUPS_PVT is a private (PVT-classified) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Internet Expenses (IES) product family and provides the low-level data manipulation logic supporting the maintenance of lookup definitions used by Oracle Internet Expenses. The package encapsulates the two core write operations required to manage lookup records: inserting a new lookup and updating an existing one. Because the API is classified as PVT rather than PUBLIC, it is intended to be called internally by other IES components rather than directly by customer-written code, which is consistent with its role as a supporting implementation layer beneath the public lookup maintenance APIs.

The package follows the standard Oracle EBS API construction pattern, including the conventional API version, initialization, commit, and validation-level parameters, the standard savepoint at the start of each procedure, and consistent exception handling that rolls back to the savepoint and returns an error status with message text. This structure aligns it with the EBS API coding standards used throughout the applications schema.

Key Procedures and Functions

The documented package metadata lists two procedures:

• INSERT_LOOKUP — Creates a new record in the lookup repository. It generates a primary key from the ies_lookups_s sequence, assembles a dynamic INSERT statement, and executes it, returning the newly generated lookup identifier to the caller through an OUT parameter. The procedure accepts inputs covering the owning user, the description identifier, the parent lookup table identifier, the lookup name, and the active status flag.
• UPDATE_LOOKUP — Modifies an existing lookup record. It accepts the lookup identifier along with the lookup table identifier, the updating user, the lookup name, and the active status, and returns the lookup identifier through an OUT parameter to confirm the affected row.

Both procedures adhere to the shared signature convention: API version, initialization message list flag, commit flag, and validation level as leading parameters, followed by the standard x_return_status, x_msg_count, and x_msg_data OUT parameters and the procedure-specific business attributes. No parameter lists are reproduced here, in keeping with the documented API contract.

Tables Accessed

The package writes to the IES_LOOKUPS table, accessed through its APPS synonym. INSERT_LOOKUP populates the columns lookup_id, created_by, creation_date, dscript_id, lookup_table_id, lookup_name, and active_status. The primary key is sourced from the ies_lookups_s sequence rather than from a table-based key mechanism. UPDATE_LOOKUP modifies the descriptive and status attributes of an existing row identified by lookup_id. The lookup table identifier links each lookup entry to its parent lookup table definition, establishing the hierarchical relationship between lookup tables and their constituent values.

Usage Notes

As a private package, IES_LOOKUPS_PVT is not exposed as a supported public interface; the ETRM metadata records no other packages referencing it, indicating its callers reside within the IES lookup maintenance stack itself. Typical invocation occurs from Oracle Forms-based lookup maintenance screens or from higher-level public APIs that delegate persistence to this package. Callers are responsible for supplying a valid API version and for invoking the standard initialization and error-checking conventions before relying on x_return_status. Because the procedures issue their own savepoint and roll back to it on failure, they may be safely composed within a larger transaction. Custom development should avoid calling this package directly and should instead use the supported public lookup APIs, since the internal signature and behavior may change between releases.