Search Results x_server_id

Overview

IEO_SVR_VALUES_PVT is a private PL/SQL package in the APPS schema that manages the persistence layer for server parameter values used by Oracle EBS iSetup (Integrated Setup) and related configuration migration utilities. The table it manipulates, IEO_SVR_VALUES, stores individual value entries that belong to a server definition. Each value row is linked to a parameter through PARAM_ID and to a server through SERVER_ID, allowing the application to capture, version, and transport server-specific configuration values across environments.

The package follows the standard Oracle Application Object Library private API pattern: it exposes low-level insert, update, delete, and lock operations around a single base table, while the corresponding public package performs validation, required-column checks, and business-rule enforcement before delegating to this layer. The $Header comment (IEOSVRVB.pls 120.1, 2005/06/12) indicates the package is a long-standing, stable component of the iSetup infrastructure carried forward into EBS 12.1.1 and 12.2.2 without structural change.

Key Procedures and Functions

• INSERT_ROW — Inserts a new row into IEO_SVR_VALUES. Before the INSERT, each attribute is wrapped in a DECODE against FND_API.G_MISS_NUM or FND_API.G_MISS_CHAR so that the API's sentinel "missing" values are converted to NULL. This is the mechanism that allows the caller to distinguish "do not set this column" from "set it to null." After the insert, the procedure re-queries the row's ROWID into the x_rowid OUT parameter and raises NO_DATA_FOUND if the row cannot be located.
• DELETE_ROW — Removes the row identified by x_value_id from IEO_SVR_VALUES. If no row is deleted (SQL%NOTFOUND), the procedure raises NO_DATA_FOUND so the caller can distinguish a genuine failure from a silent no-op.
• UPDATE_ROW — Modifies an existing value row. As with INSERT_ROW, G_MISS sentinels are normally translated to NULL, permitting partial updates where only selected columns are changed. The full parameter signature is defined by the metadata but not reproduced here; it mirrors the insert columns plus the ROWID used to target the row.
• LOCK_ROW — Acquires a row-level lock on the target value record, typically by selecting the row with the FOR UPDATE clause or by invoking the standard FND_API locking convention. This guards against concurrent modification during multi-step update or delete sequences performed by the calling public API.

Tables Accessed

The package reads and writes a single documented table, IEO_SVR_VALUES, referenced through its APPS synonym. The table carries the surrogate primary key VALUE_ID, audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), an ordinal column VALUE_INDEX, a foreign key PARAM_ID to the parameter definition, a foreign key SERVER_ID to the owning server, and the actual configuration VALUE itself. Because all four procedures target this one table, the package is a clean, single-table CRUD layer with no cross-table dependencies.

Usage Notes

IEO_SVR_VALUES_PVT is classified as a PVT (private) API, meaning it is not intended for direct invocation by customers or external integrations. It is called exclusively by the corresponding public package in the iSetup server-configuration stack, which performs validation, applies WHO-column defaults, and enforces referential and business rules before delegating to these procedures. In practice, the public API is reached from iSetup forms and concurrent programs that create, modify, or delete server definitions and their associated parameter values during configuration migration between EBS instances.

Because the package is referenced by zero other packages per the ETRM metadata, its call graph is narrow and its surface area small. Custom code should never call IEO_SVR_VALUES_PVT directly; any requirement to manipulate server values programmatically should go through the supported public API to preserve validation, auditing, and G_MISS handling semantics. When troubleshooting "x_server_id" errors, note that a G_MISS_NUM passed as x_server_id is deliberately written as NULL, so a missing or unpropagated SERVER_ID usually originates in the caller rather than in this package.