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
49546 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Categories