<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/fm/onlinemanual/000068" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Late and early execution of transport</Title>
		<Keyword><Level1>Load building</Level1>
			<Level2>execution of transport</Level2>
		</Keyword>
		<Keyword><Level1>Freight planning</Level1>
			<Level2>execution of transport</Level2>
		</Keyword>
	</Header>
	<AimSection><Paragraph>In <GUIRef href="/baanerp/fm" role="package">Freight Management</GUIRef>, you can change the earliest/latest load or unload dates for freight orders that are linked to an originating order to enable the lines of the freight orders to be planned at an earlier or later date. This functionality is useful if, for example, the items for a freight order are not available at the time the order must be shipped. By the time the item is available, the latest load date can have elapsed.</Paragraph>
		<Paragraph>If you change the default earliest and latest loading and unloading dates and times of a manually created freight order, make sure that the earliest unloading date and time is later than the earliest loading date and time augmented with the transportation time of the goods. If the earliest and latest loading and unloading dates and times are not entered correctly, an error message appears.</Paragraph>
		<Paragraph>You can change the earliest/latest load or unload dates for freight orders with lines that can still be planned or clustered. For clustering, this applies to freight orders that have freight order lines with the <GUIRef href="/baanerp/fm/domains/foc.lnst#expc" role="enum">Expected</GUIRef>, <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="enum">Actual</GUIRef>, or <GUIRef href="/baanerp/fm/domains/foc.lnst#inpr" role="enum">In Progress</GUIRef> status. For load building, this applies to freight orders that have lines with the <GUIRef href="/baanerp/fm/domains/foc.lnst#expc" role="enum">Expected</GUIRef>, <GUIRef href="/baanerp/fm/domains/foc.lnst#plnd" role="enum">Planned</GUIRef>, or <GUIRef href="/baanerp/fm/domains/foc.clst#actl" role="enum">Actual</GUIRef> status.</Paragraph>
		<Paragraph>The earliest/latest load or unload dates are changed in the <GUIRef href="/baanerp/fm/foc/fmfoc2100m000" role="session">Freight Orders (fmfoc2100m000)</GUIRef> session. If you change any of these dates, a message appears that warns you that the change you are making will affect all related freight order lines that can be planned, replanned, or clustered.</Paragraph>
		<Paragraph>If you change the earliest/latest load or unload dates for freight order lines that have the <GUIRef href="/baanerp/fm/domains/foc.lnst#plnd" role="enum">Planned</GUIRef> status or the <GUIRef href="/baanerp/fm/domains/foc.clst#clus" role="enum">Clustered</GUIRef> status, these freight order lines must be planned or clustered again. For freight order lines that are planned, replanning is carried out in accordance with the setting of the <GUIRef href="/baanerp/fm/lbd/fmlbd0100m000#fmlbd000.uald" role="formfield">Update Actual Load Data</GUIRef> field in the <GUIRef href="/baanerp/fm/lbd/fmlbd0100m000" role="session">Freight Planning Parameters (fmlbd0100m000)</GUIRef> session. Cluster lines must be reclustered manually.</Paragraph>
	</AimSection>
</ManualTopic>
