Results for “ak_web_user_sec_attr_values”

50+ results




Overview
Explore in AI Chat

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

Overview

The AK.AK_WEB_USER_SEC_ATTR_VALUES table is a repository of web user security attribute values within the Oracle E-Business Suite Common Modules-AK product. Its purpose is to store the resolved values of security attributes that are assigned to individual web users, thereby driving attribute-based access control and personalization behavior across the EBS application stack. Attribute definitions themselves are not maintained here; instead, this table records the specific value a given user holds for a given attribute, forming the operational side of the security model defined in the AK attribute framework.

From a dimensional modeling perspective, and consistent with the heuristic Data Vault classification supplied in the metadata, this object is satellite-leaning. Its row identifier is composite, combining a user identifier, an attribute identifier, and the specific value payload (character, date, or numeric). Because the table records descriptive state values attached to an actor (the web user) and references a definition table, it behaves as a satellite associated with the user hub and the attribute definition. This classification is a modeling suggestion rather than a documented architectural declaration.

Key Information Stored

The documented physical schema contains eleven columns. The most operationally significant are:

The primary key is documented as AK_WEB_USER_SEC_ATTR_VALUES_PK, spanning WEB_USER_ID, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, VARCHAR2_VALUE, DATE_VALUE, NUMBER_VALUE. A unique index, AK_WEB_USER_SEC_ATTR_VALUES_U1, mirrors the same six columns and represents the business-key candidate. Notably, the value columns participate in the key, so surrogate identifiers are not used; the natural identity of a row is the tuple of user, attribute, and value. The three value columns are mutually exclusive in practice — a given attribute populates the one column matching its declared data type.

Common Use Cases and Queries

Typical scenarios include auditing which attribute values are assigned to a web user, troubleshooting access decisions, and extracting security attribute data for reporting or migration. A representative query retrieving all attributes for a single user is:

  • SELECT attribute_code, attribute_application_id, varchar2_value, date_value, number_value FROM ak.ak_web_user_sec_attr_values WHERE web_user_id = :p_user_id;
  • Joining to the definition table to resolve attribute metadata: SELECT v.web_user_id, a.attribute_code, v.varchar2_value FROM ak.ak_web_user_sec_attr_values v, ak.ak_attributes a WHERE v.attribute_code = a.attribute_code AND v.attribute_application_id = a.attribute_application_id;
  • Filtering by a specific attribute code to find all users holding a value for it.
  • Validating value integrity across the three typed value columns when auditing data quality.

Related Objects

  • AK.AK_ATTRIBUTES — the FK-referenced definition table; joined on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
  • AK.AK_WEB_USER_SEC_ATTR_VALUES_PK — primary key constraint enforcing row uniqueness on the composite key.
  • AK.AK_WEB_USER_SEC_ATTR_VALUES_U1 — unique index underpinning business-key access.
  • Related AK web user and security framework tables that reference WEB_USER_ID for user context.
  • AK attribute assignment and personalization components that consume these values at runtime.