A Smart Import (by definition) is an import mechanism that matches objects between a system (e.g. SAP, Excel) and CiteOps with proactive issue detection and resolution.

CiteOps' Smart Import now allows work orders to be imported using excel spreadsheets. This guide explains how to import work orders in CiteOps using an excel spreadsheet.

This guide provides instructions on:

To import a spreadsheet from the Process Plan screen, please follow the steps below

1. Click on the Planning Board icon.

2. Click on the hamburger menu and then click on Import.

Info!
​Please use the following format: =Sheet1!$A:$Q where

​Sheet1 is the name of the worksheet
​

​! is the separator of the worksheet and the range (essential)
​$A:$Q is the range of the cells ($ is essential)

3. Click on the

icon to select the import spreadsheet, after that, follow the steps below:

If there were failed lookups during the import you will get the message below.

Check the Error Logs (please contact your administrator if you have difficulties accessing the logs)

Definition: An error log describes an event that causes data failure during the import. Error logs need to be investigated and fixed.

Info!
​You can access Error logs via the manage Integration screen.

The most common types of error logs for the Users Smart Import are:

Example: "Multiple CiteOps tasks in CiteOps data for 100299577020"

Explanation: More than one task exists with the same Source Id (100299577020) in CiteOps.

Possible Cause: The work order appears more than once in the Source system.

Solution: Contact the Planners of the Source system and provide the details of the work order (task) so they can delete the duplicated record(s) from the Source system.

Example: "AD Process was not found by exact match. Work Order: 600020233"

Explanation: The Source Process (AD) was not found in CiteOps by a lookup.

Possible Cause 1: The Source Process (AD) does not have a lookup that would match this Source Process to the relevant Process in CiteOps.

Solution: Add a lookup for the AD Process.

Possible Cause 2: The Source Process (AD) has a lookup that does not match an existing Process (To column is empty) in CiteOps.

Solution: Select an existing Process in CiteOps.

Possible Cause 3: A lookup exists but the From column (Source Process) has a typo in its text so the lookup can't match the Source Process to the relevant Process in CiteOps.

Solution: Contact the Planners of the Source system to get the correct name of the Source Process, correct it in the Lookup table and ask them to check the name of the Process in the Source system (for typos) to avoid further errors.

Example: "O - Occupation Type was not found by exact match. Work Order: 100274190"

Explanation: The Occupation Type (O) was not found in CiteOps by a lookup.

Possible Cause 1: The Occupation Type (O) does not have a Lookup that would match the Source Occupation Type to the relevant Occupation Type in CiteOps.

Solution: Add a Lookup for the Source Occupation.

Possible Cause 2: The Source Occupation Type (O) has a lookup that does not match an existing Occupation Type (To column is empty) in CiteOps.

Solution: Select an existing Occupation Type in CiteOps.

Example: "G Task Type was not found by exact match. Work Order: 600020295"

Explanation: The Task Type (e.g. G) was not found in CiteOps by a lookup.

Possible Cause 1: The Task Type does not have a Lookup that would match the Source Task Type to the relevant Task Type in CiteOps.

Solution: Add a lookup for the Source Task Type.

Possible Cause 2: The Source Task Type (G) has a lookup that does not match an existing Task Type (To column is empty) in CiteOps.