Settings in M3 BE

M3 Business Engine settings for Inventory Planning Workbench

Use these settings in M3 Business Engine to access the full functionality in Inventory Planning Workbench:

  • Security roles in Infor OS Portal: You must have the Security role, IPW-User, to access this setting.
  • IPW roles in (MNS405): Define these IPW roles:
    • IPWADMIN
    • IPWPLANNER
    • IPWVIEWER
    Note: The IPW roles are always used in the IPW new UI. In IPW Classic, the IPW roles are used if IPWADMIN is defined in (MNS405).
  • IPW roles per user in (MNS410): Link the user to IPW role. If you have several IPW roles, the IPW role with the most rights is used.
  • APS policy in (CRS798): Select a group of items which are planned in the application. Based on the type of company and industry, you can have several APS policies for item groups. You can select which APS policy to use and which item groups to display.
  • Warehouse group in (MMS009): Select one or more warehouses that are planned in the application.

    The type of decisions that are taken depends on each scenario. These are the logic rules on warehouses in the warehouse group when taking decisions:

    • When taking manufacturing decisions, you must have only one main warehouse where manufacturing orders are created. Otherwise, IPW cannot determine which facility creates the manufacturing orders. This is defined by acquisition code 1 (Manufactured) in (MMS002/E).
    • When taking purchase decisions, you must have a purchase warehouse that is defined by acquisition code 2 (Purchased) in (MMS002/E). If there is more than one warehouse with acquisition code 2, the purchase warehouse is the warehouse on the first item or warehouse record received from MMS080MI > SelItemWarehous.
    • When taking forecast decisions, you must have a sales warehouse that is defined by acquisition code 3 (Sales) in (MMS002/E). If there is more than one warehouse with acquisition code 3, the sales warehouse is the first item or warehouse record received from MMS080MI > SelItemWarehous. If there is no warehouse with acquisition code 3, then the warehouse with acquisition code 1 (Manufactured) is updated instead. In this scenario, the item is both manufactured and sold from the same warehouse.
  • Product structure type in (CRS787): Create Manufacturing Orders (MO) and Manufacturing Order Proposals (MOP) in the application.
  • Master Demand Schedule in (MPS300): As M3 Business Engine can contain several Master Demand Schedules (MDS), you can use MPS300 to define which MDS is going to be used in MRP to create order proposals.
  • Master Demand Schedule for manual forecast in (MPS300): To manually overrule the forecast values in the application, you must define a Master Demand Schedule (MDS) in (MPS300) for manual forecast from Inventory Planning Workbench.
  • Point of time table in (RPS080): Define the planning buckets in the application. These statuses are applicable for this setting:
    • 30: Delivery in time which also defines buckets in the grid
    • 10: Used if there is no records with status 30
    • 40: Order pacing used in forecast pacing
  • Production line in (MMS003): Sort items into groups based on how or where the items are produced.