On-premise

The difference between on-premise and other deployments is provided in this topic.

Prerequisites

  • You must install M3 Planning Workbench on-premise.
  • You must setup ION API for M3 Planning Workbench. See Setting up ION API.

Starting M3 Planning Workbench

Follow these steps to setup M3 Planning Workbench on-premise.

  1. From the start menu, launch M3 Planning Workbench.
  2. Verify if the correct Schedule Version is used.

    Alternatively, you can also import another Schedule Version.

  3. Specify the ION API OAuth2 credentials and verify the information displayed. See Configuring PWB to use OAuth2 credentials for ION API.
  4. Select ION API JSON text, then click Paste ION API JSON text from clipboard to paste the content from the ION API file.
  5. Click Test logon.

    A message is displayed that the test logon succeeded.

  6. Click OK.
  7. On the Planning Area section, specify this information:
    Company
    Verify if the company value displayed is correct.
    Warehouse group
    Specify the warehouse group defined in MMS009.
  8. On the Miscellaneous section, specify this information:
    M3 BE user
    Verify if the M3 BE user displayed is correct.
    Tenant ID
    Verify if the tenant ID displayed is correct.
  9. On the Selection of Order section, specify this information:
    Horizon for section of orders
    Specify the horizon for selection of order value.
    Division
    Verify if no exclamation mark is displayed. If exclamation mark is displayed, then the calendar in CRS900 is not defined in Horizon for section of orders. You can extend the division calendar or reduce the horizon for selection of orders until the exclamation mark is no longer displayed.
  10. Click OK.
  11. Run Initialize plan.

    Review the Messages lines displayed. You should have a defined bottleneck resource with finite capacity. Validate that only bottleneck resources are defined with finite capacity and the errors and warnings are fixed. If Shift Patterns are only in the past, you must extend the shift patterns for M3 Planning Workbench to create a plan

Schedule Versions

See Schedule Versions in AppStream for more information.

Modifying Panel Files

To modify the panel files, select System > System Information > Panel Files.

The list of all panel files are displayed.

You can do these actions on each panel files:

  • View original
    • You must have a Planner or Viewer role.
    • Open the original or unchanged panel file using an editor in which you cannot change the panel file.
      Note: If there is no custom file, all users will use this file.
  • Edit custom
    • You must have a Planner role.
    • Copy the original file to the custom directory and edit the file using an editor.
      Note: All users will use this file.
  • Delete custom
    • You must have a Planner role.
    • Delete the custom file located in the custom directory
  • Toggle activate
    • You must have a Planner role.
    • Activate or deactivate the use of the custom file.
  • Import custom files
    • You must have a Planner role.
    • Import backup of custom files from the Temp directory.
  • Export custom files
    • You must have a Planner role.
    • Export backup of custom files to the Temp directory.

Modifying Control Files

To modify the control files, select System > System Information > Control Files.

The list of all control files are displayed.

You can do these actions on each control files:

  • View original
    • You must have a Planner or Viewer role.
    • Open the original or unchanged panel file using an editor in which you cannot change the panel file.
      Note: If there is no custom file, all users will use this file.
  • Edit custom
    • You must have a Planner role.
    • Copy the original file to the custom directory and edit the file using an editor.
      Note: All users will use this file.
  • Delete custom
    • You must have a Planner role.
    • Delete the custom file located in the custom directory
  • Toggle activate
    • You must have a Planner role.
    • Activate or deactivate the use of the custom file.
  • Import custom files
    • You must have a Planner role.
    • Import backup of custom files from the Temp directory.
  • Export custom files
    • You must have a Planner role.
    • Export backup of custom files to the Temp directory.
Note: Not all users can apply modifications. For example, the parameter file MI-PARAM.DAT contains a modification with a condition based on parameter APS-ENV-01 = FAC-10. You must only apply the modification for the facility 10 users. The facility 10 users must set the parameter APS-ENV-01 = FAC-10 in M3 Planning Workbench. Select System > Parameters > Environment Variables.