Results for “msc_security_rules_v”

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

Overview

MSC_SECURITY_RULES_V is a security-enabled view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSC (Advanced Supply Chain Planning) product family. The view exposes security rule definitions that govern which planning data a given user, responsibility, company, group, or trading partner is permitted to see when working within the Advanced Supply Chain Planning module and related ETRM (Enterprise Transaction Reporting Model) reporting surfaces.

The view is a thin presentation layer over the underlying MSC_X_SECURITY_RULES base table. Its principal function is to translate raw security rule rows into a human-readable form by resolving surrogate keys — user IDs, company IDs, responsibility IDs, group IDs, site IDs, and item/category references — into meaningful names, using the MSCX_UI_UTILITIES package. It also enforces row-level VPD-style filtering via SYS_CONTEXT('MSC','COMPANY_ID') and FND_GLOBAL.USER_ID, so that the rows returned are already constrained to those the current session is entitled to view. This makes the view appropriate for both end-user reporting and integration queries that must respect planning security.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view references the following base objects:

• MSC_X_SECURITY_RULES (synonym) — the primary source table holding the actual security rule definitions, aliased as RULE1 in the view text.
• MSCX_UI_UTILITIES (package) — supplies the GET_USER_NAME, GET_COMPANY_NAME, GET_RESPONSIBILITY_NAME, GET_GROUP_NAME, GET_SITE_NAME and GET_RESPONSIBILITY_KEY functions that resolve IDs to display values.
• FND_GLOBAL (package) — provides the current session USER_ID used in the grantee predicate.
• FND_USER_RESP_GROUPS (view) — underlying source for responsibility/group lookups through the utility package.
• FND_DATE (package) — date conversion utility typically invoked for date formatting on the rule's effective date columns.
• MSC_GROUP_COMPANIES (synonym) — supports group-to-company membership resolution used by the group grantee logic.

The relationship is a straightforward one-to-many: one row in MSC_X_SECURITY_RULES corresponds to one row in the view, with all ID columns preserved and additional derived name columns appended.

Key Columns

• RULE_ID — unique identifier of the security rule.
• GRANTEE_TYPE — uppercased type of the grantee: USER, COMPANY, RESPONSIBILITY, GROUP, DOCUMENT OWNER, TRADING PARTNER, or GLOBAL.
• GRANTEE_KEY_ID / GRANTEE_KEY — the raw key and its decoded display value (user, company, responsibility, or group name) selected via DECODE on GRANTEE_TYPE.
• PRIVILEGE — uppercased access level granted by the rule.
• COMPANY_ID, COMPANY_NAME — owning company and its resolved name.
• CUSTOMER_ID / CUSTOMER_NAME, SUPPLIER_ID / SUPPLIER_NAME — trading partner identities and names.
• CUSTOMER_SITE_ID / CUSTOMER_SITE_NAME, SUPPLIER_SITE_ID / SUPPLIER_SITE_NAME — site-level scoping and resolved site names.
• ORG_ID / ORG — operating unit/site identifier and its display name.
• ITEM_ID / ITEM_NAME, CATEGORY_ID / CATEGORY_NAME — item and category scope of the rule.
• ORDER_TYPE / MEANING — order type code and its translated meaning.
• ORDER_NUMBER — order reference where the rule is order-specific.
• EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE — validity window of the rule.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include auditing who can see which planning data, diagnosing why a planner cannot view a given company or item, and building security-aware reports in ETRM/Discoverer/BI Publisher that automatically inherit the caller's MSC company context.

• List all rules visible to the current session:

  SELECT rule_id, grantee_type, grantee_key, privilege, company_name, org FROM apps.msc_security_rules_v ORDER BY grantee_type, grantee_key;

• Filter to user-level grants for a specific user:

  SELECT rule_id, grantee_key, privilege, item_name, category_name FROM apps.msc_security_rules_v WHERE grantee_type = 'USER' AND grantee_key = 'JDOE';

• Identify currently effective rules:

  SELECT rule_id, grantee_type, grantee_key, effective_from_date, effective_to_date FROM apps.msc_security_rules_v WHERE SYSDATE BETWEEN effective_from_date AND effective_to_date;

• Reconcile site-level scoping against customers and suppliers:

  SELECT rule_id, customer_name, customer_site_name, supplier_name, supplier_site_name FROM apps.msc_security_rules_v WHERE customer_site_id IS NOT NULL OR supplier_site_id IS NOT NULL;

Because the view applies session-based predicates internally, queries executed by ordinary users return only their entitled rules; administrative responsibilities such as MSCX_SC_ADMIN_FULL bypass the company filter to expose the complete rule set.