Parameters

This table shows the tabs in Parameters:

Tab Description
System

The application plans for a 10-year horizon. Define the calendar start date and the calendar end date calculated based on the specified start date. You must ensure that the calendar start date is in the past and the calendar end date is in the future.

Set the delay calculation by calendar days or alternative according to the delay calendar, which considers holidays in delay calculation.

Default Values In case of missing data, use this tab to set up default values to ensure the application can still plan.
Error Control
Environment
Database

Use this tab to set up the API connection to M3 BE. The application supports several different technologies depending on the M3 BE database.

For AppStream, you can use the ION API JSON text option. See Setting up AppStream for further details.

Run Test logon to verify if the database connection is setup correctly.

To analyze the API transactions in import or export, you can enable Temporary trace log level. The trace log level has an effect after the next server logon. Therefore, you must logoff from the server first. The trace log level 5 includes sent and received data, which is often sufficient, but you can also see the tooltip for more trace log level options.

The APIs called and mapping from the API to PWB is defined in the PWB parameter file MI-PARAM.DAT, which you can view in System > System information > Control Files > View original.

The Planning area field contains these values:
  • Company: This data is retrieved based on ION API OAuth2 credentials. Run Test logon to verify the fetch company.
  • APS policy: Optionally, you can use this function to reduce data volume based on APS Policy defined CRS798.
  • Planning area: This field is usually blank. If the facility is divided into two parallel production areas with separate resources and orders, the two users can plan for their own planning area.
  • Warehouse group: This field is required. The Warehouse group determines which warehouse controls defined in MMS009 are imported.
Bookmarks This tab is only used for Infor Smart Office.
ODBC database This tab is only visible if the ODBC transfer check box is enabled in the Environment Variables tab.
Import
Export
Report Control
File Interface This tab is only visible if the File transfer check box is enabled in the Environment Variables tab.
Local Order Generation This tab is only visible if the Local Order Generation check box is enabled in the Environment Variables tab.
Material Control You can use the settings in this tab to control Material Control, Safety Lead Time, and Coverage Days Calculation.
Scoreboard Use this tab to calculate scoreboard records in the active group to improve performance. You have an option to use large font in the scoreboard.
User Interface This tab includes the language selection and tool-tip options.
Automatic Simulation The boundary capacity definitions ensures that you can plan operations inside the application for a 10-year planning horizon. You can still plan the operation even if the resource has little capacity or the operation has too much operation time.
Decisions
Environment variables

You can enable these functionalities on this tab:

  • File transfer: This function enables the text file data transfer component in Components > Database Transfer.
  • Local order generation: This enables the generation of order locally in the application.
    Note: These orders exist locally. If exported, these orders do not exist outside the application.
  • Local parallel operations: This enables the component in Components > Resource Capacity Modeling. During the import of operation, you can setup the logic to generate extra local operations. You can use a tool resource needed for production, setup resource needed during setup, and so on.
  • ODBC transfer: This enables the ODBC data transfer component in Components > Database Transfer.
  • Plant maintenance: This enables importing and planning of plant maintenance orders.
  • Industry: The industry selection controls the conditions in the parameter file.

The Additional environment variables enables you to have additional conditions in the parameter file. For example, if you must use certain parameter file modifications in one facility, but not in others, each user or facility can enable the modification.