Results for “attribute_access_level”

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

Overview

JTF_RS_TABLE_ATTRIBUTES_B is a base table in the JTF (CRM Foundation) product schema within Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. The table stores general information about table attributes that can be modified by users, effectively acting as a metadata registry that describes which columns of resource-related tables may be exposed for end-user maintenance. This design supports the extensibility features of the CRM Foundation, allowing administrators and application logic to control attribute-level access without altering the underlying schema. In the documented 12.2.2 physical model the table contains 27 columns and carries the primary key constraint JTF_RS_TABLE_ATTRIBUTES_B_PK on ATTRIBUTE_ID. A second unique index, JTF_RS_TABLE_ATTRIBUTES_B_U1, is defined over (ATTRIBUTE_ID, ZD_EDITION_NAME). From a heuristic Data Vault modeling perspective, the table is classified as standalone, indicating it behaves primarily as a reference or hub-style entity rather than as a dependent link or satellite.

Key Information Stored

The central identifier is ATTRIBUTE_ID, the surrogate primary key that uniquely identifies each attribute registration record and serves as the target of the documented primary key constraint. The business-meaningful name is carried in ATTRIBUTE_NAME, which holds the descriptive identifier of the modifiable attribute as presented to users or consumed by the application layer. ATTRIBUTE_ACCESS_LEVEL is the principal control column, encoding the access classification that governs whether and how the attribute may be modified. ATTRIBUTE_CATEGORY provides a grouping mechanism that contextualizes the attribute within a broader descriptive framework.

The table follows the standard EBS extensibility pattern through the fifteen generic columns ATTRIBUTE1 through ATTRIBUTE15, allowing customers to store additional descriptive or controlling values without a schema change. SECURITY_GROUP_ID is a foreign key to FND_SECURITY_GROUPS, linking each row to a security group for multi-tenant or organization-level data separation. ZD_EDITION_NAME participates in the unique index and reflects the edition-based redefinition strategy used in Release 12.2. Audit and concurrency columns complete the record: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, the latter used for optimistic locking in the OAF framework.

Common Use Cases and Queries

Typical usage involves inventorying which attributes are modifiable and at what access level, supporting administration and personalization of resource-related pages. A representative query lists attributes with their access level for review:

• SELECT attribute_id, attribute_name, attribute_access_level, attribute_category FROM jtf.jtf_rs_table_attributes_b ORDER BY attribute_name;
• Filtering by access level to audit exposure: SELECT attribute_name FROM jtf.jtf_rs_table_attributes_b WHERE attribute_access_level = :p_level;
• Joining to the security group to resolve tenancy: SELECT a.attribute_name, g.security_group_id FROM jtf.jtf_rs_table_attributes_b a, fnd_security_groups g WHERE a.security_group_id = g.security_group_id;
• Extensibility reporting using the generic columns, for example listing rows where ATTRIBUTE1 is populated, to trace customer-defined metadata.

These patterns are useful for security reviews, migration validation, and confirming that attribute registrations resolve correctly after an upgrade from 12.1.1 to 12.2.2, where the ZD_EDITION_NAME column introduced by editioning must be accounted for in queries and unique-key validations.

Related Objects

The documented foreign key relationship ties this table to FND_SECURITY_GROUPS via SECURITY_GROUP_ID, making that security table its principal parent. The primary key JTF_RS_TABLE_ATTRIBUTES_B_PK on ATTRIBUTE_ID is referenced by dependent JTF resource metadata and configuration tables that consume attribute identifiers. Application programming interfaces and views in the JTF schema, including resource management and setup pages, read this registry to determine modifiable attributes, and the OAF-based maintenance flows rely on OBJECT_VERSION_NUMBER for concurrency control. Reporting objects joining through ATTRIBUTE_ID and SECURITY_GROUP_ID provide the practical linkage between this registry, the security model, and the resource tables it governs.