Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

CASE STUDY: Navigating an ERP Upgrade with Outdated Knowledge

The Problem: Knowledge Gaps in a Legacy ERP Environment

For organizations running long-established global ERP systems such as Infor Baan or LN, upgrades can be daunting. Over the years, employee turnover, internal role changes, and evolving business structures often erode institutional knowledge of the original ERP setup.

When the time comes to upgrade, teams frequently lack a clear understanding of how the system is currently being used. This knowledge gap leads to inefficient planning, costly rework, and missed opportunities for process optimization.


The Solution: A Blueprint-Based Assessment and Optimization Strategy

To address this challenge for one of our LN customers, we implemented a blueprint-driven assessment designed to provide a clear, data-backed foundation for their ERP upgrade.

Our strategic approach focused on objective comparison and actionable insight, using a step-by-step methodology:

  1. Benchmarking Against a Standard Blueprint
    We created a standard LN functionality blueprint representing the ideal model of available processes and best practices.

  2. Site-by-Site Analysis
    Each customer site’s configuration and usage were compared to the standard blueprint, identifying gaps, customizations, and inefficiencies.

  3. Efficiency and Optimization Reporting
    The comparison highlighted workflow inconsistencies and process variations across sites, enabling targeted optimization and standardization.

  4. Budgeting and Roadmap Development
    The results provided a data-driven foundation for budgeting, along with a clear, prioritized roadmap for the upcoming upgrade.


How the Solution Was Implemented

Our multi-phase execution ensured collaboration, accuracy, and adoption at every level:

  • Stakeholder Engagement
    We engaged Business Process Owners (BPOs) and Subject Matter Experts (SMEs) from each site to review and validate existing LN processes.

  • User Acceptance Testing (UAT)
    End-users participated directly in creating and testing UAT scenarios based on real-world workflows, ensuring relevance and usability.

  • Defined Project Plan and Cadence
    A clearly defined project plan with consistent milestones and review cycles ensured timely delivery and transparency.

  • Performance Metrics
    We established Key Performance Indicators (KPIs) to track progress, efficiency, and completion throughout the project.

  • Workshops for Optimized Usage
    Targeted workshops demonstrated how to leverage LN’s current capabilities more effectively and prepared users for upcoming version enhancements.

  • Post-Project Review
    A comprehensive retrospective identified additional areas for continuous improvement and long-term efficiency gains.


The Long-Term Value

This blueprint-based ERP assessment delivers long-term strategic benefits beyond the immediate upgrade:

  • Provides a clear understanding of current ERP usage across all locations.

  • Establishes a baseline for continuous improvement and standardization.

  • Enables data-driven budgeting and decision-making for future projects.

  • Reduces risk and complexity during upgrades through informed planning.

Whether conducted internally or with an experienced partner, this type of structured evaluation is a critical step for any organization preparing for an ERP upgrade. It transforms uncertainty into clarity, and sets the stage for ongoing optimization and success for years to come.

Contact Crossroads RMC to get started: 800.762.2077

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Audit Fields by Table (ttaud3125m000)
Next Article Important Update: Infor's Plan to phase out LN embedded EDI module (ECEDI/BEMIS)
Print
18 Rate this article:
5.0

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories