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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

You may be wondering if it's necessary to have separate item codes for incoming and outgoing subassemblies.

No, it is not necessary to have separate item codes for incoming and outgoing subassemblies, but it is recommended. In theory, you could have only one item code with the description subassembly and use the same item code for the outgoing subassembly and for the incoming subassembly. However, when monitoring inventory movements and financial integration transactions, it will be difficult to understand the process. Also, the costing logic is much clearer when different item codes for the incoming and outgoing subassemblies are used. Because of this, it is advised to use a different item code for the outgoing subassembly and a different item code for the incoming subassembly.

First1718192022242526Last

Theme picker

Categories