You can import multiple unmanaged Solid Edge files into a Teamcenter database without starting the Solid Edge application using Add to Teamcenter. Before running Add to Teamcenter, ensure that you are able to successfully create and save Solid Edge files. Then prepare your unmanaged files for the managed environment using the tips found in Preparing unmanaged documents for Teamcenter.

The Add to Teamcenter program is made available to you when you install Solid Edge Embedded Client. To run the application, from the Start menu, choose Programs→ Solid Edge ST5→Data Preparation→Add to Teamcenter. When you run the program, the Add to Teamcenter dialog box provides options for loading your files into the Teamcenter database. Whether you are casually adding a few documents or folders, or performing a bulk import of a massive amount of data, you should start with a dry run to analyze your data and report any problems. The dry run gives you the opportunity to correct any problems found before continuing.

One of the options on the Add to Teamcenter dialog box is to perform a dry run of adding your unmanaged documents to Teamcenter. The dry run builds a list of your files and performs a series of checks including a search for broken links, validation of file name length, and a check for duplicate file names. In the event duplicate document numbers are discovered, the dry run erases the document number of one of the parts in preparation for adding the documents to the managed environment. Log files are generated that contain errors or warnings occurring during the dry run. Any files with broken links are written to a log file and you are informed that broken links were found. You are then given the opportunity to open the log file and suspend Add to Teamcenter so you can repair the links, find alternate files of the same file name but that occur in different folders, or ignore the broken links. If you choose to find alternates, the links are not updated to point to the new file, but you are assisted with finding possible replacements in order to expedite fixing the broken links.

When you run Add to Teamcenter, log files are generated that contain errors or warnings occurring during the file upload transaction. The default location for log files is determined on the File Locations page of the Solid Edge Options dialog box.

You can use log files to monitor the success or failure of your documents loading into the Teamcenter database. The log files you will interact with most often are grouped in the subfolder \Add to Teamcenter that is created when you run Add to Teamcenter. Each file uses a naming convention consisting of a description, timestamp, and file extension. For example, TALLog_20080514131232.log. The timestamp is a 14 digit unique identifier using the format YYYYMMDDHHmmss where:

• YYYY is the year. In the example, 2008.

• MM is the month. In the example, 05 is May.

• DD is the day. In the example, 14 is the 14th.

• HH is the hour using a 24-hour clock beginning at midnight which is 00 and going through 23, which is 11:00pm. In the example, 13 is 1:00pm.

• mm is the minute. In the example, 12 is 12 minutes past the hour.

• ss is the seconds. In the example, 32 is 32 seconds past the minute.

Log File	Description
AddToTeamcenter_<timestamp>.log	Contains all Add to Teamcenter settings. The setting names are not localized for this development log file.
ATTHistory_<timestamp>.xml	Contains information regarding the blocks of data being added to the Teamcenter database, the number of links within the block, and how long each block took to load. The history is only reset and cleared if you start a new Add to Teamcenter process.
SEEC User Log <unique id>.xml	Contains a summary of actions taken by the Add to Teamcenter process to correct the data and load it into the database. These actions are logged as warnings with messages specific to why the corrective action was taken. If a file fails to load, an error is shown in the summary log with a message explaining why the file failed to load. The contents of this log file displays in the SEEC Summary dialog box when you are importing files using Add to Teamcenter.
TALLog_<timestamp>.xml	Developer log that includes a timer so the total time for input is measured accurately.

When you run Add to Teamcenter, files are generated as output of the process. All output files created from one input list have the same timestamp so it is easy to identify which output file is related to another. The default location for output files is, ...\Unigraphics Solutions\Solid Edge\Version 105\Log Files\Add to Teamcenter.

Output File	Description
BrokenLinkLog_<timestamp>.xml	Contains information regarding the broken link and the parent document.
Unordered_<timestamp>.CSV	Lists input files after the completion of the scan for broken links. Double-clicking the file opens it in Microsoft Excel. Caution: This file cannot be used as input to the Add to Teamcenter process.
Ordered_<timestamp>.CSV	Contains an ordered list of your input files along with their reverse links. If a file has a reverse link, it is listed twice with two order numbers and also listed twice in the pass/fail log. The ordered list is generated by either the output from a dry run or as a result of the pass/fail log. Note: You can rename the Ordered_<timestamp>.csv file and use it as an input file to Add to Teamcenter; however the format must match the expected input. You can only submit one .CSV file for processing at a time.
SuccessFailureLog_<timestamp>.CSV	Lists the documents you are importing and provides a summary of success or failure of the import process for each file. The log is written once per Add to Teamcenter session even if you elect to suspend or retry the upload process. Double-clicking the file opens it in Microsoft Excel. The order number in this file matches the order number from the Ordered_<timestamp>.CSV file so you can match up entries between the two files during troubleshooting.

