<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/fm/onlinemanual/000066" xml:lang="en">
   <Header>
      <Title>How freight order and originating order changes affect
		clusters</Title>
      <Keyword type="header" order="d1e501333">
         <Level1>Clustering</Level1>
         <Level2>affect clusters</Level2>
      </Keyword>
      <Keyword type="header" order="d1e501338">
         <Level1>Subcontracting</Level1>
         <Level2>affect clusters</Level2>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>In practice, the originating orders of freight orders are
		changed frequently. Originating sales orders are changed if the customer wants
		more goods, less goods, or different goods, or wants the goods delivered on a
		different date. Similarly, originating purchase orders are changed if your
		organization’s requirements from the supplier change.</Paragraph>
      <Paragraph>If an originating order is changed, the corresponding freight
		order is also changed or deleted.</Paragraph>
      <Paragraph>If order header data, such as the planned delivery date, on the
		originating order of a freight order is changed, the freight order is deleted
		and replaced with a new freight order that has the new delivery date. The lines
		of the deleted freight order are also deleted and replaced or, if a freight
		order exists with a matching delivery date, the lines are allocated to the
		freight order with the matching delivery date.</Paragraph>
      <Paragraph>If order line data, such as the quantities are changed on the
		originating order lines, the corresponding freight order lines and cluster
		lines are changed accordingly.</Paragraph>
      <Paragraph>If the data, such as the transport means group, of a freight
		order line related to a cluster line is changed, the related cluster line is
		removed from its cluster and added to a cluster that match the properties of
		the changed cluster line. If no matching cluster exists, a new cluster is
		created for the cluster line.</Paragraph>
   </AimSection>
   <GeneralSection>
      <SectionTitle>ERP deletes cluster/cluster lines</SectionTitle>
      <Paragraph>Cluster lines related to deleted freight order lines are also
		deleted if the cluster lines belong to a <GUIRef href="/baanerp/fm/domains/foc.clst#clus" role="option">Clustered</GUIRef>, <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef>,
		or <GUIRef href="/baanerp/fm/domains/foc.clst#clsd" role="option">Closed</GUIRef> cluster. If a cluster has no cluster lines left, the entire cluster is deleted.
		If cluster lines of <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef> clusters are deleted, the <GUIRef href="/baanerp/fm/foc/fmfoc3100m000#fmfoc300.chgd" role="manual">Cluster Changed</GUIRef> check box is selected for the
		cluster, in which case you are advised to check the cluster contents and
		consider rerunning the clustering process.</Paragraph>
      <Paragraph>Freight order lines that are allocated to another freight order
		with matching data are not clustered.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>ERP changes cluster lines</SectionTitle>
      <Paragraph>If order line data, such as the item, is changed on an
		originating order, the item of the corresponding freight order line and the
		related cluster line is changed accordingly.</Paragraph>
      <GeneralSection>
         <SectionTitle>Clusters and cluster lines with the Clustered
		  status</SectionTitle>
         <Paragraph>If the data, such as the transport means group, of a freight
		  order line related to a cluster line is changed, the related cluster line is
		  removed from its cluster and added to a cluster that match the properties of
		  the changed cluster line. If no matching cluster exists, a new cluster is
		  created for the cluster line.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Clusters and cluster lines with the Actual
		  status</SectionTitle>
         <Paragraph>If a cluster line of an <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef> cluster is changed, the cluster line is removed from its cluster and added to
		  an <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef> cluster that match the properties of the changed cluster line. If the <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef> cluster is changed, the <GUIRef href="/baanerp/fm/foc/fmfoc3100m000#fmfoc300.chgd" role="manual">Cluster Changed</GUIRef> check box is selected for the
		  cluster. If no <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef> cluster matches the properties of the changed
		  cluster line, the cluster line is added to a Clustered cluster with matching
		  properties. If no matching <GUIRef href="/baanerp/fm/domains/foc.clst#clus" role="option">Clustered</GUIRef> cluster exists, a new <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef> cluster is created for the cluster line.</Paragraph>
         <Paragraph>If a <GUIRef href="/baanerp/fm/domains/foc.clst#clus" role="option">Clustered</GUIRef>, <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="option">Actual</GUIRef>,
		  or <GUIRef href="/baanerp/fm/domains/foc.clst#subc" role="option">Subcontracted</GUIRef> cluster is changed, ERP Enterprise recalculates the
		  freight costs according to the setting of the <GUIRef href="/baanerp/fm/frc/fmfrc0100m000#fmfrc000.refc" role="manual">Recalculation of Freight Costs</GUIRef> parameter in the <GUIRef href="/baanerp/fm/frc/fmfrc0100m000" role="session">Freight Rates and Costs Parameters (fmfrc0100m000)</GUIRef> session.</Paragraph>
         <Paragraph>After a cluster line is added or removed from a cluster, the
		  loading and unloading time windows are recalculated for the cluster.</Paragraph>
      </GeneralSection>
   </GeneralSection>
</ManualTopic>