Results for “bne_simple_query”

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

Overview

The BNE_SIMPLE_QUERY table resides in the BNE schema, owned by the Web Applications Desktop Integrator (Web ADI) product family within Oracle E-Business Suite. Its documented purpose is the Definition of Metadata defined queries, meaning it stores the declarative query metadata that Web ADI uses to build and drive its desktop integrations and list-of-values style data retrieval at runtime rather than relying on hard-coded SQL. It is a core configuration table for Web ADI's metadata-driven query framework.

Heuristically derived from its foreign-key structure, the table leans toward a satellite classification in a Data Vault model, because it carries descriptive attributes for the BNE_QUERIES_B entity rather than acting as a pure hub or link. This is a modeling suggestion only; the table is a standard relational entity in an Oracle EBS 12.1.1 / 12.2.2 installation and remains versioned via the standard ZD_EDITION_NAME column used by EBS online patching in 12.2.x.

Key Information Stored

The table defines 19 columns. The most significant are:

• APPLICATION_ID, QUERY_CODE — the business-key composite that forms the BNE_SIMPLE_QUERY_PK primary key and the leading columns of the BNE_SIMPLE_QUERY_UK1 unique index.
• ZD_EDITION_NAME — the edition tracking column; combined with APPLICATION_ID and QUERY_CODE it completes the business-key unique index in 12.2.2.
• OBJECT_NAME — the underlying database object (table or view) the query targets.
• ID_COL, ID_COL_ALIAS — the identifier column and its exposed alias.
• MEANING_COL, MEANING_COL_ALIAS — the descriptive/meaning column and its alias.
• DESCRIPTION_COL, DESCRIPTION_COL_ALIAS — the longer description column and its alias.
• ADDITIONAL_COLS — supplementary columns exposed by the query definition.
• ADDITIONAL_WHERE_CLAUSE, ORDER_BY_CLAUSE — declarative filtering and sorting fragments applied when the query executes.
• OBJECT_VERSION_NUMBER — optimistic-locking / row versioning column.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO audit columns.

Only the business-key columns participate in the documented unique index; the surrogate identity is provided through BNE_SIMPLE_QUERY_PK.

Common Use Cases and Queries

Typical use is diagnosing why a Web ADI integration returns unexpected columns, missing rows, or incorrect ordering. Because the query shape is data-driven, DBAs and developers inspect this table to confirm the object name, column aliases, and the runtime WHERE/ORDER BY fragments.

-- Locate a query definition by application and code
SELECT application_id, query_code, object_name,
       id_col, id_col_alias, meaning_col, meaning_col_alias,
       additional_where_clause, order_by_clause
FROM   bne.bne_simple_query
WHERE  application_id = :app_id
AND    query_code     = :query_code;

-- List all simple queries for a module/edition
SELECT query_code, object_name, additional_cols
FROM   bne.bne_simple_query
WHERE  application_id = :app_id
AND    zd_edition_name = 'ORA$BASE';

This supports impact analysis before changing a base object, auditing customization of query definitions, and reporting on which database objects Web ADI queries surface to end users.

Related Objects

• BNE_QUERIES_B — the parent/master table; joined on BNE_SIMPLE_QUERY.APPLICATION_ID = BNE_QUERIES_B.APPLICATION_ID and BNE_SIMPLE_QUERY.QUERY_CODE = BNE_QUERIES_B.QUERY_CODE via the documented foreign key.
• BNE_QUERIES_TL — translation table supplying the query's display name and description.
• BNE_SIMPLE_QUERY_PK / BNE_SIMPLE_QUERY_UK1 — the primary key and business-key unique index constraints.
• BNE_QUERY_PARAMETERS — parameter definitions bound to the parent query.
• BNE_RUN_QUERIES / Web ADI integrator definitions — consume the query metadata at runtime.
• FND_APPLICATION — resolves APPLICATION_ID to the owning application.

These associations make BNE_SIMPLE_QUERY a satellite of BNE_QUERIES_B, supplying the concrete SQL-shaping metadata for each registered query.