MSP: Field Mappings Between MSP and
Classic PPM

ccppmop1593
HID_admin_map_msp
Many of the standard Microsoft Project (MSP) fields are mapped to
Classic PPM
fields. Schedule Connect exchanges data between MSP and
Classic PPM
. This documentation provides the location and default name of the MSP field as it appears on the user interface. The
Classic PPM
column lists the
Classic PPM
user interface field and then the database table and column.
2
When mapping Microsoft Project fields, you can map only the existing
Classic PPM
attributes that have not been mapped and custom attributes of the Project, Resource, Task, Assignment, and Team objects with the Microsoft Project fields. Mapping is limited to the following attribute data types:
  • Date
  • Number
  • String
  • Boolean
  • Lookup string
The following business rules apply when you map the fields:
  • Static lookup string mapping requires the new MSP driver; you cannot map lookup strings with the legacy driver.
  • Changes to any mapped resource fields are not saved to
    Classic PPM
    ; because the product owns the resource record.
  • You can specify whether the mapped data can be imported, exported, or both.
  • If an Object Type and Clarity Attribute ID mapping already exist, the Create or Update operation results in an error.
  • If an Object Type and MSP Field Name already exist, the Create or Update operation results in an error.
  • For default mappings with the
    Clarity
    Attribute ID set to
    prUID
    , the Create or Update operation results in an error.
  • For mappings with
    Clarity
    Attribute ID set to
    prUID
    , you can modify only the MSP Field Name for an update operation. For example, you can change the mapping of UID from text3 to test4.
You must have the administrator rights to view the MSP Field Mappings page. In
Classic PPM
14.2, the
Clarity
Attribute ID shows its old name of Clarity Attribute ID.
Follow these steps:
  1. Open Administration, and from Project Management, click MSP Field Mappings.
  2. Click New on the MSP Mapping list page.
  3. Complete the following information and save:
    • Object Type
      Indicates the
      Classic PPM
      object to which the mapped attribute belongs.
      Values:
      Project, Task, Resource, Assignment, and Team
    • Data Operation
      Specifies the operation to perform.
      Values:
      • Import and Export: Import and export data back and forth from
        Classic PPM
        to Microsoft Project.
      • Import: Import data from the Microsoft Project field to
        Classic PPM
        .
      • Export: Export data from the
        Classic PPM
        attribute to Microsoft Project.
    • Clarity
      (Clarity) Attribute ID
      Indicates the
      Classic PPM
      attribute ID of the attribute that is being mapped in Microsoft Project. You can find the attribute ID on the Attributes tab of the respective object.
    • MSP Field Name
      Indicates the Microsoft Project field name that you want to map to the
      Classic PPM
      attribute.
      • Text and Lookup String fields: Use Text4 to Text30
      • Boolean fields: Use Flag2 to Flag20
      • Number fields: Use Number1 to Number20
      • Date fields: Use Date1 to Date10
  • If an Object Type and
    Clarity
    Attribute ID mapping already exist, the Create or Update operation results in an error.
  • If an Object Type and MSP Field Name already exist, the Create or Update operation results in an error.
  • For out-of-the-box mappings with the
    Clarity
    Attribute ID set to
    prUID
    , the Create or Update operation results in an error.
  • For mappings with
    Clarity
    Attribute set to
    prUID
    , only the MSP Field Name can be modified for an update. For example, you can change the mapping of UID of text3.
  • Duplicates in the Lookup name display with an added “(1)”, such as Capital(1), Capital(2). Inactive lookups display in MSP in the list, but are noted with an Asterisk, such as (*)inactive.
  • You can only map lookups to Text fields in MSP.
Project Information Field Mapping
The following fields map project information from Microsoft Project to
Classic PPM
:
  • Schedule
  • Project Baseline
  • Manager
  • Other Project Attributes
  • Calendar
