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

Infor LN & Baan Tip: The ABC’s & 123’s of Serialized Items
Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: The ABC’s & 123’s of Serialized Items

A serialized item is a physical occurrence of a standard item that is given a unique lifetime serial number. This enables tracking of the individual item throughout its lifetime, for example, through the design, production, testing, installation, and maintenance phases. A serialized item can consist of other serialized components.

In Service, a serialized item can be a customer-specific or owner-specific installation. Installation groups are a group of installations/serialized items such as photocopiers, computers, air conditioners, forklifts, lathe machines, and even aircraft.

A serialized item is identified by both the item code and serial number. You can set up the mask used to generate the serial numbers so the serial number includes some fields of the item data, such as the item group and the manufacturer.

In a multi-company structure, the companies can share the serialized item data. All the service departments in the various companies can refer to the same serialized items.

The serialized item can originate from a sales order or a project. The details of a serialized item indicate their origin, for example, by using specific sets of serial numbers for items that originate from sales orders and from projects. Serialized items can also originate from an as-built structure or directly from the production bill of material in Manufacturing.

In Service, serialized items can start their respective life cycles in As-Built mode or As-Maintained mode. Each serialized item, with or without its installation group, can be covered by a service contract or a warranty.

The serialized item status

Serialized items can be status controlled. Each serialized item can have the following status:

  • Startup - The serial number has been assigned, but the item is not yet included in a service order or contract. You can only change the status to Active.
  • Active - The serialized item is part of a service order or contract. You can only change the status to Revision.
  • Revision - You can only change the status to Active.


Serial numbers

A unique serial number is assigned to every manufactured item or purchased item. The serial number is assigned to track the item in its life cycle. You can define a dummy serial number for an item. The dummy serial number is a temporary number and can be used to monitor the item until a permanent number is assigned. For each serialized item, you can define an alternative serial number for customer reference. You can use the alternative serial number to search for items when you register calls, create service order activities, or register parts lines for a maintenance sales order.


Serialized item groups

You can group serialized items by serialized item groups. A serialized item group is a group of serialized items with similar features. You can define the serialized item groups that you need, for example, to categorize the skills required for the maintenance of the items, or as a basis for enquiries and reporting. For example, you can select service engineers on the basis of their skills for a specific serialized item group.


Serialized items in physical breakdown structures

Serialized items are the building blocks of physical breakdown structures. A physical breakdown structure is the relationship definition of a set of serialized items with their underlying parts and assemblies. Some serialized items, such as a photocopier, have a simple structure whereas other serialized items such as a ship or an aircraft have a complex structure.

A top serialized item occurs at the highest level in the physical breakdown structure, while the underlying structure consists of assemblies that are either effective or outdated. Use the Tree View option to display a graphic view of the structure.

Each serialized item in the breakdown can be linked to a functional element, with a common function across the entire structure, and can be used to group serialized items based on the functional importance.

Previous Article Infor LN & Baan: Customizing Shipping Labels for All Customers
Next Article Infor LN & Baan Tip: Outbound Order Lines
Print
26478 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories