Search Results msc_st_visits




Overview
Explore in AI Chat

Overview

MSC_ST_VISITS is a staging table within the MSC schema (Advanced Supply Chain Planning) in Oracle EBS 12.1.1 and 12.2.2. In the Oracle Advanced Supply Chain Planning collection architecture, the MSC_ST_* family of tables serves as the transient landing zone for source data extracted from external and adjacent EBS modules before it is validated, transformed, and loaded into the planning engine's operational tables. MSC_ST_VISITS specifically stages visit, appointment, and scheduling-related records sourced from the Oracle Advanced Scheduler / visits model, exposing 30 documented columns in the 12.2.2 schema.

The table carries a heuristic Data Vault classification of standalone, meaning the FK-mining process identified no inbound or outbound parent-child relationships among the MSC planning tables other than a single reference to AHL_VISITS_B. In Data Vault terms this suggests the object behaves as a staging or standalone satellite rather than a true hub or link; it is best modeled as an append-only staging artifact keyed by a surrogate identifier rather than as a durable business entity.

Key Information Stored

The surrogate primary key is VISIT_ID, which also functions as the foreign-key bridge to AHL_VISITS_B.VISIT_ID, the visits base table. Natural business-key candidates visible in the schema include VISIT_NAME and VISIT_NUMBER, both of which are conventionally unique within a source instance and are typically qualified by SR_INSTANCE_CODE or the surrogate SR_INSTANCE_ID to enforce cross-instance uniqueness.

Standard audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are present as expected for an EBS-owned staging table.

Common Use Cases and Queries

The dominant use case is diagnosing collection failures. Planners and technical consultants query rows where PROCESS_FLAG indicates error status to inspect ERROR_TEXT and MESSAGE_ID:

  • SELECT VISIT_ID, VISIT_NAME, PROCESS_FLAG, ERROR_TEXT FROM MSC_ST_VISITS WHERE PROCESS_FLAG = 'E';
  • Scoping a refresh run: SELECT * FROM MSC_ST_VISITS WHERE REFRESH_ID = :refresh_id;
  • Reconciling staged data against the base table on VISIT_ID to confirm successful load.
  • Reporting on visit volume by ORGANIZATION_CODE and VISIT_STATUS within a date range using VISIT_START_DATE.

Batch-level auditing uses BATCH_ID and ST_TRANSACTION_ID to trace which extraction job produced a given row.

Related Objects

The documented FK relationship anchors this object to the Oracle Advanced Scheduler base table:

  • AHL_VISITS_B — joined on MSC_ST_VISITS.VISIT_ID = AHL_VISITS_B.VISIT_ID; the authoritative source of visit records.
  • Adjacent MSC_ST_* staging siblings (for organizations, resources, and scheduling data) loaded by the same collection programs.
  • MSC planning operational tables that receive promoted visit data after validation.
  • EBS concurrent program and refresh metadata objects referenced by REQUEST_ID, PROGRAM_ID, and REFRESH_ID.

Because the heuristic classification is standalone, no other MSC-resident parent or child tables were mined; integrations should rely on the documented AHL_VISITS_B link and the surrogate VISIT_ID as the stable correlation key.