<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/msproject/int/in000330" xml:lang="en">
   <Header>
      <Title>Connect the project</Title>
      <Keyword type="header" order="d1e2262373">
         <Level1>Connect project</Level1>
      </Keyword>
      <Keyword type="header" order="d1e2262376">
         <Level1>Project</Level1>
         <Level2>connect</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>After you define a proper project structure in LN, you can
		schedule the project in a Microsoft Project. You must, however, save the
		current project on the Microsoft Project before you attempt the
		connection.</Paragraph>
      <Paragraph>Use the <GUIRef href="" role="manual">Save As</GUIRef> option to save the file with a
		name that identifies the file with the project in LN. This
		Microsoft Project name is written in a record that is inserted in the LN External
		Schedule Links (tppss230) table. The same name appears for all the connected
		budget lines near the <GUIRef href="" role="manual">ESP Link</GUIRef> field.</Paragraph>
      <Paragraph>Example:</Paragraph>
      <Paragraph>You connect an LN Project <GUIRef href="" role="manual">Microsoft Project test</GUIRef> for the
		plan <GUIRef href="" role="manual">A1</GUIRef> to Microsoft Project. You must save this connected
		project to a file in Microsoft Project, for example, <GUIRef href="" role="manual">Connection 1</GUIRef>. This file name appears in the <GUIRef href="" role="session">External Schedule Links (tppss2530m000)</GUIRef> session and is added to the records of
		all the budget lines that are linked to this project in Microsoft Project. If
		you click the <GUIRef href="" role="manual">Connect Project</GUIRef> option, the following message
		appears:</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="119" width="315"
                   SRC="images/tr_screen_in000330_1.png"
                   alt="[...]"/>
      </Figure>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Log files</SectionTitle>
      <Keyword type="section" order="d1e2262416">
         <Level1>Log files</Level1>
      </Keyword>
      <Paragraph>Microsoft Project creates log files during connection to LN in which
		you can see if the connection is successful, or check what went wrong during
		the connection. The log files are saved in the directory where you save your
		Microsoft Project file. The naming convention used is: &lt;project
		name&gt;.log.</Paragraph>
      <Paragraph>When you connect a project the following Log file is generated.
		The file displays the data transferred and alerts you to problems, if
		any.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="519" width="765"
                   SRC="images/tr_screen_in000330_2.png"
                   alt="[...]"/>
      </Figure>
      <Paragraph>The log file displays the errors that can occur when Microsoft
		Project integrates with ERP. For example, if the log file says, "Labor is not
		transferred," you can conclude that the <GUIRef href="" role="manual">Labor Cost Object Link with the External Package</GUIRef> check box is not selected.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Connect Microsoft Project to LN Project</SectionTitle>
      <Keyword type="section" order="d1e2262433">
         <Level1>Connect project</Level1>
         <Level2>MS Project to LN</Level2>
      </Keyword>
      <Paragraph>The LN data is transferred to the saved project. If you have
		entered data in this file, the LN data replaces this data.</Paragraph>
      <List>
         <ListIntro>The following data is transferred while the project is
		  connected to LN:</ListIntro>
         <ListItem>Calendar data</ListItem>
         <ListItem>Resources, which includes standard types/project
		  types</ListItem>
         <ListItem>Activity structure</ListItem>
         <ListItem>Activity/Budget Line relationship data</ListItem>
      </List>
      <Paragraph>When you connect the project in Microsoft Project to the project
		in LN, the
		scheduled start and finish dates in LN, if any, are transferred to Microsoft
		Project. This only happens when you establish the connection for the first
		time, after which, the ownership of the scheduled dates rests with Microsoft
		Project.</Paragraph>
      <Note>
         <SectionTitle> Note</SectionTitle>
         <Paragraph>The connection you make is logical, which you must carry out
		  only once for every project.</Paragraph>
      </Note>
      <Paragraph>To connect to the LN Project, go to <GUIRef>
            <GUIRef href="" role="manual">File</GUIRef> &gt;   &gt; <GUIRef href="" role="manual">LN Project</GUIRef> &gt;   &gt; <GUIRef href="" role="manual">Connect Project</GUIRef>
         </GUIRef>.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <FigIntro>The following screen appears:</FigIntro>
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="437" width="662"
                   SRC="images/tr_screen_in000330_3.png"
                   alt="[...]"/>
      </Figure>
      <List>
         <ListIntro>The Connection tab contains the following fields:</ListIntro>
         <ListItem>Company: The default back component maintained in the
		  OpenWorldX Adapter Configuration provides the company.</ListItem>
         <ListItem>Projects: From this list, select the LN project
		  code. The project information is retrieved from LN and entered
		  automatically in this form.</ListItem>
         <ListItem>Start Date and Finish date: These fields display the start
		  date and finish date of the LN Project, for information purposes only.</ListItem>
         <ListItem>
            <List>
               <ListIntro>Plan: The activity structure from the plan is used. By
				default, the leading plan is displayed, but you can choose another plan. You
				cannot connect a plan that meets any of the following criteria:</ListIntro>
               <ListItem>Already has a live link to a Microsoft Project on the
				highest level.</ListItem>
               <ListItem>Has a project with the Active status.</ListItem>
            </List>
         </ListItem>
         <ListItem>Connection node: The activity node taken from the activity
		  structure to which the connection is made. The activities connected to the node
		  are used in Microsoft Project. You cannot link an activity to Microsoft Project
		  if the node either above or below this element is already used for another
		  project.</ListItem>
         <ListItem>Select Node: Click this button to make the activity structure
		  available as a tree. You can select an activity for connection, which is then
		  filled in the Connection Node field. The button is available only if activities
		  are defined under the selected LN Project plan.</ListItem>
         <ListItem>Ownership: Set the ownership of activity structure, budget
		  line quantities and activity/budget line relationship data. You can set the
		  ownership to Microsoft Project.</ListItem>
      </List>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="399" width="735"
                   SRC="images/tr_screen_in000330_4.png"
                   alt="[...]"/>
      </Figure>
      <List>
         <ListIntro>The <GUIRef href="" role="manual">Resources</GUIRef> tab contains the following
		  fields:</ListIntro>
         <ListItem>Transfer Resources/Cost Objects to Project: If this check box
		  is selected, you can choose cost object types from the LN source
		  data. These cost object types are transferred as resources to Microsoft
		  Project.</ListItem>
         <ListItem>Labor cost objects are transferred to an external file,
		  &lt;Microsoft Project file name&gt;.lco, which receive a reference to Microsoft
		  Project if you define budget lines.</ListItem>
         <ListItem>You must transfer the cost objects required for budget lines.
		  If you do not transfer the resource, you will not be able to create budget
		  lines in Microsoft Project.</ListItem>
         <ListItem>Resource Calendars/Availability Type: You must select the
		  resource calendars’ availability type. If the exceptions to the resource
		  calendar are defined in LN, the availability type is used. Additionally, a base
		  calendar is created in Microsoft Project with this availability
		  type.</ListItem>
         <ListItem>
            <List>
               <ListIntro>The default calendar is used as a base calendar in the
				following two cases:</ListIntro>
               <ListItem>When a calendar is not specified for a resource in LN.</ListItem>
               <ListItem>When the specified calendar is not selected for transfer to
				Microsoft Project.</ListItem>
            </List>
         </ListItem>
      </List>
      <Note>
         <SectionTitle> Note</SectionTitle>
         <Paragraph>All availability types set to <GUIRef href="" role="manual">Available</GUIRef> are
		  present. The integration verifies whether or not the availability type already
		  exists as a base calendar in Microsoft Project. In case the availability type
		  does not exist, a base calendar is created and the standard calendar template
		  details are transferred.</Paragraph>
      </Note>
      <Paragraph>If the availability type is present in Microsoft Project,
		Microsoft Project checks whether the latest calendar changes are updated, using
		a temporary collection of details.</Paragraph>
      <Paragraph>The standard calendar template details comprise of weekdays,
		such as Monday, Tuesday, and so on, and do not permit exceptions for specific
		dates. The use of the standard calendar template details can be compared to the
		three types of calendars that, by default, exist in Microsoft Project: <GUIRef href="" role="manual">24 hours</GUIRef>, <GUIRef href="" role="manual">night shift</GUIRef>, and <GUIRef href="" role="manual">standard</GUIRef>. If no parent calendar exists, the code will be <Emphasis>C.&lt;Availability type&gt;.&lt;calendar code&gt;</Emphasis>. If a
		parent exists, this parent will be added before the calendar code. With
		multiple levels, the derivation path will be used. For every calendar, a check
		is carried out to see if the calendar is present in Microsoft Project.</Paragraph>
      <Note>
         <SectionTitle> Note</SectionTitle>
         <Paragraph>The actual calendar must be up to date. By default, Microsoft
		  Project sets the project calendar for the integrated LN project. To
		  access the LN calendar, in Microsoft Project, on the <GUIRef href="" role="manual">Tools</GUIRef> menu, click <GUIRef href="" role="manual">Change Working Time</GUIRef>.</Paragraph>
      </Note>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="437" width="662"
                   SRC="images/tr_screen_in000330_5.png"
                   alt="[...]"/>
      </Figure>
      <List>
         <ListIntro>The <GUIRef href="" role="manual">Budget/Schedule</GUIRef> tab contains the
		  following fields:</ListIntro>
         <ListItem> 
            <GUIRef href="" role="manual">Create Tasks Based on Activity Structure and Budget Lines</GUIRef>: If you select this check box, the activity structure, starting
		  from the connection node, and the budget line are transferred to Microsoft
		  Project as tasks.</ListItem>
         <ListItem> 
            <GUIRef href="" role="manual">Transfer Activity and Budget Line Relationship</GUIRef>: Select this check box to transfer the activity and
		  budget line relationship to Microsoft Project as task dependencies. You can
		  select this check box only when the <GUIRef href="" role="manual">Create Tasks Based on Activity Structure and Budget Lines</GUIRef> check box is selected. By default, the
		  check box is selected for all new projects. If this check box is not selected,
		  the <GUIRef href="" role="manual">Ownership of Activity and Budget Line Relationship</GUIRef> field
		  in the <GUIRef href="" role="manual">Connection</GUIRef> tab is set to <GUIRef href="" role="manual">Not Applicable</GUIRef>.</ListItem>
         <ListItem>
            <Paragraph>
               <GUIRef href="" role="manual">Transfer Budget Lines</GUIRef>: In this group, you
			 can specify whether a budget line must be transferred as a resource assignment
			 or a task. If you transfer the budget lines with the <GUIRef href="" role="manual">External Schedule Link</GUIRef> field set to <GUIRef href="" role="manual">Create Link</GUIRef> on the <GUIRef href="" role="manual">Connected Data</GUIRef> tab, to Microsoft Project as budget-line tasks,
			 the budget lines are outlined under the task that represents the corresponding
			 activity in LN. When the equipment budget line is transferred as a
			 resource assignment, the corresponding equipment resource is also assigned for
			 scheduling purposes. The employee linked to the budget line is also assigned as
			 a resource for scheduling purposes.</Paragraph>
            <Paragraph>If a resource is used more than once as part of the same
			 activity (task), a subtask is created, irrespective of the <GUIRef href="" role="manual">Resource Assignment</GUIRef> setting, because Microsoft Project does not permit the same
			 resource to be used more than once for the same task.</Paragraph>
            <Paragraph>All the milestones linked to an activity in LN are
			 transferred as tasks linked as predecessors to the activity task. The link
			 relationship can be either <GUIRef href="" role="manual">Start-to-Start</GUIRef> or <GUIRef href="" role="manual">Finish-to-Finish</GUIRef>, depending on the milestone date’ s proximity
			 to the activity’s start/finish date in Microsoft Project.</Paragraph>
            <Paragraph>All the milestones that are not linked to an activity in LN are
			 transferred to the top of the Microsoft Project tasks as stand-alone
			 milestones. The milestones are transferred to all Microsoft Project projects
			 linked to the same LN Project.</Paragraph>
         </ListItem>
         <ListItem>
            <Paragraph>
               <GUIRef href="" role="manual">Connect Project</GUIRef>: Click this button to start
			 the process of connecting LN to a Microsoft Project. The button is available only if
			 valid data is entered in the Connect Microsoft Project to LN Project
			 form.</Paragraph>
            <Paragraph>While you connect the Microsoft Project to a project in LN, the
			 scheduled start and finish dates of activities in LN, if any,
			 are transferred to Microsoft Project. This transfer occurs when you start the
			 project in Microsoft Project to the project in LN for the
			 first time, after which Microsoft Project is the owner of the scheduled dates.</Paragraph>
         </ListItem>
      </List>
   </GeneralSection>
</ManualTopic>