Search Results msc_x_security_rules




Overview
Explore in AI Chat

Overview

MSC_X_SECURITY_RULES is a table in the MSC schema (Advanced Supply Chain Planning) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the security rules that govern how data is filtered and processed during Oracle Collaborative Planning activities. In a collaborative planning deployment, multiple trading partners, suppliers, customers, and internal organizations exchange planning data; this table supplies the access-control definitions that determine which rows of data a given grantee may view or act upon. Without these rules, Collaborative Planning would expose planning information uniformly across participants, which is neither operationally nor commercially acceptable.

From a Data Vault modeling perspective, the documented foreign key relationship (COMPANY_ID referencing PN_COMPANIES_ALL) and the standalone classification suggest this object behaves primarily as a satellite-like reference table attached to a company dimension, rather than as a transactional hub or link. This is a heuristic suggestion only; the physical design predates Data Vault conventions, and the table should be treated as an operational security configuration entity.

Key Information Stored

The table is documented with 25 columns in the 12.2.2 physical schema. The most operationally significant columns are:

  • RULE_ID — the surrogate primary key, enforced by constraint MSC_X_SECURITY_RULES_PK. It uniquely identifies each rule row.
  • COMPANY_ID — foreign key to PN_COMPANIES_ALL, tying the rule to a specific company entity; this is the principal join path to master data.
  • ORDER_TYPE and ORDER_TYPE_MEANING — the transaction or order category to which the rule applies, with its descriptive label.
  • ITEM_ID and ITEM_NAME — optional item-level scoping of the rule, with the ID serving as the internal reference and the name supporting reporting.
  • CATEGORY_ID and CATEGORY_NAME — the item category scope, used when rules apply at an aggregate level rather than to individual items.
  • CUSTOMER_ID, SUPPLIER_ID, CUSTOMER_SITE_ID, and SUPPLIER_SITE_ID — trading partner identifiers and their site-level detail, defining the external parties covered by the rule.
  • ORG_ID — the operating unit or inventory organization context.
  • ORDER_NUMBER — a specific document reference when the rule is scoped to a single order.
  • GRANTEE_TYPE, GRANTEE_KEY, and PRIVILEGE — the recipient classification, the specific grantee identity, and the access level or action permitted.
  • EFFECTIVE_FROM_DATE and EFFECTIVE_TO_DATE — the validity window controlling when the rule is active.

Standard EBS audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, PROGRAM_ID) are present and follow the usual WHO-column conventions.

Common Use Cases and Queries

Typical use cases include auditing which partners can see which planning data, diagnosing why a collaborative planning user sees incomplete results, and reporting active security grants as of a given date. A representative query retrieves currently effective rules for a company with partner detail:

SELECT r.RULE_ID, r.ITEM_NAME, r.CUSTOMER_ID, r.SUPPLIER_ID,
  r.GRANTEE_TYPE, r.GRANTEE_KEY, r.PRIVILEGE
FROM MSC.MSC_X_SECURITY_RULES r
WHERE r.COMPANY_ID = :company_id
  AND SYSDATE BETWEEN r.EFFECTIVE_FROM_DATE AND NVL(r.EFFECTIVE_TO_DATE, SYSDATE);

A second pattern joins to PN_COMPANIES_ALL to resolve company identity for reporting: SELECT r.*, c.COMPANY_NAME FROM MSC.MSC_X_SECURITY_RULES r, PN_COMPANIES_ALL c WHERE r.COMPANY_ID = c.COMPANY_ID. A third enumerates expired or future-dated rules as part of a periodic access review.

Related Objects

  • PN_COMPANIES_ALL — referenced by MSC_X_SECURITY_RULES.COMPANY_ID; the primary master-data join for company identity.
  • MSC_X_SECURITY_RULES_PK — the primary key constraint on RULE_ID, used in index and constraint inventory queries.
  • MSC application tables storing collaborative planning worksheets, supply/demand and item/category master data referenced by ITEM_ID, CATEGORY_ID, ORG_ID, CUSTOMER_ID, and SUPPLIER_ID.
  • Oracle Collaborative Planning concurrent programs and planning engine components that read these rules at runtime to filter planning output.
  • Standard EBS audit/security reporting views and the FND user and responsibility model through which GRANTEE_TYPE and GRANTEE_KEY values are interpreted.