Search Results pv_web_user_id

Overview

APPS.ICX_SETUP is a PL/SQL package body belonging to the Oracle iProcurement / Internet Procurement family of components in Oracle E-Business Suite. Its documented classification is OTHER, and it is not a public API in the conventional sense; it functions as an internal setup utility. The package renders and maintains the post-installation setup page that allows an administrator to capture and persist environment-wide configuration values into the ICX_PARAMETERS table. The header comment in the source ("Create a page for user to input post-install setup info / Store it in icx_parameters") confirms this purpose.

The package is relevant to searches for the identifier pv_web_user_id because that identifier appears as a local constant inside the GET_PARAMETERS procedure. It is declared as PV_WEB_USER_ID number := 10; and is used as a parameter value passed to icx_sec.getID to resolve the current web user identifier. It is a private, procedure-scoped constant and is not exposed as an API parameter, so it has no external signature significance.

Key Procedures and Functions

The package body documents two procedures:

• GET_PARAMETERS — Builds and displays the post-install setup page. The procedure first validates the user session through icx_sec.validateSession('ICX_SETUP'), resolves the language code and web user identifier via icx_sec.getID, and then queries the ICX_PARAMETERS row into local variables (query set, home URL, webmaster e-mail, maximum rows). It obtains the page title and field prompts from the Object Navigator through icx_util.getPrompts, using application identifier 601 and page code 'ICX_SETUP', and then generates the HTML output using HTP and HTF calls. Because it reads a single configuration row, it assumes exactly one row exists in ICX_PARAMETERS.
• UPDATE_PARAMETERS — Persists the values submitted from the setup page back into ICX_PARAMETERS. It is the write-side counterpart to GET_PARAMETERS and is invoked when the administrator saves changes on the setup screen.

No public package-level functions are documented; both members are procedures. Parameter lists are not reproduced here because they are not part of the documented metadata.

Tables Accessed

• ICX_PARAMETERS — The sole persistent configuration store. GET_PARAMETERS reads the query set, home URL, webmaster e-mail address, and maximum rows returned. UPDATE_PARAMETERS writes the modified values back to this table.
• HTF / HTP — The HTML generation packages used to emit the setup page markup; not data tables but documented dependencies of the package.
• OWA_UTIL — Used to retrieve CGI environment values, including the HTTP_USER_AGENT string, which is captured into a browser variable to support browser-specific rendering behaviour.

The package also depends on icx_sec (session validation and ID resolution) and icx_util (prompt retrieval), although these are PL/SQL dependencies rather than documented table references.

Usage Notes

ICX_SETUP is normally invoked indirectly rather than called from custom code. It is reached through the Oracle EBS setup page flow served by the Apache/mod_plsql stack: the GET_PARAMETERS procedure renders the setup form, and UPDATE_PARAMETERS is triggered by the save action on that form. The procedure includes a session check, so it cannot be run meaningfully from SQL*Plus without a valid iProcurement web session context.

The documented metadata records zero packages referencing ICX_SETUP, confirming that no shipped package calls it programmatically; it is driven by the setup page URL. Custom code should avoid direct invocation and instead interact with ICX_PARAMETERS through supported means, since the procedures assume a single configuration row and a live HTTP session.