Search Results bne_security_rules_pk

Overview

BNE_SECURITY_RULES is a foundational configuration table in the BNE schema (Web Applications Desktop Integrator, or Web ADI) within Oracle E-Business Suite 12.1.1 and 12.2.2. Each row defines a single security rule that governs how users are granted or restricted access to desktop integration content, such as spreadsheets, integrator definitions, and layout components. Because Web ADI exposes EBS data entry and retrieval through Microsoft Excel, the security model enforced by this table is critical to preventing unauthorized access to financial and operational data pulled through desktop integration.

The table is owned by the BNE schema with a documented status of VALID. Its primary key, BNE_SECURITY_RULES_PK, is composed of the composite columns APPLICATION_ID and SECURITY_CODE. A second unique index, BNE_SECURITY_RULES_UK1 (APPLICATION_ID, SECURITY_CODE, ZD_EDITION_NAME), acts as a business-key candidate and supports the edition-aware (ZD_EDITION) architecture introduced in later 12.2.x releases. The documented physical schema contains 11 columns.

Regarding Data Vault modeling, the heuristic classification for this object is standalone, meaning it is not a dependent child of a parent FK chain in the mined structure. As a modeling suggestion, this object most closely resembles a hub for the business key (APPLICATION_ID, SECURITY_CODE), with descriptive attributes such as SECURITY_TYPE and SECURITY_VALUE residing as satellite-style attributes on the same physical table rather than being split out.

Key Information Stored

The most important columns documented for BNE_SECURITY_RULES are:

• APPLICATION_ID — Identifies the owning Oracle EBS application (for example, General Ledger, Payables, or Assets). Part of the composite primary key.
• SECURITY_CODE — The business identifier for the rule. Part of the composite primary key and the value users typically search for when troubleshooting desktop integration access.
• SECURITY_TYPE — Defines the category or mechanism of the rule, determining how the rule is evaluated at runtime.
• SECURITY_VALUE — Holds the qualifying value or operand applied by the rule, such as a responsibility, user, or parameter value used during enforcement.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• ZD_EDITION_NAME — Editioning column supporting the 12.2.x online patching (editions) model; participates in the unique index BNE_SECURITY_RULES_UK1.
• CREATED_BY, CREATION_DATE — Standard WHO columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard WHO audit columns capturing the most recent modification identity and timestamp.

The surrogate/composite primary key is (APPLICATION_ID, SECURITY_CODE); the business-key candidate is the same pair extended by ZD_EDITION_NAME.

Common Use Cases and Queries

Support and implementation teams query this table to audit which security rules exist per application, to diagnose why a user cannot access a Web ADI integrator, and to migrate rule definitions between environments.

To list all rules for an application:

• SELECT security_code, security_type, security_value FROM bne.bne_security_rules WHERE application_id = :app_id ORDER BY security_code;

To locate a specific rule by the commonly searched security_code:

• SELECT application_id, security_code, security_type, security_value, last_update_date FROM bne.bne_security_rules WHERE security_code = :security_code;

To resolve the owning application name, join to FND_APPLICATION:

• SELECT r.security_code, a.application_short_name FROM bne.bne_security_rules r, fnd_application a WHERE r.application_id = a.application_id;

Edition-aware queries should filter on ZD_EDITION_NAME to isolate the active edition during 12.2.x patch cycles.

Related Objects

The following objects are most significant for understanding and joining this table:

• FND_APPLICATION — Joined on APPLICATION_ID to obtain application names and short names.
• FND_RESPONSIBILITY — Frequently referenced when SECURITY_VALUE qualifies a responsibility.
• FND_USER — Referenced when a rule targets specific named users.
• BNE_SECURITY_RULES_PK — The primary key constraint enforcing (APPLICATION_ID, SECURITY_CODE).
• BNE_SECURITY_RULES_UK1 — Unique index supporting (APPLICATION_ID, SECURITY_CODE, ZD_EDITION_NAME).
• BNE_INTEGRATOR_DEFINITIONS / BNE_LAYOUTS — Web ADI definition objects whose access is governed by rules maintained here.

Because the mined relationship data classifies this object as standalone, most associations are functional joins rather than enforced foreign keys.