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
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip of the Week: Item Deletion Option in IDF Enterprise Items

Previously, users were unable to delete items in IDF Enterprise Items when they have inventory balances or the item is connected to ancillary records, such as sales history records. This feature added in LX 8.4 provides the ability to delete an item when sales history records are found but all sales history activity is zero.

When the user attempts to delete an item in IDF Enterprise Items that is tied to a sales history record, the panel displays a message that the item cannot be deleted. The user can then run the Delete Validation Report to determine which records are tied to this item that prevents the validation. If the item no longer has manufacturing activity but had old sales history, the item can be deleted.

Previous Article Infor LN & Baan Tip of the Week: In Transit Inventory Report – LN 10.7
Next Article Infor LN & Baan Product Lifecycle Policy Support Changes for 2021
Print
13054 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

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.

If you have a parts warehouse and prefer to use SIC for planning (re-order point) but need to use MRP/MPS planning for production, create a non-nettable warehouse for the parts warehouse and run the SIC plan against that warehouse.

When running the SIC plan, be sure to set the Order System to “MPS to MRP” for Baan IV and to “Planned to Planned” for Baan V and LN.

Using this method you keep the parts inventory out of the production planning and in the hands of the parts warehouse planner.

First131132133134136138139140Last

Theme picker

Categories