Importing Planning Data

Note: This menu option only appears for DBA.ADMIN users.

This page is accessed via Operational Planning > Planning Data Import/Export > Import Planning Data.

You can import planning data that was exported using the export planning data tool. This allows you to export planning related data from an OTM production system or domain and import that data to an OTM LNM server or domain (both systems must be on the same version of OTM) for analysis. See Logistics Network Modeling Overview for more details.

1. Select a Transaction Type:
   • II: Stands for Insert and Ignore. When used, if the record already exists, then it is not updated. If it does not exist, then it is inserted.
   • IU: Stands for Insert and Update. Create a new record unless it already exists, in which case update the existing record with the new information. This is the default.
2. Make sure the Template-based Import check box is not selected.
3. Click Choose File to specify an Input Zip File. This must be a zip file created using Export Planning Data.
4. Click Upload and the page updates to show new input fields.
5. To run the action in the background, select Yes for the Run in Background.
   
   If you selected Yes for Run in Background, select a contact in the Contact ID field.
6. Specify the From Domain and To Domain:
   1. Select a From Domain. The list of domains is populated based on the manifest.xml file included in the input zip file that was created when you exported the planning data. The domain from which the planning data was exported will have (Primary) after it.
      
      You must ensure that the From and To Domains have the necessary domain grants. Any domain with grants to the primary domain should have read and write access granted to the rest of the To Domains.
   2. Specify a To Domain.
   3. Click Save.
7. Click Submit.

You see a Results screen.

Note: If you use the transaction type of IU and data already exists in the To Domain, ensure that the domains do not have identical modeling scenario IDs. The system will not validate the output of scenario bulk plans being imported and, as a result, you may get data corruption.

Using the Results Screen

The system validates the data for any missing primary keys, missing value for non-nullable columns, etc.

On the Results screen, you see the following buttons depending on the status of the import:

• Refresh: Click to update the page and monitor how the import is progressing. You can use a combination of the Status and Time to monitor a running process.
• Done: Click to return to the main import screen.
• View Log: Click to view the OTM log file. It is recommended that you turn on the Planning Data and Planning Data Log IDs so that your log file contains logging specific to export and import of planning data.
• Download: Only available if there are validation errors during import.

The Message/Results field at the top of the page displays the current status in a message, such as:

• Running: The import process is running.
• Partially Completed: The import process is complete with validation errors. Only the good data is committed. To view the records with errors, click Download to download a .zip file. You can make changes to the .csv files included in the .zip file and retry the import.
• Completed: The import process completed successfully.
• Failed: The import process failed for reasons other than validation. View the log files to diagnose.

The Process States grid shows the following data:

• Process: Lists the main process that are a part of importing data, such as loading metadata, unzipping files, etc.
• Status: Lists one of the possible statuses such as Running, Partially Completed, Completed, or Failed.
• Time: Time in seconds of the running or completed process.

The Objects grid shows the following data:

• Object Type
• Count

Downloading the Errors .zip file

To view the records with errors, click Download to download a .zip file. The ErrorDetails.txt file includes details of the errors. You can make changes to the .csv files included in the .zip file, re-zip the files, and retry the import.

If there are missing references, a template csv file is included in the error zip file, so that you can conveniently add the missing data. For example, if a location is missing from the imported files, an empty LOCATION.csv file is included in the error zip file so that you can enter the missing location.

While fixing data, take care that the domains specified on corrected records are the domains in which data has to be imported.