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

Quality Management Systems (QMS)

George Moroses 0 296 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 385 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 1668 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 1494 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 2610 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.

135678910Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: All About Invoicing Methods

Invoicing Methods are a set of parameters that define the types of orders and order lines that can be collected on an invoice, the type of invoice to be generated and the costs to be aggregated on Project invoices and Service invoices.

If options to combine tax codes, departments, sales representatives' line of business area, etc... are checked, LN will combine all available transactions ready to be invoiced that have different tax codes departments, sales representatives, etc...into only one invoice.

If options to combine sales orders, sales order types, and shipments are checked then all sales orders that are created for the same business partner where the shipment and/or sales order type is different will be combined into one invoice.

For example:

  1. If sales order SLS001 is created for BP BP1000 with 2 lines where each line has a different shipment number, and the invoice method is combining shipments, both lines will be part of the same invoice. If the option to combine shipments is not checked then LN will create an invoice per shipment.
  2. If sales order SLS001 is created for BP BP1000 with 2 lines and 2 different shipment numbers and sales order SLS002 is created for the same BP with a cost item, LN will create one invoice for both orders if the option to combine sales orders and shipments is checked. If only the option to combine sales orders is checked then 3 different invoices will be created as all 3 lines will have different shipment numbers. If they have different sales order types and this option is not checked on the invoice method session then also 3 invoices will be created but if it is checked along with sales order and shipment number then only one invoice will be created.
  3. If we take scenario 1 again and both lines have different tax codes and the option to combine tax codes is not selected then LN will create a separate invoice for each line based on the tax code.
     

Note: In the case that the Business Partner Tax Country is different, even if we select combine tax codes, the system will create a separate invoice based on the Business Partner Country to full the statutory compliances for that BP country.

Previous Article Infor LN & Baan Tip: Cash Flow Functionality and Setup
Next Article Infor LN & Baan Tip: Why was the session "General Ledger Diagnostics Workbench" built?
Print
60470 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories