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

ERP & the Importance of Accuracy & Productivity

Infor LN & Baan

Kathy Barthelt 0 9925 Article rating: 5.0

If you don't think accuracy and productivity are important, you need to take a hard look at HOW you’re running your ERP system.

  • Have you eliminated large amounts of data entry?
  • Is your data error-free at month's end?
  • Do all of your systems talk to one another?

If the answer is no, Crossroads RMC can improve accuracy and productivity with system integration and/or automation.

Too expensive you say? Too time-consuming and way too much effort to make it happen? Not necessarily... 

Effective September 30, 2023, IBM® will end support of the IBM i operating system 7.3

AND Infor will no longer support LX and related products on IBM i 7.3 as of June 1, 2024

Crossroads RMC 0 10795 Article rating: 5.0

THE CLOCK is T I C K I N G ... 

MARK YOUR CALENDARS!
Effective September 30, 2023, IBM® will end support of the IBM i operating system 7.3  AND  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 will be...

Infor LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item

Kathy Barthelt 0 15152 Article rating: 5.0

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider...

Reskilling and Upskilling Your Staff – Why You Shouldn’t Ignore This

Crossroads RMC 0 11111 Article rating: 5.0

According to the World Economic Forum, half of all employees will require significant reskilling or upskilling by 2025.

For many of you, your Infor ERP system was implemented 5, 10, 15, or 20+ years ago, and now there are only a handful of people left from that implementation if any at all. Since most of your "how and why" walked out the door, how much longer can you get by on “tribal knowledge”? While many companies understand the importance of employee training, implementing that training remains a challenge. What’s the best way to proceed you ask?

Infor LN & Baan Tip: What conditions must exist before changing an item's inventory unit?

Kathy Barthelt 0 15320 Article rating: 5.0

Is there a procedure for changing an item’s inventory unit? What conditions must exist before it can be done?

Once inventory transactions (receipts or issues) have occurred for an item, the inventory unit cannot be changed. If only orders have been placed against the item (sales or purchase), the inventory unit can be changed if these...

Infor LX & BPCS Tip: 4 Approaches to Customizing LX / BPCS - Preparing for a Future Upgrade

George Moroses 0 11803 Article rating: 5.0

How do I modify BPCS/LX to allow for the ease of upgrading in the future?

  1. Exit Points...
RSS
First1112131416181920Last

Theme picker

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

Kathy Barthelt

Infor LN & Baan Tip & Tricks for OPERATIONS: Best Practices for Purchase Order Archiving / Deleting

 Here are some best practices to follow if you are considering archiving or deleting purchase order data:

  • If Financials is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.
  • Purchase contracts must be archived before purchase orders can be archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that's linked to the purchase order line, and for which an internal invoice must be sent from the purchas office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Previous Article Infor LN & Baan Tip & Tricks for TECHNOLOGY: Using Table Boosters to Speed Up Sessions & Processes
Next Article Infor LN / Baan Tips & Tricks for EXECUTIVES
Print
9661 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories