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

Kathy Barthelt

Infor LN & Baan OPERATIONS Tip: MPS Planned vs. MRP Planned

When deciding what items should be MPS (Master Production Schedule) planned and what items should be MRP (Material Requirements Planning) planned, it's crucial to understand the nature of the items and their demand sources. Here's a breakdown:

  • Master Scheduled Items:

    • Master Scheduled Items are typically finished goods or service items.
    • These items receive their requirements from both Independent and Dependent demand sources.
       
  • Independent Demand:

    • Independent demand cannot be calculated from higher-level demand in the product structure.
    • It is driven by forecasts or actual customer orders, primarily applicable to Finished Goods or Service parts sold to customers.
       
  • Dependent Demand:

    • Dependent demand is derived from higher-level demand in the product structure.
    • It includes components, raw materials, and sub-assemblies.
    • Dependent demand items are not typically part of Master Production Scheduling (MPS).
       
  • Service Parts:

    • Service parts can have both independent demand from forecasts or customer orders and dependent demand from higher-level demand if they are used in sub-assemblies or other products.
       
  • Cumulative Lead Time:

    • Cumulative Lead Time is a concept used in MPS.
    • It combines the fixed lead time and variable lead time required to produce a product.
    • It represents the longest path through a Bill-of-Materials (BOM).
    • Your ERP system will calculate the cumulative lead time (Critical Path) based on MPS setup options.
       
  • Infor LN Approach:

    • Infor LN does not differentiate between MPS and MRP planning.
    • It uses Enterprise Planning (EP) with one set of planned orders.
    • While you can set up items and generate orders at plan levels, it's not always necessary.
    • In theory, you could treat plan level 1 similar to MPS items.
       
  • Defining Independent Demand in LN:

    • In LN terms, independent demand is demand not related to other planned items.
    • Dependent demand comes from related planned items higher up in the BOM structure.
       
  • COLT (Cumulative Order Lead Time):

    • COLT exists in the purchase and manufactured planned items.
    • It considers non-critical and critical lead times based on components marked as critical.
    • Once calculated, COLT can be used to update the order and planning horizons of a planned item.

Relevant Sessions:

In Baan IV:

  • Maintain Item Data (tiitm0101m000)
  • 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 if used


For more information and assistance, you can contact Crossroads RMC at 800.762.2077 or via email at solutions@crossroadsrmc.com.

Previous Article Infor LN & Baan TECHNOLOGY Tip: Are you running the latest Infor components?
Next Article Infor LX / BPCS Tips & Tricks for EXECUTIVES
Print
17409 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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.

1345678910Last

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.

1345678910Last

Theme picker

Categories