Results for “web_user_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ICX_USER_PROFILES is an Oracle E-Business Suite table owned by the ICX schema, which is associated with Oracle iProcurement. The ETRM metadata classifies this object with a status of VALID, but its product description is explicitly documented as Obsolete. This dual signal is significant: the physical object continues to exist in the 12.1.1 and 12.2.2 data dictionary and remains structurally intact, yet Oracle no longer designates it as an active functional component of the iProcurement feature set. In practice, ICX_USER_PROFILES is best understood as a legacy per-user configuration table that stored requisition-related defaults and behavioral toggles for individual web users of iProcurement.

The table is keyed by WEB_USER_ID, which also serves as the sole column of the primary key constraint ICX_USER_PROFILES_PK. The Data Vault classification supplied in the metadata is standalone. Phrased as a modeling suggestion, this indicates that the table behaves neither as a hub with a strong business-key identity nor as a dependent satellite tied to a parent business entity; it is an isolated user-level attribute store. The 10 documented columns include four WHO-style audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) plus LAST_UPDATE_LOGIN, leaving five functional attributes that carry the actual business payload.

Key Information Stored

The columns below represent the most consequential attributes documented in the ETRM 12.2.2 physical schema. The surrogate/business key distinction is unambiguous here: WEB_USER_ID is both the primary key column of ICX_USER_PROFILES_PK and the natural join key to the FND user model, making it the single business-key candidate on the table.

• WEB_USER_ID — Primary key (ICX_USER_PROFILES_PK) and the identifying user reference; joins to the FND_USER user model.
• REQ_DEFAULT_TEMPLATE — Stores the default requisition template applied when the user creates a requisition.
• REQ_OVERRIDE_REQUESTOR_CODE — Controls whether the requestor code may be overridden during requisition entry.
• REQ_OVERRIDE_LOCATION_FLAG — Controls whether the delivery location may be overridden on the requisition.
• DAYS_NEEDED_BY — Default lead time in days used to derive the "need by" date for requisitions.
• CREATION_DATE / CREATED_BY — Audit columns recording row creation context.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Audit columns recording the most recent modification and session context.

Common Use Cases and Queries

Because the table is documented as obsolete, primary use cases are diagnostic, migration-related, or audit-oriented rather than transactional. Typical scenarios include confirming whether a user retains legacy requisition defaults, reconciling user-level configuration before or after an upgrade, and verifying that no custom code still depends on the table.

• Profile lookup for a specific user:
  SELECT web_user_id, req_default_template, req_override_requestor_code, req_override_location_flag, days_needed_by FROM icx.icx_user_profiles WHERE web_user_id = :p_user_id;
• Orphan and coverage analysis:
  SELECT p.web_user_id FROM icx.icx_user_profiles p LEFT JOIN fnd_user u ON u.user_id = p.web_user_id WHERE u.user_id IS NULL;
• Staleness reporting on the audit columns to identify abandoned rows prior to deprecation.
• Impact assessment for AK_CUSTOMIZATIONS rows joined on WEB_USER_ID.

Related Objects

The FK metadata identifies a single documented referencing object, and the primary key implies the natural relationship to the FND user model.

• AK_CUSTOMIZATIONS — References ICX_USER_PROFILES via WEB_USER_ID; a foreign key from AK_CUSTOMIZATIONS.WEB_USER_ID to this table is documented.
• FND_USER — The natural parent of WEB_USER_ID; the standard join target for user-level attribute resolution.
• ICX_USER_PROFILES_PK — The primary key constraint enabling unique row access by WEB_USER_ID.

Given the obsolete designation, dependency review should precede any archival or cleanup activity.