Search Results msc_company_users




Overview
Explore in AI Chat

Overview

MSC_COMPANY_USERS is a table in the MSC schema, owned by the Oracle Advanced Supply Chain Planning (ASCP) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the association between application users and companies for the Oracle Collaborative Planning functionality. In practice, each row represents the assignment of a specific FND user to a specific company (a planning entity or trading partner company), enabling Collaborative Planning to scope data visibility, planning scenarios, and transactional access to the correct company context. The object is classified as VALID in the ETRM data dictionary and is documented with three columns in the 12.2.2 physical schema.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests that MSC_COMPANY_USERS behaves as a standalone reference or association table rather than a strict hub, link, or satellite. Where a formal model is desired, it can be treated as a lightweight link-style association between user and company, but the documented metadata does not assert a hub/link/satellite designation.

Key Information Stored

The documented physical schema exposes three columns. The most significant of these are:

  • USER_ID — Identifies the Oracle Applications user (FND_USER.USER_ID) associated with a company. This column is the sole documented component of the primary key MSC_COMPANY_USERS_PK, making it the primary business-key candidate and the surrogate/primary identifier for the association.
  • COMPANY_ID — Identifies the company to which the user is associated. It is a foreign key referencing PN_COMPANIES_ALL, linking the user association to the collaborative planning company definition.
  • SR_INSTANCE_ID — Identifies the source instance from which the record originated, supporting multi-instance and data-collection scenarios typical of ASCP and Collaborative Planning.

Because the documented primary key covers only USER_ID, the effective uniqueness of the user-to-company association should be verified against the actual database, as the presence of SR_INSTANCE_ID and COMPANY_ID suggests the association may be further qualified in practice.

Common Use Cases and Queries

Typical use cases include auditing which users are enabled for Collaborative Planning, reporting user-to-company assignments, and validating that planning data is scoped to the correct company. A representative query joins the association to the user and company master data:

  • List all companies for a given user: SELECT company_id FROM msc_company_users WHERE user_id = :user_id;
  • Resolve user names and company names: join MSC_COMPANY_USERS to FND_USER on USER_ID and to PN_COMPANIES_ALL on COMPANY_ID.
  • Multi-instance reporting: group or filter by SR_INSTANCE_ID to isolate records from a specific source instance.

Related Objects

  • PN_COMPANIES_ALL — Referenced by MSC_COMPANY_USERS.COMPANY_ID; the primary company definition table for collaborative planning.
  • FND_USER — Provides the user identity corresponding to USER_ID (functional relationship, not documented as an FK).
  • MSC_COMPANY_USERS_PK — The primary key constraint enforcing uniqueness on USER_ID.
  • Other MSC Collaborative Planning configuration tables that consume company and user scoping should be reviewed alongside this table when troubleshooting access or visibility issues.