Import and Export specific options

These are the fields and options that can be used in the External Scheduling Interface (tppss2231m000) session, during the import or export of data:

  • Regenerate XML file

    Use this option to generate data again, during the export process. When you export a XML file for the first time, the XML file is created based on the project data in LN. When you import the XML file from an ESP, additional ESP information is stored on the server which also includes information that is not used in LN. In further export and import processes updates are made to the existing XML information. There can be a number of reasons to use the regenerate flag:
    • In case of import errors, however, the user may decide to continue with the data that is available in LN and which is validated by LN during the import process.
    • In some External Scheduling Interfaces, the options must be modified to ensure that the next XML export is effective. Note: The regenerate process is used to recreate the XML file for the export process based on the LN data; the information that is not used by LN is deleted.

  • Task Name based on

    You can use this option to meet the Code and Description requirements when customers include explanatory Activity codes and Budget Line Cost Objects; or if descriptions are used for Activities and Budget Line Cost Objects. For example, numbers are used for Activity codes and Budget Line Cost Objects.

  • Use LN Calendars

    You can use this option to switch the process to export calendars, for example, if LN calendars are not relevant or are only required to test the XML code. When you use the option to exclude calendar information, XML files are smaller and issues in the calendar setup in LN can be avoided. Note: If the calendar must be exported again because the data is considered relevant, you must use the Regenerate option

  • Show Warnings

    Use this option to display warnings if any issues occur during the import or export process. When you export a XML file, errors can occur during the ERP Enterprise setup or if data such as dates or conversion factors is missing. Using this option, you can easily identify these issues. Note: Using the application, you can override issues during the process by defining assumed values. However, irrespective of the specified assumed values, all warnings are displayed at the end of the process. If warnings must not be displayed because the related issues are acceptable or if accurate data is redetermined in the External Scheduling Package, you can set the Show Warnings option to No. Note: By default, the errors are always displayed. Setting the Show Warnings option to No helps the user focus on resolving the errors.

  • Status information

    Use this option to view the status of the import or export process. When a XML file is successfully exported, the Synchronized by ERP Enterprise on <date/time> message is displayed. If the export fails, the XML Export failed message is displayed. Based on this message, you can initiate the required actions to resolve this issue. Note: To avoid inconsistent data issues, the application blocks the import of an XML, until an export is successful.

  • Project Selection

    Use the Project Selection (tppss2140m000) session to manage multiple projects that must be imported or exported from or to the external scheduling package (ESP). This allows the planner to update multiple projects simultaneously. A planner can be responsible for multiple projects and can use this session to specify the multiple projects that must be exported or imported.
Note: 
  • In the External Scheduling Package, it is recommended that you use the 'Import as a new project' option. Also, the use of the Merge and Append options (for the same project or alternate project) is not recommended, as the source XML file includes dependencies and during the merge process may result in renumbering or deletion of important information.
  • When you set up a new project in an external scheduling interface, you must follow the LN standards for a successful synchronization of the data. For example, in LN a project must only consist of one top activity, consequently the same structure must be implemented in the external scheduling interface.