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
7871 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

Previously, a user was able to complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings that were set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and complete the cost transfer process. After the user enters a range in the CST920 screen that is outside of their authority set up in SYS600, a message is displayed that explains they are not authorized to all facilities. Before the enhancement was applied, a user could enter any range in CST920 and it would transfer the costs, regardless of their security level. This enhancement provides security in CST920 that prevents incorrect cost transfers from being processed. 

Infor recently announced their support schedule for all versions of BPCS/LX. Not sure what your company’s strategy should be moving forward?

Let us help you figure out the best path forward for YOUR company. Our goal is to put you on a path that ensures that you are supported and that your needs are met today and in the future without breaking the bank. Learn More>
 

First6667686971737475Last

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