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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: The Production Bill of Material – 10.7

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
Previous Article IDF News: Importing LX Security into IDF
Next Article Hunter Douglas Architectural Products Selects Crossroads RMC for LN 10.6 Upgrade Project
Print
38648 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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