Transfer of data

This chapter describes the data that the user can transfer, which includes the following:

  • Calendars
  • Projects
  • Cost object/resources
  • Activity structures
  • Budget lines
  • Schedule information
  • Baselines
  • Standard activities (Activity Relationship)

LN Common Data features a Central Calendar (CCP) module that contains calendars used throughout the LN packages. Microsoft Project must have a copy of these LN calendars.

LN enables the selection and transfer of calendars used in Microsoft Project.

The following figure provides an overview of the calendar hierarchy:
[...]

In the Calendar Selection for External Scheduling Packages (tcccp0181m000) session, you can specify the calendar that needs to be transferred to Microsoft Project as the base calendar .You can define a calendar for availability types that is a work-time type, for example, you can define a calendar in which, the workday starts at 8:00 A.M. and ends at 5:00 P.M., in LN Calendars (tcccp). You can use the availability type to differentiate, for example, availability for projects from availability for service, or maintenance, activities for the same period. One resource can have one calendar but multiple availability types. Because multiple availability types can be defined as part of the same calendar, the user must select the most relevant type to be used in a linked external scheduling package, such as Microsoft Project. For the selected availability type, a base calendar is created and the standard calendar details for this availability type are transferred.

LN calendars

In LN calendars, you can have a multiple-level-calendar hierarchy. As you move down in the hierarchy, you see that the exceptions to the derived-from calendar are maintained.

In Microsoft Project, you can transfer only the base calendars and any resource calendar transferred is set as derived-from these base calendars. However, exceptions in the complete derivation path are transferred to the resource calendars. By default, the resource calendars are defined with the name of the resource itself.

To retain the hierarchy information, the base calendar codes contain the complete derivation path with the correct punctuation, a dot between every level.

To access the calendars, in Microsoft Project, on the Tools menu, click Change Working Time.