Search Results msc_designtors

Overview

MSC_ST_DESIGNATORS is a staging table within the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the intermediate landing area where the data collection program validates, transforms, and processes source designator records before they are promoted to the permanent planning table MSC_DESIGNATORS (referenced in the metadata as MSC_DESIGNTORS). In the ASCP architecture, staging tables isolate raw collected data from the live planning engine, allowing the collection manager to apply validation rules, detect errors, and reconcile records without corrupting planning results. Records failing validation remain in staging with diagnostic information written to ERROR_TEXT, while valid rows are merged into the planning tables.

From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a standalone staging entity rather than a strict hub, link, or satellite. The heuristic classification reflects the fact that staging tables denormalize attributes that would otherwise be distributed across multiple hubs and satellites in a formal Data Vault design.

Key Information Stored

The table contains 55 documented columns. The most operationally significant include:

• DESIGNATOR_ID — surrogate primary key and foreign key to MSC_DESIGNATORS; the unique identifier of the designator record.
• DESIGNATOR / SR_DESIGNATOR — the source and business-key designator value, used to match incoming records against existing definitions.
• ORGANIZATION_ID / SR_ORGANIZATION_ID — planning organization and its source-system counterpart.
• DESIGNATOR_TYPE — classifies the designator (for example demand class, customer, or forecast-related groupings).
• DEMAND_CLASS — the demand classification assigned to the designator for forecasting and ATP consumption.
• MPS_RELIEF, INVENTORY_ATP_FLAG, PRODUCTION, RECOMMENDATION_RELEASE — planning behavior flags controlling master production schedule relief and ATP processing.
• CONSUME_FORECAST, PROBABILITY, BUCKET_TYPE — forecast consumption and bucketing attributes.
• FORECAST_SET_ID / FORECAST_SET — links the designator to a forecast set.
• SR_INSTANCE_ID, REFRESH_ID, BATCH_ID, ST_TRANSACTION_ID — collection and refresh identifiers used to track the load cycle and batch that produced each row.
• PROCESS_FLAG, ERROR_TEXT, MESSAGE_ID — validation status and error diagnostics for the collection process.
• LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID — standard EBS audit and concurrent program columns.

Business-key candidates include DESIGNATOR combined with ORGANIZATION_ID and SR_INSTANCE_ID, while DESIGNATOR_ID anchors the surrogate relationship. Additional FK columns BILL_ID and COMPANY_ID point to IGS_FI_BILL_ALL and PN_COMPANIES_ALL respectively.

Common Use Cases and Queries

Typical use cases include post-collection error triage, reconciliation of staged versus promoted designators, and reporting on planning designator configuration.

• Identify failed collection rows:
  SELECT DESIGNATOR, ORGANIZATION_ID, ERROR_TEXT FROM MSC_ST_DESIGNATORS WHERE PROCESS_FLAG = 'E';
• Reconcile staged against planning records:
  SELECT s.DESIGNATOR, d.DESIGNATOR FROM MSC_ST_DESIGNATORS s, MSC_DESIGNATORS d WHERE s.DESIGNATOR_ID = d.DESIGNATOR_ID;
• Trace designators to their collection batch:
  SELECT BATCH_ID, COUNT(*) FROM MSC_ST_DESIGNATORS GROUP BY BATCH_ID;
• Report forecast consumption flags by organization.

Related Objects

• MSC_DESIGNATORS — target planning table joined on DESIGNATOR_ID.
• IGS_FI_BILL_ALL — bill-to reference via BILL_ID.
• PN_COMPANIES_ALL — company reference via COMPANY_ID.
• MSC_ST_* staging tables — sibling collection tables populating related planning entities.
• MSC_APPS_INSTANCES / SR instances — source instance resolution via SR_INSTANCE_ID.
• FND_CONCURRENT_REQUESTS — collection program audit via REQUEST_ID.