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 LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item

Kathy Barthelt 0 51889 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 12862 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 54329 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 21525 Article rating: 5.0

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

  1. Exit Points...

Is it time to get more out of your ERP?

Crossroads RMC 0 12411 Article rating: 5.0

As crazy as it sounds, we’re about to enter the 2nd half of 2023. How are you doing on your 2023 goals? Planning for 2024 projects?
Maybe it's time to get more out of your Infor ERP system.

OFF SUPPORT AND MAINTENANCE WITH INFOR AND FEEL STUCK?

⇒⇒ TIME TO UPGRADE?

⇒⇒ NOT UPGRADING?

Infor LX & BPCS Tip: Support for IBM i 7.3 and Infor LX Products

George Moroses 0 19582 Article rating: 5.0

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

First2021222325272829Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

In typical LN REST API integrations, permissions and authorizations are not implemented or rarely used. To ensure smooth data exchange and avoid errors, it is recommended to disable the authorization and security settings.

Recommendation:

  • In the Authorization and Security Parameters session (tcsec0100m000):

    • Clear the Authorization and Security Enabled check box.

    • Clear all check boxes under Authorization Enable for on the Enabling tab.

Why This Matters:

  • Enabling authorization and security without proper setup can lead to errors and blocked transactions during integration.

  • For example, work center permissions may interfere with:

    • Creating new shifts

    • Booking machine hours

    • Read more

Categories