Importing schedules

Use the ScheduleManagerFoundationImport transfer mode to import a schedule and its related data, including properties, for all schedules created in previous versions of Teamcenter (prior to 11.2).

Note: To import the custom properties on a schedule or schedule task using PLM XML, the exported schedule must have a custom PropertySet object attached to the ScheduleManagerFoundationExport transfer mode, as described in Exporting schedules.

Use the ScheduleManagerFndImportLegacy transfer mode to import a schedule and its related data, including properties, for all schedules created in Teamcenter 11.2 and later.

Note: If you create a subclass with custom properties, these properties can be attached to the out-of-the-box transfer modes.

Import behavior notes

• Orphaned tasks are ignored during import.
• If the workflow template is not present upon import, workflow tasks ignore the template and the scheduling attribute is set to NULLTAG.
• When importing resource assignments, if the user, discipline, or group is not present, the resource assignment fails.
• When importing schedule member, if the user, discipline, or group is not present, the schedule member fails.
• Re-importing an already imported schedule into the system will not update or overwrite the existing schedule-related data. The system deletes all schedule-related data like tasks, proxy tasks, assignments, dependencies, deliverables, and calendars.

  Note: If deletion of any schedule-related data fails, the system rolls back any changes made and the import operation fails. An error message is displayed.

• The system re-imports everything from the PLM XML file.
• Set the SM_PLMXML_IMPORT_EXISTING_SCHEDULE preference to True to re-import a schedule that is already in the system. Set this preference to False to block the import of a schedule that is already in the system.