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

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, Infor LX (ERP LX) will calculate the cumulative lead time (also called “the Critical Path”) for you (use the “indented BOM” display in BOM300 and find the item with the longest lead time “L/T”). Note: You may have to use Action 21, Line Detail, to see the “L/T” lead time for each item.
Previous Article Infor LN & Baan Finance Tip: MPS Planned vs. MRP Planned
Next Article What are your production orders telling you?
Print
15516 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

TECHNOLOGY: Facility Security Ranges

Previously, a user could 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 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 completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could 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 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 completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

You may be wondering if it's necessary to have separate item codes for incoming and outgoing subassemblies.

No, it is not necessary to have separate item codes for incoming and outgoing subassemblies, but it is recommended. In theory, you could have only one item code with the description subassembly and use the same item code for the outgoing subassembly and for the incoming subassembly. However, when monitoring inventory movements and financial integration transactions, it will be difficult to understand the process. Also, the costing logic is much clearer when different item codes for the incoming and outgoing subassemblies are used. Because of this, it is advised to use a different item code for the outgoing subassembly and a different item code for the incoming subassembly.

First1718192022242526Last

Theme picker

Categories