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 283 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 375 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 1636 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 1477 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 2565 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: Considerations for Release to Warehousing for a Cost Item

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider. Below is some information gathered from various KBs related to the impact of having release to Warehousing applied (or not). KBs used as reference are listed as “– REF: KB XYZ”. Editing the checkbox “Release to Warehousing” itself If there is a Sales Order (in status Free is enough) for a Cost Item, the check box is not editable. As soon as all the Sales Orders for which the Item is involved are Closed (or Canceled or Deleted) the check box becomes editable again. – REF: KB 1439313 & KB 1613780 Simultaneous/separate release to Warehousing with Physical Items In a scenario where a Cost Item (that is released to Warehousing) and a physical Item are released to Warehousing separately, then the shipment confirmation of each of these Items will occur separately. If they are released simultaneously, the shipment of the Cost Item will not be processed unless and until the physical Item is ready to be shipped. – REF: KB 1449001 Note: Ensure a Warehouse is added to Order Lines to ensure Release to Warehousing Activity is applicable. – REF: KB 2229767 Invoicing

To invoice them separately or together, factors to consider are:

  • Composing Criteria, a list of fields that need to match to have a single invoice created – REF: KB 717977
  • Invoicing Methods (tcmcs0555m000) in the General tab, select Combine, for example, Shipments, to combine different Shipments of the same Sales Order into one Invoice. This Invoicing Method is also defined in
  • Invoice-to role of a Business Partner (tccom4112s000) in the Invoicing tab. – REF: KB 812637
  • For a Return Order where a Cost Item and a Physical Item were originally invoiced together, to invoice them together again, consider using Original Document type = Invoice and link the original Invoice to the Return Order. – REF: KB 2072847 

Note: Consider solution in KB 2108605 if Composing Criteria is met, yet still Credit Notes are not combined for a Return Sales Order copied from original Sales Order for one Physical Item and one Cost Item without release to Warehousing. 

ASN ASN cannot be generated for Purchase Order Lines with Cost Item if not released to Warehousing. – REF: KB 1548301 & KB 2111341 Intercompany Trade Intercompany Trade can be applied for a Cost Item that is released to Warehousing, as Intercompany Trade needs a Warehouse and a Department. – REF: KB 2112430 Customs Value Cost Items that are released to Warehousing that are handled via normal Sales Order Lines are considered as delivered goods and will get the customs value assigned like other Items being subject to warehouse handling. Cost Items handled on Shipment Lines as "Additional Cost" are not considered as delivered goods but as pure costs. The customs value of these shipment lines gets defaulted with a zero amount and cannot be modified. The same applies to additional costs on sales order lines. – REF: KB 1600847 Freight  Cost Items cannot be used for Freight handling. – REF: KB 1830170 Additional Cost

  • For automatically generated Additional Costs in Sales Orders, Cost Items that are released to Warehousing are not released to Warehousing. This is because automatic Additional Costs are always generated with 0 quantity, therefore only the amount is filled for these Lines, which leads to the Delivery Type being set to Sales and not Warehouse. As a result, delivery must take place in Sales module. – REF: KB 1995781
  • For Additional Cost Lines added to Shipment for Cost Items, refer to KB 2236856.

Intrastat Record When using Cost Items without release to Warehousing, there is no shipping data within Invoicing. Therefore, the corresponding Intrastat record cannot be found during the printing of the Invoice. To get the Invoice data filled on the Intrastat record, Cost Items with release to warehousing should be used. Otherwise, session Update Intrastat Transactions with Invoicing Data (tccom7271m100) should be ran to update the Invoicing data in Intrastat. – REF: KB 2005482

Previous Article Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?
Next Article Infor LN & Baan Tip: Cash Flow Functionality and Setup
Print
59110 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories