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: MPS Planned vs. MRP Planned

Determining whether to use Master Production Schedule (MPS) planning or Material Requirements Planning (MRP) planning for items in Infor LX and BPCS involves understanding the nature of the items and their demand characteristics.

Master Scheduled Items typically encompass finished goods or service items. These items receive their requirements either from Independent demand, Dependent demand, or a combination of both.

  • Independent Demand: This refers to demand that originates from sources such as forecasts or actual customer orders. Items sold directly to customers fall under this category.
  • Dependent Demand: Derived from higher-level demand within the product structure, dependent demand comprises components, raw materials, and sub-assemblies. These items are not typically designated as Master Scheduled Items.
  • Service Parts may exhibit both independent demand, originating from forecasts or customer orders, and dependent demand, stemming from their use in other sub-assemblies or products.
  • A crucial concept in MPS is the Cumulative Lead Time, which combines fixed and variable lead times required to produce a product. It represents the longest path through a given Bill-of-Materials (BOM). In Infor LX (ERP LX), the system calculates the cumulative lead time, also known as the Critical Path, based on setup options. Utilize the "indented BOM" display in BOM300 to identify the item with the longest lead time. Additionally, you may need to use Action 21, Line Detail, to view the lead time ("L/T") for each item.
Previous Article Unlocking the Full Potential of Your LX/BPCS Investment - Embrace the Cloud for Enhanced Connectivity
Next Article ​Infor LN & Baan Tip: Determining What Data to Archive or Delete
Print
7887 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

What will you do when your ERP is no longer supported in 2021?

This is a confusing time for many companies with respect to their ERP system.

"Will I still be able to run my current version?"
"What happens if I want to stay on my version?"
"What options do I have?"

Crossroads RMC is here to help you sort through the confusion and get you to a place where you feel confident about your ERP future.

Let's get started with how we can help. I want Crossroads RMC to…

  • Conduct an Infor ERP Utilization Review – Should I consider moving to the latest version of LX in the cloud, or on prem? If I don’t, what are my options?
     
  • Set up an Infor ERP Demo System – I want to give my employees a chance to try out the latest version to see if it would be of benefit.
     
  • Train My Employees – I want to ensure that we’re operating based on best practices.
     
  • Integrate My ERP to External Systems – My company uses separate systems that don’t talk to one another and that is really inefficient.
     
  • Brainstorm With Me – I’m not sure what to do. I need to talk through some scenarios with someone who has been there, done that.
     
  • Support My Users – I’m short-staffed. I may upgrade, or I may stay where I’m at. Either way, I could use someone to handle our ERP issues. Please help!

Contact us at 800.762.2077 or click here to request a free phone consultation and we'll get you back on track.

Did you know that you can clear production history?

JIT900 - Production History Purge

To clear field values from Production History Inquiry (JIT300). Run monthly as Day End Run and Month End Run which clears M-T-D fields.  There is an option to clear the average per hour and maximum per hour fields. This program can be run as often as you wish.

First4849505153555657Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories