Import and Export for M3 Dataset Definitions

This document describes the import and export of dataset definitions in M3.

With the import and export of M3 dataset definitions, you can import and export M3 dataset definitions from one company or tenant to another. You can export dataset definitions in XML format from these programs and import them into the M3 database through APIs and function programs.

  • 'Dataset.Open'(OSS401)
  • 'Dataset.Connect Accumulator Fields'(OSS402)
  • 'Dataset.Connect Selection Fields'(OSS403)
  • 'Dataset.Connect Field Values'(OSS404)
  • 'Dataset.Connect Dataset Trans Types'(OSS406)
  • 'Sales Budget.Open'(OSS420)

The configuration item file supports import strategies 'Replace existing records' and 'Keep existing records' in the Business Engine Configuration Data tool. You can export up to 200 records in (OSS401) in one go.

Limitations

  • Activation of a dataset in (OSS401) and sales budget in (OSS420) and updating of a budget version in (OSS401) are only supported during 'Replace existing records'.
  • During import, if the XML file has records in (OSS402), (OSS403), (OSS404), (OSS406), or (OSS420) that do not exist in the target company, these records are added regardless of the selected option ('Keep existing records' or 'Replace existing records'). For example, you import a dataset to company B with these records, these records are deleted from the dataset after import in company B. If for any reason this dataset is imported again with these records which have been deleted in company B, they are added regardless of if 'Keep existing records' or 'Replace existing records' is selected.
  • The records in the dataset table are not part of export and import.

Before you start

You must create a dataset. (See supporting function in Export Data from Dataset to a File)

Follow these steps

  1. Export dataset.

    You can do this in two ways.

    Selection of dataset

    • Open (OSS401) and select a dataset.
    • Select related option 21='Export Configuration' on the dataset to be exported. Export configuration window is displayed.
    • Enter a file name in the 'File name' field or leave the field with the default specified. This field is mandatory.
    • Enter the file version number in the 'Version' field. This field is mandatory.
    • Enter the file description in the 'Description' field. This field is optional.
    • Enter the file dependency description in the 'Dependency desc' field. This field is optional.
    • Click OK to export the file.

    Range of dataset

    • Open (OSS401) and select a dataset.
    • Specify a range of dataset by selecting F17='Export'. Panel S is displayed.
    • Enter the range of dataset to export in 'From' and 'To' fields.
    • Enter a file name in the 'File name' field or leave the field with the default specified. This field is mandatory.
    • Enter the file version number in the 'Version' field. This field is mandatory.
    • Enter the file description in the 'Description' field. This field is optional.
    • Enter the file dependency description in the 'Dependency desc' field. This field is optional.
    • Click OK to export the file.

    The file is exported in an XML format. The file is saved on the M3 File Transfer Disk in the FileImport directory after export. To see the file, go to M3 Business Engine Files in the Administration Tools menu.

  2. Import dataset.

    You can perform import in M3 BE Administration Tools.

    To import, the source files must have been placed on the M3 File Transfer Disk in the FileImport directory after export. To see the file, use the M3 Business Engine Files app in the Administration Tools menu.

    • In H5, select the application menu. In the expanded menu, navigate to Administration Tools.
    • Select Business Engine Configuration Data.
    • Select Exported tab to see a list of all exported XML files.
    • Search for the exported XML file by searching for a file's name.
    • Select the XML file and click Import.

    • The Import configuration data window is displayed. Enter the company and division to import to. Select 'Keep existing records' if you want to keep the existing dataset or 'Replace existing records' if you want to replace the existing dataset. Select 'Log to file' to see logs after importing. This is important if import fails. The logs display why the import was not successful.

      A message is displayed if import is successful or not.

    The import tool reads the XML file and runs the required API programs to write the data to the M3 BE database. The API program and transaction to be run are specified in the XML file. If data is to be replaced, a Delete transaction is run before the Add transaction.

Related topics