<?xml version="1.0" encoding="UTF-8" ?>

<!--
        (C) Copyright 2011 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="http://schema.infor.com/InforOAGIS/2" 
		targetNamespace="http://schema.infor.com/InforOAGIS/2" 
		attributeFormDefault="unqualified" 
		elementFormDefault="qualified">
		
  <xsd:include schemaLocation="Resources/Nouns/AccountingBookDefinition.xsd"/>
  <xsd:element name="AcknowledgeAccountingBookDefinition" type="AcknowledgeAccountingBookDefinitionType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAccountingBookDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAccountingBookDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAccountingBookDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AccountingBookDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/AccountingChart.xsd"/>
  <xsd:element name="AcknowledgeAccountingChart" type="AcknowledgeAccountingChartType">
    <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 AcknowledgeAccountingChart. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingChart).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAccountingChartType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAccountingChartDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAccountingChartDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AccountingChart" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/AccountingEntity.xsd"/>
  <xsd:element name="AcknowledgeAccountingEntity" type="AcknowledgeAccountingEntityType">
    <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 AcknowledgeAccountingEntity. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge indicates the action
                                to be performed on the Noun
                                (AccountingEntity).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAccountingEntityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAccountingEntityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAccountingEntityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AccountingEntity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/AccountingJournal.xsd"/>
  <xsd:element name="AcknowledgeAccountingJournal" type="AcknowledgeAccountingJournalType">
    <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 AcknowledgeAccountingJournal. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingJournal).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAccountingJournalType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAccountingJournalDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAccountingJournalDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AccountingJournal" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/AdvanceShipNotice.xsd"/>
  <xsd:element name="AcknowledgeAdvanceShipNotice" type="AcknowledgeAdvanceShipNoticeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeAdvanceShipNotice Business Object Document is to acknowledge receipt of the AdvanceShipNotice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAdvanceShipNoticeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAdvanceShipNoticeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeAdvanceShipNotice. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (AdvanceShipNotice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAdvanceShipNoticeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AdvanceShipNotice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/AssetFinancialLedger.xsd"/>
  <xsd:element name="AcknowledgeAssetFinancialLedger" type="AcknowledgeAssetFinancialLedgerType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAssetFinancialLedgerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAssetFinancialLedgerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAssetFinancialLedgerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AssetFinancialLedger" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/AssetMaster.xsd"/>
  <xsd:element name="AcknowledgeAssetMaster" type="AcknowledgeAssetMasterType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/AssetMeterReading.xsd"/>
  <xsd:element name="AcknowledgeAssetMeterReading" type="AcknowledgeAssetMeterReadingType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeAssetMeterReadingType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeAssetMeterReadingDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeAssetMeterReadingDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="AssetMeterReading" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/BillOfMaterials.xsd"/>
  <xsd:element name="AcknowledgeBillOfMaterials" type="AcknowledgeBillOfMaterialsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SynBillOfMaterials is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Bill of Material.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeBillOfMaterialsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeBillOfMaterialsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeBillOfMaterials. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (BillOfMaterials).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeBillOfMaterialsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="BillOfMaterials" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/BillOfResources.xsd"/>
  <xsd:element name="AcknowledgeBillOfResources" type="AcknowledgeBillOfResourcesType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge BillOfResources is to notify the requestor of a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeBillOfResourcesType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeBillOfResourcesDataAreaType">
            <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 AcknowledgeBillOfResources. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (BillOfResources).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeBillOfResourcesDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="BillOfResources" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/BillToPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeBillToPartyMaster" type="AcknowledgeBillToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge BillToPartyMaster is to notify a systen
                                that requested a change to a BillTo object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeBillToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeBillToPartyMasterDataAreaType">
            <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
                                                  AcknowledgeBillToPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (BillToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeBillToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="BillToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/BusinessPlan.xsd"/>
  <xsd:element name="AcknowledgeBusinessPlan" type="AcknowledgeBusinessPlanType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeBusinessPlanType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeBusinessPlanDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeBusinessPlanDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="BusinessPlan" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Calendar.xsd"/>
  <xsd:element name="AcknowledgeCalendar" type="AcknowledgeCalendarType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Calendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Campaign.xsd"/>
  <xsd:element name="AcknowledgeCampaign" type="AcknowledgeCampaignType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCampaignType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCampaignDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCampaignDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Campaign" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Components/Common/Components.xsd"/>
  <xsd:element name="AcknowledgeCarrierParty" type="AcknowledgeCarrierPartyType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge CarrierParty is to acknowledge the
                                change of a supplier in response to a Process.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCarrierPartyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCarrierPartyDataAreaType">
            <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
                                                  AcknowledgeCarrierParty. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (CarrierParty).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCarrierPartyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CarrierParty" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CarrierRoute.xsd"/>
  <xsd:element name="AcknowledgeCarrierRoute" type="AcknowledgeCarrierRouteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeCarrierRoute is to enable an application to provide  Carrier Route information from another business application module.  The AcknowledgeCarrierRoute is typiically provided in a publish/subscribe or broadcast environment. Where the sending system is the master application of the information being provided, where the information is sent to other business applications that need to know the information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCarrierRouteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCarrierRouteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeCarrierRoute. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (CarrierRoute).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCarrierRouteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CarrierRoute" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CashReceipt.xsd"/>
  <xsd:element name="AcknowledgeCashReceipt" type="AcknowledgeCashReceiptType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeCashReceipt Business Object Document is to acknowledge receipt of the CashReceipt
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCashReceiptType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCashReceiptDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeCashReceipt. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (CashReceipt).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCashReceiptDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CashReceipt" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ChartOfAccounts.xsd"/>
  <xsd:element name="AcknowledgeChartOfAccounts" type="AcknowledgeChartOfAccountsType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the AcknowledgeChartOfAccounts is to acknowledge the
                                completion of a request for a change by an applicaiton to chart of
                                accounts code identifiers.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeChartOfAccountsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeChartOfAccountsDataAreaType">
            <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
                                                  AcknowledgeChartOfAccounts. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (ChartOfAccounts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeChartOfAccountsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ChartOfAccounts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ChartsOfAccountsMap.xsd"/>
  <xsd:element name="AcknowledgeChartsOfAccountsMap" type="AcknowledgeChartsOfAccountsMapType">
    <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 AcknowledgeCode. The information consists of a Verb and one or
                                more Nouns. The verb Acknowledge) indicates the action to be
                                performed on the Noun (Code).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeChartsOfAccountsMapType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeChartsOfAccountsMapDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                        that the BOD message carries is provided, in this case AcknowledgeChartsOfAccountsMap. The 
                                                        information consists of a Verb and one or more Nouns. The verb (Get) indicates the action 
                                                        to be performed on the Noun (ChartsOfAccountsMap).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeChartsOfAccountsMapDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ChartsOfAccountsMap" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CodeDefinition.xsd"/>
  <xsd:element name="AcknowledgeCodeDefinition" type="AcknowledgeCodeDefinitionType">
    <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 AcknowledgeCode. The information consists of a Verb and one or
                                more Nouns. The verb Acknowledge) indicates the action to be
                                performed on the Noun (Code).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCodeDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCodeDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCodeDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CodeDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ConfiguredAssetMaster.xsd"/>
  <xsd:element name="AcknowledgeConfiguredAssetMaster" type="AcknowledgeConfiguredAssetMasterType">
    <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 AcknowledgeConfiguredAssetMaster. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeConfiguredAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeConfiguredAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeConfiguredAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ConfiguredAssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ConstrainedResource.xsd"/>
  <xsd:element name="AcknowledgeConstrainedResource" type="AcknowledgeConstrainedResourceType">
    <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 AcknowledgeConstrainedResource. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeConstrainedResourceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeConstrainedResourceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeConstrainedResourceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ConstrainedResource" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ContactMaster.xsd"/>
  <xsd:element name="AcknowledgeContactMaster" type="AcknowledgeContactMasterType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeContactMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeContactMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeContactMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ContactMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Contract.xsd"/>
  <xsd:element name="AcknowledgeContract" type="AcknowledgeContractType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Contract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Currency.xsd"/>
  <xsd:element name="AcknowledgeCurrency" type="AcknowledgeCurrencyType">
    <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 AcknowledgeCurrency. The information consists of a Verb and one or
                                more Nouns. The verb Acknowledge) indicates the action to be
                                performed on the Noun (Currency).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCurrencyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCurrencyDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCurrencyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Currency" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CurrencyExchangeRateMaster.xsd"/>
  <xsd:element name="AcknowledgeCurrencyExchangeRateMaster" type="AcknowledgeCurrencyExchangeRateMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge CurrencyExchangeRate is to notify the requestor of a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCurrencyExchangeRateMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCurrencyExchangeRateMasterDataAreaType">
            <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 AcknowledgeCurrencyExchangeRate. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (CurrencyExchangeRate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCurrencyExchangeRateMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CurrencyExchangeRateMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CurrencyRateType.xsd"/>
  <xsd:element name="AcknowledgeCurrencyRateType" type="AcknowledgeCurrencyRateTypeType">
    <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 AcknowledgeCurrencyRateType. The information consists of a Verb
                                and one or more Nouns. The verb Acknowledge) indicates the action to
                                be performed on the Noun (CurrencyRateType).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCurrencyRateTypeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCurrencyRateTypeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCurrencyRateTypeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CurrencyRateType" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CustomerCall.xsd"/>
  <xsd:element name="AcknowledgeCustomerCall" type="AcknowledgeCustomerCallType">
    <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 AcknowledgeCustomerCall. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCustomerCallType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCustomerCallDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCustomerCallDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CustomerCall" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CustomerPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeCustomerPartyMaster" type="AcknowledgeCustomerPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge CustomerPartyMaster is to notify a systen
                                that requested a change to a Customer object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCustomerPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCustomerPartyMasterDataAreaType">
            <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
                                                  AcknowledgeCustomerPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (CustomerPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCustomerPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CustomerPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CustomerPurchaseOrder.xsd"/>
  <xsd:element name="AcknowledgeCustomerPurchaseOrder" type="AcknowledgeCustomerPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the
                AcknowledgeCustomerPurchaseOrder Business Object Document is to acknowledge receipt of the Purchase
                Order and to reflect any changes. Commonly, the acknowledgment is generated by an
                order management application and transmitted to a purchasing or procurement application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCustomerPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCustomerPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is the place in which the information that the BOD message carries is provided. In this case AcknowledgeCustomerPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (CustomerPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCustomerPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CustomerPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CustomerReturn.xsd"/>
  <xsd:element name="AcknowledgeCustomerReturn" type="AcknowledgeCustomerReturnType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeCustomerReturn Business Object Document is to acknowledge receipt of the CustomerReturn
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCustomerReturnType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCustomerReturnDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeCustomerReturn. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (CustomerReturn).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCustomerReturnDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CustomerReturn" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CustomerRFQ.xsd"/>
  <xsd:element name="AcknowledgeCustomerRFQ" type="AcknowledgeCustomerRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeCustomerRFQ Business Object Document is to acknowledge receipt of the CustomerRFQ
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeCustomerRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeCustomerRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeCustomerRFQ. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (CustomerRFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeCustomerRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="CustomerRFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Data.xsd"/>
  <xsd:element name="AcknowledgeData" type="AcknowledgeDataType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of Acknowledge Data is to notify the sender of the Process
                                document that the document was received and the outcome of the
                                message.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeDataType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeDataDataAreaType">
            <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 AcknowledgeData. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (Data).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeDataDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Data" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/EDITransport.xsd"/>
  <xsd:element name="AcknowledgeEDITransport" type="AcknowledgeEDITransportType">
    <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 AcknowledgeEDITransport. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge indicates the action
                                to be performed on the Noun(EDITransport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeEDITransportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeEDITransportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeEDITransportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="EDITransport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/EmployeeWorkTime.xsd"/>
  <xsd:element name="AcknowledgeEmployeeWorkTime" type="AcknowledgeEmployeeWorkTimeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeEmployeeWorkTime is to Acknowledge work time information for an employee from a data collection application to an ERP Human Resource application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeEmployeeWorkTimeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeEmployeeWorkTimeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeEmployeeWorkTime. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (EmployeeWorkTime).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeEmployeeWorkTimeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="EmployeeWorkTime" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ExpenseReport.xsd"/>
  <xsd:element name="AcknowledgeExpenseReport" type="AcknowledgeExpenseReportType">
    <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 AcknowledgeExpenseReport. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge indicates the action
                                to be performed on the Noun
                                (ExpenseReport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeExpenseReportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeExpenseReportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeExpenseReportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ExpenseReport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ExtendLicenseUsage.xsd"/>
  <xsd:element name="AcknowledgeExtendLicenseUsage" type="AcknowledgeExtendLicenseUsageType">
    <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 AcknowledgeExtendLicenseUsage. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun (ExtendLicenseUsage).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeExtendLicenseUsageType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeExtendLicenseUsageDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeExtendLicenseUsageDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ExtendLicenseUsage" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Field.xsd"/>
  <xsd:element name="AcknowledgeField" type="AcknowledgeFieldType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge Field is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeFieldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeFieldDataAreaType">
            <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 AcknowledgeField. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (Field).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeFieldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Field" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/FinancialCalendar.xsd"/>
  <xsd:element name="AcknowledgeFinancialCalendar" type="AcknowledgeFinancialCalendarType">
    <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 AcknowledgeFinancialCalendar. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (FinancialCalendar).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeFinancialCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeFinancialCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeFinancialCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="FinancialCalendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/FinancialPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeFinancialPartyMaster" type="AcknowledgeFinancialPartyMasterType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeFinancialPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeFinancialPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeFinancialPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="FinancialPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/HandlingGroup.xsd"/>
  <xsd:element name="AcknowledgeHandlingGroup" type="AcknowledgeHandlingGroupType">
    <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 AcknowledgeHandlingGroup. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (HandlingGroup).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeHandlingGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeHandlingGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeHandlingGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="HandlingGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/InspectDelivery.xsd"/>
  <xsd:element name="AcknowledgeInspectDelivery" type="AcknowledgeInspectDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeInspectDelivery is to supply InspectDelivery information for goods or services to another business application module.  This BOD may is initiated by the sending system upon some event occurring.  There are many possible business applications in several environments that may use this capability.

For example;
1.  A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 
2.  An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information.
3.  A Laboratory Information System could send quality information to an Inventory application,
4.  A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeInspectDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeInspectDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeInspectDelivery. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (InspectDelivery).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeInspectDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="InspectDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/InventoryAdjustment.xsd"/>
  <xsd:element name="AcknowledgeInventoryAdjustment" type="AcknowledgeInventoryAdjustmentType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Acknowledge InventoryAdjustment is to notify the
                                enterprise of the change to the hold status of an inventory item.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeInventoryAdjustmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeInventoryAdjustmentDataAreaType">
            <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 AcknowledgeInventoryAdjustment. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Acknowledge)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryAdjustment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeInventoryAdjustmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="InventoryAdjustment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/InventoryBalance.xsd"/>
  <xsd:element name="AcknowledgeInventoryBalance" type="AcknowledgeInventoryBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ChangeInventoryBalance is to enable the communication of a Change in the InventoryBalance data that exists on separate Inventory databases.

This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure.  

This is data that describes the ITEM as it exists at a specific location. It is
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeInventoryBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeInventoryBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeInventoryBalance. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (InventoryBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeInventoryBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="InventoryBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/InventoryConsumption.xsd"/>
  <xsd:element name="AcknowledgeInventoryConsumption" type="AcknowledgeInventoryConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeInventoryConsumption is to inform a seller or provider about InventoryConsumption of items.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeInventoryConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeInventoryConsumptionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeInventoryConsumption. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (InventoryConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeInventoryConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="InventoryConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/InventoryCount.xsd"/>
  <xsd:element name="AcknowledgeInventoryCount" type="AcknowledgeInventoryCountType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeInventoryCount is to transmit an inventory count to ERP from the actual physical inventory location. This count may be a cycle count or a physical count.  This BOD may also apply to planned or unplanned inventory counts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeInventoryCountType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeInventoryCountDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeInventoryCount. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (InventoryCount).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeInventoryCountDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="InventoryCount" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/InventoryHold.xsd"/>
  <xsd:element name="AcknowledgeInventoryHold" type="AcknowledgeInventoryHoldType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Acknowledge InventoryHold is to
                                acknowledge the successful change of a hold status by the WMS 
                                or Inventory system.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeInventoryHoldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeInventoryHoldDataAreaType">
            <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 AcknowledgeInventoryHold.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (InventoryHold).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeInventoryHoldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="InventoryHold" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Invoice.xsd"/>
  <xsd:element name="AcknowledgeInvoice" type="AcknowledgeInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeInvoice Business Object Document is to acknowledge receipt of the Invoice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeInvoice. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (Invoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Invoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ItemMaster.xsd"/>
  <xsd:element name="AcknowledgeItemMaster" type="AcknowledgeItemMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge ItemMaster is to notify a systen
                                that requested a change to an item object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeItemMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeItemMasterDataAreaType">
            <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
                                                  AcknowledgeItemMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (ItemMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeItemMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ItemMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Location.xsd"/>
  <xsd:element name="AcknowledgeLocation" type="AcknowledgeLocationType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge Location is to notify the requestor of a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeLocationType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeLocationDataAreaType">
            <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 AcknowledgeLocation. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (Location).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeLocationDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Location" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/MaintenanceOrder.xsd"/>
  <xsd:element name="AcknowledgeMaintenanceOrder" type="AcknowledgeMaintenanceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeMaintenanceOrder Business Object Document is to acknowledge receipt of the MaintenanceOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeMaintenanceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeMaintenanceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeMaintenanceOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (MaintenanceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeMaintenanceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="MaintenanceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/MatchDocument.xsd"/>
  <xsd:element name="AcknowledgeMatchDocument" type="AcknowledgeMatchDocumentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The AcknowledgeMatchDocument provides the ability to request an application/ system to create a MatchDocument
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeMatchDocumentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeMatchDocumentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeMatchDocument. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (MatchDocument).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeMatchDocumentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="MatchDocument" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/MoveInventory.xsd"/>
  <xsd:element name="AcknowledgeMoveInventory" type="AcknowledgeMoveInventoryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeMoveInventory is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeMoveInventoryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeMoveInventoryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeMoveInventory. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (MoveInventory).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeMoveInventoryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="MoveInventory" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Opportunity.xsd"/>
  <xsd:element name="AcknowledgeOpportunity" type="AcknowledgeOpportunityType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The AcknowledgeOpportunity is provided in response to the ProcessOpportunity in order to accept or reject the request to process.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeOpportunityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeOpportunityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgePurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeOpportunityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Opportunity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PayableTransaction.xsd"/>
  <xsd:element name="AcknowledgePayableTransaction" type="AcknowledgePayableTransactionType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePayableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePayableTransactionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePayableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="PayableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PayFromPartyMaster.xsd"/>
  <xsd:element name="AcknowledgePayFromPartyMaster" type="AcknowledgePayFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge PayFromPartyMaster is to notify a systen
                                that requested a change to a PayFrom object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePayFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePayFromPartyMasterDataAreaType">
            <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
                                                  AcknowledgePayFromPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (PayFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePayFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="PayFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Person.xsd"/>
  <xsd:element name="AcknowledgePerson" type="AcknowledgePersonType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePersonType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePersonDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePersonDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Person" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Personnel.xsd"/>
  <xsd:element name="AcknowledgePersonnel" type="AcknowledgePersonnelType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgePersonnel is to enable the synchronization of employee data that exists on separate data bases between manufacturing and human resource applications.  The ProcessPersonnel allows the adding of new employees and their relevant data as well as the modification of previously established employees.

The ProcessPersonnel is used to facilitate the maintenance of human resource data in a manufacturing work force planning module.  This enables the workforce planning module to use current personnel information when creating finite production schedules.  The ProcessPersonnel can also be used by a project accounting application or a work order management application to assign qualified personnel or to perform resource planning.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePersonnelType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePersonnelDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessPersonnel. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Personnel).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePersonnelDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Personnel" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Ping.xsd"/>
  <xsd:element name="AcknowledgePing" type="AcknowledgePingType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge Ping is to request that an
                                account dimension be changed or created or a valid value for one of
                                the dimensions modified or created.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePingType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePingDataAreaType">
            <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 AcknowledgePing.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Acknowledge) indicates the action to be
                                                  performed on the Noun
                                                  (Ping).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePingDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Ping" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PlannedProductionOrder.xsd"/>
  <xsd:element name="AcknowledgePlannedProductionOrder" type="AcknowledgePlannedProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgePlannedProductionOrder Business Object Document is to acknowledge receipt of the PlannedProductionOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePlannedProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePlannedProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgePlannedProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (PlannedProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePlannedProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="PlannedProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PlannedPurchaseOrder.xsd"/>
  <xsd:element name="AcknowledgePlannedPurchaseOrder" type="AcknowledgePlannedPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the
                AcknowledgePlannedPurchaseOrder Business Object Document is to acknowledge receipt of the Purchase
                Order and to reflect any changes. Commonly, the acknowledgment is generated by an
                order management application and transmitted to a purchasing or procurement application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePlannedPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePlannedPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is the place in which the information that the BOD message carries is provided. In this case AcknowledgePlannedPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (PlannedPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePlannedPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="PlannedPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PlannedTransfer.xsd"/>
  <xsd:element name="AcknowledgePlannedTransfer" type="AcknowledgePlannedTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the AcknowledgePlannedTransfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePlannedTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePlannedTransferDataAreaType">
            <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 AcknowledgePlannedTransfer. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (PlannedTransfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePlannedTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="PlannedTransfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PlanningSchedule.xsd"/>
  <xsd:element name="AcknowledgePlanningSchedule" type="AcknowledgePlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge PlanningSchedule is to to return the
                                results of a Process message.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePlanningScheduleDataAreaType">
            <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
                                                  AcknowledgePlanningSchedule. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (PlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="PlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProductionOrder.xsd"/>
  <xsd:element name="AcknowledgeProductionOrder" type="AcknowledgeProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeProductionOrder Business Object Document is to acknowledge receipt of the ProductionOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProductionReceiver.xsd"/>
  <xsd:element name="AcknowledgeProductionReceiver" type="AcknowledgeProductionReceiverType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProductionReceiverType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProductionReceiverDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProductionReceiverDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProductionReceiver" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectBalance.xsd"/>
  <xsd:element name="AcknowledgeProjectBalance" type="AcknowledgeProjectBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge ProjectBalance is to notify a systen
                                that requested a change to a Project object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectBalanceDataAreaType">
            <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 AcknowledgeProjectBalance. The
                                                  information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action
                                                  to be performed on the Noun(ProjectBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectBid.xsd"/>
  <xsd:element name="AcknowledgeProjectBid" type="AcknowledgeProjectBidType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeProjectBid Business Object Document is to acknowledge receipt of the ProjectBid
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectBidType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectBidDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeProjectBid. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProjectBid).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectBidDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectBid" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectBudget.xsd"/>
  <xsd:element name="AcknowledgeProjectBudget" type="AcknowledgeProjectBudgetType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeProjectBudget Business Object Document is to acknowledge receipt of the ProjectBudget
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectBudgetType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectBudgetDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeProjectBudget. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProjectBudget).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectBudgetDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectBudget" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectCosts.xsd"/>
  <xsd:element name="AcknowledgeProjectCosts" type="AcknowledgeProjectCostsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeProjectCosts Business Object Document is to acknowledge receipt of the ProjectCosts
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectCostsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectCostsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeProjectCosts. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProjectCosts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectCostsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectCosts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectEstimate.xsd"/>
  <xsd:element name="AcknowledgeProjectEstimate" type="AcknowledgeProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeProjectEstimate Business Object Document is to acknowledge receipt of the ProjectEstimate
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="AcknowledgeProjectEstimate" type="AcknowledgeProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeProjectEstimate Business Object Document is to acknowledge receipt of the ProjectEstimate
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectMaster.xsd"/>
  <xsd:element name="AcknowledgeProjectMaster" type="AcknowledgeProjectMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge ProjectMaster is to notify a systen
                                that requested a change to a Project object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectMasterDataAreaType">
            <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 AcknowledgeProjectMaster. The
                                                  information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action
                                                  to be performed on the Noun(ProjectMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectPeriodBalance.xsd"/>
  <xsd:element name="AcknowledgeProjectPeriodBalance" type="AcknowledgeProjectPeriodBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge ProjectPeriodBalance is to notify a systen
                                that requested a change to a Project object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectPeriodBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectPeriodBalanceDataAreaType">
            <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 AcknowledgeProjectPeriodBalance. The
                                                  information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action
                                                  to be performed on the Noun(ProjectPeriodBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectPeriodBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectPeriodBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectRevenue.xsd"/>
  <xsd:element name="AcknowledgeProjectRevenue" type="AcknowledgeProjectRevenueType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeProjectRevenue Business Object Document is to acknowledge receipt of the ProjectRevenue
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeProjectRevenueType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeProjectRevenueDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeProjectRevenue. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ProjectRevenue).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeProjectRevenueDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ProjectRevenue" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PurchaseOrder.xsd"/>
  <xsd:element name="AcknowledgePurchaseOrder" type="AcknowledgePurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the
                AcknowledgePurchaseOrder Business Object Document is to acknowledge receipt of the Purchase
                Order and to reflect any changes. Commonly, the acknowledgment is generated by an
                order management application and transmitted to a purchasing or procurement application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgePurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgePurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is the place in which the information that the BOD message carries is provided. In this case AcknowledgePurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgePurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Quote.xsd"/>
  <xsd:element name="AcknowledgeQuote" type="AcknowledgeQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeQuote Business Object Document is to acknowledge receipt of the Quote
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeQuote. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (Quote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Quote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ReceivableTransaction.xsd"/>
  <xsd:element name="AcknowledgeReceivableTransaction" type="AcknowledgeReceivableTransactionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge Receivable receipt of the invoice and to reflect any changes. Commonly, the acknowledgment is generated by an
                                order management application and transmitted to a purchasing or procurement application
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeReceivableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeReceivableTransactionDataAreaType">
            <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 AcknowledgeReceivable. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (Receivable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeReceivableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ReceivableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ReceiveDelivery.xsd"/>
  <xsd:element name="AcknowledgeReceiveDelivery" type="AcknowledgeReceiveDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The AcknowledgeReceiveDelivery may be used to notify the shipping business partner that the shipment has been received by the customer or consignee destination, and alert them to any discovered discrepancies.   The acknowledgement may contain the full detail of the receipt as created by the receiving party or just the discrepancies and other exception conditions.

The AcknowledgeReceiveDelivery BOD supports receipt acknowledgements 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="AcknowledgeReceiveDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeReceiveDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeReceiveDelivery. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) 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="AcknowledgeReceiveDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ReceiveDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/RemitFromPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeRemitFromPartyMaster" type="AcknowledgeRemitFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge RemitFromPartyMaster is to notify a systen
                                that requested a change to a RemitFrom object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeRemitFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeRemitFromPartyMasterDataAreaType">
            <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
                                                  AcknowledgeRemitFromPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (RemitFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeRemitFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="RemitFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/RemittanceAdvice.xsd"/>
  <xsd:element name="AcknowledgeRemittanceAdvice" type="AcknowledgeRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge RemittanceAdvice is to to facilitate keeping Sales
                                order information Acknowledgehronized on separate data bases throughout an
                                enterprise. The Acknowledge RemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeRemittanceAdviceDataAreaType">
            <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 AcknowledgeRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Acknowledge)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (RemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="RemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/RemitToPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeRemitToPartyMaster" type="AcknowledgeRemitToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge RemitToPartyMaster is to notify a systen
                                that requested a change to a RemitTo object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeRemitToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeRemitToPartyMasterDataAreaType">
            <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
                                                  AcknowledgeRemitToPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (RemitToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeRemitToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="RemitToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Requisition.xsd"/>
  <xsd:element name="AcknowledgeRequisition" type="AcknowledgeRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeRequisition Business Object Document is to acknowledge receipt of the Requisition
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeRequisition. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (Requisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Requisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/RFQ.xsd"/>
  <xsd:element name="AcknowledgeRFQ" type="AcknowledgeRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeRFQ Business Object Document is to acknowledge receipt of the RFQ
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeRFQ. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (RFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="RFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SalesOrder.xsd"/>
  <xsd:element name="AcknowledgeSalesOrder" type="AcknowledgeSalesOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeSalesOrder Business Object Document is to acknowledge receipt of the SalesOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSalesOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSalesOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeSalesOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (SalesOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSalesOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ServiceConsumption.xsd"/>
  <xsd:element name="AcknowledgeServiceConsumption" type="AcknowledgeServiceConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge ServiceConsumption is to notify the entire
                                enterprise of any services or associated items that have been
                                received directly ourside of the warehouse.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeServiceConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeServiceConsumptionDataAreaType">
            <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 AcknowledgeServiceConsumption.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Acknowledge) indicates the action to be
                                                  performed on the Noun
                                                  (ServiceConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeServiceConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ServiceConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ServiceContract.xsd"/>
  <xsd:element name="AcknowledgeServiceContract" type="AcknowledgeServiceContractType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeServiceContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeServiceContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeServiceContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ServiceContract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ServiceOrder.xsd"/>
  <xsd:element name="AcknowledgeServiceOrder" type="AcknowledgeServiceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeServiceOrder Business Object Document is to acknowledge receipt of the ServiceOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeServiceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeServiceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeServiceOrder. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (ServiceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeServiceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ServiceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ShipFromPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeShipFromPartyMaster" type="AcknowledgeShipFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge ShipFromPartyMaster is to notify a systen
                                that requested a change to a ShipFrom object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeShipFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeShipFromPartyMasterDataAreaType">
            <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
                                                  AcknowledgeShipFromPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (ShipFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeShipFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ShipFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Shipment.xsd"/>
  <xsd:element name="AcknowledgeShipment" type="AcknowledgeShipmentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeShipment Business Object Document is to acknowledge receipt of the Shipment
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeShipmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeShipmentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeShipment. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (Shipment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeShipmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Shipment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ShipToPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeShipToPartyMaster" type="AcknowledgeShipToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge ShipToPartyMaster is to notify a systen
                                that requested a change to a ShipTo object of the completion of
                                the processing of that request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeShipToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeShipToPartyMasterDataAreaType">
            <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
                                                  AcknowledgeShipToPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (ShipToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeShipToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="ShipToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SourceSystemJournalEntry.xsd"/>
  <xsd:element name="AcknowledgeSourceSystemJournalEntry" type="AcknowledgeSourceSystemJournalEntryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose
                                of the AcknowledgeJournalEntry is to enable an application or
                                component to respond to a ProcessSourceSystemJournalEntry. The
                                response to the AcknowledgeSourceSystemJournalEntry is the response
                                to the ProcessSourceSystemJournalEntry.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSourceSystemJournalEntryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSourceSystemJournalEntryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the
                                                  BOD message carries is provided, in
                                                  this case AcknowledgeJournalEntry.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (JournalEntry). In response to the
                                                  PostJournalEntry.
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSourceSystemJournalEntryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SourceSystemJournalEntry" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierBalance.xsd"/>
  <xsd:element name="AcknowledgeSupplierBalance" type="AcknowledgeSupplierBalanceType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSupplierBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSupplierBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSupplierBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SupplierBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierInvoice.xsd"/>
  <xsd:element name="AcknowledgeSupplierInvoice" type="AcknowledgeSupplierInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeSupplierInvoice Business Object Document is to acknowledge receipt of the SupplierInvoice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSupplierInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSupplierInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeSupplierInvoice. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (SupplierInvoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSupplierInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SupplierInvoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierPartyMaster.xsd"/>
  <xsd:element name="AcknowledgeSupplierPartyMaster" type="AcknowledgeSupplierPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge SupplierPartyMaster is to acknowledge the
                                change of a supplier in response to a Process.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSupplierPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSupplierPartyMasterDataAreaType">
            <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
                                                  AcknowledgeSupplierPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Acknowledge) indicates the action
                                                  to be performed on the Noun
                                                  (SupplierPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSupplierPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SupplierPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierPlanningSchedule.xsd"/>
  <xsd:element name="AcknowledgeSupplierPlanningSchedule" type="AcknowledgeSupplierPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge SupplierPlanningSchedule is to to return the
                                results of a Process message.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSupplierPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSupplierPlanningScheduleDataAreaType">
            <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 
                                                          AcknowledgeSupplierPlanningSchedule. The information consists of a Verb and one or 
                                                          more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun
                                                          (SupplierPlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSupplierPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SupplierPlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierQuote.xsd"/>
  <xsd:element name="AcknowledgeSupplierQuote" type="AcknowledgeSupplierQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeSupplierQuote Business Object Document is to acknowledge receipt of the SupplierQuote
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSupplierQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSupplierQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeSupplierQuote. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (SupplierQuote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSupplierQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SupplierQuote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierRemittanceAdvice.xsd"/>
  <xsd:element name="AcknowledgeSupplierRemittanceAdvice" type="AcknowledgeSupplierRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Acknowledge SupplierRemittanceAdvice is to to facilitate keeping Sales
                                order information Acknowledgehronized on separate data bases throughout an
                                enterprise. The Acknowledge SupplierRemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeSupplierRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeSupplierRemittanceAdviceDataAreaType">
            <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 AcknowledgeSupplierRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Acknowledge)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SupplierRemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeSupplierRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="SupplierRemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/TextMessage.xsd"/>
  <xsd:element name="AcknowledgeTextMessage" type="AcknowledgeTextMessageType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        Is where
                                the information that the TextMessage message carries is provided, in this
                                case AcknowledgeTextMessage. The information consists of a Verb and one or
                                more Nouns. The verb Acknowledge indicates the action to be
                                performed on the Noun(TextMessage).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeTextMessageType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeTextMessageDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeTextMessageDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="TextMessage" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/TradingPartner.xsd"/>
  <xsd:element name="AcknowledgeTradingPartner" type="AcknowledgeTradingPartnerType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeJournal is to transmit data necessary to create a journal entry from any sub ledger business application to a general ledger application.

Many applications in the enterprise environment create data that cause changes in the account balances of a 
general ledger application.  Some components that have activity which will be reflected in a general ledger 
application are:

1.	Benefits
2.	Costing
3.	Human Resources
4.	Inventory Control
5.	Manufacturing
6.	Payroll
7.	Production
8.	Treasury

By no means is this a complete list of all the components that create activity which generate a journal entry.

Many tasks that occur within the enterprise applications cause the creation of a General Ledger journal entry.  
Tasks relate directly to the Component.  For example, the adjustment of inventory value is a task that occurs within 
the Inventory Control Component.  Some of the tasks that would be catalysts for changes in a general ledger include:

1.	Receiving Inventory
2.	Issuing Inventory
3.	Transferring Inventory
4.	Adjusting Inventory Value
5.	Adjusting Inventory Count
6.	Calculating Material Variances
7.	Calculating Labor Variances
8.	Calculating Overhead Variances
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeTradingPartnerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeTradingPartnerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeTradingPartner. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (TradingPartner).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeTradingPartnerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="TradingPartner" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Transfer.xsd"/>
  <xsd:element name="AcknowledgeTransfer" type="AcknowledgeTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Acknowledge Transfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeTransferDataAreaType">
            <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 AcknowledgeTransfer. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (Transfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Transfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/TransportationRequisition.xsd"/>
  <xsd:element name="AcknowledgeTransportationRequisition" type="AcknowledgeTransportationRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeTransportationRequisition Business Object Document is to acknowledge receipt of the TransportationRequisition
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeTransportationRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeTransportationRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeTransportationRequisition. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (TransportationRequisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeTransportationRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="TransportationRequisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/TransportationStatus.xsd"/>
  <xsd:element name="AcknowledgeTransportationStatus" type="AcknowledgeTransportationStatusType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeTransportationStatus Business Object Document is to acknowledge receipt of the TransportationStatus
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeTransportationStatusType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeTransportationStatusDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeTransportationStatus. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (TransportationStatus).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeTransportationStatusDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="TransportationStatus" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Workflow.xsd"/>
  <xsd:element name="AcknowledgeWorkflow" type="AcknowledgeWorkflowType">
    <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 AcknowledgeAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeWorkflowType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeWorkflowDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeWorkflowDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="Workflow" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/BOD.xsd"/>
  <xsd:element name="ConfirmBOD" type="ConfirmBODType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ConfirmBOD may be returned for a given BOD, depending upon the value that the sender of the BOD set in the Confirmation field in sender. One NounOutcome component will be provided for each Noun Instance in the original BOD. Summary BOD-level information is reported in the Header, with noun-specific errors or warnings reported for each noun instance are reported in the NounOutcome component again one per occurance of the Noun Instance.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ConfirmBODType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ConfirmBODDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ConfirmBOD. The information consists of a Verb and one or more Nouns. The verb (Confirm) indicates the action to be performed on the Noun (BOD).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ConfirmBODDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Confirm"/>
      <xsd:element ref="BOD" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetAccountingBookDefinition" type="GetAccountingBookDefinitionType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetAccountingBookDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetAccountingBookDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetAccountingBookDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="AccountingBookDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetAccountingChart" type="GetAccountingChartType">
    <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 GetAccountingChart. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingChart).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetAccountingChartType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetAccountingChartDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetAccountingChartDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="AccountingChart" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetAccountingEntity" type="GetAccountingEntityType">
    <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 GetAccountingEntity. The
                                information consists of a Verb and one or more Nouns. The verb Get indicates the action
                                to be performed on the Noun
                                (AccountingEntity).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetAccountingEntityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetAccountingEntityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetAccountingEntityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="AccountingEntity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetAccountingJournal" type="GetAccountingJournalType">
    <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 GetAccountingJournal. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingJournal).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetAccountingJournalType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetAccountingJournalDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetAccountingJournalDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="AccountingJournal" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetAdvanceShipNotice" type="GetAdvanceShipNoticeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetAdvanceShipNotice Business Object Document is to Get receipt of the AdvanceShipNotice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetAdvanceShipNoticeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetAdvanceShipNoticeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetAdvanceShipNotice. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (AdvanceShipNotice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetAdvanceShipNoticeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="AdvanceShipNotice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetAssetMaster" type="GetAssetMasterType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="AssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetAssetMeterReading" type="GetAssetMeterReadingType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetAssetMeterReadingType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetAssetMeterReadingDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetAssetMeterReadingDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="AssetMeterReading" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetBillOfMaterials" type="GetBillOfMaterialsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SynBillOfMaterials is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Bill of Material.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetBillOfMaterialsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetBillOfMaterialsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetBillOfMaterials. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (BillOfMaterials).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetBillOfMaterialsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="BillOfMaterials" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetBillOfResources" type="GetBillOfResourcesType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the BillOfResources is to enable an application to request specific Item Bill of Material information from another business application module.  The response to the BillOfResources is the ShowBillOfResources.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate Item Bill of Material information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetBillOfResourcesType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetBillOfResourcesDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case BillOfResources. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (BillOfResources).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetBillOfResourcesDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="BillOfResources" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetBillToPartyMaster" type="GetBillToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetBillToPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The ShowBillToPartyMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetBillToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetBillToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetBillToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (BillToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetBillToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="BillToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetBusinessPlan" type="GetBusinessPlanType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetBusinessPlanType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetBusinessPlanDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetBusinessPlanDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="BusinessPlan" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCalendar" type="GetCalendarType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Calendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCampaign" type="GetCampaignType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCampaignType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCampaignDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCampaignDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Campaign" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCarrierParty" type="GetCarrierPartyType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The GetCarrierParty allows a business application to request information
                        about a given party. The ShowCarrierParty is the response to this
                        request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCarrierPartyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCarrierPartyDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided,
                                                        in this case GetCarrierParty. The information consists of a
                                                        Verb and one or more Nouns. The verb (Get) indicates the action to
                                                        be performed on the Noun (CarrierParty).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCarrierPartyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CarrierParty" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCarrierRoute" type="GetCarrierRouteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetCarrierRoute is to enable an application to request specific Carrier Route information from another business application module.  The response to the GetCarrierRoute is the ShowCarrierRoute.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCarrierRouteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCarrierRouteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetCarrierRoute. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (CarrierRoute).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCarrierRouteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CarrierRoute" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCashReceipt" type="GetCashReceiptType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetCashReceipt is to enable a request of an CashReceipt. This BOD may be used as a request by a Customer to its Supplier. The SHowCashReceipt BOD would be the expected response.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCashReceiptType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCashReceiptDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetCashReceipt. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (CashReceipt).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCashReceiptDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CashReceipt" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetChartOfAccounts" type="GetChartOfAccountsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetChartOfAccounts is to enable an application to request specific ChartOfAccounts information from another business application module.  The response to the GetChartOfAccounts is the ShowChartOfAccounts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetChartOfAccountsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetChartOfAccountsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetChartOfAccounts. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ChartOfAccounts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetChartOfAccountsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ChartOfAccounts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetChartsOfAccountsMap" type="GetChartsOfAccountsMapType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetChartsOfAccountsMap is to distribute general ledger chart of accounts code identifiers to other applications to store for validation purposes.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetChartsOfAccountsMapType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetChartsOfAccountsMapDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetChartsOfAccountsMap. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ChartsOfAccountsMap).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetChartsOfAccountsMapDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ChartsOfAccountsMap" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCodeDefinition" type="GetCodeDefinitionType">
    <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 GetCode. The information consists of a Verb and one or
                                more Nouns. The verb Get) indicates the action to be
                                performed on the Noun (Code).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCodeDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCodeDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCodeDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CodeDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetConfiguredAssetMaster" type="GetConfiguredAssetMasterType">
    <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 GetConfiguredAssetMaster. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetConfiguredAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetConfiguredAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetConfiguredAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ConfiguredAssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetConstrainedResource" type="GetConstrainedResourceType">
    <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 GetConstrainedResource. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetConstrainedResourceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetConstrainedResourceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetConstrainedResourceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ConstrainedResource" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetContactMaster" type="GetContactMasterType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetContactMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetContactMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetContactMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ContactMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetContract" type="GetContractType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Contract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCurrency" type="GetCurrencyType">
    <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 GetCurrency. The information consists of a Verb and one or
                                more Nouns. The verb Get) indicates the action to be
                                performed on the Noun (Currency).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCurrencyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCurrencyDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCurrencyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Currency" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCurrencyExchangeRateMaster" type="GetCurrencyExchangeRateMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetCurrencyExchangeRateMaster is to enable an application to request specific CurrencyExchangeRateMaster information from another business application module.  The response to the GetCurrencyExchangeRateMaster is the ShowCurrencyExchangeRateMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCurrencyExchangeRateMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCurrencyExchangeRateMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetCurrencyExchangeRateMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (CurrencyExchangeRateMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCurrencyExchangeRateMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CurrencyExchangeRateMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCurrencyRateType" type="GetCurrencyRateTypeType">
    <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 GetCurrencyRateType. The information consists of a Verb
                                and one or more Nouns. The verb Get) indicates the action to
                                be performed on the Noun (CurrencyRateType).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCurrencyRateTypeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCurrencyRateTypeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCurrencyRateTypeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CurrencyRateType" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCustomerCall" type="GetCustomerCallType">
    <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 GetCustomerCall. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCustomerCallType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCustomerCallDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCustomerCallDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CustomerCall" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCustomerPartyMaster" type="GetCustomerPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetCustomerPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The GetCustomerPartyMaster allows a business application to request information about a given party. The ShowCustomerPartyMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCustomerPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCustomerPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetCustomerPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (CustomerPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCustomerPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CustomerPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCustomerPurchaseOrder" type="GetCustomerPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the
                GetCustomerPurchaseOrder Business Object Document is to Get receipt of the Purchase
                Order and to reflect any changes. Commonly, the acknowledgment is generated by an
                order management application and transmitted to a purchasing or procurement application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCustomerPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCustomerPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is the place in which the information that the BOD message carries is provided. In this case GetCustomerPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (CustomerPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCustomerPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CustomerPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetCustomerRFQ" type="GetCustomerRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetCustomerRFQ Business Object Document is to Get receipt of the CustomerRFQ
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetCustomerRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetCustomerRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetCustomerRFQ. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (CustomerRFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetCustomerRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="CustomerRFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/EmployeeWorkSchedule.xsd"/>
  <xsd:element name="GetEmployeeWorkSchedule" type="GetEmployeeWorkScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetEmployeeWorkSchedule is to enable an application to request specific EmployeeWorkSchedule information from another business application module.  The response to the GetEmployeeWorkSchedule is the ShowEmployeeWorkSchedule.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetEmployeeWorkScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetEmployeeWorkScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetEmployeeWorkSchedule. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (EmployeeWorkSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetEmployeeWorkScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="EmployeeWorkSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetEmployeeWorkTime" type="GetEmployeeWorkTimeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetEmployeeWorkTime is to enable an application to request specific EmployeeWorkTime information from another business application module.  The response to the GetEmployeeWorkTime is the ShowEmployeeWorkTime.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetEmployeeWorkTimeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetEmployeeWorkTimeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetEmployeeWorkTime. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (EmployeeWorkTime).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetEmployeeWorkTimeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="EmployeeWorkTime" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetExpenseReport" type="GetExpenseReportType">
    <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 GetExpenseReport. The
                                information consists of a Verb and one or more Nouns. The verb Get indicates the action
                                to be performed on the Noun
                                (ExpenseReport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetExpenseReportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetExpenseReportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetExpenseReportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ExpenseReport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetField" type="GetFieldType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Get Field is to notify the requestor if a change
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetFieldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetFieldDataAreaType">
            <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 GetField. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Get) indicates the action to be
                                                  performed on the Noun
                                                  (Field).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetFieldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Field" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetFinancialCalendar" type="GetFinancialCalendarType">
    <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 GetFinancialCalendar. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (FinancialCalendar).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetFinancialCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetFinancialCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetFinancialCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="FinancialCalendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetFinancialPartyMaster" type="GetFinancialPartyMasterType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetFinancialPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetFinancialPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetFinancialPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="FinancialPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/GLMovement.xsd"/>
  <xsd:element name="GetGLMovement" type="GetGLMovementType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Get GLMovement is to Request to carry period balance/movement
                                from the SOR.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetGLMovementType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetGLMovementDataAreaType">
            <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 GetGLMovement. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Get)
                                                  indicates the action to be performed
                                                  on the Noun(GLMovement).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetGLMovementDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="GLMovement" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetHandlingGroup" type="GetHandlingGroupType">
    <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 GetHandlingGroup. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (HandlingGroup).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetHandlingGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetHandlingGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetHandlingGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="HandlingGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetInspectDelivery" type="GetInspectDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetInspectDelivery is to enable an application to request specific InspectDelivery information from another business application module.  The response to the GetInspectDelivery is the ShowInspectDelivery.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetInspectDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetInspectDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetInspectDelivery. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (InspectDelivery).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetInspectDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="InspectDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetInventoryAdjustment" type="GetInventoryAdjustmentType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Get InventoryAdjustment is to notify the
                                enterprise of the change to the hold status of an inventory item.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetInventoryAdjustmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetInventoryAdjustmentDataAreaType">
            <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 GetInventoryAdjustment. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Get)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryAdjustment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetInventoryAdjustmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="InventoryAdjustment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetInventoryBalance" type="GetInventoryBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetInventoryBalance is to enable an application to request specific InventoryBalance information from another business application module.  The response to the GetInventoryBalance is the ShowInventoryBalance.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetInventoryBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetInventoryBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetInventoryBalance. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (InventoryBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetInventoryBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="InventoryBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetInventoryConsumption" type="GetInventoryConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The most common use of the GetInventoryConsumption is to request a buyer's usage information about an item or product for the supplier of such item or product.  This BOD will not create or update either buyer's or supplier's inventory records.   The receiver of the request is responsible to make effective use of this information.

The BOD can be used in the following ways: 
(1)  for a supplier of goods to request from the buyer, the consumptn status of goods
(2)  for a vendor to request from the retailer if retail sales of goods have been made; and 
(3)  for inventory systems to request consumptn status from plant data collection and warehouse management systems.

This is an outline of the business flow that this BOD supports:
(1)  Overall purchase, replenishment or vendor managed inventory agreement is in place and/or a Get Consumptn message is sent by the supplier.
(2)  Show Consumptn Message is returned the to supplier, distributor or third party logistics provider, that material has been consumed.  This is done in response to events such as these (and/or the Get message), depending on implementation context:
  �  Material is replenished to line side at manufacturing facitliy.
  �  Material is assembled into final product.
  �  Material is purchased and removed from facility by customer.
(3)  Supplier, distributor, third party logistics provider replenishes material, using information provided in the Show Consumptn message, the demand and shipment forecasts, and the terms of the overall purchase or vendor managed inventory agreement.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetInventoryConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetInventoryConsumptionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetInventoryConsumption. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (InventoryConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetInventoryConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="InventoryConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetInventoryCount" type="GetInventoryCountType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetInventoryCount is to request an occurrences of a Inventory Count information from an ERP system. This count may be a cycle count or a physical count.  This BOD may also apply to planned or unplanned inventory counts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetInventoryCountType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetInventoryCountDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetInventoryCount. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (InventoryCount).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetInventoryCountDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="InventoryCount" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetInventoryHold" type="GetInventoryHoldType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Get InventoryHold is to
                                request the current status of all inventory items.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetInventoryHoldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetInventoryHoldDataAreaType">
            <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 GetInventoryHold.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Get) indicates the action
                                                  to be performed on the Noun
                                                  (InventoryHold).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetInventoryHoldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="InventoryHold" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetInvoice" type="GetInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetInvoice is to enable a request of an invoice. This BOD may be used as a request by a Customer to its Supplier. The SHowInvoice BOD would be the expected response.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetInvoice. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Invoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Invoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetItemMaster" type="GetItemMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetItemMaster is to enable a business application module to request information concerning a specific ITEM from another business application.  The reply to this BOD is the ShowItemMaster.

There are many possible business applications in several environments that may use this capability.  For example, an MRP, Inventory, or Manufacturing business application could use this to request item information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetItemMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetItemMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetItemMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ItemMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetItemMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ItemMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetLocation" type="GetLocationType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetLocation is to enable an application to request specific Location information from another business application module.  The response to the GetLocation is the ShowLocation.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetLocationType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetLocationDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetLocation. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Location).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetLocationDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Location" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/LocationService.xsd"/>
  <xsd:element name="GetLocationService" type="GetLocationServiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of  RequestLocationService is to enable a mechanism to ensure that the physical locations owned by the business applications are validated, geocoded, and standardized based on information returned by location service providers.

This BOD may be initiated by the sending system upon some event occurring, such as receiving a request submitted by another system for certain location service.

There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to receive processed location information from location service providers.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetLocationServiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of  ReceiveLocationService is to enable a mechanism to ensure that the physical location owned by the business applications are validated, geocoded, and standardized by the location service providers.                                                                       This BOD may also be initiated by the service provider in response to receiving a request for a particular service such as geocoding, address validation, etc.                                                                                      There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to communicate Location information to location service providers.
      </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetLocationServiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ReceiveLocationService.                                             The information consists of a Verb and one or more Nouns. The verb (Receive) indicates the action to be performed on the Noun (LocationService).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetLocationServiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="LocationService" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetMaintenanceOrder" type="GetMaintenanceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetMaintenanceOrder is to enable a business applications module to request this information from another business application.  The response to this BOD is the ShowMaintenanceOrder.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetMaintenanceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetMaintenanceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetMaintenanceOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (MaintenanceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetMaintenanceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="MaintenanceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetMatchDocument" type="GetMatchDocumentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetMatchDocument is to enable a business application module to request information concerning invoice matching  from another business application.  The reply to this BOD is the ShowMatchDocument.

This BOD does not usually cause updates to occur. There are several possible business applications in several environments that may use this capability. The description and the pictures below visualize the possible use of this BOD.

In certain application suites, purchase order and invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application.

The invoice matching process may include several document types, including the following:

Two way match - Purchase Order and the Invoice 

 Three way match - Purchase Order, Invoice, and the Receipt 

Four way match - Purchase Order, Invoice, Receipt, and Inspection results 

Note:  For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching.

When matching takes place in the purchasing application, the purchasing application may have to request the accounts payable application to provide the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched.  This is the generally the situation when the invoice is initially entered into the accounts payable application.

Note that in some situations, accounts payable will send invoices to the purchasing application unsolicited. In others, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters.

When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. Alternatively, the accounts payable application can request the information.

The purpose of the GetMatchDocument is to enable both the accounts payable application and the purchasing application to request the transactions that are required to be matched.  In both cases, the receiving application will use the ShowMatchDocument to return the requested information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetMatchDocumentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetMatchDocumentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetMatchDocument. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (MatchDocument).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetMatchDocumentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="MatchDocument" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetMoveInventory" type="GetMoveInventoryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetMoveInventory is to enable an application or component to request an MoveInventory document from another business application or component.

The response to the GetMoveInventory is is the ListMoveInventory. The GetMoveInventory also enables the retrieval of information across several documents by using selection fields.    This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetMoveInventoryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetMoveInventoryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetLocation. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (MoveInventory).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetMoveInventoryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="MoveInventory" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetOpportunity" type="GetOpportunityType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetOpportunity is to enable an application to request a specific Opportunity information from one business application to another business application. The response to the GetOpportunity is the ShowOpportunity.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetOpportunityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetOpportunityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetOpportunityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Opportunity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Payable.xsd"/>
  <xsd:element name="GetPayable" type="GetPayableType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetPayable is to facilitate keeping party information synchronized that exists on separate data bases.  The GetPayable allows a business application to request information about a given party. The ShowPayable is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPayableType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPayableDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPayable. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Payable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPayableDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Payable" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPayableTransaction" type="GetPayableTransactionType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPayableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPayableTransactionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPayableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PayableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPayFromPartyMaster" type="GetPayFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetPayFromPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The GetPayFromPartyMaster allows a business application to request information about a given party. The ShowPayFromPartyMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPayFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPayFromPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPayFromPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PayFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPayFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PayFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPerson" type="GetPersonType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPersonType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPersonDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPersonDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Person" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPersonnel" type="GetPersonnelType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetPersonnel is to request Personnel data for a worker.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPersonnelType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPersonnelDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPersonnel. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Personnel).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPersonnelDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Personnel" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPlannedProductionOrder" type="GetPlannedProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetPlannedProductionOrder is to enable an business application module to request specific Production Order information from another business application module.  The reply to this is the ShowPlannedProductionOrder.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPlannedProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPlannedProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPlannedProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PlannedProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPlannedProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PlannedProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPlannedPurchaseOrder" type="GetPlannedPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetPlannedPurchaseOrder is to enable a business application module to request information concerning a specific purchase order from another business application.  The reply to this BOD is the ShowPlannedPurchaseOrder.

There are several environments that may use this capability. For example, an MRP application may use this BOD to ask for information from a Order Management application, or a Plant Data Collection application may also use this BOD to request information from a Order Management application. This may als happen across business parties.

This BOD does not usually cause updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPlannedPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPlannedPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPlannedPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PlannedPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPlannedPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PlannedPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPlannedTransfer" type="GetPlannedTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the GetPlannedTransfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPlannedTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPlannedTransferDataAreaType">
            <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 GetPlannedTransfer. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PlannedTransfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPlannedTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PlannedTransfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPlanningSchedule" type="GetPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party.  Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional Data Type PlanningScheduleException.

The purpose of the GetPlanningSchedule is to enable a business applications module to request this Planning Schedule information from another business application. The response to this BOD is ShowPlanningSchedule.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPlanningScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPlanningSchedule. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/PriceList.xsd"/>
  <xsd:element name="GetPriceList" type="GetPriceListType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetPriceList is to enable a business application module or system to request information concerning new or existing product price lists.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in an Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, a Manufacturing, distributor or reseller business application could use this to communicate the price change or request a price list.

It may also be necessary to support Component Supplier Management (CSM) scenarios. In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog. A customer purchases the product from the Catalog provider.  They have the capability to do comparison shopping from the catalog. Supplier Certification may be provided by the Catalog provider.

This definition of price list is intended to support simple pricing scenario, especially pricing that may accompany a published price list.  It is not intended to support complex pricing environments that may be needed to support features such as;

�         Deals and Promotions

�         Coupons and Sales Incentives

�         Rebates and Accruals

This functionality will be addressed in a subsequent release.  It is a working assumption that the representation of complex qualifications, coupons and sales incentives are rarely communicated between systems.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPriceListType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPriceListDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPriceList. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PriceList).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPriceListDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PriceList" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProductionOrder" type="GetProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProductionOrder is to enable an business application module to request specific Production Order information from another business application module.  The reply to this is the ShowProductionOrder.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProductionReceiver" type="GetProductionReceiverType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProductionReceiverType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProductionReceiverDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProductionReceiverDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProductionReceiver" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectBalance" type="GetProjectBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectBalance is to facilitate keeping party information synchronized that exists on separate data bases.  The GetProjectBalance allows a business application to request information about a given party. The ShowProjectBalance is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectBalance. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectBid" type="GetProjectBidType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectBid is to enable a business applications module to request this ProjectBid information from another business application. The response to this BOD is ShowProjectBid.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectBidType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectBidDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectBid. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectBid).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectBidDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectBid" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectBudget" type="GetProjectBudgetType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectBudget is to enable a business applications module to request this ProjectBudget information from another business application. The response to this BOD is ShowProjectBudget.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectBudgetType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectBudgetDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectBudget. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectBudget).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectBudgetDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectBudget" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectCosts" type="GetProjectCostsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectCosts is to enable a business applications module to request this ProjectCosts information from another business application. The response to this BOD is ShowProjectCosts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectCostsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectCostsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectCosts. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectCosts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectCostsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectCosts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectEstimate" type="GetProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectEstimate is to enable a business applications module to request this ProjectEstimate information from another business application. The response to this BOD is GetProjectEstimate.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectEstimate" type="GetProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectEstimate is to enable a business applications module to request this ProjectEstimate information from another business application. The response to this BOD is ShowProjectEstimate.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectMaster" type="GetProjectMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The GetProjectMaster allows a business application to request information about a given party. The ShowProjectMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectPeriodBalance" type="GetProjectPeriodBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectPeriodBalance is to facilitate keeping party information synchronized that exists on separate data bases.  The GetProjectPeriodBalance allows a business application to request information about a given party. The ShowProjectPeriodBalance is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectPeriodBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectPeriodBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectPeriodBalance. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectPeriodBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectPeriodBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectPeriodBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetProjectRevenue" type="GetProjectRevenueType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetProjectRevenue is to enable a business applications module to request this ProjectRevenue information from another business application. The response to this BOD is ShowProjectRevenue.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetProjectRevenueType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetProjectRevenueDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetProjectRevenue. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ProjectRevenue).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetProjectRevenueDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ProjectRevenue" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetPurchaseOrder" type="GetPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Get PurchaseOrder is to enable a business application module to request information concerning a specific purchase order from another business application.  The reply to this BOD is the Show PurchaseOrder.

There are several environments that may use this capability. For example, an MRP application may use this BOD to ask for information from a Order Management application, or a Plant Data Collection application may also use this BOD to request information from a Order Management application. This may als happen across business parties.

This BOD does not usually cause updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetQuote" type="GetQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetQuote is to enable a business applications module to request this Quote information from another business application. The response to this BOD is ShowQuote.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetQuote. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Quote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Quote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Receivable.xsd"/>
  <xsd:element name="GetReceivable" type="GetReceivableType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetReceivable is to enable an application to request specific Receivable information from another business application module.  The response to the GetReceivable is the ShowReceivable.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetReceivableType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetReceivableDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetReceivable. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Receivable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetReceivableDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Receivable" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetReceivableTransaction" type="GetReceivableTransactionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Get Receivable is to request a collection of
                                Receivable records for initialization or disaster recovery.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetReceivableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetReceivableTransactionDataAreaType">
            <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 GetReceivable. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Get)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (Receivable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetReceivableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ReceivableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetReceiveDelivery" type="GetReceiveDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The GetReceiveDelivery may be used to request information about a specific expected (unreceived) or previously received goods delivery.  The response to the GetReceiveDelivery request is ShowReceiveDelivery.

For expected deliveries, the ShowReceiveDelivery document content may act as a receiving template or checklist to identify the quantity and shipping configuration of the expected goods.  The ShowReceiveDelivery supports describing shipment content 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="GetReceiveDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetReceiveDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetReceiveDelivery. The information consists of a Verb and one or more Nouns. The verb (Get) 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="GetReceiveDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ReceiveDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetRemittanceAdvice" type="GetRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Get RemittanceAdvice is to to facilitate keeping Sales
                                order information Gethronized on separate data bases throughout an
                                enterprise. The Get RemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetRemittanceAdviceDataAreaType">
            <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 GetRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Get)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (RemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="RemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetRemitToPartyMaster" type="GetRemitToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetRemitToPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The GetRemitToPartyMaster allows a business application to request information about a given party. The ShowRemitToPartyMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetRemitToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetRemitToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetRemitToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (RemitToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetRemitToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="RemitToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetRequisition" type="GetRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetRequisition is to enable a business application to request information concerning a specific requisition from another business application.  The reply to this BOD is the ShowRequisition.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetRequisition. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Requisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Requisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetRFQ" type="GetRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetRFQ document is to enable a business applications module to request Request for Quote information from another business application. The response to this BOD is ShowRFQ.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetRFQ. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (RFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="RFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSalesOrder" type="GetSalesOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Get SalesOrder is to enable a business application module to request information concerning a specific sales order from another business application.  The reply to this BOD is the Show SalesOrder.

There are several possible business applications in several environments that may use this capability.  For example, a Sales Automation application may use this BOD to ask for information from a Customer Order application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSalesOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSalesOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetSalesOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (SalesOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSalesOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SequenceSchedule.xsd"/>
  <xsd:element name="GetSequenceSchedule" type="GetSequenceScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application.

The purpose of the GetSequenceSchedule is to enable a business applications module to request this SequenceSchedule information from another business application. The response to this BOD is ShowSequenceSchedule.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSequenceScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSequenceScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetSequenceSchedule. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (SequenceSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSequenceScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SequenceSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetServiceConsumption" type="GetServiceConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Get ServiceConsumption is to notify the entire
                                enterprise of any services or associated items that have been
                                received directly ourside of the warehouse.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetServiceConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetServiceConsumptionDataAreaType">
            <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 GetServiceConsumption.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Get) indicates the action to be
                                                  performed on the Noun
                                                  (ServiceConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetServiceConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ServiceConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetServiceContract" type="GetServiceContractType">
    <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 GetServiceContract. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetServiceContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetServiceContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetServiceContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ServiceContract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetServiceOrder" type="GetServiceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetServiceOrder is to enable a business applications module to request this information from another business application.  The response to this BOD is the ShowServiceOrder.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetServiceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetServiceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetServiceOrder. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ServiceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetServiceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ServiceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetShipFromPartyMaster" type="GetShipFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetShipFromPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The GetShipFromPartyMaster allows a business application to request information about a given party. The ShowShipFromPartyMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetShipFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetShipFromPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetShipFromPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ShipFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetShipFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ShipFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetShipment" type="GetShipmentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetShipment is to enable an application to request specific Shipment information from another business application module.  The response to the GetShipment is the ShowShipment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetShipmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetShipmentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetShipment. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Shipment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetShipmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Shipment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ShipmentSchedule.xsd"/>
  <xsd:element name="GetShipmentSchedule" type="GetShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Commonly, the ship schedule is generated by a material planning application and transmitted to an order or material planning application.
 
The purpose of the GetShipmentSchedule is to enable a business applications module to request this ShipmentSchedule information from another business application. The response to this BOD is ShowShipmentSchedule.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetShipmentScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetShipmentSchedule. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetShipToPartyMaster" type="GetShipToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetShipToPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The ShowShipToPartyMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetShipToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetShipToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetShipToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (ShipToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetShipToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="ShipToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSourceSystemJournalEntry" type="GetSourceSystemJournalEntryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose
                                of the GetJournalEntry is to enable an application or
                                component to respond to a ProcessSourceSystemJournalEntry. The
                                response to the GetSourceSystemJournalEntry is the response
                                to the ProcessSourceSystemJournalEntry.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSourceSystemJournalEntryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSourceSystemJournalEntryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the
                                                  BOD message carries is provided, in
                                                  this case GetJournalEntry.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Get) indicates the action
                                                  to be performed on the Noun
                                                  (JournalEntry). In response to the
                                                  PostJournalEntry.
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSourceSystemJournalEntryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SourceSystemJournalEntry" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSupplierBalance" type="GetSupplierBalanceType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSupplierBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSupplierBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSupplierBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SupplierBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSupplierInvoice" type="GetSupplierInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetSupplierInvoice Business Object Document is to Get receipt of the SupplierInvoice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSupplierInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSupplierInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetSupplierInvoice. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (SupplierInvoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSupplierInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SupplierInvoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSupplierPartyMaster" type="GetSupplierPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetSupplierPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The GetSupplierPartyMaster allows a business application to request information about a given party. The ShowSupplierPartyMaster is the response to this request providing the specific information requested.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSupplierPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSupplierPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetSupplierPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (SupplierPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSupplierPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SupplierPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSupplierPlanningSchedule" type="GetSupplierPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Since collaboration between a customer and a 
                                supplier can potentially go through several rounds of negotiations, both parties can use the same BOD 
                                to communicate their current demand or supply schedule in response to what they received from the other party.  
                                Either party can indicate detailed exception descriptions along with reason code and action code to the other 
                                party why the original demand/supply requirements need to be adjusted using the optional Data Type 
                                SupplierPlanningScheduleException.  
                                
                                The purpose of the GetSupplierPlanningSchedule is to enable a business applications module to request this 
                                Planning Schedule information from another business application. The response to this BOD is 
                                ShowSupplierPlanningSchedule.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSupplierPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSupplierPlanningScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                                that the BOD message carries is provided, in this case 
                                                                GetSupplierPlanningSchedule. The information consists of a Verb and one or more 
                                                                Nouns. The verb (Get) indicates the action to be performed on the Noun 
                                                                (SupplierPlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSupplierPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SupplierPlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSupplierQuote" type="GetSupplierQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetSupplierQuote Business Object Document is to Get receipt of the SupplierQuote
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSupplierQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSupplierQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetSupplierQuote. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (SupplierQuote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSupplierQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SupplierQuote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetSupplierRemittanceAdvice" type="GetSupplierRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Get SupplierRemittanceAdvice is to to facilitate keeping Sales
                                order information Gethronized on separate data bases throughout an
                                enterprise. The Get SupplierRemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSupplierRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSupplierRemittanceAdviceDataAreaType">
            <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 GetSupplierRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Get)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SupplierRemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSupplierRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SupplierRemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierShipmentSchedule.xsd"/>
  <xsd:element name="GetSupplierShipmentSchedule" type="GetSupplierShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Commonly, the ship schedule is generated by a material 
                                planning application and transmitted to an order or material planning application.
                                
                                The purpose of the GetSupplierShipmentSchedule is to enable a business applications module to request this 
                                SupplierShipmentSchedule information from another business application. The response to this BOD is 
                                ShowSupplierShipmentSchedule.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetSupplierShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetSupplierShipmentScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                                that the BOD message carries is provided, in this case 
                                                                GetSupplierShipmentSchedule. The information consists of a Verb and one or more 
                                                                Nouns. The verb (Get) indicates the action to be performed on the Noun 
                                                                (SupplierShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetSupplierShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="SupplierShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Tenant.xsd"/>
  <xsd:element name="GetTenant" type="GetTenantType">
    <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 GetAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Get) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetTenantType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetTenantDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetTenantDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Tenant" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetTradingPartner" type="GetTradingPartnerType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Get TradingPartner is to
                        Request a collection of TradingPartner nouns from the SOR.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetTradingPartnerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetTradingPartnerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the
                                                        information that the BOD message carries is provided, in this case
                                                        GetTradingPartner. The information consists of a Verb and one or more
                                                        Nouns. The verb (Get) indicates the action to be performed on the Noun
                                                        (TradingPartner).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetTradingPartnerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="TradingPartner" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetTransfer" type="GetTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Get Transfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetTransferDataAreaType">
            <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 GetTransfer. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Transfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="Transfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="GetTransportationRequisition" type="GetTransportationRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetTransportationRequisition Business Object Document is to Get receipt of the TransportationRequisition
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetTransportationRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetTransportationRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetTransportationRequisition. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (TransportationRequisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetTransportationRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="TransportationRequisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/UOMGroup.xsd"/>
  <xsd:element name="GetUOMGroup" type="GetUOMGroupType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the GetUOMGroup is to communicate to a business application component or module a request for an existingUOMGroup to be returned in a ShowUOMGroup.

There are many possible business applications in several environments that may use this capability.  For example, an MRP, Inventory, or Manufacturing business application could use this to request alternate UOM information for one or more items.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="GetUOMGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="GetUOMGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case GetUOMGroup. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (UOMGroup).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="GetUOMGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Get"/>
      <xsd:element ref="UOMGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadAdvanceShipNotice" type="LoadAdvanceShipNoticeType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load AdvanceShipNotice is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load AdvanceShipNotice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadAdvanceShipNoticeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadAdvanceShipNoticeDataAreaType">
            <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 LoadAdvanceShipNotice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (AdvanceShipNotice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadAdvanceShipNoticeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="AdvanceShipNotice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadCashReceipt" type="LoadCashReceiptType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load CashReceipt is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load CashReceipt allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadCashReceiptType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadCashReceiptDataAreaType">
            <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 LoadCashReceipt. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (CashReceipt).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadCashReceiptDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="CashReceipt" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadContactMaster" type="LoadContactMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load ContactMaster is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load ContactMaster allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadContactMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadContactMasterDataAreaType">
            <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 LoadContactMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (ContactMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadContactMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="ContactMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadInventoryConsumption" type="LoadInventoryConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load InventoryConsumption is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load InventoryConsumption allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadInventoryConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadInventoryConsumptionDataAreaType">
            <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 LoadInventoryConsumption. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadInventoryConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="InventoryConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadCurrencyExchangeRateMaster" type="LoadCurrencyExchangeRateMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load CurrencyExchangeRateMaster is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load CurrencyExchangeRateMaster allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadCurrencyExchangeRateMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadCurrencyExchangeRateMasterDataAreaType">
            <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 LoadCurrencyExchangeRateMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (CurrencyExchangeRateMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadCurrencyExchangeRateMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="CurrencyExchangeRateMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadCustomerReturn" type="LoadCustomerReturnType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load CustomerReturn is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load CustomerReturn allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadCustomerReturnType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadCustomerReturnDataAreaType">
            <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 LoadCustomerReturn. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (CustomerReturn).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadCustomerReturnDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="CustomerReturn" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="AcknowledgeEDITransport" type="AcknowledgeEDITransportType">
    <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 AcknowledgeEDITransport. The
                                information consists of a Verb and one or more Nouns. The verb Acknowledge indicates the action
                                to be performed on the Noun(EDITransport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeEDITransportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeEDITransportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeEDITransportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="EDITransport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadInventoryConsumption" type="LoadInventoryConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load InventoryConsumption is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load InventoryConsumption allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadInventoryConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadInventoryConsumptionDataAreaType">
            <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 LoadInventoryConsumption. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadInventoryConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="InventoryConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadInventoryCount" type="LoadInventoryCountType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load InventoryCount is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load InventoryCount allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadInventoryCountType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadInventoryCountDataAreaType">
            <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 LoadInventoryCount. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryCount).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadInventoryCountDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="InventoryCount" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadInvoice" type="LoadInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load Invoice is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load Invoice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadInvoiceDataAreaType">
            <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 LoadInvoice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (Invoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="Invoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadPlanningSchedule" type="LoadPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load PlanningSchedule is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load PlanningSchedule allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadPlanningScheduleDataAreaType">
            <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 LoadPlanningSchedule. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (PlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="PlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadPurchaseOrder" type="LoadPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load PurchaseOrder is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load PurchaseOrder allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadPurchaseOrderDataAreaType">
            <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 LoadPurchaseOrder. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadReceiveDelivery" type="LoadReceiveDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load ReceiveDelivery is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load ReceiveDelivery allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadReceiveDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadReceiveDeliveryDataAreaType">
            <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 LoadReceiveDelivery. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  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="LoadReceiveDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="ReceiveDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadRemittanceAdvice" type="LoadRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load RemittanceAdvice is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load RemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadRemittanceAdviceDataAreaType">
            <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 LoadRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (RemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="RemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadSalesOrder" type="LoadSalesOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load SalesOrder is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load SalesOrder allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadSalesOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadSalesOrderDataAreaType">
            <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 LoadSalesOrder. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SalesOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadSalesOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadSequenceSchedule" type="LoadSequenceScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load SequenceSchedule is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load SequenceSchedule allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadSequenceScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadSequenceScheduleDataAreaType">
            <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 LoadSequenceSchedule. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SequenceSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadSequenceScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="SequenceSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadShipment" type="LoadShipmentType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load Shipment is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load Shipment allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadShipmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadShipmentDataAreaType">
            <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 LoadShipment. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (Shipment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadShipmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="Shipment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadShipmentSchedule" type="LoadShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load ShipmentSchedule is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load ShipmentSchedule allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadShipmentScheduleDataAreaType">
            <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 LoadShipmentSchedule. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (ShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="ShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadSupplierPlanningSchedule" type="LoadSupplierPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Load SupplierPlanningSchedule 
                                is to to facilitate keeping Sales order information synchronized on separate data bases throughout an 
                                enterprise. The Load SupplierPlanningSchedule allows the adding of new Sales orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadSupplierPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadSupplierPlanningScheduleDataAreaType">
            <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 LoadSupplierPlanningSchedule. 
                                                          The information consists of a Verb and one or more Nouns. The verb (Load) indicates 
                                                          the action to be performed on the Noun (SupplierPlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadSupplierPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="SupplierPlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SupplierRMA.xsd"/>
  <xsd:element name="LoadSupplierRMA" type="LoadSupplierRMAType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load SupplierRMA is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load SupplierRMA allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadSupplierRMAType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadSupplierRMADataAreaType">
            <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 LoadSupplierRMA. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SupplierRMA).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadSupplierRMADataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="SupplierRMA" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadSupplierShipmentSchedule" type="LoadSupplierShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load SupplierShipmentSchedule is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load SupplierShipmentSchedule allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadSupplierShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadSupplierShipmentScheduleDataAreaType">
            <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 LoadSupplierShipmentSchedule. 
                                                          The information consists of a Verb and one or more Nouns. The verb (Load) indicates 
                                                          the action to be performed on the Noun (SupplierShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadSupplierShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="SupplierShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadTransfer" type="LoadTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Load Transfer is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Load Transfer allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadTransferDataAreaType">
            <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 LoadTransfer. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Load)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (Transfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="Transfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="LoadTransportationStatus" type="LoadTransportationStatusType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the LoadTransportationStatus Business Object Document is to acknowledge receipt of the TransportationStatus
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="LoadTransportationStatusType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="LoadTransportationStatusDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case LoadTransportationStatus. The information consists of a Verb and one or more Nouns. The verb (Load) indicates the action to be performed on the Noun (TransportationStatus).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="LoadTransportationStatusDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Load"/>
      <xsd:element ref="TransportationStatus" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/CostingActivity.xsd"/>
  <xsd:element name="PostCostingActivity" type="PostCostingActivityType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        In an effort to simpilify the usage of the verbs the PostCostingActivity BOD is being deprecated as of OAGIS 9.0, the PostCostingActivity will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS.  As such for all new development we recommend that you use the PostCostingActivity BOD which may serve the same function of the PostCostingActivity BOD.

The purpose of the PostCostingActivity BOD is to enable the update of Activityinformation from a production or manufacturing application to a costing application.  This is necessary for applications that are based on a Dual Cycle Accounting model.  This Dual Cycle Accounting model does not capture the details of the Activities that caused entries to be made in the general ledger application, but instead captures them in a separate overall costing application.
This BOD commonly causes updates to occur and may be used as part of a large integration scenario or as a single tool for updating data. 

For Single Cycle accounting systems, the PostJournalEntry BOD will be used to ensure that the costing information flows from the Manufacturing Application to the Financial Application.

In most cases either PostJournal or PostActivity will be used when the Financial applications are included with Logistics, but both Business Service Requests will not be used in the same integration scenario.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="PostCostingActivityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="PostCostingActivityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case PostCostingActivity. The information consists of a Verb and one or more Nouns. The verb (Post) indicates the action to be performed on the Noun (CostingActivity).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="PostCostingActivityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Post"/>
      <xsd:element ref="CostingActivity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="PostMatchDocument" type="PostMatchDocumentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The PostMatchDocument provides the ability to request an application/ system to create a MatchDocument
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="PostMatchDocumentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="PostMatchDocumentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case PostMatchDocument. The information consists of a Verb and one or more Nouns. The verb (Post) indicates the action to be performed on the Noun (MatchDocument).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="PostMatchDocumentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Post"/>
      <xsd:element ref="MatchDocument" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAccountingBookDefinition" type="ProcessAccountingBookDefinitionType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAccountingBookDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAccountingBookDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAccountingBookDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AccountingBookDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAccountingChart" type="ProcessAccountingChartType">
    <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 ProcessAccountingChart. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingChart).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAccountingChartType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAccountingChartDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAccountingChartDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AccountingChart" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAccountingEntity" type="ProcessAccountingEntityType">
    <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 ProcessAccountingEntity. The
                                information consists of a Verb and one or more Nouns. The verb Process indicates the action
                                to be performed on the Noun
                                (AccountingEntity).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAccountingEntityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAccountingEntityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAccountingEntityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AccountingEntity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAccountingJournal" type="ProcessAccountingJournalType">
    <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 ProcessAccountingJournal. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingJournal).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAccountingJournalType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAccountingJournalDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAccountingJournalDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AccountingJournal" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAdvanceShipNotice" type="ProcessAdvanceShipNoticeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessAdvanceShipNotice Business Object Document is to Process receipt of the AdvanceShipNotice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAdvanceShipNoticeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAdvanceShipNoticeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessAdvanceShipNotice. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (AdvanceShipNotice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAdvanceShipNoticeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AdvanceShipNotice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAssetFinancialLedger" type="ProcessAssetFinancialLedgerType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAssetFinancialLedgerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAssetFinancialLedgerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAssetFinancialLedgerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AssetFinancialLedger" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAssetMaster" type="ProcessAssetMasterType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessAssetMeterReading" type="ProcessAssetMeterReadingType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessAssetMeterReadingType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessAssetMeterReadingDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessAssetMeterReadingDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="AssetMeterReading" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessBillOfMaterials" type="ProcessBillOfMaterialsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SynBillOfMaterials is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Bill of Material.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessBillOfMaterialsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessBillOfMaterialsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessBillOfMaterials. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (BillOfMaterials).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessBillOfMaterialsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="BillOfMaterials" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessBillOfResources" type="ProcessBillOfResourcesType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process BillOfResources is to requet the system of record to
                                make a change to a BillOfResources object..
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessBillOfResourcesType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessBillOfResourcesDataAreaType">
            <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 ProcessBillOfResources. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (BillOfResources).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessBillOfResourcesDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="BillOfResources" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessBillToPartyMaster" type="ProcessBillToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process BillToPartyMaster is to request that a
                                Bill-to location be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessBillToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessBillToPartyMasterDataAreaType">
            <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
                                                  ProcessBillToPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (BillToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessBillToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="BillToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessBusinessPlan" type="ProcessBusinessPlanType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessBusinessPlanType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessBusinessPlanDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessBusinessPlanDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="BusinessPlan" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCalendar" type="ProcessCalendarType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Calendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCampaign" type="ProcessCampaignType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCampaignType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCampaignDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCampaignDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Campaign" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCarrierParty" type="ProcessCarrierPartyType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Process CarrierParty request a change to carrier information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCarrierPartyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCarrierPartyDataAreaType">
            <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
                                                  ProcessCarrierParty. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action
                                                  to be performed on the Noun
                                                  (CarrierParty).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCarrierPartyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CarrierParty" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCarrierRoute" type="ProcessCarrierRouteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessCarrierRoute is to enable an application to provide  Carrier Route information from another business application module.  The ProcessCarrierRoute is typiically provided in a publish/subscribe or broadcast environment. Where the sending system is the master application of the information being provided, where the information is sent to other business applications that need to know the information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCarrierRouteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCarrierRouteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessCarrierRoute. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (CarrierRoute).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCarrierRouteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CarrierRoute" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCashReceipt" type="ProcessCashReceiptType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessCashReceipt is to transmit an CashReceipt from a supplier to a customer. Indicating that the receiver of the CashReceipt is to Process the CashReceipt for payment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCashReceiptType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCashReceiptDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessCashReceipt. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (CashReceipt).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCashReceiptDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CashReceipt" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessChartOfAccounts" type="ProcessChartOfAccountsType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Process ChartOfAccounts is to request the creation or
                                modification of an account in the chart of accounts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessChartOfAccountsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessChartOfAccountsDataAreaType">
            <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 ProcessChartOfAccounts.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (ChartOfAccounts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessChartOfAccountsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ChartOfAccounts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessChartsOfAccountsMap" type="ProcessChartsOfAccountsMapType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Process ChartOfAccounts is to request the creation or
                                modification of mapping between the chart of accounts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessChartsOfAccountsMapType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessChartsOfAccountsMapDataAreaType">
            <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 ProcessChartsOfAccountsMap. The information consists of a Verb
                                                  and one or more Nouns. The verb(Process) indicates the action to be
                                                  performed on the Noun(ChartOfAccounts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessChartsOfAccountsMapDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ChartsOfAccountsMap" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCodeDefinition" type="ProcessCodeDefinitionType">
    <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 ProcessCode. The information consists of a Verb and one or
                                more Nouns. The verb Process) indicates the action to be
                                performed on the Noun (Code).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCodeDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCodeDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCodeDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CodeDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessConfiguredAssetMaster" type="ProcessConfiguredAssetMasterType">
    <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 ProcessConfiguredAssetMaster. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessConfiguredAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessConfiguredAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessConfiguredAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ConfiguredAssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessConstrainedResource" type="ProcessConstrainedResourceType">
    <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 ProcessConstrainedResource. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessConstrainedResourceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessConstrainedResourceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessConstrainedResourceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ConstrainedResource" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessContactMaster" type="ProcessContactMasterType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessContactMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessContactMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessContactMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ContactMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessContract" type="ProcessContractType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Contract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCurrency" type="ProcessCurrencyType">
    <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 ProcessCurrency. The information consists of a Verb and one or
                                more Nouns. The verb Process) indicates the action to be
                                performed on the Noun (Currency).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCurrencyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCurrencyDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCurrencyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Currency" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCurrencyExchangeRateMaster" type="ProcessCurrencyExchangeRateMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Process CurrencyExchangeRateMaster is to notify the requestor of a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCurrencyExchangeRateMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCurrencyExchangeRateMasterDataAreaType">
            <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 ProcessCurrencyExchangeRateMaster. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (CurrencyExchangeRateMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCurrencyExchangeRateMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CurrencyExchangeRateMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCurrencyRateType" type="ProcessCurrencyRateTypeType">
    <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 ProcessCurrencyRateType. The information consists of a Verb
                                and one or more Nouns. The verb Process) indicates the action to
                                be performed on the Noun (CurrencyRateType).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCurrencyRateTypeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCurrencyRateTypeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCurrencyRateTypeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CurrencyRateType" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCustomerCall" type="ProcessCustomerCallType">
    <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 ProcessCustomerCall. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCustomerCallType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCustomerCallDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCustomerCallDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CustomerCall" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCustomerPartyMaster" type="ProcessCustomerPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process CustomerPartyMaster is to request that a
                                customer be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCustomerPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCustomerPartyMasterDataAreaType">
            <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
                                                  ProcessCustomerPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (CustomerPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCustomerPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CustomerPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCustomerPurchaseOrder" type="ProcessCustomerPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the
                ProcessCustomerPurchaseOrder Business Object Document is to Process receipt of the Purchase
                Order and to reflect any changes. Commonly, the acknowledgment is generated by an
                order management application and transmitted to a purchasing or procurement application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCustomerPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCustomerPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is the place in which the information that the BOD message carries is provided. In this case ProcessCustomerPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (CustomerPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCustomerPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CustomerPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCustomerReturn" type="ProcessCustomerReturnType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessCustomerReturn provides the ability to request an application/ system to create a CustomerReturn
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCustomerReturnType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCustomerReturnDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessCustomerReturn. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (CustomerReturn).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCustomerReturnDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CustomerReturn" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessCustomerRFQ" type="ProcessCustomerRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessCustomerRFQ Business Object Document is to Process receipt of the CustomerRFQ
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessCustomerRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessCustomerRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessCustomerRFQ. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (CustomerRFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessCustomerRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="CustomerRFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessData" type="ProcessDataType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of Process Data is to deliver the concent of an EDI document
                                between the communications fortress and the translation fortress.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessDataType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessDataDataAreaType">
            <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 ProcessData. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (Data).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessDataDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Data" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessEDITransport" type="ProcessEDITransportType">
    <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 ProcessEDITransport. The
                                information consists of a Verb and one or more Nouns. The verb Process indicates the action
                                to be performed on the Noun(EDITransport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessEDITransportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessEDITransportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessEDITransportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="EDITransport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessEmployeeWorkTime" type="ProcessEmployeeWorkTimeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessEmployeeWorkTime is to Process work time information for an employee from a data collection application to an ERP Human Resource application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessEmployeeWorkTimeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessEmployeeWorkTimeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessEmployeeWorkTime. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (EmployeeWorkTime).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessEmployeeWorkTimeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="EmployeeWorkTime" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessExpenseReport" type="ProcessExpenseReportType">
    <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 ProcessExpenseReport. The
                                information consists of a Verb and one or more Nouns. The verb Process indicates the action
                                to be performed on the Noun
                                (ExpenseReport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessExpenseReportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessExpenseReportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessExpenseReportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ExpenseReport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessExtendLicenseUsage" type="ProcessExtendLicenseUsageType">
    <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 ProcessExtendLicenseUsage. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun (ExtendLicenseUsage).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessExtendLicenseUsageType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessExtendLicenseUsageDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessExtendLicenseUsageDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ExtendLicenseUsage" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessFinancialCalendar" type="ProcessFinancialCalendarType">
    <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 ProcessFinancialCalendar. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (FinancialCalendar).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessFinancialCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessFinancialCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessFinancialCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="FinancialCalendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessFinancialPartyMaster" type="ProcessFinancialPartyMasterType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessFinancialPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessFinancialPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessFinancialPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="FinancialPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessHandlingGroup" type="ProcessHandlingGroupType">
    <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 ProcessHandlingGroup. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (HandlingGroup).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessHandlingGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessHandlingGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessHandlingGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="HandlingGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessInspectDelivery" type="ProcessInspectDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessInspectDelivery is to supply InspectDelivery information for goods or services to another business application module.  This BOD may is initiated by the sending system upon some event occurring.  There are many possible business applications in several environments that may use this capability.

For example;
1.  A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 
2.  An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information.
3.  A Laboratory Information System could send quality information to an Inventory application,
4.  A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessInspectDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessInspectDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessInspectDelivery. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (InspectDelivery).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessInspectDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="InspectDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessInventoryAdjustment" type="ProcessInventoryAdjustmentType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Process InventoryAdjustment is to notify the
                                enterprise of the change to the hold status of an inventory item.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessInventoryAdjustmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessInventoryAdjustmentDataAreaType">
            <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 ProcessInventoryAdjustment. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Process)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryAdjustment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessInventoryAdjustmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="InventoryAdjustment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessInventoryBalance" type="ProcessInventoryBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ChangeInventoryBalance is to enable the communication of a Change in the InventoryBalance data that exists on separate Inventory databases.

This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure.  

This is data that describes the ITEM as it exists at a specific location. It is
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessInventoryBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessInventoryBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessInventoryBalance. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (InventoryBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessInventoryBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="InventoryBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessInventoryConsumption" type="ProcessInventoryConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessInventoryConsumption is to inform a seller or provider about InventoryConsumption of items.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessInventoryConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessInventoryConsumptionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessInventoryConsumption. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (InventoryConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessInventoryConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="InventoryConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessInventoryCount" type="ProcessInventoryCountType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessInventoryCount is to transmit an inventory count to ERP from the actual physical inventory location. This count may be a cycle count or a physical count.  This BOD may also apply to planned or unplanned inventory counts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessInventoryCountType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessInventoryCountDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessInventoryCount. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (InventoryCount).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessInventoryCountDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="InventoryCount" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessInventoryHold" type="ProcessInventoryHoldType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Process InventoryHold is to
                                request a change of a hold status.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessInventoryHoldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessInventoryHoldDataAreaType">
            <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 ProcessInventoryHold.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Process) indicates the action
                                                  to be performed on the Noun
                                                  (InventoryHold).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessInventoryHoldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="InventoryHold" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessInvoice" type="ProcessInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessInvoice is to transmit an invoice from a supplier to a customer. Indicating that the receiver of the Invoice is to Process the Invoice for payment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessInvoice. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Invoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Invoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessItemMaster" type="ProcessItemMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Process ItemMaster is to requested a change to an item object.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessItemMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessItemMasterDataAreaType">
            <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 ProcessItemMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (ItemMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessItemMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ItemMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessLocation" type="ProcessLocationType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process Location is to requet the system of record to
                                make a change to a location object..
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessLocationType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessLocationDataAreaType">
            <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 ProcessLocation. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (Location).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessLocationDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Location" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessMaintenanceOrder" type="ProcessMaintenanceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessMaintenanceOrder provides the ability to request an application/ system to create a MaintenanceOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessMaintenanceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessMaintenanceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessMaintenanceOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (MaintenanceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessMaintenanceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="MaintenanceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessMoveInventory" type="ProcessMoveInventoryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessMoveInventory is to give the organization the ability to do a quantity movement of materials from one organizational unit to another organizational unit.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessMoveInventoryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessMoveInventoryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessMoveInventory. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (MoveInventory).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessMoveInventoryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="MoveInventory" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessOpportunity" type="ProcessOpportunityType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The ProcessOpportunity is provided in a a publishe/subscribe or broadcast buiness exchange where an application other than the owner or the master of the given information provides it to the business applications that owns the data in order to have it process or perform a function with the information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessOpportunityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessOpportunityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessOpportunityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Opportunity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPayableTransaction" type="ProcessPayableTransactionType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPayableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPayableTransactionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPayableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="PayableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPayFromPartyMaster" type="ProcessPayFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process PayFromPartyMaster is to request that a
                                Pay-to location be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPayFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPayFromPartyMasterDataAreaType">
            <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
                                                  ProcessPayFromPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (PayFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPayFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="PayFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPerson" type="ProcessPersonType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPersonType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPersonDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPersonDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Person" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPersonnel" type="ProcessPersonnelType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessPersonnel is to enable the synchronization of employee data that exists on separate data bases between manufacturing and human resource applications.  The ProcessPersonnel allows the adding of new employees and their relevant data as well as the modification of previously established employees.

The ProcessPersonnel is used to facilitate the maintenance of human resource data in a manufacturing work force planning module.  This enables the workforce planning module to use current personnel information when creating finite production schedules.  The ProcessPersonnel can also be used by a project accounting application or a work order management application to assign qualified personnel or to perform resource planning.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPersonnelType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPersonnelDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessPersonnel. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Personnel).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPersonnelDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Personnel" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPing" type="ProcessPingType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process Ping is to request that an
                                account dimension be changed or created or a valid value for one of
                                the dimensions modified or created.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPingType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPingDataAreaType">
            <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 ProcessPing.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (Ping).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPingDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Ping" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPlannedProductionOrder" type="ProcessPlannedProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessPlannedProductionOrder provides the ability to request an application/ system to create a PlannedProductionOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPlannedProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPlannedProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessPlannedProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (PlannedProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPlannedProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="PlannedProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPlannedPurchaseOrder" type="ProcessPlannedPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessPlannedPurchaseOrder Business Object Document is to transmit a purchase order to a supplier's order management application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPlannedPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPlannedPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessPlannedPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (PlannedPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPlannedPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="PlannedPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPlannedTransfer" type="ProcessPlannedTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the ProcessPlannedTransfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPlannedTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPlannedTransferDataAreaType">
            <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 ProcessPlannedTransfer. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (PlannedTransfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPlannedTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="PlannedTransfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPlanningSchedule" type="ProcessPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process PlanningSchedule is to to request that
                                another system do some processing of the Planning Schedule. This
                                other system will often be an EDI system.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPlanningScheduleDataAreaType">
            <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 ProcessPlanningSchedule.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (PlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="PlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProductionOrder" type="ProcessProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessProductionOrder provides the ability to request an application/ system to create a ProductionOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProductionReceiver" type="ProcessProductionReceiverType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProductionReceiverType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProductionReceiverDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProductionReceiverDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProductionReceiver" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectBalance" type="ProcessProjectBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process ProjectBalance is to request that a
                                project be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectBalanceDataAreaType">
            <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 ProcessProjectBalance. The
                                                  information consists of a Verb and one or more Nouns. The verb
                                                  (Process) indicates the action to be performed on the Noun (ProjectBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectBid" type="ProcessProjectBidType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessProjectBid provides the ability to request an application/ system to create a ProjectBid
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectBidType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectBidDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessProjectBid. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ProjectBid).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectBidDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectBid" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectBudget" type="ProcessProjectBudgetType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessProjectBudget provides the ability to request an application/ system to create a ProjectBudget
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectBudgetType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectBudgetDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessProjectBudget. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ProjectBudget).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectBudgetDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectBudget" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectCosts" type="ProcessProjectCostsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessProjectCosts provides the ability to request an application/ system to create a ProjectCosts
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectCostsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectCostsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessProjectCosts. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ProjectCosts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectCostsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectCosts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectEstimate" type="ProcessProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessProjectEstimate provides the ability to request an application/ system to create a ProjectEstimate
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectEstimate" type="ProcessProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessProjectEstimate provides the ability to request an application/ system to create a ProjectEstimate
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectMaster" type="ProcessProjectMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process ProjectMaster is to request that a
                                project be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectMasterDataAreaType">
            <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 ProcessProjectMaster. The
                                                  information consists of a Verb and one or more Nouns. The verb
                                                  (Process) indicates the action to be performed on the Noun (ProjectMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectPeriodBalance" type="ProcessProjectPeriodBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process ProjectPeriodBalance is to request that a
                                project be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectPeriodBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectPeriodBalanceDataAreaType">
            <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 ProcessProjectPeriodBalance. The
                                                  information consists of a Verb and one or more Nouns. The verb
                                                  (Process) indicates the action to be performed on the Noun (ProjectPeriodBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectPeriodBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectPeriodBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessProjectRevenue" type="ProcessProjectRevenueType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessProjectRevenue provides the ability to request an application/ system to create a ProjectRevenue
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessProjectRevenueType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessProjectRevenueDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessProjectRevenue. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ProjectRevenue).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessProjectRevenueDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ProjectRevenue" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessPurchaseOrder" type="ProcessPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Process PurchaseOrder Business Object Document is to transmit a purchase order to a supplier's order management application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessQuote" type="ProcessQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessQuote provides the ability to request an application/ system to create a Quote
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessQuote. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Quote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Quote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessReceivableTransaction" type="ProcessReceivableTransactionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process Receivable is to request that changes made
                                to a receivable or a new receivable be created.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessReceivableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessReceivableTransactionDataAreaType">
            <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 ProcessReceivable. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (Receivable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessReceivableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ReceivableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessReceiveDelivery" type="ProcessReceiveDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessReceiveDelivery provides the ability to request an application/ system to create a ReceiveDelivery
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessReceiveDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessReceiveDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessReceiveDelivery. The information consists of a Verb and one or more Nouns. The verb (Process) 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="ProcessReceiveDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ReceiveDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessRemittanceAdvice" type="ProcessRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process RemittanceAdvice is to to facilitate keeping Sales
                                order information Processhronized on separate data bases throughout an
                                enterprise. The Process RemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessRemittanceAdviceDataAreaType">
            <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 ProcessRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Process)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (RemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="RemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessRemitToPartyMaster" type="ProcessRemitToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process RemitToPartyMaster is to request that a
                                Ship-to location be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessRemitToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessRemitToPartyMasterDataAreaType">
            <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
                                                  ProcessRemitToPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (RemitToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessRemitToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="RemitToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessRequisition" type="ProcessRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessRequisition provides the ability to request an application/ system to create a Requisition
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessRequisition. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Requisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Requisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessRFQ" type="ProcessRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessRFQ provides the ability to request an application/ system to create a RFQ
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessRFQ. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (RFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="RFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSalesOrder" type="ProcessSalesOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessSalesOrder provides the ability to request an application/ system to create a SalesOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSalesOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSalesOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessSalesOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (SalesOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSalesOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessServiceConsumption" type="ProcessServiceConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process ServiceConsumption is to notify the entire
                                enterprise of any services or associated items that have been
                                received directly ourside of the warehouse.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessServiceConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessServiceConsumptionDataAreaType">
            <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 ProcessServiceConsumption.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (ServiceConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessServiceConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ServiceConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessServiceContract" type="ProcessServiceContractType">
    <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 ProcessServiceContract. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessServiceContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessServiceContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessServiceContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ServiceContract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessServiceOrder" type="ProcessServiceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessServiceOrder provides the ability to request an application/ system to create a ServiceOrder
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessServiceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessServiceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessServiceOrder. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (ServiceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessServiceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ServiceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessShipFromPartyMaster" type="ProcessShipFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process ShipFromPartyMaster is to request that a
                                Ship-to location be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessShipFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessShipFromPartyMasterDataAreaType">
            <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
                                                  ProcessShipFromPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (ShipFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessShipFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ShipFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessShipment" type="ProcessShipmentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessShipment provides the ability to request an application/ system to create a Shipment
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessShipmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessShipmentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessShipment. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Shipment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessShipmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Shipment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessShipToPartyMaster" type="ProcessShipToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process ShipToPartyMaster is to request that a
                                Ship-to location be created or modified in the MDM.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessShipToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessShipToPartyMasterDataAreaType">
            <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
                                                  ProcessShipToPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (ShipToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessShipToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="ShipToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSourceSystemJournalEntry" type="ProcessSourceSystemJournalEntryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose
                                of the ProcessJournalEntry is to enable an application or
                                component to respond to a ProcessSourceSystemJournalEntry. The
                                response to the ProcessSourceSystemJournalEntry is the response
                                to the ProcessSourceSystemJournalEntry.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSourceSystemJournalEntryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSourceSystemJournalEntryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the
                                                  BOD message carries is provided, in
                                                  this case ProcessJournalEntry.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Process) indicates the action
                                                  to be performed on the Noun
                                                  (JournalEntry). In response to the
                                                  PostJournalEntry.
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSourceSystemJournalEntryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SourceSystemJournalEntry" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSupplierBalance" type="ProcessSupplierBalanceType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSupplierBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSupplierBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSupplierBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SupplierBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSupplierInvoice" type="ProcessSupplierInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessSupplierInvoice Business Object Document is to Process receipt of the SupplierInvoice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSupplierInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSupplierInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessSupplierInvoice. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (SupplierInvoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSupplierInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SupplierInvoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSupplierPartyMaster" type="ProcessSupplierPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process SupplierPartyMaster is to request that the
                                SOR change some data.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSupplierPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSupplierPartyMasterDataAreaType">
            <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
                                                  ProcessSupplierPartyMaster. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Process) indicates the action to be
                                                  performed on the Noun
                                                  (SupplierPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSupplierPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SupplierPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSupplierPlanningSchedule" type="ProcessSupplierPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Process SupplierPlanningSchedule 
                                is to to request that another system do some processing of the Planning Schedule. This other system will 
                                often be an EDI system.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSupplierPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSupplierPlanningScheduleDataAreaType">
            <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 ProcessSupplierPlanningSchedule. 
                                                          The information consists of a Verb and one or more Nouns. The verb (Process) indicates 
                                                          the action to be performed on the Noun (SupplierPlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSupplierPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SupplierPlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSupplierQuote" type="ProcessSupplierQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessSupplierQuote Business Object Document is to Process receipt of the SupplierQuote
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSupplierQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSupplierQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessSupplierQuote. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (SupplierQuote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSupplierQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SupplierQuote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessSupplierRemittanceAdvice" type="ProcessSupplierRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Process SupplierRemittanceAdvice is to to facilitate keeping Sales
                                order information Processhronized on separate data bases throughout an
                                enterprise. The Process SupplierRemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessSupplierRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessSupplierRemittanceAdviceDataAreaType">
            <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 ProcessSupplierRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Process)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SupplierRemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessSupplierRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="SupplierRemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessTextMessage" type="ProcessTextMessageType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        Is where
                                the information that the TextMessage message carries is provided, in this
                                case ProcessTextMessage. The information consists of a Verb and one or more
                                Nouns. The verb Process indicates the action to be performed on the
                                Noun(TextMessage).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessTextMessageType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessTextMessageDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessTextMessageDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="TextMessage" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessTradingPartner" type="ProcessTradingPartnerType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Sync TradingPartner is to
                        requested a change to an item object.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessTradingPartnerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessTradingPartnerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the
                                                        information that the BOD message carries is provided, in this case
                                                        ProcessTradingPartner. The information consists of a Verb and one or more Nouns.
                                                        The verb (Process) indicates the action to be performed on the Noun (TradingPartner).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessTradingPartnerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="TradingPartner" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessTransfer" type="ProcessTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Process Transfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessTransferDataAreaType">
            <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 ProcessTransfer. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (Transfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Transfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessTransportationRequisition" type="ProcessTransportationRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ProcessTransportationRequisition Business Object Document is to Process receipt of the TransportationRequisition
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessTransportationRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessTransportationRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessTransportationRequisition. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (TransportationRequisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessTransportationRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="TransportationRequisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessTransportationStatus" type="ProcessTransportationStatusType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ProcessTransportationStatus provides the ability to request an application/ system to create a TransportationStatus
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessTransportationStatusType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessTransportationStatusDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ProcessTransportationStatus. The information consists of a Verb and one or more Nouns. The verb (Process) indicates the action to be performed on the Noun (TransportationStatus).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessTransportationStatusDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="TransportationStatus" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ProcessWorkflow" type="ProcessWorkflowType">
    <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 ProcessAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Process) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ProcessWorkflowType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ProcessWorkflowDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ProcessWorkflowDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Process"/>
      <xsd:element ref="Workflow" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowAccountingBookDefinition" type="ShowAccountingBookDefinitionType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowAccountingBookDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowAccountingBookDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowAccountingBookDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="AccountingBookDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowAccountingChart" type="ShowAccountingChartType">
    <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 ShowAccountingChart. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingChart).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowAccountingChartType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowAccountingChartDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowAccountingChartDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="AccountingChart" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowAccountingEntity" type="ShowAccountingEntityType">
    <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 ShowAccountingEntity. The
                                information consists of a Verb and one or more Nouns. The verb Show indicates the action
                                to be performed on the Noun
                                (AccountingEntity).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowAccountingEntityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowAccountingEntityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowAccountingEntityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="AccountingEntity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowAccountingJournal" type="ShowAccountingJournalType">
    <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 ShowAccountingJournal. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingJournal).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowAccountingJournalType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowAccountingJournalDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowAccountingJournalDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="AccountingJournal" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowAdvanceShipNotice" type="ShowAdvanceShipNoticeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowAdvanceShipNotice Business Object Document is to Show receipt of the AdvanceShipNotice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowAdvanceShipNoticeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowAdvanceShipNoticeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowAdvanceShipNotice. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (AdvanceShipNotice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowAdvanceShipNoticeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="AdvanceShipNotice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowAssetMaster" type="ShowAssetMasterType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="AssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowAssetMeterReading" type="ShowAssetMeterReadingType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowAssetMeterReadingType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowAssetMeterReadingDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowAssetMeterReadingDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="AssetMeterReading" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowBillOfMaterials" type="ShowBillOfMaterialsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SynBillOfMaterials is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Bill of Material.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowBillOfMaterialsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowBillOfMaterialsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowBillOfMaterials. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (BillOfMaterials).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowBillOfMaterialsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="BillOfMaterials" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowBillOfResources" type="ShowBillOfResourcesType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowBillOfResources is to supply Item Bill of Material information to another business application module.  This BOD may also be initiated by the sending system upon some event occurring.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate Item Bill of Material information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowBillOfResourcesType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowBillOfResourcesDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowBillOfResources. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (BillOfResources).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowBillOfResourcesDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="BillOfResources" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowBillToPartyMaster" type="ShowBillToPartyMasterType"/>
  <xsd:complexType name="ShowBillToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowBillToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowBillToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (BillToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowBillToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="BillToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowBusinessPlan" type="ShowBusinessPlanType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowBusinessPlanType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowBusinessPlanDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowBusinessPlanDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="BusinessPlan" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCalendar" type="ShowCalendarType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Calendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCampaign" type="ShowCampaignType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCampaignType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCampaignDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCampaignDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Campaign" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCarrierParty" type="ShowCarrierPartyType"/>
  <xsd:complexType name="ShowCarrierPartyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCarrierPartyDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided,
                                                        in this case ShowCarrierParty. The information consists of a Verb and
                                                        one or more Nouns. The verb (Show) indicates the action to be performed
                                                        on the Noun (CarrierParty).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCarrierPartyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CarrierParty" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCarrierRoute" type="ShowCarrierRouteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowCarrierRoute is to enable an application to provide a specific Carrier Route information from another business application module.  The response to the GetCarrierRoute is the ShowCarrierRoute.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCarrierRouteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCarrierRouteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowCarrierRoute. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (CarrierRoute).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCarrierRouteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CarrierRoute" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCashReceipt" type="ShowCashReceiptType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowCashReceipt is to transmit an CashReceipt from a supplier to a customer. This BOD may be used as a response to a GetCashReceipt request or as a push notification of an event
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCashReceiptType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCashReceiptDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowCashReceipt. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (CashReceipt).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCashReceiptDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CashReceipt" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowChartOfAccounts" type="ShowChartOfAccountsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowChartOfAccounts is to supply ChartOfAccounts information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowChartOfAccountsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowChartOfAccountsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowChartOfAccounts. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ChartOfAccounts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowChartOfAccountsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ChartOfAccounts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowChartsOfAccountsMap" type="ShowChartsOfAccountsMapType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowChartsOfAccountsMap is to distribute general ledger chart of accounts code identifiers to other applications to store for validation purposes.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowChartsOfAccountsMapType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowChartsOfAccountsMapDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowChartsOfAccountsMap. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ChartsOfAccountsMap).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowChartsOfAccountsMapDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ChartsOfAccountsMap" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCodeDefinition" type="ShowCodeDefinitionType">
    <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 ShowCode. The information consists of a Verb and one or
                                more Nouns. The verb Show) indicates the action to be
                                performed on the Noun (Code).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCodeDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCodeDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCodeDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CodeDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowConfiguredAssetMaster" type="ShowConfiguredAssetMasterType">
    <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 ShowConfiguredAssetMaster. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowConfiguredAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowConfiguredAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowConfiguredAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ConfiguredAssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowConstrainedResource" type="ShowConstrainedResourceType">
    <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 ShowConstrainedResource. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowConstrainedResourceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowConstrainedResourceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowConstrainedResourceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ConstrainedResource" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowContactMaster" type="ShowContactMasterType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowContactMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowContactMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowContactMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ContactMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowContract" type="ShowContractType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Contract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCurrency" type="ShowCurrencyType">
    <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 ShowCurrency. The information consists of a Verb and one or
                                more Nouns. The verb Show) indicates the action to be
                                performed on the Noun (Currency).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCurrencyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCurrencyDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCurrencyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Currency" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCurrencyExchangeRateMaster" type="ShowCurrencyExchangeRateMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowCurrencyExchangeRateMaster is to supply CurrencyExchangeRateTypeMaster information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCurrencyExchangeRateMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCurrencyExchangeRateMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowCurrencyExchangeRateTypeMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (CurrencyExchangeRateTypeMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCurrencyExchangeRateMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CurrencyExchangeRateMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCurrencyRateType" type="ShowCurrencyRateTypeType">
    <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 ShowCurrencyRateType. The information consists of a Verb
                                and one or more Nouns. The verb Show) indicates the action to
                                be performed on the Noun (CurrencyRateType).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCurrencyRateTypeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCurrencyRateTypeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCurrencyRateTypeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CurrencyRateType" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCustomerCall" type="ShowCustomerCallType">
    <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 ShowCustomerCall. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCustomerCallType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCustomerCallDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCustomerCallDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CustomerCall" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCustomerPartyMaster" type="ShowCustomerPartyMasterType"/>
  <xsd:complexType name="ShowCustomerPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCustomerPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowCustomerPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (CustomerPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCustomerPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CustomerPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCustomerPurchaseOrder" type="ShowCustomerPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the
                ShowCustomerPurchaseOrder Business Object Document is to Show receipt of the Purchase
                Order and to reflect any changes. Commonly, the acknowledgment is generated by an
                order management application and transmitted to a purchasing or procurement application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCustomerPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCustomerPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is the place in which the information that the BOD message carries is provided. In this case ShowCustomerPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (CustomerPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCustomerPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CustomerPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowCustomerRFQ" type="ShowCustomerRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowCustomerRFQ Business Object Document is to Show receipt of the CustomerRFQ
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowCustomerRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowCustomerRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowCustomerRFQ. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (CustomerRFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowCustomerRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="CustomerRFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowEmployeeWorkSchedule" type="ShowEmployeeWorkScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowEmployeeWorkSchedule is to supply EmployeeWorkSchedule information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowEmployeeWorkScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowEmployeeWorkScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowEmployeeWorkSchedule. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (EmployeeWorkSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowEmployeeWorkScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="EmployeeWorkSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowEmployeeWorkTime" type="ShowEmployeeWorkTimeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowEmployeeWorkTime is to supply EmployeeWorkTime information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowEmployeeWorkTimeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowEmployeeWorkTimeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowEmployeeWorkTime. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (EmployeeWorkTime).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowEmployeeWorkTimeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="EmployeeWorkTime" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowExpenseReport" type="ShowExpenseReportType">
    <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 ShowExpenseReport. The
                                information consists of a Verb and one or more Nouns. The verb Show indicates the action
                                to be performed on the Noun
                                (ExpenseReport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowExpenseReportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowExpenseReportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowExpenseReportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ExpenseReport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowField" type="ShowFieldType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show Field is to notify the requestor if a change
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowFieldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowFieldDataAreaType">
            <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 ShowField. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Show) indicates the action to be
                                                  performed on the Noun
                                                  (Field).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowFieldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Field" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowFinancialCalendar" type="ShowFinancialCalendarType">
    <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 ShowFinancialCalendar. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (FinancialCalendar).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowFinancialCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowFinancialCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowFinancialCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="FinancialCalendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowFinancialPartyMaster" type="ShowFinancialPartyMasterType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowFinancialPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowFinancialPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowFinancialPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="FinancialPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowGLMovement" type="ShowGLMovementType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show GLMovement return period balance/movement
                                to the requesting system.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowGLMovementType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowGLMovementDataAreaType">
            <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 ShowGLMovement. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Show)
                                                  indicates the action to be performed
                                                  on the Noun(GLMovement).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowGLMovementDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="GLMovement" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowHandlingGroup" type="ShowHandlingGroupType">
    <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 ShowHandlingGroup. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (HandlingGroup).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowHandlingGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowHandlingGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowHandlingGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="HandlingGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowInspectDelivery" type="ShowInspectDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowInspectDelivery is to supply InspectDelivery information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowInspectDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowInspectDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowInspectDelivery. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (InspectDelivery).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowInspectDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="InspectDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowInventoryAdjustment" type="ShowInventoryAdjustmentType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show InventoryAdjustment allow adjustments to be
                                retrieved to initialize another system that uses them.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowInventoryAdjustmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowInventoryAdjustmentDataAreaType">
            <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 ShowInventoryAdjustment.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Show) indicates the action to be
                                                  performed on the Noun
                                                  (InventoryAdjustment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowInventoryAdjustmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="InventoryAdjustment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowInventoryBalance" type="ShowInventoryBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowInventoryBalance is to supply InventoryBalance information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowInventoryBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowInventoryBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowInventoryBalance. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (InventoryBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowInventoryBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="InventoryBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowInventoryConsumption" type="ShowInventoryConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The most common use of the ShowInventoryConsumption is to share a buyer's usage information about an item or product with the supplier of such item or product.  This BOD will not create or update either buyer's or supplier's inventory records.   The receiver of the request is responsible to make effective use of this information.

The BOD can be used in the following ways: 
(1)  for a buyer of goods to inform the supplier that goods have been consumed, and replenishment will likely be required; 
(2)  for a retailer to inform the vendor that retail sales of goods have been made; and 
(3)  for plant data collection systems and warehouse management systems to inform inventory systems that goods have been consumed and inventory records should be adjusted accordingly.

This is an outline of the business flow that this BOD supports:
(1)  Overall purchase, replenishment or vendor managed inventory agreement is in place.
(2)  Message is sent to supplier, distributor or third party logistics provider, that material has been consumed.  This is done in response to events such as these, depending on implementation context:
  �  Material is replenished to line side at manufacturing facitliy.
  �  Material is assembled into final product.
  �  Material is purchased and removed from facility by customer.
(3)  Supplier, distributor, third party logistics provider replenishes material, using information provided in the ShowInventoryConsumption message, the demand and shipment forecasts, and the terms of the overall purchase or vendor managed inventory agreement.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowInventoryConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowInventoryConsumptionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowInventoryConsumption. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (InventoryConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowInventoryConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="InventoryConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowInventoryCount" type="ShowInventoryCountType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowInventoryCount is to response to the Get request an occurrences of a Inventory Count information from an ERP system. This count may be a cycle count or a physical count.  This BOD may also apply to planned or unplanned inventory counts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowInventoryCountType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowInventoryCountDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowInventoryCount. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (InventoryCount).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowInventoryCountDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="InventoryCount" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowInventoryHold" type="ShowInventoryHoldType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Show InventoryHold is to
                                return the hold information for inventory items.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowInventoryHoldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowInventoryHoldDataAreaType">
            <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 ShowInventoryHold.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Show) indicates the action
                                                  to be performed on the Noun
                                                  (InventoryHold).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowInventoryHoldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="InventoryHold" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowInvoice" type="ShowInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowInvoice is to transmit an invoice from a supplier to a customer. This BOD may be used as a response to a GetInvoice request or as a push notification of an event
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowInvoice. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Invoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Invoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowItemMaster" type="ShowItemMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowItemMaster is to supply ITEM Information to another business application module.  This request may be used as a response to a GetItemMaster request or as the result of some other business event.  This BOD does not usually cause updates to occur.

There are many possible business applications in several environments that may use this capability.  For example, an MRP, Inventory, or Manufacturing business application could use this to request item information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowItemMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowItemMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowItemMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ItemMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowItemMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ItemMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowLocation" type="ShowLocationType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowLocation is to supply Location information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowLocationType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowLocationDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowLocation. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Location).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowLocationDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Location" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowLocationService" type="ShowLocationServiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of  ShowLocationService is to enable a mechanism to ensure that the physical locations owned by the business applications are validated, geocoded, and standardized based on information returned by location service providers.

This BOD may be initiated by the sending system upon some event occurring, such as receiving a request submitted by another system for certain location service.

There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to receive processed location information from location service providers.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowLocationServiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of  ReceiveLocationService is to enable a mechanism to ensure that the physical location owned by the business applications are validated, geocoded, and standardized by the location service providers.                                                                       This BOD may also be initiated by the service provider in response to receiving a request for a particular service such as geocoding, address validation, etc.                                                                                      There are many possible business applications in several environments that may use this capability. For example, the customer management, the supplier management, or HRMS business applications could use this to communicate Location information to location service providers.
      </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowLocationServiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ReceiveLocationService.                                             The information consists of a Verb and one or more Nouns. The verb (Receive) indicates the action to be performed on the Noun (LocationService).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowLocationServiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="LocationService" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowMaintenanceOrder" type="ShowMaintenanceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowMaintenanceOrder is to communicate to a business application module or system the sending systems representation of maintenance order information.  This request may be used as a response to a GetMaintenanceOrder request or as a push notification of an event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowMaintenanceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowMaintenanceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowMaintenanceOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (MaintenanceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowMaintenanceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="MaintenanceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowMatchDocument" type="ShowMatchDocumentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        In certain application suites, purchase order / invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application.

The invoice matching process may include several document types, including the following:

Two way match - Purchase Order and the Invoice 

Three way match - Purchase Order, Invoice, and the Receipt 

Four way match - Purchase Order, Invoice, Receipt, and Inspection results 

For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching.

When matching takes place in the purchasing application, the accounts payable application may have to inform the purchasing application of the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched if the invoice is initially entered into the accounts payable application. Note that in some situations, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters.

When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. 

These integration scenarios have been developed for document matching to occur at the line level within the PurchaseOrder document and the Invoice document.  This may be a one to one relationship, or it may be a many to one relationship from Invoice to PurchaseOrder or from the PurchaseOrder to the Invoice.  Charges not associated with a specific Invoice line match be matched individually.

The purpose of the ShowMatchDocument is to enable the accounts payable application and the purchasing application to exchange information required either by request or initiated by some business event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowMatchDocumentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowMatchDocumentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowMatchDocument. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (MatchDocument).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowMatchDocumentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="MatchDocument" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowMoveInventory" type="ShowMoveInventoryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowMoveInventory is to enable an application or component to request an MoveInventory document from another business application or component.

The response to the ShowMoveInventory is is the ListMoveInventory. The ShowMoveInventory also enables the retrieval of information across several documents by using selection fields.    This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowMoveInventoryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowMoveInventoryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowLocation. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (MoveInventory).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowMoveInventoryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="MoveInventory" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowOpportunity" type="ShowOpportunityType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The response to the GetOpportunity is the ShowOpportunity.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowOpportunityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowOpportunityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowOpportunityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Opportunity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPayable" type="ShowPayableType"/>
  <xsd:complexType name="ShowPayableType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPayableDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPayable. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Payable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPayableDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Payable" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPayableTransaction" type="ShowPayableTransactionType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPayableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPayableTransactionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPayableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PayableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPayFromPartyMaster" type="ShowPayFromPartyMasterType"/>
  <xsd:complexType name="ShowPayFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPayFromPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPayFromPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PayFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPayFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PayFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPerson" type="ShowPersonType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPersonType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPersonDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPersonDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Person" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPersonnel" type="ShowPersonnelType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowPersonnel is to provide Personnel data for a worker to a requesting business application.  This BOD may be in response to a GetPersonnel request, or it may be triggered by a business event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPersonnelType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPersonnelDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPersonnel. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Personnel).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPersonnelDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Personnel" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPlannedProductionOrder" type="ShowPlannedProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowPlannedProductionOrder is to supply PlannedProductionOrder information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPlannedProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPlannedProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPlannedProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PlannedProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPlannedProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PlannedProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPlannedPurchaseOrder" type="ShowPlannedPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowPlannedPurchaseOrder is to supply Purchase Order Information to another business application module.  This request may be used as a response to a Get PlannedPurchaseOrder request or as a push notification of an event.

There are many possible business applications in several environments that may use this capability.  Examples include:

1. A Order Management application could use this BOD to send information to a Plant Data Collection application.

2. An MRP, Inventory or Manufacturing business application could use this to obtain order information.

3. The Order Management application can notify the MRP/Inventory application when a vendor gives or changes a promise day.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPlannedPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPlannedPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPlannedPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PlannedPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPlannedPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PlannedPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPlannedTransfer" type="ShowPlannedTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the ShowPlannedTransfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPlannedTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPlannedTransferDataAreaType">
            <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 ShowPlannedTransfer. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PlannedTransfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPlannedTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PlannedTransfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPlanningSchedule" type="ShowPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party.  Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional Data Type PlanningScheduleException.

Customers can use this PlanningSchedule to communicate demand requirement in three different ways.  It can be as specific as the Item level or at the Commodity code level, which is higher than item.  Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValues.

The purpose of the ShowPlanningSchedule is to communicate to a business application module or system the sending systems representation of PlanningSchedule information.  This request may be used as a response to a GetPlanningSchedule request or as a push notification of an event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPlanningScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPlanningSchedule. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPriceList" type="ShowPriceListType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowPriceList is to supply a business application module or system with information concerning new or existing product price lists.
This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, a Manufacturing, distributor or reseller business application could use this to communicate the price change or request a price list.

It may also be necessary to support Component Supplier Management (CSM) scenarios.  In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog.  A customer purchases the product from the Catalog provider.  They have the capability to do comparison shopping from the catalog.  Supplier Certification may be provided by the Catalog provider.

This definition of price list is intended to support simple pricing scenario, especially pricing that may accompany a published price list.  It is not intended to support complex pricing environments that may be needed to support features such as;
�	Deals and Promotions
�	Coupons and Sales Incentives
�	Rebates and Accruals

This functionality will be addressed in a subsequent release.  It is a working assumption that the representation of complex qualifications, coupons and sales incentives are rarely communicated between systems.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPriceListType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPriceListDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPriceList. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PriceList).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPriceListDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PriceList" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProductionOrder" type="ShowProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowProductionOrder is to supply Production Order information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProductionReceiver" type="ShowProductionReceiverType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProductionReceiverType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProductionReceiverDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProductionReceiverDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProductionReceiver" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectBalance" type="ShowProjectBalanceType"/>
  <xsd:complexType name="ShowProjectBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectBalance. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectBid" type="ShowProjectBidType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowProjectBid is to communicate to a business application module or system the sending systems representation of ProjectBid information.  This request may be used as a response to a GetProjectBid request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProjectBidType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectBidDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectBid. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectBid).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectBidDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectBid" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectBudget" type="ShowProjectBudgetType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowProjectBudget is to communicate to a business application module or system the sending systems representation of ProjectBudget information.  This request may be used as a response to a GetProjectBudget request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProjectBudgetType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectBudgetDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectBudget. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectBudget).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectBudgetDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectBudget" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectCosts" type="ShowProjectCostsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowProjectCosts is to communicate to a business application module or system the sending systems representation of ProjectCosts information.  This request may be used as a response to a GetProjectCosts request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProjectCostsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectCostsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectCosts. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectCosts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectCostsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectCosts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectEstimate" type="ShowProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowProjectEstimate is to communicate to a business application module or system the sending systems representation of ProjectEstimate information.  This request may be used as a response to a ShowProjectEstimate request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectEstimate" type="ShowProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowProjectEstimate is to communicate to a business application module or system the sending systems representation of ProjectEstimate information.  This request may be used as a response to a GetProjectEstimate request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectMaster" type="ShowProjectMasterType"/>
  <xsd:complexType name="ShowProjectMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectPeriodBalance" type="ShowProjectPeriodBalanceType"/>
  <xsd:complexType name="ShowProjectPeriodBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectPeriodBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectPeriodBalance. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectPeriodBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectPeriodBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectPeriodBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowProjectRevenue" type="ShowProjectRevenueType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowProjectRevenue is to communicate to a business application module or system the sending systems representation of ProjectRevenue information.  This request may be used as a response to a GetProjectRevenue request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowProjectRevenueType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowProjectRevenueDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowProjectRevenue. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ProjectRevenue).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowProjectRevenueDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ProjectRevenue" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowPurchaseOrder" type="ShowPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Show PurchaseOrder is to supply Purchase Order Information to another business application module.  This request may be used as a response to a Get PurchaseOrder request or as a push notification of an event.

There are many possible business applications in several environments that may use this capability.  Examples include:

1. A Order Management application could use this BOD to send information to a Plant Data Collection application.

2. An MRP, Inventory or Manufacturing business application could use this to obtain order information.

3. The Order Management application can notify the MRP/Inventory application when a vendor gives or changes a promise day.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowQuote" type="ShowQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowQuote is to communicate to a business application module or system the sending systems representation of Quote information.  This request may be used as a response to a GetQuote request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowQuote. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Quote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Quote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowReceivable" type="ShowReceivableType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowReceivable is to supply Receivable information to another business application module.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowReceivableType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowReceivableDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowReceivable. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Receivable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowReceivableDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Receivable" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowReceivableTransaction" type="ShowReceivableTransactionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show Receivable is to return the collection of
                                receivable balances.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowReceivableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowReceivableTransactionDataAreaType">
            <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 ShowReceivable. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Show)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (Receivable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowReceivableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ReceivableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowReceiveDelivery" type="ShowReceiveDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The ShowReceiveDelivery may be used to obtain information about a specific expected (unreceived) or previously received goods delivery.   The ShowReceiveDelivery may be issued in response to a GetReceiveDelivery request, or emitted asynchronously for notification upon some business event.

For expected deliveries, the ShowReceiveDelivery document content may act as a receiving template or checklist to identify the quantity and shipping configuration of the expected goods.  In this manner the ShowReceiveDelivery may be considered logically equivalent to the Advance Ship Notice information in a ShowShipment document.   This similarity is by design, as the receiver's ShowReceiveDelivery may be directly derived from shipper's ShowShipment content after the receiver's business logic has appropriately validated the Advance Ship Notification information.

The ShowReceiveDelivery supports describing shipment content 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="ShowReceiveDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowReceiveDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowReceiveDelivery. The information consists of a Verb and one or more Nouns. The verb (Show) 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="ShowReceiveDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ReceiveDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowRemittanceAdvice" type="ShowRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show RemittanceAdvice is to to facilitate keeping Sales
                                order information Showhronized on separate data bases throughout an
                                enterprise. The Show RemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowRemittanceAdviceDataAreaType">
            <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 ShowRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Show)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (RemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="RemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowRemitToPartyMaster" type="ShowRemitToPartyMasterType"/>
  <xsd:complexType name="ShowRemitToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowRemitToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowRemitToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (RemitToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowRemitToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="RemitToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowRequisition" type="ShowRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowRequisition is to send information relative to demand for goods or services to another business application.  This may be in response to a GetRequisition request, or it may be a notification vehicle, initiated upon an event in a business application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowRequisition. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Requisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Requisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowRFQ" type="ShowRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowRFQ is to communicate to a business application module or system the sending systems representation of Request for Quote information.  This request may be used as a response to a GetRFQ request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowRFQ. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (RFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="RFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSalesOrder" type="ShowSalesOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Show SalesOrder is to supply Sales Order Information to another business application module.  This request may be used as a response to a Get Salesorder request or as a push notification of an event.  This BOD does not usually cause updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSalesOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSalesOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowSalesOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (SalesOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSalesOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSequenceSchedule" type="ShowSequenceScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application.

The purpose of the ShowSequenceSchedule is to communicate to a business application module or system the sending systems representation of SequenceSchedule information.  This request may be used as a response to a GetSequenceSchedule request or as a push notification of an event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSequenceScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSequenceScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowSequenceSchedule. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (SequenceSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSequenceScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SequenceSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowServiceConsumption" type="ShowServiceConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show ServiceConsumption is to notify the entire
                                enterprise of any services or associated items that have been
                                received directly ourside of the warehouse.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowServiceConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowServiceConsumptionDataAreaType">
            <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 ShowServiceConsumption.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Show) indicates the action to be
                                                  performed on the Noun
                                                  (ServiceConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowServiceConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ServiceConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowServiceContract" type="ShowServiceContractType">
    <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 ShowServiceContract. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowServiceContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowServiceContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowServiceContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ServiceContract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowServiceOrder" type="ShowServiceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowServiceOrder is to communicate to a business application module or system the sending systems representation of ServiceOrder order information.  This request may be used as a response to a GetServiceOrder request or as a push notification of an event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowServiceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowServiceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowServiceOrder. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ServiceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowServiceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ServiceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowShipFromPartyMaster" type="ShowShipFromPartyMasterType"/>
  <xsd:complexType name="ShowShipFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowShipFromPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowShipFromPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ShipFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowShipFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ShipFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowShipment" type="ShowShipmentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        A Shipment is a business document that details the intent to transport a specific quantity of material goods from a supplier to a single customer business partner destination.  The Shipment has been modeled after similar proprietary documents on popular business software packages (SAP's Delivery Note, Oracle Applications' Delivery document, etc.)

A Shipment is typically derived from the shipping schedule associated with a customer's purchase or sales order, once overall demand and various other business factors which prioritize the availability of the supplier's goods inventory have been evaluated.

The Shipment document is designed to have a dynamic structure and content. Initial shipment planning information can be updated and significant detail (actual picked inventory attributes, ship unit packaging, etc.) may be added during the execution phase of the supplier's order fulfillment and shipping business processes.  

The final form of the Shipment document can provide detail about the carrier and level of service used to transport the material, the exact quantity and attributes of the material shipped, and how that material is physically packaged and identified for transport.   

To aid the customer's planning and receiving business processes, the supplier may transmit the final Shipment document to customer in advance so that they can prepare for carrier arrival and then efficiently accept and utilize the ordered material.  In this use case, the Shipment document may function as a traditional Advance Ship Notice (ASN).

A ShipUnit is a data element that identifies and describes a specific collection of goods inventory that is packaged by a supplier for carrier transportation to a customer business partner destination. 

A ShipUnit is generally the smallest &quot;thing&quot; that can be individually moved and tracked throughout a carrier's transportation network.  The physical size, inventory, content and internal nested container complexity within a ShipUnit is arbitrary.  The ShipUnit component was specifically designed to be transportation mode independent.  It may be used to represent any uniquely identifiable and trackable assembly, container or vessel including, but not limited to: a parcel express package; a pallet of identical or mixed items; a truck trailer, rail car or an ocean cargo container.

This BOD does not usually cause updates to occur.
Shipment Characteristics

A Shipment document does not necessarily have a one-to-one relationship with any customer purchase/sales order document, line item or line item schedule. For shipping efficiency, a Shipment document may consolidate inventory shipment requests from a variety of different orders that have the same ultimate physical destination.  In fact, there may be no customer sale at all, as when the supplier is simply transferring inventory from one warehouse site to another within their enterprise to maintain optimum stocking levels.  

A Shipment typically involves a minimum of three business partner entities: Supplier, Carrier, and Customer in the most common business transaction scenario.   However these partner titles are more useful as descriptions of the basic roles in the Shipment process.  The actual number and relationship of the potential business partners/parties involved in the transaction is intended to be flexible in usage to accommodate agents working on behalf of partners and unique or complex scenarios.

The ShipUnit component identify and describe the physical shipping container(s) and internal packaging structure of the delivered goods.  ShipUnit component are typically constructed to describe the result of an inventory picking and packing operation.

The ShipUnit structure complements the line-item oriented summary information provided in the Shipment's ShipItem and InventoryDetail component with detailed information to accurately describe complex shipping unit assemblies and item packaging.  This robust level of detail is often demanded by customers to improve the efficiency of their receiving operations.  If the supplier provides trustworthy ship unit packaging information in advance, the customer does not have to spend valuable receiving personnel time breaking down the containers to inspect and tally each inventory item.

The general industry trend toward smaller just-in-time deliveries of only the required amount of goods, customer-imposed packaging configurations and requirements, and suppliers performing value-added light assembly customization at the time of shipment is driving the need for more detailed information about the product as it is actually delivered.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowShipmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowShipmentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowShipment. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Shipment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowShipmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Shipment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowShipmentSchedule" type="ShowShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Commonly, the ship schedule is generated by a material planning application and transmitted to an order or material planning application.
   
The purpose of the ShowShipmentSchedule is to communicate to a business application module or system the sending systems representation of ShipmentSchedule information.  This request may be used as a response to a GetShipmentSchedule request or as a push notification of an event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowShipmentScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowShipmentSchedule. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowShipToPartyMaster" type="ShowShipToPartyMasterType"/>
  <xsd:complexType name="ShowShipToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowShipToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowShipToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ShipToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowShipToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="ShipToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/SourceSystemGLMovement.xsd"/>
  <xsd:element name="ShowSourceSystemGLMovement" type="ShowSourceSystemGLMovementType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show SourceSystemGLMovement return period balance/movement
                                to the requesting system.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSourceSystemGLMovementType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSourceSystemGLMovementDataAreaType">
            <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 ShowSourceSystemGLMovement. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Show)
                                                  indicates the action to be performed
                                                  on the Noun(SourceSystemGLMovement).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSourceSystemGLMovementDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SourceSystemGLMovement" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSourceSystemJournalEntry" type="ShowSourceSystemJournalEntryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose
                                of the ShowJournalEntry is to enable an application or
                                component to respond to a ShowSourceSystemJournalEntry. The
                                response to the ShowSourceSystemJournalEntry is the response
                                to the ShowSourceSystemJournalEntry.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSourceSystemJournalEntryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSourceSystemJournalEntryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the
                                                  BOD message carries is provided, in
                                                  this case ShowJournalEntry.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Show) indicates the action
                                                  to be performed on the Noun
                                                  (JournalEntry). In response to the
                                                  PostJournalEntry.
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSourceSystemJournalEntryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SourceSystemJournalEntry" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSupplierBalance" type="ShowSupplierBalanceType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSupplierBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSupplierBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSupplierBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SupplierBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSupplierInvoice" type="ShowSupplierInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowSupplierInvoice Business Object Document is to Show receipt of the SupplierInvoice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSupplierInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSupplierInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowSupplierInvoice. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (SupplierInvoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSupplierInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SupplierInvoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSupplierPartyMaster" type="ShowSupplierPartyMasterType"/>
  <xsd:complexType name="ShowSupplierPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSupplierPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowSupplierPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (SupplierPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSupplierPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SupplierPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSupplierPlanningSchedule" type="ShowSupplierPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Since collaboration between a customer and a supplier 
                                can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate 
                                their current demand or supply schedule in response to what they received from the other party.  Either party 
                                can indicate detailed exception descriptions along with reason code and action code to the other party why the 
                                original demand/supply requirements need to be adjusted using the optional Data Type 
                                SupplierPlanningScheduleException. 
                                
                                Customers can use this SupplierPlanningSchedule to communicate demand requirement in three different ways.  
                                It can be as specific as the Item level or at the Commodity code level, which is higher than item.  Furthermore, 
                                it can be required simply by functional specification via feature identifiers and values using the optional 
                                component FeatureValues. 
                                
                                The purpose of the ShowSupplierPlanningSchedule is to communicate to a business application module or system 
                                the sending systems representation of SupplierPlanningSchedule information.  This request may be used as a 
                                response to a GetSupplierPlanningSchedule request or as a push notification of an event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSupplierPlanningScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSupplierPlanningScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                                that the BOD message carries is provided, in this case 
                                                                ShowSupplierPlanningSchedule. The information consists of a Verb and one or more 
                                                                Nouns. The verb (Show) indicates the action to be performed on the Noun (
                                                                SupplierPlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSupplierPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SupplierPlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSupplierQuote" type="ShowSupplierQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowSupplierQuote Business Object Document is to Show receipt of the SupplierQuote
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSupplierQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSupplierQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowSupplierQuote. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (SupplierQuote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSupplierQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SupplierQuote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSupplierRemittanceAdvice" type="ShowSupplierRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Show SupplierRemittanceAdvice is to to facilitate keeping Sales
                                order information Showhronized on separate data bases throughout an
                                enterprise. The Show SupplierRemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSupplierRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSupplierRemittanceAdviceDataAreaType">
            <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 ShowSupplierRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Show)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SupplierRemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSupplierRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SupplierRemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowSupplierShipmentSchedule" type="ShowSupplierShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Commonly, the ship schedule is generated by a material 
                               planning application and transmitted to an order or material planning application.
                               
                               The purpose of the ShowSupplierShipmentSchedule is to communicate to a business application module or system the 
                               sending systems representation of SupplierShipmentSchedule information.  This request may be used as a response 
                               to a GetSupplierShipmentSchedule request or as a push notification of an event.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowSupplierShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowSupplierShipmentScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                                that the BOD message carries is provided, in this case 
                                                                ShowSupplierShipmentSchedule. The information consists of a Verb and one or more 
                                                                Nouns. The verb (Show) indicates the action to be performed on the Noun 
                                                                (SupplierShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowSupplierShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="SupplierShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowTenant" type="ShowTenantType">
    <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 ShowAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Show) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowTenantType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowTenantDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowTenantDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Tenant" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="AcknowledgeTradingPartner" type="AcknowledgeTradingPartnerType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the AcknowledgeJournal is to transmit data necessary to create a journal entry from any sub ledger business application to a general ledger application.

Many applications in the enterprise environment create data that cause changes in the account balances of a 
general ledger application.  Some components that have activity which will be reflected in a general ledger 
application are:

1.	Benefits
2.	Costing
3.	Human Resources
4.	Inventory Control
5.	Manufacturing
6.	Payroll
7.	Production
8.	Treasury

By no means is this a complete list of all the components that create activity which generate a journal entry.

Many tasks that occur within the enterprise applications cause the creation of a General Ledger journal entry.  
Tasks relate directly to the Component.  For example, the adjustment of inventory value is a task that occurs within 
the Inventory Control Component.  Some of the tasks that would be catalysts for changes in a general ledger include:

1.	Receiving Inventory
2.	Issuing Inventory
3.	Transferring Inventory
4.	Adjusting Inventory Value
5.	Adjusting Inventory Count
6.	Calculating Material Variances
7.	Calculating Labor Variances
8.	Calculating Overhead Variances
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="AcknowledgeTradingPartnerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="AcknowledgeTradingPartnerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case AcknowledgeTradingPartner. The information consists of a Verb and one or more Nouns. The verb (Acknowledge) indicates the action to be performed on the Noun (TradingPartner).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="AcknowledgeTradingPartnerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Acknowledge"/>
      <xsd:element ref="TradingPartner" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowTransfer" type="ShowTransferType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Show Transfer is to notify the requestor if a change 
                                to a field the outcome of the change request.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowTransferDataAreaType">
            <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 ShowTransfer. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Transfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="Transfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowTransportationRequisition" type="ShowTransportationRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowTransportationRequisition Business Object Document is to Show receipt of the TransportationRequisition
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowTransportationRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowTransportationRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowTransportationRequisition. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (TransportationRequisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowTransportationRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="TransportationRequisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ShowUOMGroup" type="ShowUOMGroupType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the ShowUOMGroup is to supply Unit-of-Measure Group relationship information to another business application module.  This request may be issued as a response to a GetUOMGroup request or as the result of some other business event.

There are many possible business applications in several environments that may use this capability.  For example, an MRP, Inventory, or Manufacturing business application could use this to request alternate UOM information for one or more items.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="ShowUOMGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="ShowUOMGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case ShowUOMGroup. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (UOMGroup).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="ShowUOMGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Show"/>
      <xsd:element ref="UOMGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAccountingBookDefinition" type="SyncAccountingBookDefinitionType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAccountingBookDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAccountingBookDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAccountingBookDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AccountingBookDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAccountingChart" type="SyncAccountingChartType">
    <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 SyncAccountingChart. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingChart).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAccountingChartType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAccountingChartDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAccountingChartDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AccountingChart" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAccountingEntity" type="SyncAccountingEntityType">
    <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 SyncAccountingEntity. The
                                information consists of a Verb and one or more Nouns. The verb Sync indicates the action
                                to be performed on the Noun
                                (AccountingEntity).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAccountingEntityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAccountingEntityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAccountingEntityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AccountingEntity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAccountingJournal" type="SyncAccountingJournalType">
    <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 SyncAccountingJournal. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingJournal).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAccountingJournalType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAccountingJournalDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAccountingJournalDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AccountingJournal" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAdvanceShipNotice" type="SyncAdvanceShipNoticeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncAdvanceShipNotice Business Object Document is to Sync receipt of the AdvanceShipNotice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAdvanceShipNoticeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAdvanceShipNoticeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncAdvanceShipNotice. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (AdvanceShipNotice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAdvanceShipNoticeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AdvanceShipNotice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAssetFinancialLedger" type="SyncAssetFinancialLedgerType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAssetFinancialLedgerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAssetFinancialLedgerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAssetFinancialLedgerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AssetFinancialLedger" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAssetMaster" type="SyncAssetMasterType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncAssetMeterReading" type="SyncAssetMeterReadingType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncAssetMeterReadingType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncAssetMeterReadingDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncAssetMeterReadingDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="AssetMeterReading" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncBillOfMaterials" type="SyncBillOfMaterialsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SynBillOfMaterials is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Bill of Material.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncBillOfMaterialsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncBillOfMaterialsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncBillOfMaterials. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (BillOfMaterials).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncBillOfMaterialsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="BillOfMaterials" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncBillOfResources" type="SyncBillOfResourcesType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SynBillOfResources is to communicate to a business application module or system the need to initiate the creation of a Bill of Material structure.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to communicate the requirement to synchronize a Bill of Material.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncBillOfResourcesType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncBillOfResourcesDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncBillOfResources. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (BillOfResources).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncBillOfResourcesDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="BillOfResources" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncBillToPartyMaster" type="SyncBillToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncBillToPartyMaster is to facilitate keeping ship-to  information synchronized that exists on separate data bases.  The SyncBillToPartyMaster allows the adding of new ship-to location and the modification of previously established BillToPartyMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncBillToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncBillToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncBillToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (BillToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncBillToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="BillToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncBusinessPlan" type="SyncBusinessPlanType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncBusinessPlanType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncBusinessPlanDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncBusinessPlanDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="BusinessPlan" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCalendar" type="SyncCalendarType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Calendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCampaign" type="SyncCampaignType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCampaignType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCampaignDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCampaignDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Campaign" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCarrierParty" type="SyncCarrierPartyType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Sync CarrierParty is to publish information to the enterprise about carriers.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCarrierPartyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCarrierPartyDataAreaType">
            <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
                                                  SyncCarrierParty. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb
                                                  (Sync) indicates the action
                                                  to be performed on the Noun
                                                  (CarrierParty).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCarrierPartyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CarrierParty" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCarrierRoute" type="SyncCarrierRouteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncCarrierRoute is to enable an application to provide  Carrier Route information from another business application module.  The SyncCarrierRoute is typiically provided in a publish/subscribe or broadcast environment. Where the sending system is the master application of the information being provided, where the information is sent to other business applications that need to know the information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCarrierRouteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCarrierRouteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncCarrierRoute. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (CarrierRoute).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCarrierRouteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CarrierRoute" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCashReceipt" type="SyncCashReceiptType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncCashReceipt is to transmit an CashReceipt from a supplier to a customer. This information is passed in order to keep the customer updated on the number of CashReceipts they have.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCashReceiptType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCashReceiptDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncCashReceipt. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (CashReceipt).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCashReceiptDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CashReceipt" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/Catalog.xsd"/>
  <xsd:element name="SyncCatalog" type="SyncCatalogType"/>
  <xsd:complexType name="SyncCatalogType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCatalogDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncCatalog. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Catalog).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCatalogDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Catalog" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncChartOfAccounts" type="SyncChartOfAccountsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncChartOfAccounts is to distribute general ledger chart of accounts code identifiers to other applications to store for validation purposes.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncChartOfAccountsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncChartOfAccountsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncChartOfAccounts. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ChartOfAccounts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncChartOfAccountsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ChartOfAccounts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncChartsOfAccountsMap" type="SyncChartsOfAccountsMapType">
    <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 SyncCode. The information consists of a Verb and one or
                                more Nouns. The verb Sync) indicates the action to be
                                performed on the Noun (Code).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncChartsOfAccountsMapType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncChartsOfAccountsMapDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                        that the BOD message carries is provided, in this case SyncChartsOfAccountsMap. The 
                                                        information consists of a Verb and one or more Nouns. The verb (Get) indicates the action 
                                                        to be performed on the Noun (ChartsOfAccountsMap).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncChartsOfAccountsMapDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ChartsOfAccountsMap" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCodeDefinition" type="SyncCodeDefinitionType">
    <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 SyncCode. The information consists of a Verb and one or
                                more Nouns. The verb Sync) indicates the action to be
                                performed on the Noun (Code).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCodeDefinitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCodeDefinitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCodeDefinitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CodeDefinition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncConfiguredAssetMaster" type="SyncConfiguredAssetMasterType">
    <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 SyncConfiguredConfiguredAssetMaster. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncConfiguredAssetMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncConfiguredAssetMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncConfiguredAssetMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ConfiguredAssetMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncConstrainedResource" type="SyncConstrainedResourceType">
    <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 SyncConstrainedResource. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncConstrainedResourceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncConstrainedResourceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncConstrainedResourceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ConstrainedResource" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncContactMaster" type="SyncContactMasterType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncContactMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncContactMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncContactMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ContactMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncContract" type="SyncContractType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Contract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCurrency" type="SyncCurrencyType">
    <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 SyncCurrency. The information consists of a Verb and one or
                                more Nouns. The verb Sync) indicates the action to be
                                performed on the Noun (Currency).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCurrencyType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCurrencyDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCurrencyDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Currency" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCurrencyExchangeRateMaster" type="SyncCurrencyExchangeRateMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncCurrencyExchangeRateTypeMasterTypeMaster is to enable the passing of updates of currency exchange rates to other applications that have exchange rate tables.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCurrencyExchangeRateMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCurrencyExchangeRateMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncCurrencyExchangeRateTypeMasterTypeMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (CurrencyExchangeRateTypeMasterTypeMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCurrencyExchangeRateMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CurrencyExchangeRateMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCurrencyRateType" type="SyncCurrencyRateTypeType">
    <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 SyncCurrencyRateType. The information consists of a Verb
                                and one or more Nouns. The verb Sync) indicates the action to
                                be performed on the Noun (CurrencyRateType).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCurrencyRateTypeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCurrencyRateTypeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCurrencyRateTypeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CurrencyRateType" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCustomerCall" type="SyncCustomerCallType">
    <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 SyncCustomerCall. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCustomerCallType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCustomerCallDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCustomerCallDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CustomerCall" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCustomerPartyMaster" type="SyncCustomerPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncCustomerPartyMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The SyncCustomerPartyMaster allows the adding of new party and the modification of previously established CustomerPartyMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCustomerPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCustomerPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncCustomerPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (CustomerPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCustomerPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CustomerPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCustomerPurchaseOrder" type="SyncCustomerPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the
                SyncCustomerPurchaseOrder Business Object Document is to Sync receipt of the Purchase
                Order and to reflect any changes. Commonly, the acknowledgment is generated by an
                order management application and transmitted to a purchasing or procurement application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCustomerPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCustomerPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is the place in which the information that the BOD message carries is provided. In this case SyncCustomerPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (CustomerPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCustomerPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CustomerPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCustomerReturn" type="SyncCustomerReturnType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Sync CustomerReturn is to facilitate keeping sales or customer order information synchronized on separate data bases throughout an enterprise.  The Sync CustomerReturn allows the adding of new sales orders and the modification of previously established sales orders.

This BOD commonly causes updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCustomerReturnType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCustomerReturnDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncCustomerReturn. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (CustomerReturn).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCustomerReturnDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CustomerReturn" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncCustomerRFQ" type="SyncCustomerRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncCustomerRFQ Business Object Document is to Sync receipt of the CustomerRFQ
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncCustomerRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncCustomerRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncCustomerRFQ. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (CustomerRFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncCustomerRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="CustomerRFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncEDITransport" type="SyncEDITransportType">
    <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 SyncEDITransport. The
                                information consists of a Verb and one or more Nouns. The verb Sync indicates the action
                                to be performed on the Noun(EDITransport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncEDITransportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncEDITransportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncEDITransportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="EDITransport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncEmployeeWorkSchedule" type="SyncEmployeeWorkScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncEmployeeWorkSchedule is to enable the synchronization of Employee Work Schedule data that exists on separate data bases.  The SyncEmployeeWorkSchedule allows the adding of new Employee Work Schedules as well as the modification of previously established Employee Work Schedules.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncEmployeeWorkScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncEmployeeWorkScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncEmployeeWorkSchedule. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (EmployeeWorkSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncEmployeeWorkScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="EmployeeWorkSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncEmployeeWorkTime" type="SyncEmployeeWorkTimeType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncEmployeeWorkTime is to Sync work time information for an employee from a data collection application to an ERP Human Resource application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncEmployeeWorkTimeType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncEmployeeWorkTimeDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncEmployeeWorkTime. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (EmployeeWorkTime).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncEmployeeWorkTimeDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="EmployeeWorkTime" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncExpenseReport" type="SyncExpenseReportType">
    <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 SyncExpenseReport. The
                                information consists of a Verb and one or more Nouns. The verb Sync indicates the action
                                to be performed on the Noun
                                (ExpenseReport).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncExpenseReportType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncExpenseReportDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncExpenseReportDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ExpenseReport" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncFinancialCalendar" type="SyncFinancialCalendarType">
    <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 SyncFinancialCalendar. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (FinancialCalendar).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncFinancialCalendarType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncFinancialCalendarDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncFinancialCalendarDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="FinancialCalendar" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncFinancialPartyMaster" type="SyncFinancialPartyMasterType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncFinancialPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncFinancialPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncFinancialPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="FinancialPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncGLMovement" type="SyncGLMovementType">
    <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 SyncGLMovement. The
                                information consists of a Verb and one or more Nouns. The verb Sync indicates the action
                                to be performed on the Noun (GLMovement).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncGLMovementType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncGLMovementDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncGLMovementDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="GLMovement" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncHandlingGroup" type="SyncHandlingGroupType">
    <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 SyncHandlingGroup. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (HandlingGroup).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncHandlingGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncHandlingGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncHandlingGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="HandlingGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncInspectDelivery" type="SyncInspectDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncInspectDelivery is to supply InspectDelivery information for goods or services to another business application module.  This BOD may is initiated by the sending system upon some event occurring.  There are many possible business applications in several environments that may use this capability.

For example;
1.  A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 
2.  An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate InspectDelivery information.
3.  A Laboratory Information System could send quality information to an Inventory application,
4.  A Quality Control application could send information to an MRP, Inventory, or Purchasing application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncInspectDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncInspectDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncInspectDelivery. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (InspectDelivery).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncInspectDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="InspectDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncInventoryAdjustment" type="SyncInventoryAdjustmentType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Sync InventoryAdjustment is to notify the
                                enterprise of the change to the hold status of an inventory item.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncInventoryAdjustmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncInventoryAdjustmentDataAreaType">
            <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 SyncInventoryAdjustment. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Sync)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryAdjustment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncInventoryAdjustmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="InventoryAdjustment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncInventoryBalance" type="SyncInventoryBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncInventoryBalance is to enable the synchronization of InventoryBalance data that exists on separate Item Master databases.  This data is not the master data that describes the attributes of the item such as dimensions, weight, or unit of measure.

This is data that describes the ITEM as it exists at a specific location.

The primary focus of this BOD is to synchronize the quantity of an item by stocking location.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncInventoryBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncInventoryBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncInventoryBalance. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (InventoryBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncInventoryBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="InventoryBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncInventoryConsumption" type="SyncInventoryConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncInventoryConsumption is to inform a seller or provider about InventoryConsumption of items.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncInventoryConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncInventoryConsumptionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncInventoryConsumption. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (InventoryConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncInventoryConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="InventoryConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncInventoryCount" type="SyncInventoryCountType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncInventoryCount is to transmit an inventory count to ERP from the actual physical inventory location. This count may be a cycle count or a physical count.  This BOD may also apply to planned or unplanned inventory counts.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncInventoryCountType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncInventoryCountDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncInventoryCount. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (InventoryCount).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncInventoryCountDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="InventoryCount" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncInventoryHold" type="SyncInventoryHoldType">
    <xsd:annotation>
      <xsd:documentation>
        The purpose of the Sync InventoryHold is to notify the
                                enterprise of the change to the hold status of an inventory item.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncInventoryHoldType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncInventoryHoldDataAreaType">
            <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 SyncInventoryHold. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Sync)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (InventoryHold).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncInventoryHoldDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="InventoryHold" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncInvoice" type="SyncInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncInvoice is to transmit an invoice from a supplier to a customer. This information is passed in order to keep the customer updated on the number of Invoices they have.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncInvoice. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Invoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Invoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncItemMaster" type="SyncItemMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncItemMaster is to supply Item information for goods or services to another business application module.  This BOD may also be initiated by the sending system upon some event occurring.

This BOD is not for synchronizing ITEM quantities at each inventory location.   The SyncInventoryBalance Business Object Document is used for this purpose.

There are many possible business applications in several environments that may use this capability. For example, a MRP, Inventory, or Manufacturing business application could use this to communicate item information. 

This BOD can be used to synchronize items used in finished goods, raw materials, work-in-process or components in a bill of materials.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncItemMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncItemMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncItemMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ItemMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncItemMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ItemMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncLocation" type="SyncLocationType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Sync Location is to enable a mechanism to ensure that the physical location identifiers are synchronized between the business applications that require this to communicate clearly.  This is particularly critical when only the codes that identify locations are used.  Without the meaning of the codes clearly communicated, the integration is not effective.  This BOD enables the Location codes to be synchronized among business applications.

This BOD may also be initiated by the sending system upon some event occurring.

There are many possible business applications in several environments that may use this capability. For example, a MRP, Inventory, or Manufacturing business application could use this to communicate Location information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncLocationType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncLocationDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncLocation. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Location).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncLocationDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Location" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncMaintenanceOrder" type="SyncMaintenanceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncMaintenanceOrder is to ensure that all business software components in a specific integration instance have the current Maintenance Order information. This BOD is commonly used to publish the need to create or update a Maintenance Order in a publish and subscribe integration environment.

One possible scenario is the synchronization of Maintenance Order between field devices, service trucks, etc. with a CMMS system.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncMaintenanceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncMaintenanceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncMaintenanceOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (MaintenanceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncMaintenanceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="MaintenanceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncOpportunity" type="SyncOpportunityType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncOpportunity is to enable an application to provide Opportunity information from one business application to another business application. The SyncOpportunity is provided in a a publishe/subscribe or broadcast buiness exchange wher the owner or the master of the given information provides it to the other business applications that need to know the information or have expressed interest.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncOpportunityType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncOpportunityDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncOpportunityDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Opportunity" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPayableTransaction" type="SyncPayableTransactionType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPayableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPayableTransactionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPayableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PayableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPayFromPartyMaster" type="SyncPayFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncPayFromPartyMaster is to facilitate keeping Pay-From  information synchronized that exists on separate data bases.  The SyncPayTFromartyMaster allows the adding of new Pay-From location and the modification of previously established PayFromPartyMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPayFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPayFromPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPayFromPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PayFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPayFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PayFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPerson" type="SyncPersonType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPersonType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPersonDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPersonDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Person" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPersonnel" type="SyncPersonnelType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncPersonnel is to enable the synchronization of employee data that exists on separate data bases between manufacturing and human resource applications.  The SyncPersonnel allows the adding of new employees and their relevant data as well as the modification of previously established employees.

The SyncPersonnel is used to facilitate the maintenance of human resource data in a manufacturing work force planning module.  This enables the workforce planning module to use current personnel information when creating finite production schedules.  The SyncPersonnel can also be used by a project accounting application or a work order management application to assign qualified personnel or to perform resource planning.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPersonnelType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPersonnelDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPersonnel. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Personnel).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPersonnelDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Personnel" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPlannedProductionOrder" type="SyncPlannedProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncPlannedProductionOrder is to ensure that all business software components in a specific integration instance have the current PlannedProductionOrder information.  This BOD is commonly used in a publish and subscribe integration environment.

This BOD commonly causes updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPlannedProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPlannedProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPlannedProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PlannedProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPlannedProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PlannedProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPlannedPurchaseOrder" type="SyncPlannedPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncPlannedPurchaseOrder is to facilitate keeping purchase order information synchronized on separate data bases throughout an enterprise.  The Sync PlannedPurchaseOrder allows the adding of new purchase orders and the modification of previously established purchase orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPlannedPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPlannedPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPlannedPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PlannedPurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPlannedPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PlannedPurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPlannedTransfer" type="SyncPlannedTransferType"/>
  <xsd:complexType name="SyncPlannedTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPlannedTransferDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPlannedTransfer. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PlannedTransfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPlannedTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PlannedTransfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPlanningSchedule" type="SyncPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party.  Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional component PlanningScheduleException
.
The purpose of the SyncPlanningSchedule is to communicate requirement information (part number, quantity, etc.) between a customer and their supplier on a regular basis, for example daily, weekly etc, or for a user-defined time bucket type definition (Component FexibileBucket) that is sent as part of this PlanningSchedule.  

SyncPlanningSchedule allows the adding of new requirements and the modification of previously established requirements.  

Customers can use this PlanningSchedule to communicate demand requirement in three different ways.  It can be as specific as the Item level or at the Commodity code level, which is higher than item.  Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValue.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Allows the adding of new requirements and the modification of previously established requirements through various Sync Indicator values.
Customers can use PlanningSchedule to communicate demand requirement in three different ways.  It can be as specific as the Item level or at the Commodity code level, which is higher than item.  Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional Data Type FeatureValueData.
      </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPlanningScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPlanningSchedule. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPriceList" type="SyncPriceListType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncPriceList is to communicate to a business application module or system the need to initiate the creation of product price list information as well as update existing price lists.

This BOD may be necessary to address the Make to Order, Assemble to Order, or Mixed Mode business ordering scenarios in a Order Management to Manufacturing application integration scenario.

There are many possible business applications in several environments that may use this capability. For example, a Manufacturing, distributor or reseller business application could use this to communicate the price change or request a price list.

It may also be necessary to support Component Supplier Management (CSM) scenarios.  In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog.  A customer purchases the product from the Catalog provider.  They have the capability to do comparison shopping from the catalog.  Supplier Certification may be provided by the Catalog provider.

This definition of price list is intended to support simple pricing scenario, especially pricing that may accompany a published price list. It is not intended to support complex pricing environments that may be needed to support features such as;
�	Deals and Promotions
�	Coupons and Sales Incentives
�	Rebates and Accruals

This functionality will be addressed in a subsequent release. It is a working assumption that the representation of complex qualifications, coupons and sales incentives are rarely communicated between systems.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPriceListType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPriceListDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPriceList. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PriceList).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPriceListDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PriceList" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProductionOrder" type="SyncProductionOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProductionOrder is to ensure that all business software components in a specific integration instance have the current Production Order information.  This BOD is commonly used in a publish and subscribe integration environment.

This BOD commonly causes updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProductionOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProductionOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProductionOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProductionOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProductionOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProductionOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProductionReceiver" type="SyncProductionReceiverType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProductionReceiverType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProductionReceiverDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProductionReceiverDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProductionReceiver" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectBalance" type="SyncProjectBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectBalance is to facilitate keeping party information synchronized that exists on separate data bases.  The SyncProjectBalance allows the adding of new party and the modification of previously established ProjectBalance.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectBalance. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectBid" type="SyncProjectBidType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectBid is to ensure that all business software components in a specific integration instance have the current ProjectBid information. This BOD is commonly used to publish the need to create or update a ProjectBid in a publish and subscribe integration environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectBidType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectBidDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectBid. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectBid).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectBidDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectBid" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectBudget" type="SyncProjectBudgetType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectBudget is to ensure that all business software components in a specific integration instance have the current ProjectBudget information. This BOD is commonly used to publish the need to create or update a ProjectBudget in a publish and subscribe integration environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectBudgetType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectBudgetDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectBudget. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectBudget).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectBudgetDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectBudget" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectCosts" type="SyncProjectCostsType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectCosts is to ensure that all business software components in a specific integration instance have the current ProjectCosts information. This BOD is commonly used to publish the need to create or update a ProjectCosts in a publish and subscribe integration environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectCostsType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectCostsDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectCosts. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectCosts).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectCostsDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectCosts" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectEstimate" type="SyncProjectEstimateType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectEstimate is to ensure that all business software components in a specific integration instance have the current ProjectEstimate information. This BOD is commonly used to publish the need to create or update a ProjectEstimate in a publish and subscribe integration environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectEstimateType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectEstimateDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectEstimate. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectEstimate).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectEstimateDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectEstimate" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:include schemaLocation="Resources/Nouns/ProjectExtension.xsd"/>
  <xsd:element name="SyncProjectExtension" type="SyncProjectExtensionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectExtension is to ensure 
                                that all business software components in a specific integration instance have the current ProjectExtension information. 
                                This BOD is commonly used to publish the need to create or update a ProjectExtension in a publish and subscribe integration 
                                environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectExtensionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectExtensionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the 
                                                                BOD message carries is provided, in this case SyncProjectExtension. The information consists 
                                                                of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the 
                                                                Noun (ProjectExtension).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectExtensionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectExtension" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectMaster" type="SyncProjectMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectMaster is to facilitate keeping party information synchronized that exists on separate data bases.  The SyncProjectMaster allows the adding of new party and the modification of previously established ProjectMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectPeriodBalance" type="SyncProjectPeriodBalanceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectPeriodBalance is to facilitate keeping party information synchronized that exists on separate data bases.  The SyncProjectPeriodBalance allows the adding of new party and the modification of previously established ProjectPeriodBalance.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectPeriodBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectPeriodBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectPeriodBalance. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectPeriodBalance).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectPeriodBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectPeriodBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncProjectRevenue" type="SyncProjectRevenueType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncProjectRevenue is to ensure that all business software components in a specific integration instance have the current ProjectRevenue information. This BOD is commonly used to publish the need to create or update a ProjectRevenue in a publish and subscribe integration environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncProjectRevenueType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncProjectRevenueDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncProjectRevenue. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ProjectRevenue).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncProjectRevenueDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ProjectRevenue" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncPurchaseOrder" type="SyncPurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Sync PurchaseOrder is to facilitate keeping purchase order information synchronized on separate data bases throughout an enterprise.  The Sync PurchaseOrder allows the adding of new purchase orders and the modification of previously established purchase orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncPurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncPurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncPurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncQuote" type="SyncQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncQuote is to ensure that all business software components in a specific integration instance have the current Quote information. This BOD is commonly used to publish the need to create or update a Quote in a publish and subscribe integration environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncQuote. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Quote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Quote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncReceivableTransaction" type="SyncReceivableTransactionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Sync Receivable is to notify the entire enterprise of 
                                any changes to the accounts receivable.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncReceivableTransactionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncReceivableTransactionDataAreaType">
            <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 SyncReceivable. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Sync)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (Receivable).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncReceivableTransactionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ReceivableTransaction" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncReceiveDelivery" type="SyncReceiveDeliveryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The SyncReceiveDelivery may be used to notify the shipping business partner that the shipment has been received by the customer or consignee destination, and alert them to any discovered discrepancies.   The acknowledgement may contain the full detail of the receipt as created by the receiving party or just the discrepancies and other exception conditions.

The SyncReceiveDelivery BOD supports receipt acknowledgements 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="SyncReceiveDeliveryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncReceiveDeliveryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncReceiveDelivery. The information consists of a Verb and one or more Nouns. The verb (Sync) 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="SyncReceiveDeliveryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ReceiveDelivery" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncRemittanceAdvice" type="SyncRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Sync RemittanceAdvice is to to facilitate keeping Sales
                                order information synchronized on separate data bases throughout an
                                enterprise. The Sync RemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncRemittanceAdviceDataAreaType">
            <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 SyncRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Sync)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (RemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="RemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncRemitToPartyMaster" type="SyncRemitToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncRemitToPartyMaster is to facilitate keeping ship-From  information synchronized that exists on separate data bases.  The SyncShipTFromartyMaster allows the adding of new ship-From location and the modification of previously established RemitToPartyMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncRemitToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncRemitToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncRemitToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (RemitToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncRemitToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="RemitToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncRequisition" type="SyncRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        SyncRequisition is used to synchronize Requisition information with other applications
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncRequisition. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Requisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Requisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncRFQ" type="SyncRFQType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncRFQ is to ensure that all business software components in a specific integration instance have the current Request for Quote information. This BOD is commonly used to publish the need to create or update a Request for Quote in a publish and subscribe integration environment.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncRFQType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncRFQDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncRFQ. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (RFQ).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncRFQDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="RFQ" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSalesOrder" type="SyncSalesOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Sync SalesOrder is to facilitate keeping sales or customer order information synchronized on separate data bases throughout an enterprise.  The Sync SalesOrder allows the adding of new sales orders and the modification of previously established sales orders.

This BOD commonly causes updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSalesOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSalesOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncSalesOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (SalesOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSalesOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSequenceSchedule" type="SyncSequenceScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncSequenceSchedule is to enable the exchange of sequence schedule information authorizing a sequenced shipment of parts for specific trading partners and addresses.

Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSequenceScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSequenceScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncSequenceSchedule. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (SequenceSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSequenceScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SequenceSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncServiceConsumption" type="SyncServiceConsumptionType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Sync ServiceConsumption is to notify the entire
                                enterprise of any services or associated items that have been
                                received directly ourside of the warehouse.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncServiceConsumptionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncServiceConsumptionDataAreaType">
            <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 SyncServiceConsumption.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Sync) indicates the action to be
                                                  performed on the Noun
                                                  (ServiceConsumption).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncServiceConsumptionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ServiceConsumption" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncServiceContract" type="SyncServiceContractType">
    <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 SyncServiceContract. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncServiceContractType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncServiceContractDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncServiceContractDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ServiceContract" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncServiceOrder" type="SyncServiceOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncServiceOrder is to ensure that all business software components in a specific integration instance have the current ServiceOrder Order information. This BOD is commonly used to publish the need to create or update a ServiceOrder Order in a publish and subscribe integration environment.

One possible scenario is the synchronization of ServiceOrder Order between field devices, service trucks, etc. with a CMMS system.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncServiceOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncServiceOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncServiceOrder. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ServiceOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncServiceOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ServiceOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncShipFromPartyMaster" type="SyncShipFromPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncShipFromPartyMaster is to facilitate keeping ship-From  information synchronized that exists on separate data bases.  The SyncShipTFromartyMaster allows the adding of new ship-From location and the modification of previously established ShipFromPartyMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncShipFromPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncShipFromPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncShipFromPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ShipFromPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncShipFromPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ShipFromPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncShipment" type="SyncShipmentType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        SyncShipment is used to synchronize Shipment information with other applications
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncShipmentType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncShipmentDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncShipment. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Shipment).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncShipmentDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Shipment" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncShipmentSchedule" type="SyncShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncShipmentSchedule is to enable the exchange of shipment schedule information, authorizing a shipment quantity and date for specific trading partners and addresses.

Commonly, the ship schedule is generated by a material planning application and transmitted to an order or material planning application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncShipmentScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncShipmentSchedule. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncShipToPartyMaster" type="SyncShipToPartyMasterType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncShipToPartyMaster is to facilitate keeping ship-to  information synchronized that exists on separate data bases.  The SyncShipToPartyMaster allows the adding of new ship-to location and the modification of previously established ShipToPartyMaster.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncShipToPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncShipToPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncShipToPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (ShipToPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncShipToPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="ShipToPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSourceSystemGLMovement" type="SyncSourceSystemGLMovementType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSourceSystemGLMovementType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSourceSystemGLMovementDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSourceSystemGLMovementDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SourceSystemGLMovement" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSourceSystemJournalEntry" type="SyncSourceSystemJournalEntryType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose
                                of the SyncJournalEntry is to enable an application or
                                component to respond to a SyncSourceSystemJournalEntry. The
                                response to the SyncSourceSystemJournalEntry is the response
                                to the SyncSourceSystemJournalEntry.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSourceSystemJournalEntryType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSourceSystemJournalEntryDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the
                                                  BOD message carries is provided, in
                                                  this case SyncJournalEntry.
                                                  The information consists of a Verb
                                                  and one or more Nouns. The verb
                                                  (Sync) indicates the action
                                                  to be performed on the Noun
                                                  (JournalEntry). In response to the
                                                  PostJournalEntry.
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSourceSystemJournalEntryDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SourceSystemJournalEntry" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierBalance" type="SyncSupplierBalanceType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSupplierBalanceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierBalanceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierBalanceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierBalance" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierInvoice" type="SyncSupplierInvoiceType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncSupplierInvoice Business Object Document is to Sync receipt of the SupplierInvoice
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSupplierInvoiceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierInvoiceDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncSupplierInvoice. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (SupplierInvoice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierInvoiceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierInvoice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierPartyMaster" type="SyncSupplierPartyMasterType"/>
  <xsd:complexType name="SyncSupplierPartyMasterType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierPartyMasterDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncSupplierPartyMaster. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (SupplierPartyMaster).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierPartyMasterDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierPartyMaster" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierPlanningSchedule" type="SyncSupplierPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Since collaboration between a customer and a supplier 
                                can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate 
                                their current demand or supply schedule in response to what they received from the other party.  Either party 
                                can indicate detailed exception descriptions along with reason code and action code to the other party why the 
                                original demand/supply requirements need to be adjusted using the optional component 
                                SupplierPlanningScheduleException.  
                                
                                The purpose of the SyncSupplierPlanningSchedule is to communicate requirement information (part number, quantity, 
                                etc.) between a customer and their supplier on a regular basis, for example daily, weekly etc, or for a 
                                user-defined time bucket type definition (Component FexibileBucket) that is sent as part of this 
                                SupplierPlanningSchedule.  
                                
                                SyncSupplierPlanningSchedule allows the adding of new requirements and the modification of previously 
                                established requirements.  Customers can use this SupplierPlanningSchedule to communicate demand requirement 
                                in three different ways.  It can be as specific as the Item level or at the Commodity code level, which is 
                                higher than item.  Furthermore, it can be required simply by functional specification via feature identifiers 
                                and values using the optional component FeatureValue.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSupplierPlanningScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        Allows the adding of new requirements and the 
                                modification of previously established requirements through various Sync Indicator values. 
                                Customers can use SupplierPlanningSchedule to communicate demand requirement in three different ways.  
                                It can be as specific as the Item level or at the Commodity code level, which is higher than item.  
                                Furthermore, it can be required simply by functional specification via feature identifiers and values 
                                using the optional Data Type FeatureValueData.
      </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierPlanningScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                                that the BOD message carries is provided, in this case 
                                                                SyncSupplierPlanningSchedule. The information consists of a Verb and one or more 
                                                                Nouns. The verb (Sync) indicates the action to be performed on the Noun 
                                                                (SupplierPlanningSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierPlanningScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierPlanningSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierQuote" type="SyncSupplierQuoteType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncSupplierQuote Business Object Document is to Sync receipt of the SupplierQuote
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSupplierQuoteType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierQuoteDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncSupplierQuote. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (SupplierQuote).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierQuoteDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierQuote" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierRemittanceAdvice" type="SyncSupplierRemittanceAdviceType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The
                                purpose of the Sync SupplierRemittanceAdvice is to to facilitate keeping Sales
                                order information Synchronized on separate data bases throughout an
                                enterprise. The Sync SupplierRemittanceAdvice allows the adding of new Sales
                                orders.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSupplierRemittanceAdviceType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierRemittanceAdviceDataAreaType">
            <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 SyncSupplierRemittanceAdvice. The
                                                  information consists of a Verb and
                                                  one or more Nouns. The verb (Sync)
                                                  indicates the action to be performed
                                                  on the Noun
                                                  (SupplierRemittanceAdvice).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierRemittanceAdviceDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierRemittanceAdvice" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierRMA" type="SyncSupplierRMAType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncSupplierRMA Business Object Document is to Sync receipt of the SupplierRMA
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSupplierRMAType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierRMADataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncSupplierRMA. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (SupplierRMA).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierRMADataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierRMA" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncSupplierShipmentSchedule" type="SyncSupplierShipmentScheduleType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncSupplierShipmentSchedule is to 
                                enable the exchange of shipment schedule information, authorizing a shipment quantity and date for specific 
                                trading partners and addresses. 
                                
                                Commonly, the ship schedule is generated by a material planning application and transmitted to an order or 
                                material planning application.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncSupplierShipmentScheduleType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncSupplierShipmentScheduleDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information 
                                                                that the BOD message carries is provided, in this case 
                                                                SyncSupplierShipmentSchedule. The information consists of a Verb and one or more 
                                                                Nouns. The verb (Sync) indicates the action to be performed on the Noun 
                                                                (SupplierShipmentSchedule).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncSupplierShipmentScheduleDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="SupplierShipmentSchedule" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncTenant" type="SyncTenantType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncTenantType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncTenantDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncTenantDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Tenant" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncTextMessage" type="SyncTextMessageType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        Is where
                                the information that the TextMessage message carries is provided, in
                                this case SyncAccountingBook. The information consists of a Verb and
                                one or more Nouns. The verb Sync) indicates the action to be
                                performed on the Noun(TextMessage).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncTextMessageType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncTextMessageDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncTextMessageDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="TextMessage" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncTradingPartner" type="SyncTradingPartnerType">
    <xsd:annotation>
      <xsd:documentation source="http://www.openapplications.org/oagis/9">
        The purpose of the Sync TradingPartner is
                        to notify the entire enterprise of any changes.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncTradingPartnerType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncTradingPartnerDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the
                                                        information that the BOD message carries is provided, in this case
                                                        SyncTradingPartner. The information consists of a Verb and one or more Nouns.
                                                        The verb (Sync) indicates the action to be performed on the Noun (TradingPartner).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncTradingPartnerDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="TradingPartner" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncTransfer" type="SyncTransferType"/>
  <xsd:complexType name="SyncTransferType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncTransferDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncTransfer. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Transfer).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncTransferDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Transfer" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncTransportationRequisition" type="SyncTransportationRequisitionType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncTransportationRequisition Business Object Document is to Sync receipt of the TransportationRequisition
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncTransportationRequisitionType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncTransportationRequisitionDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncTransportationRequisition. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (TransportationRequisition).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncTransportationRequisitionDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="TransportationRequisition" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncTransportationStatus" type="SyncTransportationStatusType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Sync TransportationStatus is to facilitate keeping sales or customer order information synchronized on separate data bases throughout an enterprise.  The Sync TransportationStatus allows the adding of new sales orders and the modification of previously established sales orders.

This BOD commonly causes updates to occur.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncTransportationStatusType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncTransportationStatusDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncTransportationStatus. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (TransportationStatus).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncTransportationStatusDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="TransportationStatus" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncUOMGroup" type="SyncUOMGroupType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the SyncUOMGroup is to supply a set of Unit-Of-Measure relationships to another business application module.

This BOD addresses the need for applications to exchange item-independent alternative UOM information beyond the stocking UOM. See the Item UOM Integration Scenario for more detailed information.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncUOMGroupType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncUOMGroupDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case SyncUOMGroup. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (UOMGroup).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncUOMGroupDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="UOMGroup" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="SyncWorkflow" type="SyncWorkflowType">
    <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 SyncAccountingBook. The
                                information consists of a Verb and one or more Nouns. The verb Sync) indicates the action
                                to be performed on the Noun
                                (AccountingBook).
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="SyncWorkflowType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="SyncWorkflowDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://www.openapplications.org/oagis/9"/>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="SyncWorkflowDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Sync"/>
      <xsd:element ref="Workflow" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="UpdatePurchaseOrder" type="UpdatePurchaseOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Update Purchaseorder is to request another business application to make Updates to an existing Purchase Order.  This Update must refer to the original document and/or item ordered.  The Update processing assumes replacement of fields sent, with the exception the identifying fields of the Purchase Order.

If any of these key fields require changing, (i.e. the PurchaseOrder Document Id or a LineNumber) that constitutes a cancellation of the request and/or the addition of another Purchase Order.
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="UpdatePurchaseOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="UpdatePurchaseOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case UpdatePurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Update) indicates the action to be performed on the Noun (PurchaseOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="UpdatePurchaseOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Update"/>
      <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="UpdateSalesOrder" type="UpdateSalesOrderType">
    <xsd:annotation>
      <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
        The purpose of the Update SalesOrder is to request that another business application component make Updates to an existing Sales Order.

Processing Note:  This Update must refer to the original document and/or item ordered.  The Update processing assumes replacement of fields sent, with the exception of the fields that uniquely identify the document and/or its line, schedule or subline. These include the DocumentId and the LineNumber for the Line, Subline, and Schedule.

If any of the Field Identifiers above require changing, that constitutes a cancellation of the request and/or the addition of another Sales Order.

This BOD commonly causes updates to occur
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>
  <xsd:complexType name="UpdateSalesOrderType">
    <xsd:complexContent>
      <xsd:extension base="BusinessObjectDocumentType">
        <xsd:sequence>
          <xsd:element name="DataArea" type="UpdateSalesOrderDataAreaType">
            <xsd:annotation>
              <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">
                Is where the information that the BOD message carries is provided, in this case UpdateSalesOrder. The information consists of a Verb and one or more Nouns. The verb (Update) indicates the action to be performed on the Noun (SalesOrder).
              </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
  <xsd:complexType name="UpdateSalesOrderDataAreaType">
    <xsd:sequence>
      <xsd:element ref="Update"/>
      <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:schema>
