Siebel Professional Services Automation Guide > Microsoft Project Integration > Administrator Procedures for Microsoft Project Integration >

Creating Mapping Templates

If your organization needs templates that differ from those provided with Siebel Professional Services Automation, you can create them. The following procedure explains how to create a mapping template.

NOTE:  The Start and Finish columns in Microsoft Project's Resource Sheet are auto-populated based on resource assignments. Therefore, resource Start Date and End Date values from the Siebel Project Team Workbook view cannot be exported to Start and Finish columns in a Microsoft Project Resource Sheet. If these two fields need to be exported to Microsoft Project, map the Siebel Start Date and End Date fields to Start1 and Finish1 fields in Microsoft Project.

To create a mapping template

1. Navigate to the Administration - Data screen > Project Mappings view.
2. In the Project Mappings list, create a new record.
3. In the Project Mappings list, in the Mapping Name field, enter a name of your own choosing to identify the mapping template you are creating and the data relationships it defines.
4. In the Description field, enter a description of the mapping.
5. In the Mapping Categories list, add a new record.
6. In the new record, select the appropriate category from the Category drop-down list:
   • If you are creating a mapping template for importing and exporting project resource information, select Project Resources.
   • If you are creating a mapping template for importing and exporting task information, select Tasks.
   • If you are creating a mapping template for importing and exporting both project resource and task information, choose either category. After you finish defining mappings for the first category you choose, a later step of this procedure will direct you to repeat the necessary steps to define mappings for the other category.
7. In the Category Fields list, below the Mapping Categories list, create a new record.
8. Complete the necessary fields.

   Some of the fields are described in the following table.

   Field	Comments
   Comments	Text field for comments about the mapping between the specified Siebel field and the specified Microsoft Project field.
   Import/Export	Indicates whether the mapping specified in this record can be used to import data from Microsoft Project into the Siebel database, export data from the Siebel database into Microsoft Project, or both.
   MS Project Field Name	Name of a field in Microsoft Project that you want to map to the Siebel field specified in this record. Available values are set in the PS_MPP_FIELD_TYPE list of values. Some items listed in the MS Project Field Name drop-down list may not have corresponding Siebel fields. If a corresponding Siebel field does not exist, an extension field can be created. For more information on creating an extension field, see Using Siebel Tools and Configuring Siebel eBusiness Applications.
   Sequence	(Optional) Determines the order in which the fields from the Siebel application that have Sequence specified will be exported to Microsoft Project. This sequence can affect scheduling. When fields have interrelated values, the last field to be exported determines the outcome. For example, if Start and Duration are exported before End, Microsoft Project calculates a value for Duration, instead of using the exported value. If Start and End are exported before Duration, Microsoft Project calculates a value for End, instead of using the exported value.
   Siebel Field Name	Name of a Siebel task or resource field that you want to map to the Microsoft Project field specified in this record. Available values are the business component fields of the business component that you selected for the template's Category.

   NOTE:  Repeat Step 7 and Step 8 of this procedure until you have mapped each needed field for the selected Category. If you need an additional Category for this template, repeat Step 6 through Step 8 of this procedure, specifying the additional Category in Step 6.