Bookshelf v7.5: Understanding Mapping Templates (Administrator)

Siebel Professional Services Automation Guide > Microsoft Project Integration >

Understanding Mapping Templates (Administrator)

The tasks and resources you define for a project in your Siebel application can be exported to and imported from a Microsoft Project .mpp file. To exchange data between these two applications, however, you must use a mapping template that defines how Siebel fields and Microsoft fields map to each other.

Siebel Professional Services Automation includes three preconfigured mapping templates:

Tasks Only. This template maps Microsoft Project tasks and summary tasks to the Siebel Projects Tasks view. Resource information is not imported or exported. For information about specific mappings in the Tasks Only template, see Table 2.

Resources Only. This template maps Microsoft Project resources to the Siebel Projects Team Workbook view. Task information is not imported or exported. For information about specific mappings in the Resources Only template, see Table 3.

Standard. This template is a combination of Tasks Only and Resources Only templates. Information about both tasks and resources is imported or exported. For information about specific mappings in the Standard template, see Table 4.

If you create or modify a mapping template, you must assign one or more mapping categories to the template. Each category indicates the kind of fields that are mapped in the template. In the preconfigured templates described in the preceding paragraphs, the Tasks Only template is set to use the Tasks category, the Resources Only template is set to use the Project Resources category, and the Standard template is set to use both the Tasks category and the Project Resources category.

If necessary, a Siebel administrator can modify these templates or create additional templates to meet the needs of your organization. For information about creating or modifying mapping templates, see Creating Mapping Templates (Administrator) or Modifying Mapping Templates (Administrator).

Table 2. Task Only Mapping Template Between Siebel Professional Services
Automation and Microsoft Project
Siebel	Microsoft	Import	Export	Sequence
Actual End Date	Actual Finish	X	X	5
Actual Start Date	Actual Start	X	X	2
Complete Percentage	Percent Complete	X	X
Description	Text 2	X	X
Duration Hours	Duration	X	X	4
Est Cost Amount	Cost	X	X
Item Alt Type	Text 1	X	X
Name	Name	X	X
Note	Notes	X	X
Planned End Date	Finish	X	X	3
Planned Start Date	Start	X	X	1
Priority	Text 5	X	X
Resource Number (Nickname)	Resource Names	X	X
Status	Text 3	X	X

Table 3. Resources Only Mapping Template Between Siebel Professional Services Automation and Microsoft Project
Siebel	Microsoft	Import	Export
Comments	Notes	X	X
eMail	eMail Address		X
End Date	Finish	X
Full Name (calculated field based on First and Last Name)	Text 1		X
Rate	Standard Rate	X	X
Resource Number (Nickname)	Name	X	X
Role	Group		X
Start Date	Start	X

Table 4. Standard Mapping Template Between Siebel Professional Services
Automation and Microsoft Project
Siebel	Microsoft	Import	Export	Sequence
Task Mappings
Actual End Date	Actual Finish	X	X	5
Actual Start Date	Actual Start	X	X	2
Resource Number (Nickname)	Resource Names	X	X
Complete Percentage	Percent Complete	X	X
Description	Text 2	X	X
Duration Hours	Duration	X	X	4
Est Cost Amount	Cost	X	X
Item Alt Type	Text 1	X	X
Name	Name	X	X
Note	Notes	X	X
Planned End Date	Finish	X	X	3
Planned Start Date	Start	X	X	1
Priority	Text 5	X	X
Status	Text 3	X	X
Resource Mappings
Comments	Notes	X	X
eMail	eMail Address		X
End Date	Finish	X
Full Name (calculated field based on First and Last Name)	Text 1		X
Rate	Standard Rate	X	X
Resource Number (Nickname)	Name	X	X
Role	Group		X
Start Date	Start	X

While you are planning the details of how data will be exchanged between Siebel Professional Services Automation and Microsoft Project, be sure to consider the following constraints:

List of Values. If a Siebel task or resource field is implemented as a list of values (LOV), and if it will receive imported data from Microsoft Project, the list of values available for the field must contain the exact values that will be imported, with the case matching for each character of the imported value. For example, the Priority, Status, and Type fields in Siebel Professional Services Automation are implemented as LOVs. For information about modifying LOVs, see Siebel Applications Administration Guide.

Resources. If resources in Microsoft Project are specified using User IDs, exactly the same User IDs must be must be reflected in the Siebel application's employee list, using the same case for each character.

Configuration. Not every field in Microsoft Project can be imported or exported without configuration in Siebel Tools.