<!--
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/RemittanceAdvice.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="RemittanceAdvice" type="RemittanceAdviceType">
<xsd:annotation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">The purpose of the RemittanceAdvice Business Object Document is to provides a detailed breakdown of a payment amount. It includes all credits, debits, discounts, adjustments taken on an invoice, and adjustment reason codes. A payment can attach a Remittance Advice Notification. Payment can be for products only, transportation, or other services. </xsd:documentation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">The Process RemittanceAdvice sends the electronic form of a remittance advice document from a payer to a payee. It is usually executed when an outstanding accounts payable balance (credit or debit) exists. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="RemittanceAdviceHeader" type="RemittanceAdviceHeaderType">
<xsd:annotation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">The Remittance Advice Header contains information that applies to the entire remittance advice. This Component is required.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="RemittanceAdviceLine" type="RemittanceAdviceLineType">
<xsd:annotation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">To be entered.
At least one occurrence of this Component is required for each occurrence of the Remittance Advice.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="RemittanceAdviceType">
<xsd:annotation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">The schema type for RemittanceAdvice. To be entered.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="RemittanceAdviceHeader" minOccurs="0"/>
<xsd:element ref="RemittanceAdviceLine" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="RemittanceAdviceHeaderType">
<xsd:complexContent>
<xsd:extension base="StatusEnabledHeaderType">
<xsd:sequence>
<xsd:element ref="EffectiveDate" minOccurs="0"/>
<xsd:element ref="InitiatingParty" minOccurs="0"/>
<xsd:element ref="BillToParty" minOccurs="0"/>
<xsd:element ref="FinancialParty" minOccurs="0"/>
<xsd:element ref="RemitToParty" minOccurs="0"/>
<xsd:element ref="Party" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="ChequeInstruction" minOccurs="0"/>
<xsd:element ref="PaymentMethodCode" minOccurs="0"/>
<xsd:element ref="TotalAmount" minOccurs="0"/>
<xsd:element ref="TransactionID" minOccurs="0"/>
<xsd:element ref="UserArea" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="RemittanceAdviceLineType">
<xsd:complexContent>
<xsd:extension base="StatusEnabledLineType">
<xsd:sequence>
<xsd:element ref="PaymentAmount" minOccurs="0"/>
<xsd:element ref="UserArea" minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
|
XSD Schema Code: