Results for “ak_customizations_u2”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AK.AK_CUSTOMIZATIONS is a transactional table in the Application Object Library (AK) schema of Oracle E-Business Suite, documented as VALID and registered under FND Design Data as AK.AK_CUSTOMIZATIONS. Its purpose is to store customizations applied to regions at multiple levels of the EBS runtime hierarchy. Rather than duplicating or editing seeded region definitions, Oracle EBS records customization metadata in this table so that region behavior can be overridden or extended for a specific verticalization, localization, operating unit, site, responsibility, or individual web user, without altering the base product code.
The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, which is consistent with a table that is written to occasionally and read frequently during page rendering and personalization checks. Access to customization records is typically short and cached, since region rendering depends on resolving the effective customization level quickly. A heuristic Data Vault classification of this structure is standalone, meaning it does not behave as a classic hub or link with a distributed set of dependent satellites in this documentation; it functions as a self-contained configuration table whose business key identifies the region and customization scope.
Key Information Stored
The table's identity and scope columns define which customization exists, where it applies, and who it affects. The documented primary key AK_CUSTOMIZATIONS_PK is composed of CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, REGION_APPLICATION_ID, and REGION_CODE. A unique index, AK_CUSTOMIZATIONS_U2, covers REGION_CODE, REGION_APPLICATION_ID, CUSTOMIZATION_CODE, CUSTOMIZATION_APPLICATION_ID, and ZD_EDITION_NAME, making this the strongest business-key candidate and enforcing uniqueness in the Edition-aware 12.2 model.
- CUSTOMIZATION_APPLICATION_ID — application identifier for the application in which the customization is used.
- CUSTOMIZATION_CODE — code identifying the specific customization.
- REGION_APPLICATION_ID — application identifier for the region being customized.
- REGION_CODE — code identifying the region.
- CUSTOMIZATION_LEVEL_ID — numeric indicator of the level (verticalization, localization, org, site, responsibility, or user) at which the customization applies.
- VERTICALIZATION_ID — populated when the customization is a verticalization-level record.
- LOCALIZATION_CODE — populated when the customization is a localization-level record.
- ORG_ID — populated for an organization-level customization.
- SITE_ID — populated for a site-level customization.
- RESPONSIBILITY_ID — populated for a responsibility-level customization.
- WEB_USER_ID — populated for a user-level customization; this column is documented as referencing ICX_USER_PROFILES.
- DEFAULT_CUSTOMIZATION_FLAG — indicates the default customization for a user-level record.
- REFERENCE_PATH — reference path for a specific portlet customization.
- FUNCTION_NAME and DEVELOPER_MODE — additional documented columns supporting functional scoping and developer-mode behavior.
- START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating columns, along with the WHO columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
Common Use Cases and Queries
Administrators and developers query AK_CUSTOMIZATIONS to determine which customization is effective for a given region and runtime context. A typical pattern filters by region identity and then narrows by level-specific columns:
- Resolving user-level customizations:
SELECT customization_code, default_customization_flag, reference_path FROM ak.ak_customizations WHERE region_code = :p_region AND region_application_id = :p_app AND web_user_id = :p_user AND sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate + 1); - Auditing responsibility-level overrides: filter on RESPONSIBILITY_ID and CUSTOMIZATION_LEVEL_ID.
- Reporting reference-path assignments for portlets using REFERENCE_PATH and FUNCTION_NAME.
- Detecting conflicting or duplicate customizations by joining the business-key columns against AK_CUSTOMIZATIONS_U2 expectations.
- Reviewing maintenance history through LAST_UPDATED_BY and LAST_UPDATE_DATE for change-tracking reports.
Because the table mixes level columns in a single structure, prudent queries should always constrain on the appropriate level column (for example, WEB_USER_ID for user-level data) rather than assuming all rows are relevant. The DEFAULT_CUSTOMIZATION_FLAG is most meaningful in user-level scenarios.
Related Objects
The documented foreign key from WEB_USER_ID to ICX_USER_PROFILES links customization records to the user profile repository, allowing user-level lookups to be resolved against the EBS framework's user metadata. Beyond this documented relationship, AK_CUSTOMIZATIONS is commonly associated with region-definition and personalization framework objects within the AK schema.
- ICX_USER_PROFILES — joined on AK_CUSTOMIZATIONS.WEB_USER_ID = ICX_USER_PROFILES.WEB_USER_ID (documented FK).
- Region metadata definitions in the AK schema — matched via REGION_CODE and REGION_APPLICATION_ID.
- FND Application and Responsibility definitions — used to validate CUSTOMIZATION_APPLICATION_ID and RESPONSIBILITY_ID.
- ORG and Site-related tables — referenced indirectly when ORG_ID and SITE_ID are populated.
- Verticalization and localization definitions — matched via VERTICALIZATION_ID and LOCALIZATION_CODE.
These relationships make AK_CUSTOMIZATIONS a central resolution point for layered region personalization in Oracle EBS 12.1.1 and 12.2.2.
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
TABLE: AK.AK_CUSTOMIZATIONS 12.1.1
-
TABLE: AK.AK_CUSTOMIZATIONS 12.2.2
-
Stores region customizations
-
Stores region customizations
-
eTRM - AK Tables and Views 12.1.1
-
eTRM - AK Tables and Views 12.2.2