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.

You can define internal trade relationships between enterprise units or individual warehouses of the same logistic company for the transfer of material, labor, or other costs between warehouses, and to generate invoices for these without using sales orders and purchase orders. For example, you can use this to transfer goods between warehouses in different countries.

You can define warehouse surcharges, which are added to the actual costs of the goods either when the goods are issued from a warehouse or when the goods are received.

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In Infor LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period.

For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.