Search Results icx_parameters_pk

Overview

ICX_PARAMETERS is a setup information table owned by the ICX schema, which supports Oracle iProcurement and the broader Oracle E-Business Suite self-service web layer. In Oracle EBS 12.1.1 and 12.2.2, the table functions as a repository for configuration parameters that govern how the ICX-based application framework behaves at runtime, particularly in relation to URL resolution, session handling, and browser cookie management. The table carries a status of VALID and is documented with 13 physical columns in the ETRM 12.2.2 schema.

The heuristic Data Vault classification mined from the foreign-key structure identifies ICX_PARAMETERS as standalone. In data-vault modeling terms, this suggests the table is best treated as an independent reference or configuration structure rather than as a link table joining multiple business entities or as a satellite dependent on a parent hub. Its single-row or low-cardinality nature means it typically does not participate in complex relational hierarchies, and no dependent foreign-key relationships are documented for it.

Key Information Stored

The documented primary key is ICX_PARAMETERS_PK, defined on the HOME_URL column. This is notable: rather than using a synthetic surrogate sequence, the table employs HOME_URL as its business-key primary key. HOME_URL therefore serves as both the identifier and a functional configuration value, holding the base URL used by the ICX framework to resolve application home pages and generate navigation links.

The most significant columns among the 13 documented are:

• HOME_URL — the primary key and the base home-page URL for the ICX application context.
• QUERY_SET — identifies the query set used for default data retrieval behavior.
• MAX_ROWS — controls the maximum number of rows returned by ICX list-of-values and query pages, a key guard against oversized result sets.
• WEBMASTER_EMAIL — the contact address displayed for administrative or error-related correspondence.
• SESSION_COOKIE_NAME — the name assigned to the session cookie issued by the ICX mid-tier.
• SESSION_COOKIE_DOMAIN — the domain scope within which the session cookie is valid.
• SESSION_COOKIE — a stored value or flag relating to session cookie handling.
• WINDOW_COOKIE_NAME — the cookie name used for window or multi-window state tracking.

The table also carries the standard EBS audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These support WHO-column auditing but are not business keys.

Common Use Cases and Queries

Typical usage centers on diagnosing iProcurement configuration and web-tier behavior. A DBA or functional consultant queries the table to confirm the home URL, cookie naming, and row-limit settings when users report navigation or session issues.

• Retrieving the active configuration: SELECT * FROM icx.icx_parameters;
• Confirming the home URL and session cookie name: SELECT home_url, session_cookie_name, session_cookie_domain FROM icx.icx_parameters;
• Auditing recent changes: SELECT home_url, last_updated_by, last_update_date FROM icx.icx_parameters ORDER BY last_update_date DESC;
• Reporting on row-limit governance: SELECT home_url, max_rows, query_set FROM icx.icx_parameters;

Because the table is a low-volume setup repository, reporting is generally limited to configuration verification rather than transactional analysis.

Related Objects

The documented metadata records no outbound foreign keys, consistent with the standalone classification. Related objects are therefore functional rather than referential:

• ICX_PARAMETERS_PK — the primary-key constraint on HOME_URL.
• ICX schema tables — companion ICX configuration and session objects that share the same application context.
• FND profile options — which frequently mirror or override ICX parameter settings.
• iProcurement web pages — which consume HOME_URL and cookie settings at runtime.
• Oracle iProcurement setup forms — the UI layer through which these values are maintained.

No views or APIs are documented as directly referencing this table in the provided metadata; integration is primarily through the ICX application code path.