<!--
** 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\LoadReceivable.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/Receivable.xsd"/>
<xsd:element name="LoadReceivable" type="LoadReceivableType">
<xsd:annotation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">The purpose of the LoadReceiveable is to transmit data to create a receivable open item in a receivable application from the billing information generated in an order management application. The LoadReceiveable may also update the General Ledger, depending on the specific architecture of the accounting application.
The scope of the LoadReceiveable is to create a BOD to recognize customer obligation (accounts receivable asset). Specific transactions include:
1. Sales Invoice
2. Credit Memo
3. Debit Memo
4. Charge Back
The LoadReceiveable may also be used for transaction that do not originate from an order management application.
The following two models illustrate that the LoadReceiveable may, in some cases, be adequate to update the financial applications, i.e., Receivables and General Ledger, and in other cases, will also require the PostJournal Business Object Document (BOD) to assure the General Ledger account balances are updated.
</xsd:documentation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">In the model above, the receivable application is a sub-ledger of the general ledger. Updates to G/L balances occur via the receivables module, therefore the Load Receivable contains both receivable and general ledger transaction information.</xsd:documentation>
<xsd:documentation source="http://www.openapplications.org/oagis/9">This other model illustrates the environment that sometime exists when General Ledger updates occur directly from the Order Management application. The reconciliation between the receivable and general ledger is a function within the financial applications and not of the integration space. This model allows the G/L balances to be updated in either detail or summarized form.
The scope of the role of the receivable application includes functions such as:
· Allowing Cash Application
· Dunning
· Dispute management
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="LoadReceivableType">
<xsd:complexContent>
<xsd:extension base="BusinessObjectDocumentType">
<xsd:sequence>
<xsd:element name="DataArea" type="LoadReceivableDataAreaType">
<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 LoadReceivable. The information consists of a Verb and one or more Nouns. The verb (Load) indicates the action to be performed on the Noun (Receivable).</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="LoadReceivableDataAreaType">
<xsd:sequence>
<xsd:element ref="Load"/>
<xsd:element ref="Receivable" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
|
XSD Schema Code: