Results for “bne_raw_query”

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

Overview

BNE_RAW_QUERY is a table in the BNE schema (Web Applications Desktop Integrator) that stores the definition of metadata-defined queries. In Oracle EBS 12.1.1 and 12.2.2, BNE underpins the Desktop Integration framework used by Web ADI, where metadata definitions drive the generation of integrator layouts, mappings, and data extracts. BNE_RAW_QUERY holds the raw SQL query text associated with each query definition, allowing the Desktop Integrator to resolve, at runtime, the data set that populates a given integrator or report.

Each row represents a single query segment (identified by SEQUENCE_NUM) belonging to a parent query definition held in BNE_QUERIES_B. Because multiple rows can attach to one parent query and carry descriptive payload (the QUERY text, audit columns, and versioning attributes), the object behaves as a child/detail record. The metadata's heuristic Data Vault classification labels BNE_RAW_QUERY as satellite-leaning, suggesting that in a data-warehouse model it is best treated as a satellite table describing the BNE_QUERIES_B business key rather than as an independent hub or a pure link.

Key Information Stored

The table is defined with a composite primary key and several descriptive and audit columns. The most significant columns are:

• APPLICATION_ID — Identifies the owning application; part of the primary key and foreign key to BNE_QUERIES_B.
• QUERY_CODE — The business identifier of the parent query definition; part of the primary key and foreign key.
• SEQUENCE_NUM — Orders/segments the raw query rows belonging to a single query definition; part of the primary key.
• QUERY — The stored raw SQL query text, the core payload of the table.
• OBJECT_VERSION_NUMBER — Optimistic locking/versioning column used by the framework.
• CREATION_DATE, CREATED_BY — Standard who-column creation audit.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard who-column update audit.
• ZD_EDITION_NAME — Editioning column supporting Edition-Based Redefinition in 12.2.x.

The surrogate composite primary key is BNE_RAW_QUERY_PK (APPLICATION_ID, QUERY_CODE, SEQUENCE_NUM). A documented unique index, BNE_RAW_QUERY_UK1, spans APPLICATION_ID, QUERY_CODE, SEQUENCE_NUM, and ZD_EDITION_NAME, serving as the business-key candidate that also accommodates editioning.

Common Use Cases and Queries

Typical uses include auditing the SQL behind a Web ADI integrator, tracing a failing layout back to its query text, and migrating query definitions between environments. A representative lookup for all raw segments of a query is:

• SELECT sequence_num, query FROM bne.bne_raw_query WHERE application_id = :app_id AND query_code = :code ORDER BY sequence_num;
• Join to the parent definition to resolve names: SELECT r.query_code, r.sequence_num, r.query FROM bne.bne_raw_query r, bne.bne_queries_b b WHERE r.application_id = b.application_id AND r.query_code = b.query_code;
• Reporting on recently modified definitions: filter on LAST_UPDATE_DATE or LAST_UPDATED_BY.

Related Objects

The principal related objects, grounded in the documented foreign-key relationship, are:

• BNE_QUERIES_B — Parent table; joined on APPLICATION_ID and QUERY_CODE.
• BNE_RAW_QUERY_PK — Primary key constraint over (APPLICATION_ID, QUERY_CODE, SEQUENCE_NUM).
• BNE_RAW_QUERY_UK1 — Unique index/business-key candidate including ZD_EDITION_NAME.
• Other BNE query and metadata definition tables (for example parameter and layout definitions) depend on the same APPLICATION_ID/QUERY_CODE key space.

Because the documented metadata lists only BNE_QUERIES_B as the direct FK target, integration work should treat BNE_QUERIES_B as the authoritative parent and confirm any additional BNE metadata dependencies in the target instance.