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.

The main purpose of the Report Designer is to enable changes to the design of a 4GL application report, without modifying the standard report or using an external reporting solution. The changes are stored as personalizations. Therefore, the effort that is required to implement changes, after the standard is updated, is reduced.

You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer, or modify them in LN Studio.

• The Report Designer is available with LN 10.5 and later.
• Enterprise Server 10.6 is required.
• The Report Designer is only supported in LN UI.

Note:  On LN 10.5 you must re-compile the reports once with Enterprise Server 10.6 to enable them for the Report Designer.

Customer Defined Fields (CDFs) can be added to tables, screens, reports and BODs and validation and calculation logic can be defined around those fields.

Use the CDF concept to store additional data in the standard Infor LN tables. The CDF definitions are stored separately from the table definitions in the Data Dictionary. For the end user, the CDFs behave in the same way as the standard fields, if defaulting, validations, etc. are built using the CDF logic of the table extension point. The session extension point also has features for the CDFs.

CDFs are configured per package combination. This implies that when moving your companies from one package combination to another, the CDF definitions must be present in the target package combination. Otherwise you lose the data in the CDFs.