<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/fm/onlinemanual/000106" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Limitations in multisite Freight Management</Title>
		<Keyword><Level1>Limitations</Level1>
			<Level2>multisite Freight Management</Level2>
		</Keyword>
		<Keyword><Level1>multisite Freight Management</Level1>
			<Level2>limitations</Level2>
		</Keyword>
	</Header>
	<AimSection><Paragraph>The following limitations occur in the multisite functionality for <GUIRef href="/baanerp/fm" role="package">Freight Management</GUIRef>
		</Paragraph>
	</AimSection>
	<GeneralSection><SectionTitle>Generate freight order</SectionTitle>
		<Paragraph>Freight orders are initiated by originating orders such as sales or purchase orders. Therefore, the <GUIRef href="/baanerp/fm/foc/fmfoc1234m000" role="session">Generate Freight Orders (fmfoc1234m000)</GUIRef> session must be run in the logistic company of the originating orders. Freight orders are then generated for orders in the current logistic company.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>Means of transport calendar</SectionTitle>
		<Paragraph>If you use means of transport in a multisite setup, you must define a calendar for the means of transport or the carrier. If no calendar is defined, as a rule, the company calendar is used. As each company can have its own calendar, the results depend on the freight planning company. As means of transport calendars are shared, using the means of transport calendar in another freight planning company will result in an update with the company calendar of that freight planning company. This might lead to unexpected results.</Paragraph>
	</GeneralSection>
</ManualTopic>
