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

Infor LN & Baan Tip: MPS planned vs. MRP planned

What items should be MPS planned, and what items should be MRP 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, your ERP will calculate cumulative lead time (also called “the Critical Path”) for you.

Infor LN does not differentiate between the two. Here, it is simply an enterprise planning EP with one set of planned orders. It is possible to set up items and generate orders at plan levels, but not necessary. In theory, you could make plan level 1 similar to MPS items.

Another way of defining independent demand in LN terms is that it is demand not related to other planned items. Dependent demand comes from related planned items above in the BOM structure.

COLT still exists both in purchase and manufactured planned items. It has both non-critical and critical lead times based on components set as critical. Once calculated it can be used to update the order and planning horizons of a plan item.

Relevant Sessions:

In Baan IV
Maintain Item Data tiitem0101m000
Generate MPS timps3201m000
Maintain Master Production Schedule timps3101m000
Display Planned Inventory Movements by Item timrp1510m000
Display Planned MRP Purchase Orders timrp1521m000

In Baan V
Plan Item Data cprpd1500m000
Item Master Plan cprmp2101m000
Time-Phased Overview cprrp0520m000

In Infor LN
Item – Planning cprpd1100m000
Item Master Plan cprmp2101m000 (same as Master MPS above if used)

Previous Article Avalara - AvaTax Integration to Infor LX, BPCS, Infor LN, Baan, and M3
Next Article Infor LN & Baan: What are your production orders telling you?
Print
64974 Rate this article:
3.8
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

To utilize the Security Rules Optimization feature, a system administrator can assign security codes to 100 pre-defined user groups. User groups are created in the Group Security Maintenance (SYS603) program. All users assigned to this group possess the same level of security.   

A system administrator can assign security codes for up to 100 of the user groups. All user groups over 100 are still administered by all security reject/allow rules assigned to them but are not able to utilize the optimized process. 

Each of the security codes and access levels are assigned to user groups and are mapped to the account strings and stored in the Account Cross Reference (CEA106D1) file.   

Once security codes have been assigned, the system administrator must: 

  • Determine which level each group is allowed access.

  • Determine which segment values/account strings are assigned to which user groups.

  • Create security rules for specific segment values/account strings and assign these groups to the created rules.

  • Select the rules to be processed.  Processing can be done in either batch mode or interactively.

  • The Security Rules flag must be on in the CEA Control Parameters program before any rules are effective. 

This feature provides a parameter that allows the user to enter expiration dates on the Inventory Transaction Posting screen, INV500, and Purchase Order Receipts screen, PUR5505, when they have received a lot controlled item that is not QMS controlled. This new field allows an expiration date to be entered and not overridden. A system parameter was added to Advanced Process Industries Parameters, API820D. When the parameter is set to Yes, a new lot expiration date is available in the Inventory Transaction Posting, INV500D2, and Purchase Order Receipts, PUR550D2, screens.

FirstLast

Tips: LN | Baan

Categories