Results for “ak_customizations”

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

Overview

AK_CUSTOMIZATIONS is a core configuration table in the AK (Common Modules) product schema of Oracle E-Business Suite, holding the definition of region-level customizations that drive the Oracle Application Framework (OAF) and related runtime personalization behavior. In EBS 12.1.1 and 12.2.2, the table stores the metadata that determines which customized region substitute is applied for a given combination of application, region, verticalization, localization, organization, responsibility, or web user. Each row effectively declares that a specific customization code should be used for a specific region, optionally scoped to an audience. The table is populated and maintained primarily through the Customization Manager and registration utilities rather than by end users.

The provided metadata classifies this object heuristically as "standalone" under a Data Vault model. In practice the row itself is the customization assignment, so it behaves most like a satellite capturing attributes around a region/customization key, though it carries no hub-side FK to its parent AK_REGIONS object in the documented constraint set. The classification should be read as a modeling suggestion rather than a hard dependency declaration.

Key Information Stored

The surrogate primary key is AK_CUSTOMIZATIONS_PK, composed of CUSTOMIZATION_APPLICATION_ID, CUSTOMIZATION_CODE, REGION_APPLICATION_ID, and REGION_CODE. A secondary unique index, AK_CUSTOMIZATIONS_U2, exists on REGION_CODE, REGION_APPLICATION_ID, CUSTOMIZATION_CODE, CUSTOMIZATION_APPLICATION_ID, and ZD_EDITION_NAME, confirming that the four-key combination plus edition is the effective business uniqueness across editions.

• CUSTOMIZATION_APPLICATION_ID / CUSTOMIZATION_CODE — identify the substitute customization that will be applied to the region.
• REGION_APPLICATION_ID / REGION_CODE — identify the target region being customized.
• VERTICALIZATION_ID and LOCALIZATION_CODE — constrain the customization to a specific industry vertical or language/localization.
• ORG_ID and SITE_ID — restrict the customization to a particular operating unit or inventory/HR site.
• RESPONSIBILITY_ID and WEB_USER_ID — restrict the customization to a responsibility or a named application user; WEB_USER_ID is the only documented foreign key, pointing to ICX_USER_PROFILES.
• CUSTOMIZATION_LEVEL_ID and DEFAULT_CUSTOMIZATION_FLAG — indicate the scope level of the record and whether it is the default customization for its region.
• START_DATE_ACTIVE and END_DATE_ACTIVE — date-effective range during which the customization is active.
• REFERENCE_PATH and FUNCTION_NAME — locate the customization artifact and any function invoked.
• DEVELOPER_MODE — flags developer-oriented customizations for diagnostic use.
• ZD_EDITION_NAME — the edition discriminator used by the 12.2 online patching architecture.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit history.

Common Use Cases and Queries

Typical uses include auditing which region customizations exist, identifying personalizations applied for a responsibility or user, and troubleshooting why a customization is not being invoked at runtime. Because date-effectivity and audience columns are important, queries usually filter on today's date.

• List active customizations for a responsibility:

  SELECT region_code, customization_code, default_customization_flag, start_date_active, end_date_active
  FROM   ak.ak_customizations
  WHERE  responsibility_id = :resp_id
  AND    NVL(end_date_active, SYSDATE+1) > SYSDATE;

• Find the default customization for a region:

  SELECT customization_code
  FROM   ak.ak_customizations
  WHERE  region_code = :region_code
  AND    default_customization_flag = 'Y';

• Audit user-level personalizations by joining WEB_USER_ID to ICX_USER_PROFILES.
• Report by ORG_ID or VERTICALIZATION_ID to determine which business units have custom behavior.

Because the table is frequently read at page-render time, reporting queries should be restricted to avoid contention on production systems.

Related Objects

• ICX_USER_PROFILES — referenced by WEB_USER_ID; used to identify the user scope of a customization.
• AK_REGIONS — the logical parent region definition (join on REGION_APPLICATION_ID, REGION_CODE).
• AK_CUSTOMIZATIONS_PK / AK_CUSTOMIZATIONS_U2 — the primary and unique indexes enforcing row identity and business uniqueness.
• AK_REGION_ITEMS and AK_ATTRIBUTES — define the region structure that a customization modifies.
• FND_RESPONSIBILITY / FND_APPLICATION — join targets for RESPONSIBILITY_ID and the application identifiers.
• FND_ORG / HR_ALL_ORGANIZATION_UNITS — used to resolve ORG_ID and SITE_ID scoping.
• AK_CUSTOMIZATION_LEVELS (or equivalent lookups) — resolve CUSTOMIZATION_LEVEL_ID.