<?xml version="1.0" encoding="utf-8"?>
<!--
        
        ** OAGIS® Revision: 9.1  **
        ** Date: 11 May 2007 **
        ** Copyright 1997-2007, All Rights Reserved **
        
        This is an OAGIS® BOD XML Schema (XSD) Definition.
        
       License information for this file is provided in the file **OAGi License Agreement.txt** that is provided with this download package.
        
        For support, more information, or to report implementation bugs, please contact the Open Applications Group at xml@openapplications.org.
        
        XML Schema 
        
-->
 
<!--
© Copyright 2007 Infor Global Solutions Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. The 
word and design marks set forth herein are trademarks and/or registered trademarks of Infor Global Solutions 
Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. All other trademarks listed herein 
are the property of their respective owners.
 
-->
 
<!--    *****     Update Log     *****
 
Date          By      Note
10 Apr 2008    JB      Added correct Copyright and update comments to schema.
 
        *****     Update End     *****
 
-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schema.infor.com/InforOAGIS/2" targetNamespace="http://schema.infor.com/InforOAGIS/2" elementFormDefault="qualified" attributeFormDefault="unqualified">
        
        <xsd:include schemaLocation="../../Resources/Nouns/JournalEntry.xsd"/>
        
        <xsd:element name="AcknowledgeJournalEntry" type="AcknowledgeJournalEntryType">
                
                <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="AcknowledgeJournalEntryType">
                
                <xsd:complexContent>
                        
                        <xsd:extension base="BusinessObjectDocumentType">
                                
                                <xsd:sequence>
                                        
                                        <xsd:element name="DataArea" type="AcknowledgeJournalEntryDataAreaType">
                                                
                                                <xsd: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).</xsd:documentation>
                                                
                                                </xsd:annotation>
                                        
                                        </xsd:element>
                                
                                </xsd:sequence>
                        
                        </xsd:extension>
                
                </xsd:complexContent>
        
        </xsd:complexType>
        
        <xsd:complexType name="AcknowledgeJournalEntryDataAreaType">
                
                <xsd:sequence>
                        
                        <xsd:element ref="Acknowledge"/>
                        
                        <xsd:element ref="JournalEntry" maxOccurs="unbounded"/>
                
                </xsd:sequence>
        
        </xsd:complexType>

</xsd:schema>
