Search Results msc_files




Overview
Explore in AI Chat

Overview

The MSC_FILES table is a core data object within the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. As indicated by its description, it is responsible for storing file names used by the planner. This table functions as a metadata repository for files generated or utilized during the planning cycle, such as input data extracts, output reports, log files, and other planning-related documents. Its primary role is to maintain a controlled reference of these files, linking them to specific planning instances to facilitate tracking, auditing, and management of the planning process artifacts within the ASCP engine.

Key Information Stored

While the provided ETRM excerpt does not list specific columns, the documented foreign key relationship provides critical structural insight. The table's key stored information revolves around file metadata and its association with a planning run. The most significant column is PLAN_ID, which is a foreign key to the MSC_PLANS table. This column is essential for linking every file record to a specific planning instance. Other typical columns in such a table would include a unique FILE_ID, the FILE_NAME, FILE_TYPE (to classify the file's purpose, e.g., 'LOG', 'OUTPUT', 'INPUT'), CREATION_DATE, and potentially a column for the physical file path or a reference pointer. The data stored enables administrators and planners to identify all files associated with a particular plan execution.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting planning runs. Database administrators and functional consultants query this table to locate log files for error analysis or to archive planning outputs. Common SQL patterns involve joining to the MSC_PLANS table to filter by plan name or execution date.

  • Finding files for a specific plan: SELECT f.file_name, f.file_type FROM msc_files f, msc_plans p WHERE f.plan_id = p.plan_id AND p.plan_name = 'MY_PRODUCTION_PLAN';
  • Identifying log files from recent plan runs: SELECT p.plan_name, f.file_name, f.creation_date FROM msc_files f, msc_plans p WHERE f.plan_id = p.plan_id AND f.file_type LIKE '%LOG%' ORDER BY f.creation_date DESC;

These queries are fundamental for managing the file system artifacts of the planning engine and ensuring proper cleanup or retention of planning data.

Related Objects

The most directly related object, as explicitly documented, is the MSC_PLANS table. The foreign key constraint (MSC_FILES.PLAN_ID references MSC_PLANS.PLAN_ID) establishes a strict dependency where a file record must be associated with a valid plan. This relationship is central to the table's purpose. While not listed in the excerpt, other objects likely to interact with or reference MSC_FILES include the planning engine's concurrent programs and internal APIs responsible for generating and registering plan output files. The table may also be referenced in standard ASCP purge scripts to remove file metadata when old planning data is cleared.