Search Results bne_graph_columns_uk1




Overview

BNE.BNE_GRAPH_COLUMNS is a transactional table in the Oracle E-Business Suite 12.1.1 and 12.2.2 BNE (Business Intelligence/Graphing) schema. It serves as the base table for graph information, storing the column-level definitions that make up the graphs rendered within EBS components such as Oracle iSetup, Oracle Approvals Management, and other BNE-based visualization features. Each row describes one column belonging to a specific graph, keyed by the owning application, integrator code, graph sequence number, and sequence number. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, while its unique index BNE_GRAPH_COLUMNS_UK1 sits in APPS_TS_TX_IDX.

From a data modeling perspective, the heuristic Data Vault classification for this object is a link. The table's composite key bridges the graph definition (BNE_GRAPHS_B) and the interface column definition (BNE_INTERFACE_COLS_B), making it a natural relationship or link entity rather than a pure hub or satellite. This classification is a modeling suggestion based on the observed foreign-key structure, not an enforced design constraint.

Key Information Stored

The table contains 15 documented columns. The most important for identification and business meaning are:

The surrogate/primary key is BNE_GRAPH_COLUMNS_PK on (APPLICATION_ID, INTEGRATOR_CODE, GRAPH_SEQ_NUM, SEQUENCE_NUM). The business-key candidate is captured by the unique index the user searched for, BNE_GRAPH_COLUMNS_UK1, defined on (APPLICATION_ID, INTEGRATOR_CODE, GRAPH_SEQ_NUM, SEQUENCE_NUM, ZD_EDITION_NAME). The inclusion of ZD_EDITION_NAME in the unique index is required so that uniqueness holds per edition under 12.2 edition-based redefinition.

Common Use Cases and Queries

Typical uses include diagnosing why a graph renders incorrectly, auditing column ordering, and reporting on graph configuration across applications. A common pattern retrieves all columns for a given graph:

  • List columns for a graph: SELECT APPLICATION_ID, INTEGRATOR_CODE, GRAPH_SEQ_NUM, SEQUENCE_NUM, INTERFACE_CODE, LOCATION_CODE FROM BNE.BNE_GRAPH_COLUMNS WHERE APPLICATION_ID = :app_id AND INTEGRATOR_CODE = :code AND GRAPH_SEQ_NUM = :graph ORDER BY SEQUENCE_NUM;
  • Join to interface columns: Link INTERFACE_APP_ID/INTERFACE_SEQ_NUM to BNE_INTERFACE_COLS_B to see which interface attributes back each graph column.
  • Join to graph headers: Link APPLICATION_ID/INTEGRATOR_CODE/GRAPH_SEQ_NUM to BNE_GRAPHS_B to resolve graph titles and metadata.
  • Audit changes: Filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent configuration edits.
  • Duplicate detection: Because BNE_GRAPH_COLUMNS_UK1 enforces uniqueness, querying it can reveal attempted duplicates within a given edition.

Related Objects

The following objects are most significant to BNE.BNE_GRAPH_COLUMNS, based on the documented dependency and foreign-key relationships:

  • BNE.BNE_GRAPHS_B – Parent graph definition; joined on APPLICATION_ID, INTEGRATOR_CODE, and GRAPH_SEQ_NUM.
  • BNE.BNE_INTERFACE_COLS_B – Interface column definition referenced via INTERFACE_APP_ID, INTERFACE_CODE, and INTERFACE_SEQ_NUM.
  • FND_APPLICATIONS – Resolves APPLICATION_ID to the owning application name and short name.
  • FND_USER – Resolves CREATED_BY and LAST_UPDATED_BY to user identities.
  • FND_LOGINS – Resolves LAST_UPDATE_LOGIN to the originating login session.
  • BNE_GRAPH_COLUMNS_PK / BNE_GRAPH_COLUMNS_UK1 – Primary and unique indexes enforcing row identity and business-key uniqueness.
  • BNE_GRAPH_COLUMNS (view/API consumers) – BNE graphing runtime components that read this table to render graph columns.