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

The Cycle Counting Sub-System Within Inventory Management

The system uses the following information as the basis for cycle counting selection:

  • Cycle Counts/Year: The system calculates the time between cycle counts based on your entry in this Item Master file field for each item (optional).
  • Last Cycle Count Date: This date is in the Location Inventory file, ILI, if you use locations, or in the Warehouse Inventory file, IWI, if you don't.

The system adds the time between cycle counts (calculated as described above) to this date. If the result is less than or equal to today's date, the item is selected for cycle counting. If it is greater than today's date, the item is not selected, it is not due yet for cycle counting.

There is another special condition that causes an item to be selected for cycle counting. If the ILI/IWI record of the item has a Y in the Cycle Flag field, the item is selected automatically. This flag indicates that the item's on-hand balance has gone to a negative value sometime since the last cycle count. That applies even if the value is not negative at selection time. The programs that can set this field are INV500D, INV510, and BIL540.

You can also limit the items selected for counting by specifying limits of the item numbers or warehouses to be searched.

First2324252628303132Last

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