Results for “region_application_id”

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

Overview

AK_CATEGORY_USAGES_V is a seeded, read-only database view owned by the APPS schema and shipped as part of the AK (Common Modules – Application Framework) product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose the contents of the AK_CATEGORY_USAGES table for framework use, joining it to region-item metadata and to document categories so that category assignments can be reported with human-readable descriptions rather than bare identifiers. Because it belongs to the AK framework layer rather than to a functional module, it is not end-user-facing; it is consumed internally by the Application Framework and by diagnostic or integration queries that need to resolve how categories are attached to region attributes.

The user search term fnd_document_categories_vl is significant: that object appears nowhere in the view text under its own name, but it is one of the three referenced base objects and is aliased as FDC. This makes AK_CATEGORY_USAGES_V a convenient bridge for anyone inspecting category usage, since it already performs the join to FND_DOCUMENT_CATEGORIES_VL that would otherwise have to be written by hand.

Underlying Base Objects

The view is defined over exactly three documented objects:

• AK_CATEGORY_USAGES (SYNONYM, aliased ACU) — the driving table; supplies region, attribute, category, user name and the SHOW_ALL flag.
• AK_REGION_ITEMS (SYNONYM, aliased AR) — supplies ITEM_NAME, the display name of the region item (attribute).
• FND_DOCUMENT_CATEGORIES_VL (VIEW, aliased FDC) — supplies CATEGORY_ID, USER_NAME and APPLICATION_ID for the category.

The join condition is fully equijoined on four key pairs between ACU and AR: region application, region code, attribute application and attribute code. The category is then matched with ACU.CATEGORY_ID = FDC.CATEGORY_ID. FND_DOCUMENT_CATEGORIES_VL is itself a _VL ("view with language") object, so this outer view inherits its language-enabled behaviour, notably the translated USER_NAME returned according to the session's language setting.

Key Columns

• REGION_CODE / REGION_APPLICATION_ID — identify the AK region in which the category usage is defined.
• ATTRIBUTE_CODE / ATTRIBUTE_APPLICATION_ID — identify the specific region item (attribute) using the category.
• ITEM_NAME — the descriptive name of that region item, resolved from AK_REGION_ITEMS.
• CATEGORY_ID — the numeric key of the document category.
• NAME (documented column listing; sourced from FDC.USER_NAME) — the user-facing, language-sensitive category name.
• USER_NAME — the category user name as exposed by FND_DOCUMENT_CATEGORIES_VL.
• APPLICATION_ID — the owning application of the category, useful for product-based filtering.
• SHOW_ALL — framework indicator controlling whether all category values are surfaced for the region item.

Common Use Cases and Queries

Typical uses include auditing which categories have been attached to which region attributes, locating configurations where a specific document category drives framework behaviour, and resolving category IDs to readable names during troubleshooting of AK personalisations or attachments.

List all category usages with resolved names:

• SELECT region_code, attribute_code, item_name, name, show_all FROM apps.ak_category_usages_v ORDER BY region_code, attribute_code;

Find every region item configured for a given category:

• SELECT region_code, attribute_code, item_name FROM apps.ak_category_usages_v WHERE category_id = :p_category_id;

Restrict to a single owning application:

• SELECT region_code, attribute_code, name FROM apps.ak_category_usages_v WHERE application_id = :p_application_id;

As the underlying data is maintained through the AK framework rather than through this view, all statements above should be treated as read-only; direct DML against the view is not supported.