Search Results mrp_files




Overview
Explore in AI Chat

Overview

The MRP_FILES table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It functions as a system-level registry for tracking the names and types of output files generated by the planning engine during a Material Requirements Planning (MRP) or Master Production Schedule (MPS) run. Its primary role is to maintain a controlled association between a specific planning instance, identified by a compile designator and organization, and the various data files produced for planner review and analysis. This structured logging is essential for auditability, troubleshooting, and ensuring planners can locate the correct output from their planning processes.

Key Information Stored

The table's structure is defined by a concise set of columns that uniquely identify a file within the context of a plan. The primary key consists of three columns: ORGANIZATION_ID, which specifies the inventory organization; COMPILE_DESIGNATOR, which identifies the specific MRP or MPS plan name; and FILE_TYPE, which categorizes the output file. While the exact list of FILE_TYPE values is not detailed in the provided metadata, typical examples in MRP include reports such as the MRP Detail Report, Planned Order Report, or Exception Messages Report. The table presumably contains at least one additional column to store the actual physical file name or path, though this specific column name is not listed in the excerpt.

Common Use Cases and Queries

The primary use case is to programmatically or manually determine what output files exist for a completed plan. This is critical for post-processing, archival, or generating direct links to report outputs from custom front-ends. A common query would retrieve all files for a specific plan to present to a user. For instance, to list all output files for the 'MASTER_PLAN' in organization 204, a developer might use: SELECT file_type, <file_name_column> FROM mrp.mrp_files WHERE organization_id = 204 AND compile_designator = 'MASTER_PLAN';. Another typical scenario involves data purging scripts, which might join to this table to identify and clean up obsolete physical files when their associated plan data is purged from the system.

Related Objects

As documented in the provided foreign key metadata, MRP_FILES has a direct and fundamental relationship with the MRP_PLANS table, which is the master definition table for all plans in the system. The relationship is established through a composite foreign key on (ORGANIZATION_ID, COMPILE_DESIGNATOR). This ensures that every record in MRP_FILES corresponds to a valid, defined plan in MRP_PLANS. Consequently, any join to retrieve plan details (like plan type or description) for a file would use these columns. For example: SELECT mp.compile_designator, mp.description, mf.file_type FROM mrp.mrp_plans mp, mrp.mrp_files mf WHERE mp.organization_id = mf.organization_id AND mp.compile_designator = mf.compile_designator;.