Definition Type: Element
Name: LoadPayable
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:LoadPayableType
Containing Schema: LoadPayable.xsd
Abstract
Documentation:
The purpose of the LoadPayable is to transmit data to create a payable open item in a payables application from the purchasing information generated in a purchasing application. The LoadPayable may also update the General Ledger, depending on the specific architecture of the financial applications. The scope of the LoadPayable indicates that the supplier's invoice is ready to be paid and has already been approved before the information moves to the accounts payable application. An approved invoice is also known as the voucher. OAGIS will define the scenario of invoices that get matched within the accounts payable application in a separate Business Service Request later. Some financial applications have the general ledger and accounts payable databases tightly integrated where updates to the accounts payable application are automatically reflected in the general ledger balances. The LoadPayable will transmit all information needed for both the accounts payable and the general ledger. Other applications allow the general ledger balances to be updated separately from the accounts payable. The second model illustrates that the combination of the LoadPayable and PostJournalEntry will accomplish this scenario.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema loadpayable_xsd Drilldown into ApplicationArea in schema meta_xsd Drilldown into languageCode in schema meta_xsd Drilldown into systemEnvironmentCode in schema meta_xsd Drilldown into versionID in schema meta_xsd Drilldown into releaseID in schema meta_xsd Drilldown into BusinessObjectDocumentType in schema meta_xsd Drilldown into LoadPayableType in schema loadpayable_xsdXSD Diagram of LoadPayable in schema loadpayable_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code:
<xsd:element name="LoadPayable" type="LoadPayableType">
    <xsd:annotation>
        <xsd:documentation source="http://www.openapplications.org/oagis/9">The purpose of the LoadPayable is to transmit data to create a payable open item in a payables application from the purchasing information generated in a purchasing application.  The LoadPayable may also update the General Ledger, depending on the specific architecture of the financial applications.

The scope of the LoadPayable indicates that the supplier's invoice is ready to be paid and has already been approved before the information moves to the accounts payable application.  An approved invoice is also known as the voucher.  OAGIS will define the scenario of invoices that get matched within the accounts payable application in a separate Business Service Request later.

Some financial applications have the general ledger and accounts payable databases tightly integrated where updates to the accounts payable application are automatically reflected in the general ledger balances.
</xsd:documentation>
        <xsd:documentation source="http://www.openapplications.org/oagis/9">The LoadPayable will transmit all information needed for both the accounts payable and the general ledger.

Other applications allow the general ledger balances to be updated separately from the accounts payable.  The second model illustrates that the combination of the LoadPayable and PostJournalEntry will accomplish this scenario.
</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
ApplicationArea nsA:ApplicationArea (1) (1)
DataArea nsA:DataArea (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
releaseID nsA:releaseID Required
versionID nsA:versionID Optional
systemEnvironmentCode nsA:systemEnvironmentCode Production Optional
languageCode nsA:languageCode en-US Optional
Collapse Derivation Tree: