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
13184 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 production bill of material is globally specified at the company level. It can be used as a source for the definition of the local material lists, such as:

  • The production model in the repetitive module.
  • The production model in the job shop module.
  • The subcontracting model in the subcontracting module.

The production bill of material can be generated through the engineering bill of material. The new production bill of material differs from the old bill of material:

  • It has a header and a status.
  • It is always revision controlled.
  • The effective dates have been moved from the material lines to the header.
  • The BOM quantity has been moved from item production data to the header.
  • The use up has been moved from alternatives to the material line.
  • The material line excludes logistic data (no warehouse nor routing operation).

The production bill of material is not mandatory.

Production bill of material revisions:
The production bill of material is revision controlled. The objective of the revision is to control the changes to the bill of material over time.

The P-bom includes this revision-related data:

  • Revision number
  • Effective date and Expiry date
  • Status (New, Approved, Expired)
  • Creation date and Created by: user
  • Approval date and Approved by: user
  • Expiry date and Expired by: user
  • Source information
First5758596062646566Last

Theme picker

Categories