Where Can You Find Epicor MRP Log Information?
Start in the Epicor application and identify the MRP process or planning activity associated with the result you want to investigate. Depending on the version and configuration, the relevant details may be available through process monitoring, system activity, or the interface used to launch planning. Menu names and available options can vary, so use the navigation and documentation specific to your environment.
If the application does not expose the required details, an authorized system administrator can determine whether additional server-side logs are available. In hosted environments, access to operating-system directories may be managed by the hosting provider, while on-premises installations may use administrator-configured server locations.
- Application-level messages: Review messages and process details associated with the MRP run.
- Process monitoring: Identify the relevant execution, status, and available diagnostic information.
- Server-side logs: Ask an administrator to check applicable service or application logs when deeper technical information is required.
- Hosted environments: Follow the provider's supported process for retrieving logs that are not directly accessible to users.
How to Identify the Correct MRP Log
Several planning runs may occur close together, especially when planners adjust demand, inventory, or planning parameters and run MRP again. Match the log to the correct execution before interpreting its messages. Record the company, plant, date and time, user or process identifier where available, and the planning horizon.
Next, connect the log to the business result under investigation. If a component appears to be short, compare the planning output with its inventory balance, allocations, open purchase orders, job supply, and demand dates. This helps establish whether the recommendation reflects the underlying records or warrants a closer review of the planning configuration.
The Mrp Module uses planning inputs to calculate material requirements and propose supply actions. Its output is influenced by Mrp Demand, inventory availability, lead times, order policies, and other configured parameters. Reviewing the relevant log alongside these inputs provides a more complete view than relying on a single message.
Application Logs Versus Physical Log Files
Application-level messages and physical log files serve related but different purposes. Application messages help users understand process status and planning outcomes. Physical logs may contain technical details about services, execution, or application behavior that administrators use for diagnosis.
These sources should not be treated as interchangeable. A message displayed in the application does not necessarily correspond to a standalone file named for MRP, and the file path may differ between environments. Avoid assuming a universal folder or filename. Instead, confirm the relevant process, deployment configuration, and supported logging method with your Epicor administrator.
Because Epicor ERP connects planning with purchasing, inventory, production, and other operational records, log investigations should also verify the associated transactions in the appropriate screens. This keeps the technical finding aligned with the actual material and supply position.
Common Reasons to Locate an MRP Log
Teams typically look for MRP log information when a planning run does not produce the expected result or when they need to document what happened during execution. A repeatable investigation process helps distinguish input-data changes from planning-parameter changes.
- A purchase suggestion is missing or differs from the expected quantity.
- A planned job or rescheduling recommendation needs explanation.
- Changes to demand, inventory, lead time, or order policy affect planning output.
- An administrator needs to investigate a process status or technical message.
- Operations needs traceability between a planning run and a purchasing or production decision.
When finance and operations teams extend epicor through ERP integration, keeping process identifiers and supporting records consistent can also improve traceability across connected workflows. For related finance processes, How Hyperbots AI Agents 10x Epicor Finance Operations discusses customer payment matching, remittance processing, unapplied cash, deductions, and receipt posting. Closing Epicor Finance Gaps with Hyperbots AI Agents explores additional ways to extend these payment and posting workflows around Epicor. For finance leaders reviewing compensation information, the Director of Finance Salary Benchmark Report provides educational context on salary ranges and compensation drivers across industries, company sizes, and locations.
Access, Automation, and Review Practices
Use the access level appropriate to the investigation. Planners can usually begin with the information available in the application, while deeper technical logs may require administrator assistance. Record the run identifier, relevant messages, related transactions, and the action taken so another team member can reproduce the review.
The Hyperbots Platform supports company-specific configurations for ERP integration, workflows, roles, and general ledger structures through a no-code framework. Process Specific Capabilities support domain-trained automation across defined workflows, while Ready to Deploy Capabilities provide pre-trained agents, pre-built ERP connectors, and configurable finance processes.
Self Learning Capabilities enable co-pilots to learn from human actions and refine workflows through inference-time learning. With Human in the Loop oversight, exceptions can be routed for review, approval workflows supported, and human feedback incorporated into subsequent handling. These capabilities can support connected finance workflows, while Epicor's own configuration and administrator guidance determine where MRP log information is stored and how it can be accessed.
Summary
The location of an Epicor MRP Log depends on the deployment, application version, permissions, and logging configuration. Begin with the MRP process details available in the application, then work with an authorized administrator to locate server-side logs when needed. Matching the correct run to demand, inventory, supply transactions, and planning settings helps teams investigate recommendations and maintain clear operational traceability.