Results for “ak_excluded_items”

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

Overview

AK_EXCLUDED_ITEMS is a table in the AK schema (Common Modules–AK product) of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to hold the list of secured attributes that should be hidden from a user based on their responsibility id. In practice, it is the exclusion or "deny" side of the AK attribute-security framework: where AK attribute assignments grant visibility or editability, AK_EXCLUDED_ITEMS removes specific attributes from view for users operating under a given responsibility. The table therefore participates directly in runtime security filtering performed by the AK attribute layer that underpins many descriptive flexfield and setup screens.

From the mined foreign-key structure, the heuristic Data Vault classification for this object is a link — it resolves the many-to-many relationship between responsibilities and secured attributes, rather than storing descriptive history on its own. This is a modeling suggestion only; the physical table is a standard EBS intersection table with audit columns.

Key Information Stored

The primary key, AK_EXCLUDED_ITEMS_PK, is composed of RESPONSIBILITY_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. A second documented unique index, AK_EXCLUDED_ITEMS_U1, extends the business key with RESP_APPLICATION_ID and ZD_EDITION_NAME, reflecting the multi-application and editioning-aware nature of the AK data model.

• RESPONSIBILITY_ID — identifies the responsibility for which an attribute is excluded; joins to FND_RESPONSIBILITY.
• RESP_APPLICATION_ID — the application owning the responsibility, completing the responsibility identity in the U1 key.
• ATTRIBUTE_CODE — the secured attribute being hidden; joins to AK_ATTRIBUTES.
• ATTRIBUTE_APPLICATION_ID — the application that owns the attribute, disambiguating attribute codes across products.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns identifying who created and last maintained each exclusion row.
• ZD_EDITION_NAME — the editioning column introduced in 12.2 online patching, used to scope rows to the active edition.

There is no documented surrogate key column; the intersection is identified by its composite business key.

Common Use Cases and Queries

Typical scenarios include auditing which attributes are hidden from a responsibility, diagnosing why a field is missing from a form for a particular user, and comparing exclusions between responsibilities. A representative query joins the table to the responsibility and attribute definitions:

SELECT e.responsibility_id, r.responsibility_name, e.attribute_code, e.attribute_application_id
FROM ak.ak_excluded_items e, fnd_responsibility r, ak.ak_attributes a
WHERE e.responsibility_id = r.responsibility_id
AND e.attribute_code = a.attribute_code
AND e.attribute_application_id = a.attribute_application_id;

Reporting use cases include producing a matrix of responsibility versus excluded attribute for security reviews, and verifying that no unintended exclusions exist after a responsibility is cloned or a patch is applied. Administrators also query the table when troubleshooting attribute-level access complaints.

Related Objects

• FND_RESPONSIBILITY — referenced through RESPONSIBILITY_ID and the ATTRIBUTE_APPLICATION_ID relationship; supplies the responsibility definition and name.
• AK_ATTRIBUTES — referenced through ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID; holds the secured attribute definitions.
• AK_ATTRIBUTE_ASSIGNMENTS — the complementary grant-side assignment table, examined alongside exclusions when resolving effective attribute security.
• AK_REGIONS / AK_REGION_ITEMS — define the regions and items to which secured attributes belong, useful for contextual reporting.
• FND_APPLICATION — resolves application names for RESP_APPLICATION_ID and ATTRIBUTE_APPLICATION_ID.
• FND_USER — links users to responsibilities when tracing why a specific user sees a hidden attribute.

Direct DML against AK_EXCLUDED_ITEMS is not recommended; changes should be made through supported AK attribute security setup, as the AK layer caches attribute metadata and unsynchronized manual inserts can produce inconsistent runtime behavior.