Schedule Field Mapping
The following table maps fields from Microsoft Project to fields on the scheduling properties page in
Classic PPM
:
Microsoft Project
Classic PPM
Notes
Start Date
Start Date
PRJ_PROJECTS: PRSTART
Not Applicable
Finish Date
Finish Date
PRJ_PROJECTS: PRFINISH
Not Applicable
Schedule From
Start Imposed
This field is not displayed by default.
PRJ_PROJECTS: PRSTARTIMPOSED
Finish Imposed
This field is not displayed by default.
PRJ_PROJECTS: PRFINISHIMPOSED
If this field is displayed, the Schedule From field is set to the Start Date when you open the project in Microsoft Project. Otherwise, Schedule From is set to the Finish Date.
Status Date
As Of Date
PRJ_PROJECTS: PRASOF
You cannot programmatically set this field to NA in Microsoft Project. If the As of Date in
Classic PPM
is blank, the existing value in this field is retained.
Priority
Priority
PRJ_PROJECTS: PRPRIORITY
Priorities are translated between the range (0-1000) in Microsoft Project and the range (36-0) in
Classic PPM
.
Manager Field Mapping
The following table maps fields in Microsoft Project to fields on the general properties page in
Classic PPM
.
Microsoft Project
Classic PPM
Notes
Manager
Manager
When opening the project in Microsoft Project, this field is set to the user name in
Classic PPM
identified as the project manager. This value is not saved back to
Classic PPM
.
Title
Title
SRM_PPROJECTS:
NAME
Not Applicable
Calendar Field Mapping
The following table maps fields from Microsoft Project to the
Classic PPM
base calendar fields.
The project calendar in Microsoft Project is always reset to the base calendar in
Classic PPM
.
Microsoft Project
Classic PPM
Notes
For
Calendar Name
PRCalendar: PRNAME
Not used for resource calendars.
Base Calendar
Base Calendar
PRCalendar: PRBASECALENDARID
In Microsoft Project, only resource calendars have base calendars.
Combines system calendars with their base calendars when this information is set in Microsoft Project.
Set Working Time for Selected Dates
PRCalendar: PRVALUE
Calendar information that is defined in
Classic PPM
appears in the Set Working Time options in Microsoft Project.
Resource Information Field Mapping
General Tab
The following table maps the fields from Resource information in Microsoft Project to fields on the resource properties page in
Classic PPM
:
Microsoft Project
Classic PPM
Notes
Resource Name
Resource/Role Name
SRM_RESOURCE: Full_Name
The name of the role and non-labor resource in
Classic PPM
. For labor resources, the concatenated last and first name of the resource without commas.
When opening the project in Microsoft Project, commas are replaced with a space. When saving the project back to
Classic PPM
, spaces are replaced with commas.
Initials
Resource ID
SRM_RESOURCE: UNIQUE_NAME
When saving the project to
Classic PPM
, this field checks for an existing
Classic PPM
resource ID.
If the matching resource ID is found, the project is saved to
Classic PPM
. If no matching resource ID is found, you are asked to provide a valid resource ID.
Resource Type
Employment Type
SRM_RESOURCE: RESOURCE_TYPE
In
Classic PPM
, this field is set to:
  • Work for labor resources and roles.
  • Material for all other resource types.
Generic
n/a
This field is set to On for roles and set to Off for resources.
Booking Type
n/a
Not mapped to
Classic PPM
, but the value is retained in the .MPP file.
Email
Email Address
SRM_RESOURCE: EMAIL
Not Applicable
Group
Category
PRJ_RESOURCES: PRCATEGORY
Not Applicable
Code
Input Type Code
PRJ_RESOURCES: prTypeCode
Not Applicable
Resource Availability
In Microsoft Project, resource availability is the units that a resource is available to work on the project. In
Classic PPM
, resource availability is based on the system-wide availability of the resource in hours, and the percent a resource is allocated to projects.
When opening a project in Microsoft, the resource availability is set from
Classic PPM
using the following formula:
  Resource systemwide Availability * Resource Project % Allocation
