<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/diffsp2/tp/onlinemanual/000020Diff61SP2" xml:lang="en">
   <Header>
      <Title>MSP-TP Integration</Title>
      <Keyword type="header" order="d1e269906">
         <Level1>Differences Infor ERP LN 6.1 FP2</Level1>
         <Level2>MSP Integration</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <SectionTitle>Infor ERP LN 6.1 SP1</SectionTitle>
      <Paragraph>In Infor ERP LN 6.1 SP1, the activity relationship between activities and budget lines is
		maintained in MS Project only.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Infor ERP LN 6.1 FP2</SectionTitle>
      <Paragraph>It is possible to maintain relationships between activities,
		between budget lines and between an activity and a budget line and update the
		activity relationships defined in ERP Enterprise Project from Microsoft Project and vice-versa. The status of the
		ownership for the project’s activity and budget line relationships can be set
		to either MS Project or ERP Enterprise. The ownership of activity relationships depends on the ownership
		of activity structure/budget lines. Following scenarios are
		possible:</Paragraph>
      <List>
         <ListItem>
            <GUIRef href="" role="manual">Activity Structure and Budget Line owned by ERP Enterprise and Activity Relationship owned by ERP Enterprise</GUIRef>:The complete activity structure and the budget lines,
		  including the activity relationships are maintained in ERP Enterprise and MS Project is
		  used for resource planning. This option is useful when the activity structure
		  and the budget lines including the relationships are part of the ERP Enterprise template project.
		  The option is used to create projects from templates.</ListItem>
         <ListItem>
            <GUIRef href="" role="manual">Activity Structure and Budget Line owned by ERP Enterprise and Activity Relationship owned by MSP</GUIRef>: The complete activity structure, and the
		  budget lines are maintained in ERP Enterprise and the activity/budget lines relationship (task dependencies) is
		  maintained in MS Project client side to use the graphical functionality
		  provided in MS Project. MS Projects checks the circular relationship (circular
		  relationship is not checked in ERP Enterprise). While establishing the connection, the default activity
		  relationships, if present, in the ERP Enterprise, are transferred as default dependencies and MS Project owns the
		  task dependencies. This option is useful to create template
		  projects.</ListItem>
         <ListItem>
            <GUIRef href="" role="manual">Activity Structure and Budget Line owned by MSP and Activity Relationship owned by MSP</GUIRef>: The complete activity structure,
		  the budget lines and task dependencies are maintained in the MS Project client
		  side in order to use the planning functionality provided by MS Project. While
		  establishing the connection, the ownership is set to MSP and a connection is
		  made to an empty ERP Enterprise Project plan with no activities. The top summary task in MS Project becomes the
		  top activity in ERP Enterprise and
		  the connection node. The structure under the top summary task in MS Project is
		  transferred as the activity structure in ERP Enterprise. All the budget
		  lines are transferred to ERP Enterprise. After the activity structure and the activity budget lines are
		  created, the activity/budget line relationship is created in ERP Enterprise from MS
		  Project.</ListItem>
      </List>
      <Paragraph>Microsoft project 2002 allows the user to define/save multiple
		baselines. This functionality is used to prevent overwriting of data in ERP Enterprise. The user can
		select the baseline with which the planned date is to be updated in ERP Enterprise.</Paragraph>
      <Paragraph>The MSP-TP integration certifies the working of existing ERP LN 6.1 Project – Microsoft Project integration solution with
		Microsoft Project 2003 on Windows XP environment.</Paragraph>
   </GeneralSection>
</ManualTopic>