Performing initial load from M3 to Data Fabric

During normal processing, events containing data are generated when a user makes a data change or completes a transaction in M3. The initial load function in M3 generates events without creating corresponding transactions. These events are sent to Data Fabric through streaming or ION by an M3 program referenced in EVS002MI. To perform the initial load of M3 data when using ION, you must synchronize the ION Data Flow with the selected tables in Data Lake Publisher to publish.

Take note of the name of the master tables to send to Infor Data Lake.

  1. In M3, select Administration Tools > M3 Metadata Publisher > M3 API Repository > Test API.
  2. Click the Settings icon.
  3. Specify a value in the Company (cono) field. Standard value is 100.
  4. Click OK.
  5. Specify this information:
    Program
    Select EVS002MI and then click Select.
    Transaction
    Select Initiate.
    FILE
    Specify the table name to trigger publishing of Item master data. For example, use MITMAS.
    DIVI
    Specify the division of events, if applicable.
    Note: The Division parameter functions only if the Division field (DIVI) is part of the primary key in the specified table of FILE.
    FRDT
    Specify a value in this field and in the TODT field to filter the records registration date (RGDT) in the M3 table.
    TODT
    Omitting the TODT sends data with a registration date (creation date) from FRDT and higher.
    DTLK
    Specify 2. Specifying 1 uses the streaming or ION architecture, which is not recommended for initial load.
    FRTS
    Specify a value in (YYYY-MM-DD) or (YYYY-MM-DDTHH:MM:SS.sss) format to define the lowest LMTS for which the data is generated.
    Partial load based on the LMTS timestamp is useful for loading or reloading data updated at a specific time. If the table does not include LMTS, an error message shows:
    “XFL0003 = Field &1 is missing in table &2“
    TOTS
    Specify a value to define the highest LMTS to which the data is generated.
    You can define FRTS and TOTS on day level (YYYY-MM-DD) or provide a complete datetime specification down to the millisecond level.
    Note: Ensure that the FRDT and TODT fields are blank since their values override FRTS and TOTS values.
  6. Click Run.