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

Join Us at inPOWER 2024!

We are excited to invite you to the Infor user group inPower event this September 23-26, 2024.

As a Gold Sponsor, Crossroads RMC is proud to support this premier event. Here are some reasons you should attend:

  • Networking: Connect with peers and industry experts.
  • Product Updates: Discover the latest features and future roadmaps.
  • Training: Participate in hands-on workshops and expert-led sessions.
  • Problem Solving: Learn from other users’ success stories.
  • Influence: Provide feedback to Infor’s product development teams.
  • ROI: Gain insights on maximizing your Infor investments.
  • Community: Engage with special interest groups and regional user communities.

This event is a great opportunity to enhance your knowledge, solve challenges, and optimize your use of Infor solutions. Don't miss out!

What's in it for me?

inPower has something for everyone!

Technology:

  • What's new with LX 8.4.2 and Upgrading     
  • Modernize With Webtop 4.8
  • More on LX Security
  • LX Tools
  • Patch Management
  • Leverage Infor's Tools for Systems Integration
  • How does IOS add to the LX user experience?
  • LX: IDF Data Visualization
  • API's, ION Workflows & Document Workflows
  • IDM Customer Success Story
  • IDF Business Objects Roundtable
  • Feedback from the customers - Chat with your Infor LX Team
  • Custom Cards in IDF
  • SQL Views in Real Life
  • Infor OS, BI, AI, Cloud
  • All the Cool Stuff in ACS

Operations:

  • What's new with LX 8.4.2 and Upgrading     
  • Country Localizations
  • LX Pricing Workshop
  • Feedback from the customers - Chat with your Infor LX Team
  • Advanced Supply Chain Planning
  • Infor CPQ, BI, CRM, AI
  • Infor Warehouse Management
  • Advanced ECM
  • VMI

Finance:

  • What's new with LX 8.4.2 and Upgrading     
  • Country Localizations
  • Moving from CEA to eGLi
  • LX Pricing Workshop
  • Feedback from the customers - Chat with your Infor LX Team
  • Infor CPQ, BI, CRM, AI
  • Infor F-9 (User friendly Microsoft Excel add-in)

Executives:

  • What's new with LX 8.4.2 and Upgrading
  • Modernize With Webtop 4.8
  • Country Localizations
  • LX Pricing Workshop
  • Infor CPQ, BI, CRM, AI, Cloud
  • Infor Warehouse Management

Previous Article Infor News You Can Use | Infor and IBM i - An Aligned Strategy for the Future
Next Article Bring New Life to Your Infor LN & Baan ERP System
Print
4965 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

Baan/LN Tip: New Mapping Scheme

After a new mapping scheme is copied from an existing one, it is possible to check transactions in a simulation mode, before activating the new scheme. However, before the simulation can take place, the new mapping scheme needs to have completed the “Check Mapping Scheme” step. When the check is completed, a transaction can be simulated by highlighting it and from the Specific menu, selecting “Map with Specific Mapping Scheme.” Any errors can be corrected without having to activate the new mapping scheme.

This has come up as an issue during various stages of warehouse material movements – transfers, outbounds, shipments. We have seen it right up to 10.4. The inventory structure table (whinr150) becomes a problem. The error points to that table, but users are lost as to how to fix it.

In the session Units by Unit Set many companies let the field Storage default to Yes. If the UOM is not intended to be used in inventory then that setting should be No. 

If an item is purchased in UOM different from the inventory unit and the setting is Yes then LN adds a record in that UOM to the inventory structure table. It is that record that causes problem later.

The session has an option to change the value of the storage field. Specific > Convert Use for Storage. This option works both ways and will correct all inventory in the UOM range. 

Should a user receive an error that references inventory structure table then the solution is to check that session to see if an odd UOM exists in it. If so use the Convert Use for Storage to correct the problem.

First7374757678808182Last

Theme picker

Categories