<!--

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

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

License information for this file is provided in the file **2005 OAGi License Agreement.txt** that is provided with this download package.

For support, more information, or to report implementation bugs, please contact the Open Applications Group at xml@openapplications.org.
    
     XML Schema 
     
    Name: \OAGIS\9.0\BODs\Developer\LoadInvoiceLedgerEntry.xsd
-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.openapplications.org/oagis/9" targetNamespace="http://www.openapplications.org/oagis/9" elementFormDefault="qualified" attributeFormDefault="unqualified">
        <xsd:include schemaLocation="../../Resources/Nouns/InvoiceLedgerEntry.xsd"/>
        <xsd:element name="LoadInvoiceLedgerEntry" type="LoadInvoiceLedgerEntryType">
                <xsd:annotation>
                        <xsd:documentation source="http://www.openapplications.org/oagis/9">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

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 accounts payable application may have to inform the purchasing application of the unapproved 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.

The purpose of the LoadInvoiceLedgerEntry is to transmit data to create an unapproved open item in either a payables application or a purchasing application.

The scope of the LoadInvoiceLedgerEntry indicates that the supplier's invoice has not yet been approved and the invoice is to be used as part of the invoice matching process.

OAGIS has already defined the scenario for invoices that are approved for payment in a separate BOD namely LoadPayable.
</xsd:documentation>
                </xsd:annotation>
        </xsd:element>
        <xsd:complexType name="LoadInvoiceLedgerEntryType">
                <xsd:complexContent>
                        <xsd:extension base="BusinessObjectDocumentType">
                                <xsd:sequence>
                                        <xsd:element name="DataArea" type="LoadInvoiceLedgerEntryDataAreaType">
                                                <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 LoadInvoiceLedgerEntry. The information consists of a Verb and one or more Nouns. The verb (Load) indicates the action to be performed on the Noun (InvoiceLedgerEntry).</xsd:documentation>
                                                </xsd:annotation>
                                        </xsd:element>
                                </xsd:sequence>
                        </xsd:extension>
                </xsd:complexContent>
        </xsd:complexType>
        <xsd:complexType name="LoadInvoiceLedgerEntryDataAreaType">
                <xsd:sequence>
                        <xsd:element ref="Load"/>
                        <xsd:element ref="InvoiceLedgerEntry" maxOccurs="unbounded"/>
                </xsd:sequence>
        </xsd:complexType>
</xsd:schema>

• LoadInvoiceLedgerEntryDataAreaType
• LoadInvoiceLedgerEntryType

• LoadInvoiceLedgerEntry