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: What items should be M-P-S planned vs. M-R-P planned?

Master Scheduled Items are those items that are finished goods, or service items, that receive their requirements either specifically from Independent demand, or both Dependent and Independent demand.

  • Independent Demand is demand that cannot be calculated from higher-level demand in the product structure and therefore must be either a forecast or an actual customer order (Finished Goods or Service parts sold to customers).
  • Dependent demand is derived from higher-level demand in the product structure. Dependent demand includes components, raw materials, and sub-assemblies. (these are not normally Master Scheduled Items).
  • Service Parts may have both independent demand from forecast and/or customer orders, as well as dependent demand from higher-level demand if that item is also used in other sub-assemblies or products.
  • Cumulative Lead Time is a concept used in Master Production Scheduling (MPS) that combines the “fixed” lead time, and the “variable” lead time needed to produce the product. It is the longest path through a given Bill-of-material. Based on the MPS setup options, Infor LX (ERP LX) will calculate the cumulative lead time (also called “the Critical Path”) for you (use the “indented BOM” display in BOM300 and find the item with the longest lead time “L/T”). Note: You may have to use Action 21, Line Detail, to see the “L/T” lead time for each item.

Previous Article Infor LN & Baan Tip: Separate item codes for incoming & outgoing subassemblies
Next Article Infor LN & Baan Finance Tip: Unallocated Payment
Print
35789 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

You use LN audit features to fully or partially log changes that users make to the LN database tables when they use LN sessions.

The audit functionality is based on the concept of audit profiles. In an audit profile, you define which tables and fields are audited and when, in the context of an audit profile. To bundle profiles in the same functional area, you can relate the profiles to audit categories. You can export and import audit profiles with various options to enable a quick configuration. The audit trail is stored in sequence files, which are generated for each combination of company and table.

Note: For some important parameter tables it is required that auditing is enabled.

You can view or print the history of modifications.

Categories