Search Results ak_query_objects




Overview
Explore in AI Chat

Overview

The AK_QUERY_OBJECTS table resides in the AK (Common Modules-AK) schema, which provides the shared infrastructure layer used throughout Oracle E-Business Suite for metadata-driven functionality such as flexfields, descriptive flexfields, and the Applications Query framework. The table defines a query object and the application id of the owner of that query object, serving as the registration point for named, code-identified queries that the EBS runtime can resolve and execute.

In Oracle EBS 12.1.1 and 12.2.2, AK_QUERY_OBJECTS acts as the anchor for the query-object layer within the AK module. Each row associates a unique query code with the owning application, allowing the system to scope queries to the correct product and enforce ownership boundaries. Because the documented relationship data classifies this object as standalone, with no foreign keys mined from its structure, it is best modeled as a reference or hub-style entity: a controlled registry of query objects that other AK and product-specific components resolve against by query code. In a heuristic Data Vault sense, this suggests treating AK_QUERY_OBJECTS as a hub keyed on QUERY_CODE, with descriptive and audit attributes carried on a satellite.

Key Information Stored

The documented physical schema contains eight columns. The most significant are listed below.

  • QUERY_CODE — The business identifier for the query object. It also constitutes the surrogate primary key column of AK_QUERY_OBJECT_PK1, making it the natural lookup key used throughout the AK framework.
  • APPLICATION_ID — Identifies the application that owns the query object. This scopes the query to a specific product and supports multi-application deployments within a single EBS instance.
  • ZD_EDITION_NAME — The editioning column introduced with the 12.2 online patching architecture. It participates in the unique index AK_QUERY_OBJECTS_U1 (QUERY_CODE, ZD_EDITION_NAME), and distinguishes rows across editions during patch cycles. In 12.1.1 this column does not apply in the same way, reflecting the 12.1 non-editioned model.
  • CREATED_BY, CREATION_DATE — Standard WHO columns capturing the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the last modifying user, timestamp, and login session.

The primary key AK_QUERY_OBJECT_PK1 is defined on QUERY_CODE, while the unique index AK_QUERY_OBJECTS_U1 on (QUERY_CODE, ZD_EDITION_NAME) serves as the business-key candidate in the 12.2 editioned schema.

Common Use Cases and Queries

Typical scenarios involve resolving a query code to its owning application, validating that a query object is registered before invoking it, and reporting on query objects by product. A simple lookup might read:

  • SELECT query_code, application_id FROM ak_query_objects WHERE query_code = :code;
  • Join to FND_APPLICATION to translate APPLICATION_ID into a product short name: SELECT q.query_code, a.application_short_name FROM ak_query_objects q, fnd_application a WHERE q.application_id = a.application_id AND a.application_short_name = 'XXCUSTOM';
  • For 12.2 environments, filter by edition to avoid ambiguity across patch editions: SELECT query_code, application_id FROM ak_query_objects WHERE zd_edition_name = 'SET1';

Reporting use cases include auditing query-object ownership, confirming that custom query codes are registered under the correct application, and tracing which product introduced a given query during upgrade validation.

Related Objects

Although the documented FK structure marks AK_QUERY_OBJECTS as standalone, it participates logically with the following significant objects.

  • FND_APPLICATION — joined on APPLICATION_ID to resolve the owning application.
  • FND_APPLICATION_TL — provides the translated application name for reporting.
  • AK_QUERY_COLUMNS — the companion AK table describing the columns exposed by each QUERY_CODE.
  • AK_QUERY_OBJECTS_U1 / AK_QUERY_OBJECT_PK1 — the unique index and primary key enforcing uniqueness of QUERY_CODE within an edition.
  • AK_REGIONS / AK_ATTRIBUTES — related AK metadata constructs that frequently reference query codes when rendering regions.
  • FND_APPLICATION-related WHO columns — CREATED_BY and LAST_UPDATED_BY resolve to FND_USER.