Results for “ak_resp_security_attributes”

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

Overview

The AK_RESP_SECURITY_ATTRIBUTES table resides in the AK schema, which supports Oracle E-Business Suite's Common Modules-AK infrastructure for attribute-driven configuration and security. The table specifies which attribute values a given user responsibility is permitted to access. In practical terms, it acts as an authorization filter that binds a responsibility to a set of attribute codes, allowing the application to restrict the data visible to users operating under that responsibility. This mechanism is central to attribute-level security in Oracle EBS releases 12.1.1 and 12.2.2, where access must often be scoped more granularly than at the responsibility level alone.

The ETRM documentation classifies this object heuristically as a link in a Data Vault modeling sense. This designation is a modeling suggestion rather than a physical property: AK_RESP_SECURITY_ATTRIBUTES logically resolves the many-to-many relationship between responsibilities and attribute definitions, carrying no descriptive measures of its own.

Key Information Stored

The table is defined with ten documented columns. The most significant include:

• RESPONSIBILITY_ID — identifies the responsibility to which the attribute access rule applies.
• RESP_APPLICATION_ID — the application context of the responsibility, forming part of the composite unique key.
• ATTRIBUTE_CODE — the code of the attribute that the responsibility may access.
• ATTRIBUTE_APPLICATION_ID — the application that owns the referenced attribute, resolving the attribute definition.
• CREATED_BY / CREATION_DATE — standard who-columns recording row creation.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard audit columns capturing the last modification.
• ZD_EDITION_NAME — the editioning column introduced for edition-based redefinition support in the 12.2 online patching architecture.

The surrogate primary key is AK_RESP_SECURITY_ATTRIBUTES_PK, defined over (RESPONSIBILITY_ID, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID). The documented unique index AK_RESP_SECURITY_ATTRIBUTES_U1 spans (RESPONSIBILITY_ID, RESP_APPLICATION_ID, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, ZD_EDITION_NAME) and represents the business-key candidate, uniquely identifying an access rule within an edition.

Common Use Cases and Queries

Typical usage includes diagnosing why a user cannot see a particular attribute value, auditing which attributes a responsibility is authorized for, and comparing security grants across responsibilities or during upgrade validation.

To list attributes granted to a responsibility:

• SELECT attribute_code, attribute_application_id FROM ak.ak_resp_security_attributes WHERE responsibility_id = :resp_id;

To check whether a specific attribute is granted:

• SELECT 1 FROM ak.ak_resp_security_attributes WHERE responsibility_id = :resp_id AND attribute_code = :code AND attribute_application_id = :app_id;

To reconcile against the attribute definition and responsibility master data:

• SELECT r.responsibility_name, a.attribute_code FROM ak.ak_resp_security_attributes arsa JOIN fnd_responsibility r ON r.responsibility_id = arsa.responsibility_id JOIN ak.ak_attributes a ON a.attribute_code = arsa.attribute_code AND a.attribute_application_id = arsa.attribute_application_id;

Reporting frequently emphasizes audit columns to detect recent security changes, and analysts should filter on ZD_EDITION_NAME in 12.2.2 when analyzing active runtime editions.

Related Objects

The following objects are most significant to AK_RESP_SECURITY_ATTRIBUTES:

• FND_RESPONSIBILITY — the responsibility master. Joined on RESPONSIBILITY_ID (and related application context) to retrieve responsibility names and validate ownership.
• AK_ATTRIBUTES — the attribute definition table. Joined on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID to resolve attribute metadata.
• FND_RESPONSIBILITY_VL — the translated view of responsibilities, commonly used in reporting joins.
• AK_RESP_SECURITY_ATTRIBUTES_PK and AK_RESP_SECURITY_ATTRIBUTES_U1 — the primary and unique constraints governing row identity.
• FND_USER_RESP_GROUPS — links users to responsibilities, useful when tracing effective attribute access end-to-end.

Together these relationships place AK_RESP_SECURITY_ATTRIBUTES at the intersection of responsibility administration and attribute configuration within the AK framework.