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 scenario

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.

Use this session to view the documents linked to a sales contract. You can view these documents only when a sales order line or a sales schedule line is linked to a sales contract line.

Note: 

• You can view this session only if the Contracts check box is selected in the Sales Parameters (tdsls0100s000) session.
• You can use the Linked Document option from the References menu to view the details of a specific linked document.

Field Information

Contract: The code of the sales contract.

Description

Line: The sequence number of the sales contract line.

Sales Office: The code of the sales office.

Description

Linked Document: The document type that is linked to the sales contract line.

Note: This field can be set to Sales Order Line or Sales Schedule Line only.

Allowed values

Linked Document Company: The company in which the document is linked to the sales contract line.

Linked Document: The code of the document that is linked to the sales contract line.

Note: 

• The code of the sales order is defaulted from the Order Line field in Sales Order Lines (tdsls4101m000) session.
• The code of the sales schedule is defaulted from the Schedule field in the Sales Schedule Lines (tdsls3107m000) session.

Linked Document Reference: The reference number of the linked document.

Note: 

• The line number of the sales order line is defaulted from the Line field in the Sales Order Lines (tdsls4101m000) session.
• The line number of the sales schedule line is defaulted from the Line field in the Sales Schedule Lines (tdsls3107m000) session.

Link Sequence: The sequence number of the linked document.

Use this session to adjust the rounding difference transactions, calculated during the internal conversion, for inter-period postings.

Inter-period postings are the postings made to the ledger accounts defined in the Finance Company Parameters (tfgld0503m000) session for fiscal and reporting period changes.

If inter-period postings exist, very big rounding differences are calculated . If you run this session, those rounding differences are replaced with values that properly deal with an observed period change.

If inter-period postings exist, during the internal conversion rounding differences can be calculated for the wrong period. If you run this session, those rounding differences are deleted and the rounding differences are created for the correct period.

FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)

OPERATIONS: Sales Contract Linked Documents (tdsls3506m000)

TECHNOLOGY: Audit Fields by Table (ttaud3125m000)

Imagine being able to ask questions directly to your IBM i data and get answers in real time. In this session, we’ll demonstrate how AI-driven tools can connect with your IBM i, making data analysis faster, more intuitive, and more accessible than ever before.

• Thursday, October 16, 2025

• 1:00-2:00PM US/Eastern

• Presenter: Nick Olson, Crossroads RMC

Register Today: https://ibmi.workoutloud.com/Event/ai-in-manufacturing/Register

Crossroads RMC debuted its new AI-powered NextTrack Insights Analytics Dashboard at Infor’s inPOWER 2025 event in Wisconsin. The latest version lets users chat with their ERP data in plain English—no code, no custom reports, just instant answers.

Built on .NET Core with advanced AI and API integration, the dashboard connects directly to Infor ERP LX, XA, and Db2 for i, delivering real-time KPIs like cycle times, downtime, and equipment effectiveness.

📰 Read the full story on IT Jungle:
Crossroads RMC Shows Off New AI Dashboard at inPOWER 2025 ›

This enhancement modifies the subfile used in MRP320D Master Schedule Detail Inquiry (SCR001) to expand the subfile with data instead of clearing it as the user pages. This update enables full compatibility with the WebTop 4.8 Grid decorator.

To implement this enhancement, request and apply MR 81428.

Functionally, this change only affects how the subfile is populated to support a deployed WebTop Grid. There is no visible change or user impact in how the program operates.

In summary, the enhancement improves functionality and ensures full WebTop Grid support for the