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
21173 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Note: The Blocked Operations (tisfc0540m000) session displays the blocked operations.

Introduction

Sometimes a problem occurs that must be solved before an operation proceeds. Examples of such situations are:

  • The quality of an intermediate product must first be inspected.
  • A machine is in repair.
  • A supplier cannot deliver an essential component in time.
  • A customer is late with its payments.

In these situations the operation can get the operation status Blocked.

An operation can be blocked:

  • Manually.
  • Automatically by Quality.

Blocking reasons

Every blocked operation must have a blocking reason. The blocking reason of a blocked operation has two purposes:

  • To indicate why the operation is blocked.
  • To determine which actions you can no longer perform on the operation.

Types of blocking

The following actions can be blocked by means of a blocking reason:

  • Reporting a quantity completed.
  • Reporting a quantity rejected.
  • Reporting a quantity to be inspected.
  • Reporting an operation completed.

You normally carry out these actions in the Report Operations Completed (tisfc0130m000) session.

You can define blocking reasons in the Blocking Reasons (tisfc2100m000) session.

Manual blocking

Use the Report Operations Completed (tisfc0130m000) session to block an operation. When you block an operation, you must also enter a blocking reason. If Quality has already blocked the operation, you can only enter a blocking reason, which is more restrictive than the blocking reason of Quality.

Blocking by Quality Managem

Categories