The following table maps the resource availability fields in Microsoft Project to fields on the project team staff page and resource properties page in
Classic PPM
:
Microsoft Project
Classic PPM
Notes
Not Applicable
PRJ_RESOURCE: PRAVAILCURVE
Used only for labor resources in Microsoft Project.
This field is combined with the resource-to-project allocation information when opening the project in Microsoft Project. The field gets factored out when saving the project to
Classic PPM
.
Not Applicable
PRTeam:
PRALLOCCURVE
Used only for labor resources in Microsoft Project.
This field is combined with resource availability when opening the project in Microsoft Project and then gets factored out when saving the project to
Classic PPM
.
Available From
Project Team: Staff: Start
PRTeam:
PRAVAILSTART
When saving the project to
Classic PPM
, this field is set to the date the resource is available to finish the project.
If the Available To field is set to NA in Microsoft Project, this field in
Classic PPM
is set to blank indicating that the resource is available when the project starts.
Available To
Project Team: Staff: Finish
PRTeam:
PRAVAILFINISH
When saving the project to
Classic PPM
, this field is set to the date the resource is available to finish the project.
If the Available To field is set to NA in Microsoft Project, this field in
Classic PPM
is set to blank indicating that the resource is available when the project starts.
Working Time Tab
Work Time information in Microsoft Project is set to the base calendar and any resource-specific exceptions from the resource calendar settings on the edit resource calendar page in
Classic PPM
. The calendar is used only for labor resources in Microsoft Project.
Costs Tab
When opening the project in Microsoft Project, cost information is set to the first cost rate table from the
Classic PPM
cost matrix.
Task Information Field Mapping
The following table maps fields from Microsoft Project to fields on the task properties page in
Classic PPM
:
Microsoft Project
Classic PPM
Notes
General Tab
Name
Name
PRTask: PRNAME
When saving the project to
Classic PPM
, if the Name field is blank in Microsoft Project, it is set to the
Classic PPM
internal ID.
This field cannot be blank.
Text1
ID
PRTask: PREXTERNALID
Task ID in the same project must be unique in
Classic PPM
(except blank).
Start
Start
PRTask: PRSTART
The same calendar information is reflected in the Set Working Time in Microsoft Project.
Finish
Finish
PRTask: PRFINISH
The same calendar information reflected in the Set Working Time options in the Change Working Time dialog.
Duration
Duration
This field is not displayed by default.
PRTask: PRDURATION
In Microsoft Project, you can set the duration unit in the
Duration is entered in
field on the Options dialog (Tools, Options).
Elapsed durations are converted to their equivalent in work time duration, but the model is changed.
Priority
Priority
This field is not displayed by default.
PRTask: PRPRIORITY
Priorities are translated between the range (0-1000) in Microsoft Project and the range (36-0) in
Classic PPM
.
Precision is lost.
Flag1
Key Task
PRTask: PRISKEY
The default mapping, which you can change.
Any user text field
Charge Code
PRTask: PRCHARGECODEID
The name of the charge code appears in Microsoft Project. To modify the charge code for a task, use the drop-down to select from the list of available codes.
% Complete
% Complete
PRTask: PRSTATUS
and
PRTask: PRPCTCOMPLETE
The task status is set to "Started" when the percent complete is greater than zero, or to "Complete" when it is 100. Otherwise, this field is set to "Not Started".
Advanced Tab
Mark Task as Milestone
Milestone
PRTask:
PRISMILESTONE
In Microsoft Project, any task can be flagged a milestone as a means to drive Gantt bar rules. For example, drawing the diamond and other features such as filtering. Microsoft Project automatically sets this flag when a task acquires zero duration.
Calendar
You can use calendars in Microsoft Project, but the list of available calendars comes from
Classic PPM
.
Task Type
Fixed Duration
PRTask: PRISFIXED
All task types in Microsoft Project are supported. In Microsoft Project:
  • Fixed duration task type maps to True.
  • Fixed unit and fixed work maps to False.
Effort Driven
No Mapping
Tasks flagged as Effort Driven in Microsoft Project take more processing.
If there are many tasks, system memory requirements and performance can degrade noticeably.
Constraints
The constraints that are defined in Microsoft Project are stored in
Classic PPM
, but you cannot edit them from Schedule Connect.
Microsoft Project automatically sets the Start No Earlier Than constraint to hold a task start date. If you add a Start No Earlier Than constraint and Microsoft Project then adds a later Start No Earlier Than constraint to hold a task start date, the saved Start No Earlier Than constraint is not set.
Constraint Type
No
Classic PPM
user interface field available
PRConstraint: PRTYPE
When opening the project in Microsoft Project, if multiple constraints in
Classic PPM
exist for a task, the first constraint that is encountered is processed.
Constraint Date
No
Classic PPM
user interface field available
PRConstraint: PRTIME
Not Applicable
Resource Assignment Information Field Mapping
The following table details the resource assignment information that is mapped from Microsoft Project to fields in
Classic PPM
.
Any assignment that exists in
Classic PPM
when a timesheet for that resource is posted gets an Actuals Thru date equal to the end of the timesheet period. Conditions can exist where you inadvertently place remaining work before this date. The following examples illustrate this condition:
  • A task has actuals that end before the Actuals Thru date and has no remaining work, but require to add work. You enter an updated Remaining Work amount and Microsoft Project places it at the end of the task, which is in the prior week.
  • A task is scheduled to start next week and has not yet started. You remove a predecessor dependency on the task, which reschedules the task to two weeks ago.
