<!--

** OAGIS® Revision: 9.0 **
** Date: 08 April 2005 **
** Copyright 1998-2005, All Rights Reserved **

This is an OAGIS® BOD XML Schema (XSD) Definition.

License information for this file is provided in the file **2005 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 
     
    Name: \OAGIS\9.0\BODs\Developer\UpdateReceiveDelivery.xsd
-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.openapplications.org/oagis/9" targetNamespace="http://www.openapplications.org/oagis/9" elementFormDefault="qualified" attributeFormDefault="unqualified">
        <xsd:include schemaLocation="../../Resources/Nouns/ReceiveDelivery.xsd"/>
        <xsd:element name="UpdateReceiveDelivery" type="UpdateReceiveDeliveryType">
                <xsd:annotation>
                        <xsd:documentation source="http://www.openapplications.org/oagis/9">The UpdateReceiveDelivery may be used to update the receiver's internal receiving and order management business applications to indicate that the requested material has arrived, including any unexpected quantity, condition or other exception discrepancies.

There are many other possible business applications in several environments that may use this capability.  For example:
1. A Purchasing application may use this BOD to notify an Accounts Payable application of a specific delivery.  This will enable the Accounts Payable application to accurately calculate the amount it needs to pay a business partner.

2. A Purchasing application could use this to notify a MRP, Inventory, or Manufacturing business application that a delivery has occurred and the goods are available for use or inspection, etc.

3. An MRP/Inventory system could use this BSR to communicate changes on a physical receipt in inventory to the Purchasing system.

The UpdateReceiveDelivery supports receipts at either the line item level and/or the ship unit level.  Intermediate transportation/logistics providers or freight forwarding partners can use this document to acknowledge the receipt of entire shipping units without detailing the corresponding contents.</xsd:documentation>
                </xsd:annotation>
        </xsd:element>
        <xsd:complexType name="UpdateReceiveDeliveryType">
                <xsd:complexContent>
                        <xsd:extension base="BusinessObjectDocumentType">
                                <xsd:sequence>
                                        <xsd:element name="DataArea" type="UpdateReceiveDeliveryDataAreaType">
                                                <xsd:annotation>
                                                        <xsd:documentation source="http://www.openapplications.org/oagis/9">Is where the information that the BOD message carries is provided, in this case UpdateReceiveDelivery. The information consists of a Verb and one or more Nouns. The verb (Update) indicates the action to be performed on the Noun (ReceiveDelivery).</xsd:documentation>
                                                </xsd:annotation>
                                        </xsd:element>
                                </xsd:sequence>
                        </xsd:extension>
                </xsd:complexContent>
        </xsd:complexType>
        <xsd:complexType name="UpdateReceiveDeliveryDataAreaType">
                <xsd:sequence>
                        <xsd:element ref="Update"/>
                        <xsd:element ref="ReceiveDelivery" maxOccurs="unbounded"/>
                </xsd:sequence>
        </xsd:complexType>
</xsd:schema>

• UpdateReceiveDeliveryDataAreaType
• UpdateReceiveDeliveryType

• UpdateReceiveDelivery