Defining the settings in M3 Graphical Lot Tracker

The initial load process starts with the setup of M3 Graphical Lot Tracker configuration options. These options can be set only at initialization. After the database has been populated with data from M3 Business Engine, these options cannot be changed. If an option must be changed, a full reinitialization is required.

Note: If a full reinitialization is required, and Infor Data Lake is in use, see Scenario 3: Perform a full M3 Graphical Lot Tracker re-load when Infor Data Lake integration is enabled.

To define the required settings, complete these steps:

  1. In M3 Business Engine, select Menu > Administration Tools > Graphical Lot Tracker Administration.

    The application management pages are displayed. Working connections and executed tasks are marked in green. Remaining tasks and missing connections are marked in red. Until the application has been fully initialized, red markers are displayed, but this is normal.

    After the application initialization, you can view the list of users who have the IFS role ‘M3 GLT Administrator’. This list is displayed in the Admin Users table in M3 Business Engine. Using this list, you can verify that the roles have been correctly set up in M3 Business Engine.

    Note: Only users with the IFS role ‘M3 GLT Administrator’ can access the application management pages.
  2. To prepare the configuration option for system initialization, select GLT Settings and Import and specify the configuration options that are required for the initial load.

    In the Define GLT Settings and Import dialog box, specify this information:

    Organization
    Specify the M3 Business Engine company code for the company from which data must be imported.
    Key Separator
    Specify the separator to be used when the step ID is being built. The default value is the dot (.). If the dot is used in the M3 Business Engine warehouse, item, or lot code, then specify a character that is not already used. Valid separators are (.¤!@:).
    MO Trace Level
    This setting determines the level of trace objects for manufacturing. For production environments in which one or few lots are produced per order, leave this setting at the lot level (LOT). If numerous lots are produced per order, keep the manufacturing object at the order level (MO) to ensure that the number of trace transactions is reduced at the order level.
    Trace CO by Lot
    To prevent a possible erroneous trace relation on customer returns, you can add the lot number to the step ID. If this setting is enabled, then the lot number is added as a postfix to the previous definition of the step ID:

    CO.OrderNumber.LineNumber.DeliveryNumber.LotNumber

    Security program
    To manage security at the function level in M3 Business Engine, you can use the M3 Business Engine method ‘Function. Connect Authorization by Role’ (SES400) or ‘Function. Connect Authorization’ (SES003). The Security program configuration option is set to SES400 by default. See Definition of user security in M3 Business Engine.
    Function category

    You must specify the same value as in ‘’ (MNS110). We recommend that you specify MSH-Mashup. The default value is ‘MSH’.

    See Setting up user group settings – security through roles (SES400).

    Component group
    You must specify the same value as in (MNS110). We recommend that you leave the default value, which is GLT.

    See Setting up user group settings – security through roles (SES400).

    Auto accept days

    During the initial data load, unknown starting points are inserted and all circular traces are set to ‘inspected’. Thus, the work with rejected transactions at start-up is reduced. The Auto accept days setting indicates the cut-off date from which unknown transactions are no longer automatically accepted. By default, this setting is set to 30 days before the current date.

    The M3 Business Engine stock can be populated through physical inventory variance rather than from purchase or manufacturing transactions, which is common when data are being migrated from another system. In that case, adjust the Auto accept days setting so that the cut-off date is later than the migration date.

    Override subcontract
    If this setting is enabled, then the issue method ‘Issue from MO’ is overridden for any raw material that is used for the subcontracted operation. The issue method is transformed into a valid ‘Issue from RO’ transaction, thus preventing M3 Graphical Lot Tracker from rejecting the transaction. This setting is set by default to ‘Disabled’.
    Note: If the initial load process is completed, and the GLT Settings and Import function are run again, the operation clears all transactional data and performs a full import. If a new organization is selected, all GLT Application settings are reset to their default values.