<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/onlinemanual/000352" xml:lang="en">
   <Header>
      <Title>Integration of Projects with Data Management</Title>
      <Keyword type="header" order="d1e2277167">
         <Level1>Link to Data Management</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>
         <GUIRef href="/baanerp/dm" role="package">Data Management</GUIRef> provides the function that can be called by other
		ERP packages to copy the link or copy documents between objects.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>Documents linked while entering project hours and expenses
		remain linked while processing these transactions in ERP People, thereby
		creating records in Project. As a consequence, the transactions in
		Project will have the same link. Processing these transactions in Project
		results in Project cost history. These history records also have the link. The
		link allows the users to reference relevant documents while recording time and
		expense.</Paragraph>
      <Paragraph>
         <GUIRef href="" role="manual">Examples of linked documents</GUIRef>: Customer visit
		reports, an expense sheet detailing the amount entered in People. Because
		the examples stated have more relevance for hours and expenses relating to
		projects, only this option is offered for the interaction of People and
		Project. There is no or less relevance for production environments amongst
		other taking into account the percentage of backflushing. Documents linked to
		Planned Purchase Orders are linked to the resulting purchase order lines. These
		are examples where exactly the same link is kept intact. Although other
		situations can be identified they are more subject to debate. The user can
		decide on the relevance and have the option to keep the link, to be added as a
		customization.</Paragraph>
   </GeneralSection>
</ManualTopic>