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

Infor LN & Baan Finance 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 the cumulative lead time (also called “the Critical Path”) for you.


Infor LN does not differentiate between the two. It is simply Enterprise Planning EP with one set of planned orders. It's 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 in the purchase and manufactured planned items. It has non-critical and critical lead time 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)

Contact us today to learn more:  800.762.2077 | solutions@crossroadsrmc.com

Previous Article LX User Group Event: Infor Partner Spotlight | Crossroads RMC
Next Article Infor LX & BPCS Tip: MPS Planned vs. MRP Planned
Print
19393 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

From time to time, your employees need access to information related to logistical and financial transactions that have occurred in the past. Before you archive or delete this information, you must understand the need for this information. Baan and LN contain standard archiving sessions in the major modules that tend to have a high volume of historical transactions. These sessions are designed to copy historical data to the archive company, and then delete the data from the operational company.

You have three options in archiving sessions...

First1718192022242526Last

Theme picker

Categories