Results for “date_value”

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

Overview

AK.AK_RESP_SECURITY_ATTR_VALUES is a foundational table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Common Modules architecture, owned by the AK schema. It stores responsibility-level security attribute values, providing the mechanism by which specific values of a securing attribute are granted or restricted for a given responsibility. Within EBS, this table underpins the flexible data-security model used by function security, data security, and the broader Applications Object Library, allowing administrators to scope a responsibility's access to specific attribute values such as ledger, operating unit, or inventory organization.

The primary key is defined by AK_RESP_SEC_ATTR_VAL_PK over the composite columns RESPONSIBILITY_ID, RESP_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. From a Data Vault modeling perspective, the supplied metadata classifies this object heuristically as a standalone construct. In practice it can be modeled as a satellite type record that captures attribute-value assignments keyed to a responsibility-and-attribute combination, though the physical schema contains no foreign-key relationships to other tables and is therefore treated as independent.

Key Information Stored

The table contains seven documented columns. The most significant are summarized below.

• RESPONSIBILITY_ID — Identifies the responsibility to which the security attribute value applies; part of the composite primary key.
• RESP_APPLICATION_ID — The application owning the responsibility; together with RESPONSIBILITY_ID it uniquely identifies the responsibility context (this is the column commonly matched to the resp_application_id search term).
• ATTRIBUTE_CODE — The code of the securing attribute being constrained or granted; part of the composite primary key.
• ATTRIBUTE_APPLICATION_ID — The application that owns the securing attribute; combined with ATTRIBUTE_CODE it identifies the attribute uniquely.
• VARCHAR2_VALUE — The alphanumeric value assigned to the attribute for the responsibility.
• DATE_VALUE — The date value assigned where the attribute is date-typed.
• NUMBER_VALUE — The numeric value assigned where the attribute is number-typed.

The surrogate identifier in this schema is the composite primary key AK_RESP_SEC_ATTR_VAL_PK. The metadata also documents a unique index, AK_RESP_SECURITY_ATTR_VALUES_U, spanning the same four key columns plus VARCHAR2_VALUE, DATE_VALUE, and NUMBER_VALUE, which serves as a business-key candidate enforcing uniqueness of the full attribute-value assignment. The value columns are polymorphic: only the column matching the attribute's datatype is populated for a given row.

Common Use Cases and Queries

Typical uses include auditing which values a responsibility is permitted to see, troubleshooting unexpected security restrictions, and reporting on data-security configurations. A common query retrieves all attribute values secured for a responsibility:

SELECT 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;

Administrators frequently join to FND_RESPONSIBILITY and FND_APPLICATION to translate identifiers into meaningful names when producing security matrices. Reporting scenarios include confirming that a responsibility has been assigned a required securing attribute value after cloning or migration, and reconciling responsibility-level security across environments.

Related Objects

Because the physical schema is standalone, relationships are logical rather than enforced by foreign keys. The most significant related objects and join columns are:

• FND_RESPONSIBILITY — joined on RESPONSIBILITY_ID and APPLICATION_ID to resolve the responsibility and its owning application.
• FND_APPLICATION — joined via RESP_APPLICATION_ID and ATTRIBUTE_APPLICATION_ID to resolve application names.
• AK_SECURING_ATTRIBUTES — provides attribute definitions matched on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• FND_FORM_FUNCTIONS and FND_MENUS — govern function-level access that often complements attribute-value security.
• FND_RESPONSIBILITY_VL — reporting view used alongside this table for responsibility lookups.

These objects are commonly referenced together when validating responsibility security configuration within the Oracle E-Business Suite.