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
1917 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

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

  • The quality of an intermediate product must first be inspected.
  • A machine is in repair.
  • A supplier cannot deliver an essential component in time.
  • A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

  • Manually.
  • Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

  • To indicate why the operation is blocked.
  • To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

  • Reporting a quantity completed.
  • Reporting a quantity rejected.
  • Reporting a quantity to be inspected.
  • Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Managem

Categories