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

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: Support for IBM i 7.3 and Infor LX Products

On September 30, 2022, IBM® announced the end of support of IBM i operating system 7.3 effective September 30, 2023. In line with IBM’s support policy, Infor will no longer support LX and related products on IBM i 7.3 after May 31, 2024. All Infor LX releases, patches, and related solutions are planned to be delivered and compiled at IBM i 7.4, effective June 1, 2024. These deliverables will install and function on version 7 release 4 (IBM i 7.4) and above. This will require that your operating system is at a minimum release level of IBM i 7.4.

This policy extends to other Infor LX-related technologies including WebTop, System i Workspace (SiW), and Infor Development Framework (IDF).

Action Steps If you have not done so already, we recommend that you start planning and completing your upgrade to IBM i 7.4 or above prior to June 1, 2024. After this date, if you register a support call with Infor Support, and your application still runs on IBM i 7.3 or older, you may be requested to upgrade to a supported version of the IBM i operating system.

In addition, we invite you to log on to Infor Support to view and download important information regarding Infor LX. Knowledge Base (KB) articles have been created to proactively provide you with information regarding this Announcement. ​Please consider clicking on the “Subscribe” feature within each KB article to receive notifications. Once you have subscribed, you will receive notifications when they are updated.

  • View KB article 1397381 | Infor LX Product Bulletins and Announcements
  • View KB article 1947086 | Infor BPCS/LX Product Lifecycle Policy


If you need assistance in planning this project, Crossroads RMC is happy to help you strategize, and create project plans, test plans, 3rd party product due diligence, and cutover assistance. Contact us today to learn more. 800.762.2077  | solutions@crossroadsrmc.com

Previous Article Have You Heard About the Latest & Greatest Way to BOOST Productivity?
Next Article Infor LN & Baan Tip: Serialized Controlled Item >> to >> Non-Serialized Controlled item
Print
13262 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

EGLi provides Infor LX Configurable Enterprise Accounting (CEA) functionality including Advanced Transaction Processing (ATP), a configurable ledger, and batch transaction processing in the IDF architecture.

EGLi is a complete replacement for CEA. Infor LX applications integrate with EGLi, and subsystem transactions generated in Infor LX are used to create journal entries in EGLi. The Infor LX integration system parameters allow you to specify whether CEA or EGLi is your primary financial product.

We recommend that you select CEA while you test the integration. The primary financial product flag and the CEA migration programs are designed to assist existing CEA clients with their implementation of EGLi. Journals are produced in both GL systems so you can verify that the data in both GL systems are the same. This integration includes migration programs that copy your existing CEA files to corresponding EGLi files. After you run the migration programs, EGLi should be configured and ready to use. If you are already running IDF via Ming.le or SiW, before you install EGLi, you will need to see the Ming.le integration guide for instructions on how to export EGLi tasks from IDF to SiW/Ming.le.

Learn More > Infor LX Integration Guide for Enterprise General Ledger

  • Control Date Lead Times – LX provides five separate Control Date Lead Time fields so you can specify additional lead time values for Shop Orders, Purchase Orders and Planned and Firm Planned orders. Each Control Lead Time Date represents additional time (days) required at each step in the process that needs more time (Quarantine, Stabilize), that is to say, when a component is due, and when it can be used. (working with an aerospace  precision bearing manufacturer, I had to account for the QA requirement that no measurements could be taken until the parts had been “soaked” (stored) in an atmospheric controlled environment (72 degrees, and controlled humidity) for 24 hours. This requirement added one full day of lead time between each machining operation) The MPS/MRP Generation program, as well as programs that Shop Order Material Allocation records use the five control date lead times to adjust component required dates to function in the same way as the BOM Offset Lead Time.
     
  • All programs that create MRP Planned Orders, MRP Firm Planned Orders, Shop Orders, and Purchase Orders call the Control Date Calculation program (MRP515B) to establish all five control dates. A Control Lead Time Date is used to adjust the component Required Dates data in the Material Requirements file (KMR), based on planned orders for a parent, and the FMA Required Dates data, based on shop order release dates for a parent.
First5859606163656667Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories