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
43354 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

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders. For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In ERP LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period. For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

You can add safety time in the item master for the item. This will add the number of days safety time to the order lead time thus bringing the order in x number of days early. (x is the safety time).

The safety time is on form 4 of the item master in Baan IV and in Item Ordering Data – Generation I tab in Baan V and LN.

First146147148149151153154155Last

Theme picker

Categories