<?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.
    
-->


<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:oa="http://www.openapplications.org/oagis/9"
    xmlns="http://schema.infor.com/Infor1.0"
    targetNamespace="http://schema.infor.com/Infor1.0"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
    
    <xsd:import namespace="http://www.openapplications.org/oagis/9" 
        schemaLocation="../../../9.0/Resources/Nouns/Shipment.xsd"/>
    
    <xsd:include schemaLocation="Shipment.xsd"/>
   
    <xsd:element name="ServiceConsumption" type="ServiceConsumptionType">
        <xsd:annotation>
            <xsd:documentation source="http://www.openapplications.org/oagis/9">Represents a transaction for the receiving of goods or services.  It may be used to indicate receipt of goods in conjunction with a purchase order system.</xsd:documentation>
            <xsd:documentation source="http://www.openapplications.org/oagis/9">The Delivery document contains CHARGE and DISTRIBUTN elements at various levels to support the assessment of receiving service or compliance penalty charges.  Several large retailers that demand receiving efficiency commonly assess penalty charges for supplier deliveries that are not compliant with the retailer's policies.  Charges may be incurred for deliveries, ship units or items that contain discrepancies from what was ordered or electronically manifested, for improper labeling of items and ship units and the incorrect packing or loading of ship units.</xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    
    <xsd:element name="ServiceConsumptionHeader" type="ServiceConsumptionHeaderType">
        <xsd:annotation>
            <xsd:documentation source="http://www.openapplications.org/oagis/9">Provides general information about the ServiceConsumption receipt document that is used to receive a specific quantity of material goods from a supplier.</xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    
    <xsd:element name="ServiceConsumptionItem" type="ServiceConsumptionItemType">
        <xsd:annotation>
            <xsd:documentation source="http://www.openapplications.org/oagis/9">Provides general information about the item inventory being delivered, including the requested and actual quantities.  This information usually directly references a line item or Delivery schedule line on a sales order, purchase order or other inventory transfer document.  </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    
    <xsd:complexType name="ServiceConsumptionType">
        <xsd:annotation>
            <xsd:documentation source="http://www.openapplications.org/oagis/9">ServiceConsumption typically report on the ServiceConsumptionItems.</xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
            <xsd:element ref="ServiceConsumptionHeader" minOccurs="0"/>
            <xsd:element ref="ServiceConsumptionItem" minOccurs="0" maxOccurs="unbounded"/>
        </xsd:sequence>
    </xsd:complexType>
    
    <xsd:complexType name="ServiceConsumptionHeaderType">
        <xsd:annotation>
            <xsd:documentation source="http://www.openapplications.org/oagis/9">Provides general information about the ServiceConsumption document that is used to receive a specific quantity of material goods
                The EffectiveDateTime is the date/time the received material is posted to other business systems as being available for use.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexContent>
            <xsd:extension base="oa:ShipmentHeaderBaseType">
                <xsd:sequence>
                    <xsd:element ref="oa:ReceivingServiceChargeAmount" minOccurs="0"/>
                    <xsd:element ref="oa:EffectiveDateTime" minOccurs="0"/>
                    <xsd:element ref="oa:ReceivedDateTime" minOccurs="0"/>
                    <xsd:element ref="oa:DeliverToParty" minOccurs="0"/>
                    <xsd:element ref="oa:ReceivingLocation" minOccurs="0"/>
                    <xsd:element ref="oa:UserArea" minOccurs="0"/>
                </xsd:sequence>
            </xsd:extension>
        </xsd:complexContent>
    </xsd:complexType>
    
    <xsd:complexType name="ServiceConsumptionItemType">
        <xsd:annotation>
            <xsd:documentation source="http://www.openapplications.org/oagis/9">ReceiptLine represents the goods line item detail of the receipt document. THis can be used by itself for traditional receiving against Purchase Orders or other line-item oriented buisness documents, or in conjunction with the ReceiptUnit element to summarize ship unit item detail at line level</xsd:documentation>
        </xsd:annotation>
        <xsd:complexContent>
            <xsd:extension base="oa:ShipItemBaseType">
                <xsd:sequence>
                    <xsd:element ref="oa:Status" minOccurs="0"/>
                    <xsd:element ref="oa:ReceivingServiceChargeAmount" minOccurs="0"/>
                    <xsd:element ref="oa:PackingSlipQuantity" minOccurs="0"/>
                    <xsd:element ref="oa:ReceivedQuantity" minOccurs="0"/>
                    <xsd:element ref="oa:ReturnedQuantity" minOccurs="0"/>
                    <xsd:element ref="oa:ReceiptRoutingCode" minOccurs="0"/>
                    <xsd:group ref="oa:CatchWeightGroup" minOccurs="0"/>
                    <xsd:element ref="oa:UserArea" minOccurs="0"/>
                </xsd:sequence>
            </xsd:extension>
        </xsd:complexContent>
    </xsd:complexType>
       
</xsd:schema>