TeamcenterKnowledge

Schedule Management > Exchanging data between Microsoft Project and Schedule Manager > Map custom schedule task properties between Microsoft Project and Teamcenter Schedule Manager

Map custom schedule task properties between Microsoft Project and Teamcenter Schedule Manager

Use this procedure to map custom schedule task properties between Microsoft Project and Teamcenter Schedule Manager. This ensures that when a Microsoft Project schedule is imported into Schedule Manager, custom property data is transferred and does not have to be manually re-entered.

Teamcenter uses two Schedule Manager preferences to manage the import of schedule task properties:

  • SM_MPP_OOTB_MAP — a system preference that identifies the out-of-the-box (OOTB) schedule task properties included during the import process. These values cannot be modified.
  • SM_MPP_CUSTOM_MAP — a site preference, set by a system administrator, used to identify any custom properties of schedule tasks.

Teamcenter Schedule Manager supports the following custom property types: Boolean, Character, Date, Double, Integer, String, and Long String.

Note: Only custom properties for out-of-the-box schedule tasks are supported.

Procedure

  1. If your custom task properties don't already exist, create them using the Business Modeler IDE and then deploy your template.

  2. Use the SM_MPP_CUSTOM_MAP preference to map the custom properties of schedule tasks with the Microsoft Project task fields. You can view the preference syntax in the Edit → Options dialog box.

  3. Match Microsoft Project fields to Teamcenter Schedule Manager property types:

    Microsoft Project task field Type
    Date1–10 Date
    Flag1–20 Boolean
    Number1–20 Integer, Double
    Text1–30 String, Character, Long String
  4. Add the custom properties to the tcmspaddin.xml policy file. This file is typically located in TC_DATA\soa\policies.

  5. (Optional) If you want to display the properties in Teamcenter Schedule Manager, add the custom schedule task properties to the stylesheet.

  6. Restart the server.

Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.plm00054/xid1503697 · retrieved 2026-07-10