Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Kathy Barthelt
/ Categories: Infor ERP Tips, Infor LN & Baan Tips, Manufacturing

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
65314 Rate this article:
3.8
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Understanding: How many hours remain in total and at each operation?

Now let’s look at what information is being supplied from the shop floor.

It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.

The big question is, is anything done with the data? Is it collected and keyed to a  spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.

Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:

  • The type of hours being reported – machine, run labor, setup labor
  • If reporting setup and run labor you want an employee clock number
  • The shop order and the operation that is being reported
  • Is the operation complete
  • How many good were produced at this operation
  • How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.

Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.

Read more

Understanding: How many hours remain in total and at each operation?

First let’s look at some key BPCS Master File data starting with the routing file.

How many routing steps (operations) are set up that reflect how the product is produced in the factory? If you take a short cut and set up only one operation for the entire process, then you will limit the information seen on the SO inquiry program. Set up the operation steps to reflect what you want to report back to from the factory floor.

Will each of the routing steps run in one work center, or in different work centers? To keep it simple you may want to set up work centers as departments. For example:

  • Assembly
  • Machine
  • Paint
  • Etc.

For each operation setup consider how you have set up the following:

  • Load Codes – for example a code 5 is used if reporting both setup time and run labor time. These codes are maintained in the work center file
  • Basis Code – typical codes are P for pieces per hour,  3 is used for hours per 1,000 pieces
  • Setup hours – if you set them up, you also want to report them
  • Run hours – Direct Labor
  • Machine hours

How you set up th

Read more
FirstLast

Tips: LN | Baan

Categories