When you use the Add to Teamcenter program, some requested actions may not complete, or they may complete with warnings. In either case, a notification dialog box is displayed. You cannot start a new import of files into the Teamcenter database until the previous one is completed or canceled.

The options on the notification dialog box determine how you proceed. You can view the log generated by the process, view a summary, continue, cancel, suspend, or view help regarding the upload process.

• View Log —Displays the Add to Teamcenter log file.

• Summary—Displays the SEEC Information dialog box providing a quick summary of errors or warnings encountered during the Add to Teamcenter process.

• Continue-Continues the Add to Teamcenter process and starts loading the files into the managed environment. This option is disabled if there are errors noted.

• Cancel—Exits the Add to Teamcenter process so you can start over. Any processing is discarded and the queue is cleared of documents being loaded into Teamcenter. You are returned to the Add to Teamcenter dialog box.

• Suspend—Interrupts processing and exits the Add to Teamcenter program, but leaves the import queue intact. Data already created in Teamcenter is not deleted. When you later restart the Add to Teamcenter process using the Retry button, the files resume loading from this point.

• Help—Displays help information regarding the dialog box.

If you previously suspended the transaction, the notification dialog box is displayed automatically when you next start the Add to Teamcenter program.

The Add to Teamcenter program compares the item number, revision, and dataset values of a document with those existing in the Teamcenter database. As a result, you can import files over files that already exist in the Teamcenter database. Add to Teamcenter adds the import time to the original file, and on subsequent loads it checks to see if the modified date is after the import date. If the document being imported has not been modified since the last import, it is recognized as already being in the database and is not re-added to Teamcenter on subsequent imports. However, if the unmanaged file is modified after its initial import into the database, on subsequent imports you are given the options to:

• Check out the document and overwrite it.

• Check out all files that exist and overwrite them.

• Leave the file and use the file already in the database.

• Leave all files and use the ones that already exist in the database.

• Cancel the import process.

In the event the Add to Teamcenter comparison discovers an item number that already exists in the database, it compares the file being imported to all revisions, datasets, and files that comprise the dataset. If a match is found, you are given the opportunity to determine the action on the file being imported. If no match is found, the file is assigned a new item number and a record of the action will be placed in the log file.

For example, if the following information exists in Teamcenter:

Then when you import a file with 000100 as the document number, a comparison is made between the file name of the file being imported against all named references (ie., part1_04112007.par and 000100.par in this example). If it matches, you are given the option to overwrite the file. If you choose not to overwrite, the file is assigned a new item ID, which is recorded in the log file.

A BOM validation is also a component of the Add to Teamcenter process for all assembly (.asm) and weldment (.pwd) files. This validation considers the references in Solid Edge compared to the corresponding Item Revision view and first level children to ensure that the number of links Teamcenter recognizes in the file matches the number of Solid Edge reports that it has. If a mismatch occurs, an error is recorded in the developer log file indicating the file name and number of occurrences. The summary log indicates the document failed to load if the number of occurrences does not match after all retries.

Families of Parts (FOP) are represented in Teamcenter by a set of relations. These relations are equivalent to those found in Solid Edge in that there is a bidirectional link between the master and the children. The master points to children and the children point to the master.

There are three conditions where the FOP's can have bad links in a Teamcenter-managed environment:

• A child points to a single master, but the master is missing the reference to the child.

  

• A child has more than one master. For example, a child points to a master and that master points back to that child, but another master also points to the same child.

  

• A master points to a child, but the child does not point to the master. This can happen when the child was deleted and replaced with a document of the same name or type.

  

In each of these cases, a warning is recorded in the log file during both the dry run and the upload into Teamcenter indicating the file names of the master and child along with a recommendation for resolving the warning.

• Suspend or pause Add to Teamcenter

• Add unmanaged documents to Teamcenter

• Migrate a standard part to Teamcenter

• Assign unmanaged documents to a project during Add to Teamcenter

• Preparing unmanaged documents for Teamcenter

• Manage documents and data