Data not imported as expected

If the data is not imported as expected, you can start by validating the data defined in BE. If the data in BE is correct, you can record the import of data in a trace log file.

These are the steps to record the data in a trace log file:

  1. Select System > Parameters > Database.
  2. On Temporary trace log level, set the value to 5.
  3. Click OK.
  4. Run the import of data that is saved in the MI_TRACE.LOG file.
  5. Select System > View MI Trace file to open the MI_TRACE.LOG in the editor.
  6. Analyze if the API transactions contains the expected values.
    • If API does not contain the expected values, you must investigate the BE setup and API.
    • If API contains the expected values, you must investigate PWB. If reporting as issue to support, attach the exported schedule version that includes the MI_TRACE.LOG file.
You can use these steps for exporting the schedule version in AppStream for issue reporting.
  1. On PWB, select System > Schedule Versions.
  2. Click Export.
  3. Specify this information:
    Warehouse group
    Select the warehouse group file name.
    M3 BE user
    Select the M3 BE user file name.
    Current date
    Specify a value for the date.
  4. Click OK.
  5. On the AppStream directory for Temporary files, click Save.
  6. On the AppStream menu, select My Files > Temporary Files.
  7. Click the arrow on the right of the zip file that was created.
  8. Click Download.
  9. You can attach the zip file to the support incident.

The data import is delivered based on the standard parameter file and you must validate any data import issue on the standard parameter file. To disable a modified parameter file, select System > System information > Control Files then click Activate. When you report the issues to support, you must use the standard parameter file.