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

Infor LX/BPCS Tips & Tricks for EXECUTIVES

OPERATIONS:
Shelf Life Days and Retest Days
This feature provides the ability to enter information in the shelf life days and retest days fields for non-QMS lot controlled items, even when the QMS product is installed. The purpose of this enhancement is to allow the user to enter information for non-QMS lot controlled items even when QMS is activated in Parameters Generation, SYS800D.

In previous versions, when QMS was activated, the Shelf Life Days and Retest Days fields in Facility Planning Maintenance (MRP140) and Item Master Maintenance (INV100) were not maintainable for non-QMS lot controlled items.

FINANCE
Inventory Transaction Post to G/L by Cost Type
This enhancement provides a method to post material, labor, and overhead values on inventory postings to the general ledger to meet financial reporting requirements. The solution provides an optional further breakdown of cost by cost bucket using the new G/L Cost Type.

TECHNOLOGY:
Role-Based Security
Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

Previous Article Infor LX/BPCS Tips & Tricks for OPERATIONS: Shelf Life Days and Retest Days
Next Article Infor LX/BPCS Tips & Tricks for FINANCE: Inventory Transaction Post to G/L by Cost Type
Print
4551 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

There has been a recent porting set change due to Infor’s Product Life Cycle Policy.  

How to determine the maintenance stage of an Infor LN product version and release

Before a customer starts deploying Porting Set 9.4a or a later release, they must determine the actual maintenance stage of their Baan / Infor LN product. The definition of the maintenance stages for the product versions and releases of all versions of Baan and Infor LN are outlined in the Product Support schedule as published in the PLC policy. The maintenance stage of the ERP version is either “Mainstream Maintenance”, “Extended Maintenance” or “Sustaining Maintenance”.

How to manage Porting Set updates

The following conditions apply to customers who intend to upgrade to Porting Set 9.4a or later Porting Set releases:

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

First2930313234363738Last

Theme picker

Categories