When these situations occur, the work is moved beyond the Actuals Thru date when you save the project to
Classic PPM
. A message appears warning you of the change.
Changes to any mapped resource fields are not saved to
Classic PPM
because the product owns the resource record.
Microsoft Project
Classic PPM
Notes
Units
Max % Load
PRAssignment: PRESTMAX
When opening the project in Microsoft Project, this field is set to the value in
Classic PPM
multiplied by the resource maximum units (or by 1 if the maximum unit is 0). This value is set only for the not contoured assignment of labor resources to unfixed tasks.
When saving the project to
Classic PPM
, this field is set to the assignment units divided by the resource maximum units. If either value is 0, sets the value to 1. This value is set only for assignments of labor resources.
Number1
Task Assignment: Proposed ETC (Not displayed by default)
PRAssignment: PRPENDESTSUM
When opening the project in Microsoft Project, this field is set to the value in the field or to -1 when the Pending Estimates in
Classic PPM
is blank.
This field is saved to
Classic PPM
only in these situations:
  • Either the project or the assigned resource is tracked in
    Classic PPM
    (the Track Mode is set to Clarity or Other).
  • Value is -1, which clears the Pending Estimates in
    Classic PPM
    .
Number2
Pending Actuals (not displayed by default)
PRAssignment: PRPENDACTSUM
This field is not saved back to
Classic PPM
.
Task Properties: Status
PRAssignment: PRSTATUS
This field is set to the following:
  • Not Started. There are no actuals in Microsoft Project.
  • Started. The remaining work is greater than 0.
  • Complete. There is no remaining work.
Resume
Actuals Thru Date
PRAssignment: PRactThru
This field must always be on or after the last day of the actuals on the assignment.
If either the project or the assigned resource has Track Mode set to None, the following applies:
  • This field can be implicitly modified to correspond with updates to actuals when saving the project to
    Classic PPM
    .
  • If the Resume field is set beyond the first day of the remaining work, the remaining work is modified when saving the project to
    Classic PPM
    .
Actual Work
Actuals
PRJ_BASELINE_ DETAILS:
PREXTENSION
This information is saved to
Classic PPM
only if the Track Mode is set to None for either the project or the assigned resource.
Remaining Work
Assignment Properties:
Assignments: ETC
Work
Assignment Properties:
Assignments: Actuals and ETC
PRASSIGNMENT: PREXTENSION
This field is set when saving to
Classic PPM
and is a combination of Actual Work and Remaining Work. Only the Remaining Work portion is saved back unless the assigned resource has Track Mode set to None.
Baseline Start
Assignment Properties: Baseline: Baseline Start Date (not displayed by default)
PRJ_BASELINE_ DETAILS:
START_DATE
Not Applicable
Baseline Finish
Assignment Properties: Baseline: Baseline Finish (not displayed by default)
PRJ_BASELINE_ DETAILS:
FINISH_DATE
Not Applicable
Baseline Cost
Assignment Properties: Baseline: Baseline Cost (not displayed by default)
PRJ_BASELINE_ DETAILS:
COSTSUM
Not Applicable
Baseline Work
Assignment Properties: Baseline: Baseline Usage (not displayed by default)
PRJ_BASELINE_ DETAILS:
USAGESUM
You must have Modify Baseline rights to save a baseline to
Classic PPM
.
Notes Field Mapping
The following table maps fields from Files Properties or from Task Information, Resource Information, and Assignments in Microsoft Project to fields in
Classic PPM
.
Microsoft Project
Classic PPM
Notes
None
PRNote: PRCREATEDBY
This field is set to the name of the current user when saving the project to
Classic PPM
.
None
PRNote: PRCREATEDTIME
This field is set to the current system time when saving the project to
Classic PPM
.
Comments field for projects
Notes field for tasks, resources, and assignments
PRNote:
PRVALUE
Concatenates multiple notes on the same object (such as project, task, resource, or assignment) into a single Notes field when opening the project in Microsoft Project.
How Notes Are Saved Back to
Classic PPM
The Internal ID is the key that is used to identify the note when the note is saved to
Classic PPM
. Do not edit the note or any information. New notes are added after the Add new note(s).
The Intern[date/time note is entered by the user (internal ID)] note #1 [date/time note is entered by the user (internal ID)] note #2 Add new note(s) under here:
A hard return starts a new note. Blank lines are removed.
Private Field Mapping
The Text3 field is for Resource, Project, Task, and Assignment. This field is used for information that Schedule Connect requires. If your organization uses Text3 for another purpose, change the mapping.
Relevant mapping is for PRUID. You must have it mapped. Do not remove it without remapping. These mappings are system-wide. You cannot remap Text3 on one project and cannot keep the same on other projects.
The Text4 field is for the work breakdown structure (WBS). Schedule Connect uses this field internally to order the WBS when opening the project in Microsoft Project. You cannot remap this field.
The following table maps private fields.
Microsoft Project
Classic PPM
Notes
Custom property/prVersion
PRJ_PROJECTS: PRVERSION
Sets the version (internal use only) when opening the project in Microsoft Project and when saving back to
Classic PPM
.