Search Results developer_mode

Overview

AK_CUSTOMIZATIONS_VL is a validation-level (VL) view owned by the APPS schema within the AK — Common Modules-AK product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents translated customization definitions registered against Oracle EBS regions and applications, joining the base customization entity with its multilingual (_TL) translation rows and with application and region lookup views. Because the underlying records are language-aware, the view resolves names and descriptions according to the session language through the USERENV('LANG') predicate, returning one row per customization per translation for the active language. The view serves as the reporting and integration surface for the AK customization framework, exposing both denormalized application/region/account names and the technical keys required to drive the customization engine.

Underlying Base Objects

The view is defined over four documented base objects: AK_CUSTOMIZATIONS (synonym to the base customization table), AK_CUSTOMIZATIONS_TL (translation table), AK_REGIONS_TL (region translation table), and FND_APPLICATION_VL (application validation view). AK_CUSTOMIZATIONS supplies the primary attributes such as customization code, region code, verticalization, localization, organization, site, responsibility, web user, reference path, and developer mode flags. AK_CUSTOMIZATIONS_TL supplies the language-specific customization name and description, joined on customization application ID and customization code. AK_REGIONS_TL provides the translated region name and description, joined on region application ID and region code. FND_APPLICATION_VL resolves the customization application and region application short names and full names. All translation joins are filtered by LANGUAGE = USERENV('LANG'), ensuring the returned rows reflect the caller's language environment.

Key Columns

• ROW_ID — the ROWID of the AK_CUSTOMIZATIONS base row, useful for direct row navigation and DML against the base table.
• CUSTOMIZATION_APPLICATION_ID / CUSTOMIZATION_CODE — the composite key uniquely identifying the customization.
• CUSTOMIZATION_APPL_SHORT_NAME / CUSTOMIZATION_APPL_NAME — the short and long names of the application owning the customization.
• CUSTOMIZATION_NAME / CUSTOMIZATION_DESCRIPTION — the translated customization text.
• REGION_APPLICATION_ID / REGION_CODE — the region the customization targets.
• REGION_APPL_SHORT_NAME / REGION_APPL_NAME / REGION_NAME / REGION_DESCRIPTION — denormalized application and translated region descriptors.
• VERTICALIZATION_ID / LOCALIZATION_CODE — industry and country scope controlling when the customization applies.
• ORG_ID / SITE_ID / RESPONSIBILITY_ID / WEB_USER_ID — the organizational and responsibility/self-service targeting context.
• REFERENCE_PATH — the path reference used to associate the customization with its runtime location; this is the attribute most frequently queried by name.
• DEFAULT_CUSTOMIZATION_FLAG, CUSTOMIZATION_LEVEL_ID, FUNCTION_NAME, DEVELOPER_MODE — control attributes governing default selection and developer behavior.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the customization.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical use cases include auditing active customizations, tracing which responsibility or organization a customization targets, and identifying records by reference path. The following sample retrieves all active customizations for a given reference path in the current language:

SELECT customization_code,
       customization_name,
       region_name,
       reference_path,
       responsibility_id,
       start_date_active,
       end_date_active
  FROM apps.ak_customizations_vl
 WHERE reference_path = :p_reference_path
   AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

The view can also be joined to FND_RESPONSIBILITY for administrative reporting:

SELECT ak.customization_name,
       ak.region_name,
       kr.responsibility_name,
       ak.reference_path
  FROM apps.ak_customizations_vl ak,
       apps.fnd_responsibility_vl kr
 WHERE ak.responsibility_id = kr.responsibility_id
   AND ak.default_customization_flag = 'Y';

Because the view is a VL construct, join predicates on language are already resolved, and no additional language filter is required on the consumer side.