<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/dm/doc/dmdoc1540m000" xml:lang="en">
   <Header>
      <Title>Document Revision Links (dmdoc1540m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <List>
            <ListIntro>Use this session to maintain links between <Link href="/baanerp/dm/glossary/glossary#000020" role="glossary">document revision</Link>. Depending on how the user accesses the
			 session, this session lists links from a selected document revision to one of
			 the following:</ListIntro>
            <ListItem>Child document
			 revisions</ListItem>
            <ListItem>Related document
			 revisions</ListItem>
         </List>
      </AimSection>
      <GeneralSection>
         <Paragraph>You can add new links
		  to document revisions and remove existing links.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/dm/onlinemanual/000025" role="manual">Links between Document Revisions</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="dmdoc140.did1">
         <Header>
            <Title>Document</Title>
         </Header>
         <FuncDesc>The document ID to which the child/related documents are
		  linked.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc140.typ1">
         <Header>
            <Title>Type</Title>
         </Header>
         <FuncDesc>The document type ID.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc140.rev1">
         <Header>
            <Title>Revision</Title>
         </Header>
         <FuncDesc>The document revision which is attached to the current
		  document.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc140.did2">
         <Header>
            <Title>Document</Title>
         </Header>
         <FuncDesc>The document ID to which the child/related documents are
		  linked.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc140.typ2">
         <Header>
            <Title>Type</Title>
         </Header>
         <FuncDesc>The document type of the child/related document.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc140.rev2">
         <Header>
            <Title>Revision</Title>
         </Header>
         <FuncDesc>The document revision of the child/related document.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc140.lnks">
         <Header>
            <Title>Link Type (Related Documents)</Title>
         </Header>
         <FuncDesc>Displays the drop-down list of two link types, namely
		  unidirectional and bidirectional. Unidirectional is a one-way link between the
		  originating/source document ( <GUIRef href="" role="manual">Document</GUIRef> in the <GUIRef href="" role="manual">View</GUIRef> field) to the target document ( <GUIRef href="" role="manual">Document</GUIRef> in the <GUIRef href="" role="manual">Grid</GUIRef> fields). This link is applicable only from the
		  source to the target document. You can only view the target document linked to
		  the source only when you view the related documents session from the source
		  document. If you view the related documents session from the target document
		  then you can not find the source in the related documents list of the target
		  document.</FuncDesc>
         <SimpleSection>
            <Paragraph>Bidirectional is a two way link between the source and
			 target documents.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="dmdoc140.lnkp">
         <Header>
            <Title>Link Type (Child Documents)</Title>
         </Header>
         <FuncDesc>Displays the drop-down list of the parent/child link, namely,
		  logical parent/child, and physical parent/child. Select the linkage based on
		  the following facts: A child document is logically an element of the parent
		  document. For example, a revision that contains data on a drawing can be linked
		  as a logical child link to the revision to which the actual drawing file is
		  attached. Similarly for a physical parent/child, a document revision (rev-1)
		  contains the design file of the entire aircraft. The revisions that contain
		  design files of each component (of the aircraft) can be physically linked to
		  rev-1 as child documents.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc110.dscr">
         <Header>
            <Title>Document</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmdoc120.stat">
         <Header>
            <Title>Status</Title>
         </Header>
         <FuncDesc>The status of the parent document.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmsys020.dsca">
         <Header>
            <Title>Secondary Status</Title>
         </Header>
         <FuncDesc>The status that an individual company assigns to entities based
		  on system status, also called user-defined status.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>