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

A Quality Management System (QMS) provides airtight validation of your product testing requirements, protecting both your business and your customers.

Benefits of Using QMS

1. Permanent Recordkeeping: Test results can be securely archived and accessed indefinitely.

2. Regulatory Compliance: Meets all industry and government testing standards and requirements.

Who Uses QMS?

• Pharmaceutical Manufacturers

• Health Product Manufacturers

• Chemical Manufacturers

• Food & Beverage Producers

• Government Contractors
  …and many others.

What Does a Typical QMS Engagement Look Like?

Operations: Infor Business Context Messages (IBC) are now supported from ORD700D1 Order Entry - Fast Line Entry screen

Finance: Tax Code Table window (WINZRTD)

Technology: Improve PUR500 Navigation for WebTop Grids

Please be aware that the Infor LN embedded EDI module (ECEDI/BEMIS) will transition to sustaining maintenance in the second half of 2027. This feature has not received enhancements in recent years, and no future updates are planned.

Existing customers using the embedded EDI module are encouraged to transition to EDI Exchange or Automotive Exchange, in order to benefit from ongoing enhancements and future capabilities. Infor has invested significantly in EDI Exchange and Automotive Exchange to support a broad range of EDI communications with external parties, as part of continued innovation within Infor LN Cloud.

For new LN CE customers, the embedded EDI module will no longer be provisioned.

Action steps
For more information please see Knowledge Base (KB) article 3632427.
 

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

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.