| Data mapping: export data from PCS to Microsoft ProjectTo work on PCS projects in Microsoft Project, use the Export / Import PCS Activities via XML (tipcs4172m000) session to transfer data
related to the PCS projects in LN to Microsoft Project . The table shows how data in LN matches the data
in Microsoft Project. If no matching field exists, automatically a custom field is
inserted in Microsoft Project. To display custom fields in the Microsoft Project grid, do the
following: - Right-click on the column header.
- Select insert column.
- In the column definition screen, select field name text3,
text4, text5, text6 or text7.
To modify GLOBAL.MPT, so that custom fields are displayed in
the grid by default: - Copy GLOBAL.MPT, which is located in C:\Documents and
Settings\<user>\Application Data\Microsoft Data\Microsoft\MS
Project\11\1033\.
- Perform the steps described above to display customs fields,
and save the template file.
- Replace the GLOBAL.MPT file by your modified copy.
Note You can always recover the original GLOBAL.MPT
file: - Delete the modified MPT file.
- Create a Microsoft Project file. A new GLOBAL.MPT file is
copied from the globally installed template located in C:\Program
Files\Microsoft Office\OFFICE11\1033\.
LN | Microsoft
Project | Remarks |
---|
| | | PCS Project | Summary Task | -- |
---|
Project | Task Name | -- | Description | LN Task Description (custom
field) | -- | The PCS start dates
and end dates are not exported. Microsoft Project determines the project's
start date and end date during loading the XML file into Microsoft Project,
based on the dates of the individual tasks. | | A Microsoft Project file consists of only one project.
This project can contain all activities of multiple LN PCS
projects. | PCS Planning Method | ScheduleFromStart | -- | Project (selection range) - Start Date of first project
- Completion Date of last project
| | A Microsoft Project file consists of only one project.
This project can contain all activities of multiple LN PCS
projects. | | Fixed values: - DurationFormat: 5 (=hours)
- DefaultFixedCostAccrual: 3 (=end)
- Project ExternallyEdited: 0 (no)
| -- | Activity | Task | -- |
---|
Activity | Task Name: <project
code> - <activity code> | -- | Description | LN Activity Description (custom
field) | -- | Task | LN Task (custom field) | -- | Task | LN Task Description (custom field) | -- | Activity Manager | LN Activity Manager (custom field) | -- | Work Center | LN Work Center (custom field) | Refer also to Resource | Calendar that is valid for the activity's work
center: - Availability as defined in routing
parameters
- Company calendar or work center calendar, dependent on Used Calendar Type in the routing
parameters.
| Calendar - Value: <availability> .
<calendar>
- IgnoreResourceCalendar: 1 (=yes)
| Microsoft Project only uses the task calendar.
The work center calendar is not used. | --- | Task Type: Fixed Work | -- | - Desired Start Date
- Desired End Date
If these fields have no dates, other date fields are used: - In case of forward planning: Earliest Start Date and Earliest End Date
- In case of backward planning: Latest Start Date and Latest End Date
| | -- | Activity Duration | Duration | The duration in LN is the number of
working hours between the Desired Start Date and the Desired End Date. Dependent on the routing parameter,
the calendar of the activity's work center or the company calendar is used to
calculate the number of hours. Refer also to Desired Start Date and Desired End Date. Microsoft Project uses Start Date, Duration, and the
imported Calendar definition to calculate the task's Finish Date. | Preceding Activity (as defined in Activity Relationships (tipcs4110m000)) | Predecessor | The float time in days is multiplied by the work center's basic
capacity to convert the time to hours (working time). In Microsoft Project, the float time is imported in
hours, but the time is displayed in days (working time). The calendar of the
current task ( Next Activity in Activity Relationships (tipcs4110m000)) is used to offset the time. | Calendar | Calendar | -- |
---|
All
calendars used for the network planning are exported to Microsoft Project - Availability type as defined in the routing
parameters
- Dependent on the routing parameter, the company
calendar is exported, or a calendar for each work center. For each calendar the
default availability type as defined in the routing parameters is
exported.
- A maximum of three working time blocks per day is
exported.
| Calendar - Value: <availability> .
<calendar>
- Calendars are linked to tasks
| -- | Work
Center | Resource | -- |
---|
Work Center (used on the activity) | Resource - For each task, a custom field 'LN Work Center' is
available
- During XML import, resources are not formally linked to
tasks
| -- | Code | Name | -- | Calendar | Calendar | -- |
| |