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

<!--   Schema agency: 	Open Applications Group 


   OAGIS® Revision:    OAGIS 9_6  
   Date:               02 Jul 2012
   Copyright 1997-2012, All Rights Reserved 

  	
   Copyright (C) Open Applications Group (1997-2012). 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_6/Developer/Global/Nouns/DebitTransfer.xsd
-->

<!--
© Copyright 2013 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" elementFormDefault="qualified"
	attributeFormDefault="unqualified">
	
	<xsd:include schemaLocation="../Components/Financial/Components.xsd"/>
	<xsd:element name="DebitTransfer" type="DebitTransferType"/>
	<xsd:complexType name="DebitTransferType">
		<xsd:sequence>
			<xsd:element ref="DebitTransferHeader" minOccurs="0"/>
			<xsd:element ref="DebitTransferPayment" minOccurs="0" maxOccurs="unbounded">
				<xsd:annotation>
					<xsd:documentation source="http://www.openapplications.org/oagis/9">Set of
						characteristics that applies to the debit sideof the payment transactions
						included in the payment initiation.</xsd:documentation>
				</xsd:annotation>
			</xsd:element>
		</xsd:sequence>
	</xsd:complexType>
	<xsd:element name="DebitTransferHeader" type="DebitTransferHeaderType"/>
	<xsd:complexType name="DebitTransferHeaderType">
		<xsd:complexContent>
			<xsd:extension base="StatusEnabledHeaderType">
				<xsd:sequence>
					<xsd:element ref="AuthorizationID" minOccurs="0" maxOccurs="unbounded">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Identifyies the authorization level of the user or application that
								is sending the Business Object Document Message. This authorization
								level being recognized be the receiving system indicates what can be
								done on the receiving system(s).</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
										
					<xsd:element ref="TotalTransactions" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Number of individual transactions contained in the payment
								initiation, i.e., the number of occurrences of payment transaction.
							</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
					<xsd:element ref="GroupingIndicator" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Indicates that the common debit information in the transactions is
								included once and not repeated for each
								transaction.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
					<xsd:element ref="InitiatingParty" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Party initiating the payment to the forwarding or first agent. This
								can be the debtor (in a credit transfer), the creditor (in a direct
								debit) or a party that initiates the payment on behalf of the debtor
								or creditor.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
					<xsd:element ref="ForwardingAgentParty" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Financial institution that receives the payment transaction from
								the initiating party and processes the instruction.
							</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
					<xsd:element ref="UserArea" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Allows the user of OAGIS to extend the specification in order to
								provide additional information that is not captured in
								OAGIS.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>This is done by defining the additional information in XML Schema
								and referencing the new schema in the xml instance document through
								the use of namespaces. Once this is done the additional information
								defined there can be carried in the BOD XML instance
								document.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>The Open Applications Group will make best efforts to quickly
								consider all proposed submissions.The USERAREA is always the last
								element in all components, except where the component has been
								extended inline.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
				</xsd:sequence>
			</xsd:extension>
		</xsd:complexContent>
	</xsd:complexType>
	<xsd:complexType name="DebitTransferPaymentType">
		<xsd:complexContent>
			<xsd:extension base="TransferPaymentType">
				<xsd:sequence>
					<xsd:element ref="DebitTransferAgreement" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/oagis/9">Set
								of elements that further identifies the type of credit transfer
								being requested by the initiating party. Business Rule: This
								component may be present if payment method is TRF. It must not be
								present if payment method is CHK.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
					<xsd:element ref="UserArea" minOccurs="0">
						<xsd:annotation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>Allows the user of OAGIS to extend the specification in order to
								provide additional information that is not captured in
								OAGIS.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>This is done by defining the additional information in XML Schema
								and referencing the new schema in the xml instance document through
								the use of namespaces. Once this is done the additional information
								defined there can be carried in the BOD XML instance
								document.</xsd:documentation>
							<xsd:documentation source="http://www.openapplications.org/platform/1"
								>The Open Applications Group will make best efforts to quickly
								consider all proposed submissions.The USERAREA is always the last
								element in all components, except where the component has been
								extended inline.</xsd:documentation>
						</xsd:annotation>
					</xsd:element>
				</xsd:sequence>
			</xsd:extension>
		</xsd:complexContent>
	</xsd:complexType>
	<xsd:element name="DebitTransferPayment" type="DebitTransferPaymentType">
		<xsd:annotation>
			<xsd:documentation source="http://www.openapplications.org/oagis/9">Set of
				characteristics that applies to the debit sideof the payment transactions included
				in the payment initiation.</xsd:documentation>
		</xsd:annotation>
	</xsd:element>
	
</xsd:schema>
