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

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Improve PUR500 Navigation for WebTop Grids

George Moroses 0 3339 Article rating: 5.0

Present PUR500-07 “folded” Purchase Order Line Entry screen as the default Line Entry screen.

Supply Chain Management Enhancements:

WebTop Grid users can personalize the main Purchase Order Line Entry screen to resequencing columns, sort and filter on data values, change column headings, and other features.

In LX 8.4.2, the PUR500-07 “folded” screen is the default Purchase Order Line Entry screen presented to the user. Users can still access the “unfolded” PUR500-06 screen with limited fields displayed, on request.

Quality Management Systems (QMS)

George Moroses 0 1528 Article rating: 5.0

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?

Infor LX/BPCS Tips & Tricks for EXECUTIVES

George Moroses 0 1876 Article rating: 5.0

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

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

Kathy Barthelt 0 4439 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 3511 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...

First2345791011Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES:

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

  • Select the Quantity-dependent Routing check box in the Item - Production (tiipd0101m000) session.

  • Enter the routing codes in the Item - Routings (tirou1101m000) session. Enter the maximum quantity for which a routing is valid in the Up to Quantity field.

Note: If multisite functionality is activated, the routings available may vary per site on the job shop bill of material selected. Differences in routings have an impact on the standard cost calculation.

Default routing

If the Quantity-dependent Routing check box is not selected, the default routing applies to an item. However, this default routing must also be linked to the item. To find out, LN checks the default routing code in the Default Routing field of the Job Shop Master Data Parameters (tirou0100m000) session. Next, LN checks whether the default routing code is linked to the item in the Item - Routings (tirou1101m000) session. If so, the default routing applies to the item. If the default routing is not linked to the item, no routing is used.


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.

  • The destination financial company.

  • The transaction type and series.

  • The ledger account and dimensions.

  • The transaction currency.

  • The fiscal year and the financial period, the tax period, and the reporting period.

  • The integration document type and the Debit/Credit indicator.

  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

 
TECHNOLOGY: Infor LN Rest API

Frequently Asked Questions (KB2316174)

For Infor LN a framework has been developed to support REST API-based services for lean integrations. This framework is now made available for the LN application. This KB answers some common questions you may have and procedures that are needed for using the LN Rest APIs.

More details on these topics can be found in the Infor LN REST API Administration Guide.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Ledger Account Blocked Error
Print
30437 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories