Search Results ak_resp_security_attr_values_u

Overview

The AK.AK_RESP_SECURITY_ATTR_VALUES table is a core data object in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 application foundation layer, owned by the AK schema. It stores securing attribute values at the responsibility level, forming the persistence layer that drives the Oracle EBS function security and attribute-based security model. Whereas standard responsibility-based security controls which menus, functions, and data a user may access, this table carries the specific attribute values — string, date, or numeric — against which runtime security decisions are evaluated for a given responsibility.

The object is classified as VALID and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its FND Design Data identifier confirms it as a registered, designed application object rather than an ad-hoc table. From a Data Vault modeling perspective, the heuristic classification for this object is standalone; it is not a hub, link, or satellite, since it references no other database object through foreign keys. It therefore behaves as an independent reference/value store keyed by responsibility and attribute identity rather than as a relationship-joining entity.

Key Information Stored

The table contains seven documented columns. The composite primary key, AK_RESP_SEC_ATTR_VAL_PK, is composed of RESPONSIBILITY_ID, RESP_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. This is the true business key: it uniquely identifies the securing attribute defined for a particular responsibility within a particular application.

• RESPONSIBILITY_ID (NUMBER, 15) — the FND responsibility identifier to which the securing attribute value applies.
• RESP_APPLICATION_ID (NUMBER, 15) — the FND application to which the owning responsibility belongs.
• ATTRIBUTE_CODE (VARCHAR2, 30) — the AK attribute code that names the securing attribute being valued.
• ATTRIBUTE_APPLICATION_ID (NUMBER, 15) — the FND application to which the attribute definition belongs.
• VARCHAR2_VALUE (VARCHAR2, 240) — the character value of the securing attribute for the current attribute and responsibility pairing.
• DATE_VALUE (DATE) — the date value of the securing attribute for the current attribute and responsibility.
• NUMBER_VALUE (NUMBER, 15) — the numeric value of the securing attribute for the current attribute and responsibility.

Two indexes support access. AK_RESP_SECURITY_ATTR_VALUES_U is a UNIQUE index in APPS_TS_TX_IDX over all four key columns plus VARCHAR2_VALUE, DATE_VALUE, and NUMBER_VALUE; it is the documented business-key candidate, effectively the full uniqueness guarantee across both identity and value. AK_RESP_SECURITY_ATTR_VALUES_N is a NONUNIQUE index over ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, and RESPONSIBILITY_ID, supporting attribute-centric lookups.

Common Use Cases and Queries

Typical use cases include diagnosing security-related behavior for a responsibility, auditing which attribute values are assigned, and reporting on attribute-based data restriction across applications. A common query retrieves all attribute values for a given responsibility:

SELECT RESPONSIBILITY_ID, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID,
       VARCHAR2_VALUE, DATE_VALUE, NUMBER_VALUE
FROM   AK.AK_RESP_SECURITY_ATTR_VALUES
WHERE  RESPONSIBILITY_ID = :resp_id
AND    RESP_APPLICATION_ID = :resp_app_id;

Alternatively, the nonunique index is leveraged when searching by attribute across all responsibilities:

SELECT RESPONSIBILITY_ID, VARCHAR2_VALUE, DATE_VALUE, NUMBER_VALUE
FROM   AK.AK_RESP_SECURITY_ATTR_VALUES
WHERE  ATTRIBUTE_CODE = :attr_code
AND    ATTRIBUTE_APPLICATION_ID = :attr_app_id;

Because values may be held in any of the three typed columns, reporting logic must coalesce VARCHAR2_VALUE, DATE_VALUE, and NUMBER_VALUE depending on the attribute's declared type.

Related Objects

The metadata states that AK.AK_RESP_SECURITY_ATTR_VALUES references no database object, and it is referenced only by the Oracle-internal constraint backing object AK.AK_RESP_SECURITY_ATTR_VALUES#. Based on EBS schema conventions, the objects most significant to this table are:

• FND_RESPONSIBILITY — joined via RESPONSIBILITY_ID and RESP_APPLICATION_ID to resolve responsibility and application names.
• FND_APPLICATION — joined via RESP_APPLICATION_ID and ATTRIBUTE_APPLICATION_ID to resolve application identity.
• AK_ATTRIBUTES — provides the attribute definitions referenced by ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• FND_RESPONSIBILITY_VL — the translatable view of responsibilities used in reporting joins.
• AK_RESP_SECURITY_ATTRS — the definition-side counterpart recording which attributes are secured for a responsibility.
• FND_USER_RESP_GROUPS — links users to responsibilities, enabling end-to-end security auditing.
• FND_COMPILED_MENU_FUNCTIONS — function security compilation output often examined alongside attribute values.

Collectively these objects allow administrators and developers to trace from a user, through assigned responsibilities, to the securing attribute values evaluated at runtime.