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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan & LN Tip of the Week: Get Real!

You’ve got an ERP system, so everything should be real-time and everyone should have access to information in real-time, right? RIGHT?!

Why not? Why are there spreadsheets, and separate Access databases off to the side?

Data loses value over time, so why not give everyone up to date, accurate information all the time? Take a look at those silos of information and see how you can eliminate them. Your business will benefit greatly as a result.

Optimize Your Manufacturing Today!

Previous Article BPCS & LX Tip of the Week: Get Real!
Next Article Crossroads RMC named as Avalara's Certified Integration Partner for Infor LX
Print
78547 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

FirstLast

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