Results for “ak_category_usages”

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

Overview

AK_CATEGORY_USAGES is an Oracle E-Business Suite table owned by the AK (Common Modules-AK) schema. Its documented purpose is to define the relationship between an attachment region item and the categories assigned to it. In practical terms, the table records which attachment categories are enabled for a given attribute (region item) within a region, allowing Oracle EBS to control how attachments are classified, displayed, and validated when users interact with attachment regions on a form. This makes the table a configuration and metadata object rather than a transactional one: it governs the behavior of the Attachments infrastructure that underlies many EBS forms.

Because AK objects are shared across products, AK_CATEGORY_USAGES is referenced wherever attachment categories are configured, including self-service and Forms-based attachment regions. The table is marked VALID and contains 14 documented columns in the ETRM 12.2.2 schema snapshot. Based on its foreign key structure, the heuristic Data Vault classification is satellite-leaning: the table is dependent on the region item defined in AK_REGION_ITEMS and carries descriptive attributes about category usage rather than acting as an independent hub or a pure associative link. This classification is offered as a modeling suggestion, not an Oracle declaration.

Key Information Stored

The table's business identity is captured by the primary key AK_CATEGORY_USAGES_PK, which is composed of REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, and CATEGORY_NAME. A unique index, AK_CATEGORY_USAGES_U1, extends this same set with ZD_EDITION_NAME, reflecting the editioning column used in the 12.2.2 Online Patching model. Notable columns include:

• REGION_CODE — identifies the attachment region that owns the usage definition.
• REGION_APPLICATION_ID — the application context for the region, paired with REGION_CODE to resolve the region.
• ATTRIBUTE_CODE — identifies the specific region item (attribute) to which the category applies.
• ATTRIBUTE_APPLICATION_ID — the application context for the attribute.
• CATEGORY_NAME — the attachment category name associated with the region item.
• CATEGORY_ID — the internal identifier for the category, distinct from the name.
• APPLICATION_ID — the application identifier for the usage record.
• SHOW_ALL — a flag indicating whether all categories are displayed for the region item.
• ZD_EDITION_NAME — the editioning column supporting Online Patching in 12.2.x.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO audit columns tracking record creation and modification.

The primary key is effectively the surrogate business key here, since the documented columns do not include a single synthetic ID column; the composite key and the unique index serve as the business-key candidates.

Common Use Cases and Queries

Typical uses include auditing which categories are enabled for a given attachment region item, troubleshooting why a category does or does not appear on a form, and reporting on attachment configuration across applications. A representative query joins the table to its parent region item:

• List usages for a region: SELECT REGION_CODE, ATTRIBUTE_CODE, CATEGORY_NAME, SHOW_ALL FROM AK.AK_CATEGORY_USAGES WHERE REGION_CODE = :region_code AND REGION_APPLICATION_ID = :app_id;
• Resolve category identity: join CATEGORY_ID or CATEGORY_NAME to the attachment category definition to report the displayed category.
• Configuration audit: SELECT * FROM AK.AK_CATEGORY_USAGES WHERE SHOW_ALL = 'Y'; to find region items configured to show all categories.
• Change tracking: filter on LAST_UPDATE_DATE to identify recently modified category usages.

Related Objects

The most significant related object is the parent table that this table references:

• AK_REGION_ITEMS — joined on REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID via the documented foreign key. This is the primary dependency.
• AK_CATEGORY_USAGES_PK — the primary key constraint enforcing uniqueness.
• AK_CATEGORY_USAGES_U1 — the unique index that includes ZD_EDITION_NAME.

Additional dependent objects include the AK attachment configuration views and the category definition used by CATEGORY_ID and CATEGORY_NAME. Administrators should treat AK_REGION_ITEMS as the authoritative parent when tracing attachment category behavior.