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

Important Update: Infor's Plan to phase out LN embedded EDI module (ECEDI/BEMIS)

Kathy Barthelt 0 848 Article rating: 5.0

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.

 

CASE STUDY: Navigating an ERP Upgrade with Outdated Knowledge

Kathy Barthelt 0 788 Article rating: 5.0

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

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Audit Fields by Table (ttaud3125m000)

Kathy Barthelt 0 803 Article rating: 5.0

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.

Infor LN & Baan Tips & Tricks for OPERATIONS: Sales Contract Linked Documents (tdsls3506m000)

Kathy Barthelt 0 546 Article rating: 5.0

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: The description of the sales contract

Line: The sequence number of the sales contract line.

Sales Office: The code of the sales office.

Description: The description of the Sales Office

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.

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.

Infor LN & Baan Tips & Tricks for FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)

Kathy Barthelt 0 457 Article rating: 5.0

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.

JOIN WEBINAR: Chat With Your IBM i Data

Thursday, October 16 2025 --- 1:00-2:00pm US/Eastern

Nick Olson 0 589 Article rating: 5.0

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 Shows Off New AI Dashboard at inPOWER 2025

📰 Read the full story on IT Jungle

Nick Olson 0 462 Article rating: 5.0

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 ›

12345678910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Manufacturing Tip: All About Routings

The planning data for the method of manufacturing is defined in Routing. A routing consists of operations, with each operation identifying the last to be carried out in a work center and/or on a certain machine defined for a specific site.

Routings can be as follows:

  • Standard Routing - A generic routing that can be attached to multiple items
  • Item specific - A routing that is applied to one item
  • Network routing - A routing containing sequentially ordered operations and parallel operations
  • Order quantity dependent routing - A routing that is defined for a specific quantity of items

You use the Routing module to record routings for manufactured items. You can define the following:

Work centers - A work center is where production activities are performed. Resources, such as people and machines, are linked to a work center. A work center is a group of resource units used as a functional planning unit. The operation rate code, which is linked to the work center, is used to calculate the standard cost of an item or the estimated and actual costs. The capacity load on a work center is used in the planning of production. Work centers can be part of enterprise units used for multi-company modeling purposes.

Machines - Machines are linked to work centers and are used to plan operations. The rate defined for a machine is used to calculate the actual machine costs. The capacity load on a machine is used for production planning.

Reference operations - Classified according to the nature of the work performed, reference operations are used to describe activities that take place in the job shop. Reference operations are linked to operation rate codes, which are used to calculate the standard cost of an item or the estimated and actual costs. Reference operations are used in production planning.

Operations - The operation data for standard and customized manufactured items is maintained with operations. Operation data is stored and maintained for standard items and customized items. A series of operations are performed to manufacture an item. The sequence of operations is defined as a routing in operations. Yield and scrap are defined per operation.

Norm times - The run time and production rate of an operation are determined using norm tables. After a matrix is defined for two physical characteristics, such as length and width you can maintain a set of standard operation times for the X-Y coordinates. When tasks and routings are defined, the run time and production rate can be calculated by using a norm table.

Skills - Certain skills may be mandatory to perform a specific operation. To ensure employees assigned to an operation possess the necessary knowledge, skills are linked to both employees and operations.

Previous Article Infor LN & Baan Tip: Deleting Records
Next Article Infor LN & Baan Finance Tip: What Can You Do in the Financial Statements Module?
Print
65984 Rate this article:
4.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories