<?xml version="1.0" encoding="utf-8"?>
<!--
        
        ** OAGIS® Revision: 9.1  **
        ** Date: 11 May 2007 **
        ** Copyright 1997-2007, All Rights Reserved **
        
        This is an OAGIS® BOD XML Schema (XSD) Definition.
        
       License information for this file is provided in the file **OAGi License Agreement.txt** that is provided with this download package.
        
        For support, more information, or to report implementation bugs, please contact the Open Applications Group at xml@openapplications.org.
        
        XML Schema 
        
-->

<!--
© Copyright 2007 Infor Global Solutions Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. The 
word and design marks set forth herein are trademarks and/or registered trademarks of Infor Global Solutions 
Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. All other trademarks listed herein 
are the property of their respective owners.
 
-->

<!--    *****     Update Log     *****
 
Date           By      Note
10 Apr 2008    JB      Added correct Copyright and update comments to schema.
13 Jul 2009    JB      Added RemoteWarehouseIndicator 
09 Dec 2009    PO      Added new elements for specialized content for AutoConnect - BOD-1161
08 Oct 2010	   NO      Added InspectionRequiredIndicator and AutoAdjustIndicator elements (BOD-1377). 
13 Oct 2010    NO      Added Rejection element and PickedQuantity (JIRA BOD-1446).
29 Apr 2011    NO      Added ShipmentPurposeCode element (JIRA BOD-1541).
02 May 2011    NO      Added new fields for JIRA BOD-1495: ReceivedVolumeMeasure, ShippedVolumeMeasure, TotalReceivedVolumeMeasure, and TotalShippedVolumeMeasure.
        *****     Update End     *****
 
-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns="http://schema.infor.com/InforOAGIS/2"
	targetNamespace="http://schema.infor.com/InforOAGIS/2" elementFormDefault="qualified"
	attributeFormDefault="unqualified">

	<xsd:include schemaLocation="../Components/Operational/LogisticsComponents.xsd"/>
	<xsd:element name="ShippersExportDeclaration" type="ShippersExportDeclarationType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/oagis/9">A
				ShippersExportDeclaration document identifies and describes a specific collection of
				goods to be transported by a carrier and delivered to one or more business partner
				destinations. A ShippersExportDeclaration document represents the extent and content
				of "transportation work" to be done by the carrier. For transportation efficiency, a
				ShippersExportDeclaration document typically consolidates deliveries to multiple
				destinations within a certain geographic region and may provide carrier routing
				instructions to each delivery stop.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ShippersExportDeclarationHeader" type="ShippersExportDeclarationHeaderType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/oagis/9">Provides general
				information about the document that is used to transport a specific quantity of
				material goods from a supplier to a single customer business partner
				destination.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:element name="ShippersExportDeclarationItem" type="ShippersExportDeclarationItemType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/oagis/9">Provides general
				information about the item inventory being delivered, including the planned and
				actual quantities. This information usually directly references a line item or
				shipment schedule line on a sales order, purchase order or other inventory transfer
				document. </xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	<xsd:complexType name="ShippersExportDeclarationType">
		<xsd:sequence>
			<xsd:element ref="ShippersExportDeclarationHeader" minOccurs="0">
				<xsd:annotation>
					<xsd:documentation source="http://www.openapplications.org/oagis/9">Provides
						general information about the document that is used to transport a specific
						quantity of material goods from a supplier to a single customer business
						partner destination.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
			<xsd:element ref="ShippersExportDeclarationItem" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation source="http://www.openapplications.org/oagis/9">Provides
						general information about the item inventory being delivered, including the
						planned and actual quantities. This information usually directly references
						a line item or shipment schedule line on a sales order, purchase order or
						other inventory transfer document. </xsd:documentation>
				</xsd:annotation>
			</xsd:element>
		</xsd:sequence>
	</xsd:complexType>
	<xsd:complexType name="ShippersExportDeclarationHeaderType">
		<xsd:complexContent>
			<xsd:extension base="ExportDeclarationHeaderBaseType">
				<xsd:sequence>
					<xsd:element ref="Type" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Indicates the type of the object in which
								assoicated.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
					<xsd:element ref="Event" minOccurs="0" maxOccurs="unbounded">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9"/>
						</xsd:annotation>
					</xsd:element>
					<xsd:element ref="UserArea" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Allows the user of OAGIS to extend the specification in order to
								provide additional information that is not captured in
								OAGIS.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>This is done by defining the additional information in XML Schema
								and referencing the new schema in the xml instance document through
								the use of namespaces. Once this is done the additional information
								defined there can be carried in the BOD XML instance
								document.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>The Open Applications Group will make best efforts to quickly
								consider all proposed submissions.The USERAREA is always the last
								element in all components, except where the component has been
								extended inline.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
				</xsd:sequence>
			</xsd:extension>
		</xsd:complexContent>
	</xsd:complexType>
	<xsd:complexType name="ShippersExportDeclarationItemType">
		<xsd:complexContent>
			<xsd:extension base="ExportDeclarationItemBaseType">
				<xsd:sequence>
					<xsd:element ref="ContainsHazardousMaterialIndicator" minOccurs="0"/>
					<xsd:element ref="UserArea" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Allows the user of OAGIS to extend the specification in order to
								provide additional information that is not captured in
								OAGIS.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>This is done by defining the additional information in XML Schema
								and referencing the new schema in the xml instance document through
								the use of namespaces. Once this is done the additional information
								defined there can be carried in the BOD XML instance
								document.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>The Open Applications Group will make best efforts to quickly
								consider all proposed submissions.The USERAREA is always the last
								element in all components, except where the component has been
								extended inline.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
				</xsd:sequence>
			</xsd:extension>
		</xsd:complexContent>
	</xsd:complexType>
</xsd:schema>
