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 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 Infor LX/BPCS Tips & Tricks for FINANCE: Override Exchange Rate
Next Article Infor LX/BPCS -Join Us for an Exclusive Insight into Data Collection Streamlining
Print
832 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

When an attempt is made to change an item’s type to a non-inventory item from any other value, a new validation is performed to determine if the item has any inventory on hand and, if so, prevents changing the item’s type.

This enhancement available in LX 8.4 prevents LX from showing an on-hand inventory balance for a non-inventory item.

The programs or areas impacted include:

  • Facility/Planning Data Maintenance, MRP140D2
  • IDF Enterprise Item

To get this enhancement, request and apply MR 80120.

An 8.4.1 EGL audit enhancement now provides visibility to who and when a financial journal was last maintained and to who and when the journal was approved. The enhancement provides audit attributes for last maintain user, date, time and approval user, date time on the Financial Journal Entry and Financial Journal Entry Lines.  

The programs or areas impacted include:

First1718192022242526Last

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