Search Results msc_planners_u1

Overview

MSC.MSC_PLANNERS is a transactional master table in the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It stores and maintains the list of planner codes that are exchanged between a source application instance and the MSC schema, which acts as the planning repository. The table is owned by the MSC schema and resides in the APPS_TS_TX_DATA tablespace with a PCT_FREE of 10. Its FND design data reference confirms that it is an application-defined object that is registered and maintained through the standard Oracle EBS dictionary.

The table is multi-tenant by design. Every row is qualified by both SR_INSTANCE_ID and ORGANIZATION_ID, so the same planner code can be recorded independently per source instance and per inventory organization. This scoping allows one MSC planning installation to consolidate planner data collected from multiple EBS source instances and operating units through the collections process. In Data Vault terms, the mined relationship data classifies MSC_PLANNERS as a standalone object, which suggests modeling it as a hub-like reference entity for the planner business key rather than as a pure transaction satellite. There is a documented foreign key from EMPLOYEE_ID to PSB_EMPLOYEES, but the heuristic classification remains standalone.

Key Information Stored

The primary key of the table is MSC_PLANNERS_PK, defined on the composite of PLANNER_CODE, ORGANIZATION_ID, and SR_INSTANCE_ID. The unique index MSC_PLANNERS_U1 covers the same three columns in the order SR_INSTANCE_ID, PLANNER_CODE, ORGANIZATION_ID, and is documented in the APPS_TS_TX_IDX tablespace. This index is the effective business-key candidate and enforces the natural uniqueness of a planner within a given source instance and organization.

• PLANNER_CODE (VARCHAR2 10) — the planner identifier as maintained in the source application.
• ORGANIZATION_ID (NUMBER) — the inventory organization to which the planner assignment applies.
• SR_INSTANCE_ID (NUMBER) — identifies the source application instance from which the record was collected.
• DESCRIPTION (VARCHAR2 50) — a descriptive label for the planner.
• DISABLE_DATE (DATE) — the date on which the planner record is disabled.
• EMPLOYEE_ID — the employee associated with the planner; it carries the documented foreign key to PSB_EMPLOYEES.
• ELECTRONIC_MAIL_ADDRESS — the planner's e-mail address, used for notification and reporting.
• USER_NAME — the application user name linked to the planner.
• CURRENT_EMPLOYEE_FLAG — indicates whether the planner is a current employee.
• REFRESH_NUMBER — supports the collection and refresh cycle that keeps MSC data synchronized.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield structure and segments for site-specific extensions.
• Standard Who and Concurrent Who columns — including LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical reporting resolves planner codes to descriptions and employee details, validates that a planner is active, or reports on collection freshness. The following pattern selects active planners for a specific organization and source instance:

• SELECT planner_code, description, electronic_mail_address FROM msc.msc_planners WHERE organization_id = :org_id AND sr_instance_id = :inst_id AND (disable_date IS NULL OR disable_date > SYSDATE);
• A join to PSB_EMPLOYEES via EMPLOYEE_ID enriches planner records with employee name and assignment data for operational reports.
• Grouping by SR_INSTANCE_ID and ORGANIZATION_ID identifies planner assignments per source and organization for collection reconciliation.

Because MSC_PLANNERS is maintained by the collections process, direct DML in the MSC schema is not advisable in a production environment; changes should originate in the source application and be refreshed through planning data collection.

Related Objects

• PSB_EMPLOYEES — referenced by the documented foreign key on EMPLOYEE_ID; supplies employee attributes for planner records.
• MSC_PLANNERS_U1 — the unique index enforcing the SR_INSTANCE_ID, PLANNER_CODE, ORGANIZATION_ID business key.
• MSC_PLANNERS_PK — the primary key constraint on PLANNER_CODE, ORGANIZATION_ID, and SR_INSTANCE_ID.
• MSC.MSC_PLANNERS (APPS synonym) — the APPS-level synonym through which concurrent programs and reports reference the table.
• MSC_ORGANIZATIONS / MSC_SYSTEM_ITEMS — organization and item planning entities whose planner assignments depend on valid planner codes stored here.
• MSC_PLANNER_UTIL / planner assignment interfaces — planning processes that consume planner codes for item and organization assignment during plan runs.