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:

TECHNOLOGY: Change SyncBillofMaterial BOD
This enhancement provides the ability to enable setting facility-specific bill of material BOD's accounting entity from the facility's stocking warehouse's company. The bill of material BOD can be consistent with the bill of resources BOD which sets its accounting entity from the company associated with the facility's stocking warehouse.

FINANCE: Override Exchange Rate
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.

OPERATIONS: Multi-Level Shop Order Release Due Dates
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.

Previous Article Crossroads RMC Presents 4 Must-Attend Sessions at inPOWER 2024
Next Article Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Change SyncBillofMaterial BOD
Print
1252 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

IBM® has released its latest operating system for the IBM i. IBM i 7.3™ has many new features and enhancements that you may want to take advantage of.

Infor is pleased to announce the following Infor LX products are supported on this new version, effective June 12.

Supported products and versions

The following Infor products have been evaluated for compatibility with IBM i 7.3 and are supported on that version of the platform:

  • Infor LX 8.3 (all release levels)
  • Brazil Pack for Infor LX 8.3
  • Argentina Pack for Infor LX 8.3
  • Infor BPCS 8.2 (all release levels)

Optimize Your Manufacturing Today!

Sales tax nexus is the connection between a seller and a state that requires the seller to collect and remit tax on sales made in that state. If you have nexus in California and Texas, for example, you must collect and remit sales tax in California and Texas.

Many states are expanding their nexus rules. Business activities like trade show attendance, drop shipping, employing remote workers, advertising, and housing inventory in other states can establish nexus. The rules vary by state and it can be challenging to keep up with all the places your business needs to register, collect, and remit sales tax.

Optimize Your Manufacturing Today!

First7172737476787980Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories