Search Results itemset_name

Overview

BIS.EDW_SEC_ITEMSET_INFO_T is a security metadata configuration table within the Oracle E-Business Suite Business Intelligence System (BIS) schema. It stores the definitions of "itemsets" — logical groupings that govern row-level security enforcement inside the Oracle EBS Data Warehouse / ETRM security framework. Each row associates a warehouse fact (identified by FACT_ID and FACT_NAME) with an itemset name and with the foreign-key column used to resolve the security predicate at query time. Because the table lives in the BIS schema and is registered in FND Design Data as BIS.EDW_SEC_ITEMSET_INFO_T, it participates directly in the runtime security resolution performed by the EDW security engine.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone, meaning no satellite or link relationship is enforced through database constraints beyond the single outbound reference noted in the FK metadata. It is best treated as a reference or configuration table rather than as a transactional fact or hub.

Key Information Stored

The documented schema exposes five columns, each of which carries functional significance:

• FACT_ID (NUMBER) — Surrogate identifier for the warehouse fact associated with the itemset. This is the column indexed by EDW_SEC_ITEMSET_INFO_T_N1 and is the target of the documented foreign-key relationship to ASO_ER_DATA_BIN_FACT.
• FACT_NAME (VARCHAR2, 255) — Short business name of the fact, used by the security engine to match the itemset to the correct fact object.
• FACT_LONG_NAME (VARCHAR2, 2000) — Descriptive name or label for the fact, typically surfaced in administrative UI and diagnostic reports.
• ITEMSET_NAME (VARCHAR2, 255) — Business-key candidate and the central column of interest. It names the security itemset and is indexed by EDW_SEC_ITEMSET_INFO_T_N2. Applications and administrators query this column directly to locate the security definition applied to a given fact.
• FK_COL_NAME (VARCHAR2, 255) — Identifies the foreign-key or join column within the fact against which the itemset filter is applied. This determines how the security predicate is joined back to the transactional or dimensional data.

The table does not expose an explicitly documented primary-key constraint; FACT_ID functions as the de facto surrogate identifier, while ITEMSET_NAME is the strongest business-key candidate and is separately indexed for lookup efficiency.

Common Use Cases and Queries

The most frequent access pattern is a direct lookup by itemset name, since that is the column administrators and security configuration tools reference. A typical query is:

• SELECT FACT_ID, FACT_NAME, FACT_LONG_NAME, FK_COL_NAME FROM BIS.EDW_SEC_ITEMSET_INFO_T WHERE ITEMSET_NAME = :p_itemset_name;
• Joining the table to ASO_ER_DATA_BIN_FACT on FACT_ID to resolve fact-level context for an itemset.
• Reporting on the itemset inventory per fact, grouping by FACT_NAME to identify which facts are secured or unsecured.

Reporting scenarios include security audits that verify every active fact has an associated itemset, and diagnostic queries that determine which FK column a given itemset will filter on. Because the table is small and reference-oriented, queries are dominated by equality filters on ITEMSET_NAME and FACT_ID rather than range scans.

Related Objects

The documented relationships and dependencies for this object include:

• ASO_ER_DATA_BIN_FACT — Referenced through the FK on FACT_ID; the primary outbound dependency and the source of fact-level security context.
• APPS.EDW_SEC_ITEMSET_INFO_T — The APPS-schema synonym or view through which the table is commonly queried by application code and BI tools.
• EDW_SEC_ITEMSET_INFO_T_N1 and EDW_SEC_ITEMSET_INFO_T_N2 — The two non-unique indexes in APPS_TS_TX_IDX that support the FACT_ID and ITEMSET_NAME access paths respectively.

No further database objects are documented as directly referencing this table within the supplied metadata, which reinforces its role as a leaf-level configuration object consumed by the broader EDW security framework rather than a hub of referential activity.