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 will no longer support LX or BPCS on IBM i 7.2 after April 30, 2021

On September 10, 2019, IBM® announced the end of support of IBM i 7.2 effective April 30, 2021. In line with IBM’s support policy, Infor will no longer support LX, BPCS, SSAEAM, PRMS, BOSS and related products on IBM i 7.2 after April 30, 2021.

All releases, patches, and solutions are expected to be delivered and compiled for IBM i 7.3 effective May 1, 2021. These deliverables should install and function on version 7 release 3 (IBM i 7.3) and above. This will require that your operating system be at a minimum release level of IBM i 7.3.

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

If you have not done so already, we recommend you start planning and completing your upgrade to IBM i 7.3 or above prior to April 30, 2021. After this date, if you register a support call with Infor Support, and your application still runs on IBM i 7.2, 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 Concierge to view and download important information regarding Infor LX, BPCS, and Infor SSAEAM. General KB Articles have been created to proactively provide you with information regarding this Announcement (1397381) and the Infor BPCS/LX Product Lifecycle Policy (1947086).

Previous Article Infor LX & BPCS Tip of the Week: Journal Upload – EGLi
Next Article Infor LN & Baan Tip of the Week LN 10.7 - Draft Printing
Print
43295 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

In the Shop Floor Control Module, you have the ability to key in both direct labor and indirect labor. However you want to establish specific types (reasons) for the indirect labor. The SFC600 labor entry program shows a reason code field, but it is designed for reject quantity and machine downtime reasons, not indirect labor reasons.

There is a way around this. With an MES solution you have the ability to setup and report indirect time against a specific reason code.

You can see the status of the Shop Order when using SFC300 Shop Order Inquiry. You want to be sure that your shop orders are at the correct status in order to report against them.

The following are the shop order status codes:

04 = The Shop order has been entered.

05 = The Shop order has been released and printed.

14 = The Shop order has been released, but not printed. If a shop order is at this status, you have released it and it is not printed due to a system failure, or the order has been put on hold.

XX = The Shop order is closed.

First148149150151153155156157Last

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