<!--




   Schema agency: 	Open Applications Group 


   OAGIS® Revision:    9.3  
   Date:               11 August 2008 
   Copyright 1997-2008, All Rights Reserved 

  	
   Copyright (C) Open Applications Group (1997-2008). All Rights Reserved.
  
  
   This is an OAGIS® BOD XML Schema (XSD) Definition.

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

   For support, more information, or to report implementation bugs, please contact the Open Applications Group at oagis@openapplications.org.
    
   XML Schema 
     
    Name: /OAGi-BPI-Platform/org_openapplications_oagis/9_3/Developer/Nouns/JournalEntry.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="../../../../org_openapplications_platform/1_0/Common/OAGi/Components/FinancialComponents.xsd"/>
        <xsd:element name="JournalEntry" type="JournalEntryType"/>
        <xsd:element name="JournalEntryHeader" type="JournalEntryHeaderType"/>
        <xsd:element name="JournalEntryLine" type="JournalEntryLineType"/>
        <xsd:complexType name="JournalEntryType">
                <xsd:annotation>
                        <xsd:documentation source="http://www.openapplications.org/oagis/9">A journal represents a change in the balances of a business's financial accounts.  Many tasks or transactions throughout an enterprise will result in the creation of a journal.  Some examples are creating a customer invoice, paying a vendor, transferring inventory, or paying employees.  A journal consists of a header with general information, and two or more lines specifying what accounts will be affected.  A journal typically includes balanced debit and credit lines.</xsd:documentation>
                </xsd:annotation>
                <xsd:sequence>
                        <xsd:element ref="JournalEntryHeader" minOccurs="0"/>
                        <xsd:element ref="JournalEntryLine" minOccurs="0" maxOccurs="unbounded"/>
                </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="JournalEntryHeaderType">
                <xsd:annotation>
                        <xsd:documentation source="http://www.openapplications.org/oagis/9">In the Header, DocumentReferences is the link that ties back to a sub ledger transaction entry ID.  It is the identifier of an original transaction or document.  For example, it could be the receipt or the summarized inventory activity.  This is the element that refers to an audit record.  Together with the Sender information, the DocumentReferences is part of the referencing system, which will enable drill back audit trail functionality.</xsd:documentation>
                </xsd:annotation>
                <xsd:complexContent>
                        <xsd:extension base="LedgerEntryHeaderType">
                                <xsd:sequence>
                                        <xsd:element ref="UserArea" minOccurs="0"/>
                                </xsd:sequence>
                        </xsd:extension>
                </xsd:complexContent>
        </xsd:complexType>
        <xsd:complexType name="JournalEntryLineType">
                <xsd:complexContent>
                        <xsd:extension base="LedgerEntryLineType">
                                <xsd:sequence>
                                        <xsd:element ref="UserArea" minOccurs="0"/>
                                </xsd:sequence>
                        </xsd:extension>
                </xsd:complexContent>
        </xsd:complexType>
</xsd:schema>

• JournalEntryHeaderType
• JournalEntryLineType
• JournalEntryType

• JournalEntry
• JournalEntryHeader
• JournalEntryLine