How to interface external application to WIN UR
|
|
|
- Camron Rice
- 5 years ago
- Views:
Transcription
1 XML Interfaces How to interface external application to WIN UR Version 1.0 Le 4 juillet 2007 ADE Page 1
2 XML INTERFACE OVERWIEW... 5 WHAT IS IT?... 5 WHO IS IT FOR, AND HOW TO IMPLEMENT IT?... 5 DOCUMENTS KIT (ZIP FILE)... 5 WHAT IS AN XML SCHEMA?... 6 HOW TO EXPORT XML DATA FROM WINEUR... 6 SAMPLE:... 6 HOW TO EXPORT... 8 HOW TO IMPORT XML DATA TO WINEUR CREATION OF A DEFINITION FORMAT HOW TO IMPORT A FILE: DETAILED SCHEMA ACCOUNTINGXML.XSD ELEMENT ACCOUNT ELEMENT ADDRESSLINE ELEMENT ADDRESSLINE ELEMENT ADDRESSLINE ELEMENT ADDRESSLINE ELEMENT ADDRESSLINE ELEMENT AMOUNTSTOREVALUE ELEMENT ANALYSISSPLIT ELEMENT ANALYTICALACCOUNT ELEMENT ANALYTICALAMOUNT ELEMENT ANALYTICALCURRENCY ELEMENT ANALYTICALTYPE ELEMENT BANK ELEMENT BANKACCOUNT ELEMENT BANKADDRESS ELEMENT BANKADDRESS ELEMENT BANKADDRESS ELEMENT BANKADDRESS ELEMENT BANKADDRESS ELEMENT BCCYAMOUNT ELEMENT BCCYBALANCE ELEMENT BCCYPAYMENT ELEMENT CLIENTCODE ELEMENT CLIENTCURRENCY ELEMENT CLIENTSUBLEDGERACCOUNT ELEMENT CLIENTVATNUMBER Page 2
3 ELEMENT CODE ELEMENT COMMODITY ELEMENT CURRENCY ELEMENT CUSTOMERFLAG ELEMENT DESCRIPTION ELEMENT DESCRIPTION ELEMENT DESCRIPTION ELEMENT DUEDATE ELEMENT ELEMENT ENTRYDATE ELEMENT FAX ELEMENT FILENAME ELEMENT FOREX ELEMENT GAINSONEXCHANGEACCOUNT ELEMENT INVOICEBANKCODE ELEMENT INVOICEDATE ELEMENT INVOICEDUEDATE ELEMENT INVOICENUMBER ELEMENT INVOICETEXT ELEMENT JOURNALCODE ELEMENT LANGUAGE ELEMENT LOSSESONEXCHANGEACCOUNT ELEMENT MASTERANALYTICALACCOUNT ELEMENT NAME ELEMENT NETMASSKG ELEMENT NUMBER ELEMENT OCCYAMOUNT ELEMENT OCCYBALANCE ELEMENT OCCYPAYMENT ELEMENT PAYMENT ELEMENT PAYMENTDATE ELEMENT PHONE ELEMENT PRINTCODE ELEMENT SUBLEDGERACCOUNT ELEMENT SUBTYPE ELEMENT TAXCODE ELEMENT TEXT ELEMENT TEXTLINE ELEMENT TEXTLINE ELEMENT TRANSCORBANKACCOUNT ELEMENT TYPE ELEMENT TYPEOFINVOICE ELEMENT VALUEDATE ELEMENT VATNUMBER Page 3
4 ELEMENT VATNUMBERUSEDBYTRANSCOR ELEMENT VERSION ELEMENT VOUCHER ELEMENT WEBSITE ELEMENT XML2WINEUR ELEMENT XML2WINEUR/GENERALLEDGERACCOUNTS ELEMENT XML2WINEUR/ANALYTICALACCOUNTS ELEMENT XML2WINEUR/CLIENTS ELEMENT XML2WINEUR/INVOICES ELEMENT XML2WINEUR/ENTRIES COMPLEXTYPE ADDRESSESTYPE ELEMENT ADDRESSESTYPE/ADDRESS COMPLEXTYPE ADDRESSTYPE COMPLEXTYPE ANALYTICALACCOUNTSTYPE ELEMENT ANALYTICALACCOUNTSTYPE/ANALYTICALACCOUNT COMPLEXTYPE ANALYTICALACCOUNTTYPE COMPLEXTYPE CLIENTLINETYPE ELEMENT CLIENTLINETYPE/INVOICEVATINFORMATION COMPLEXTYPE CLIENTSTYPE ELEMENT CLIENTSTYPE/CLIENT COMPLEXTYPE CLIENTTYPE ELEMENT CLIENTTYPE/ADDRESSES COMPLEXTYPE ENTRIESTYPE ELEMENT ENTRIESTYPE/ENTRY COMPLEXTYPE ENTRYTYPE ELEMENT ENTRYTYPE/HEADER ELEMENT ENTRYTYPE/GENERALLEDGERLINE ELEMENT ENTRYTYPE/CLIENTLINE COMPLEXTYPE GENERALLEDGERACCOUNTSTYPE ELEMENT GENERALLEDGERACCOUNTSTYPE/GENERALLEDGERACCOUNT COMPLEXTYPE GENERALLEDGERACCOUNTTYPE COMPLEXTYPE GENERALLEDGERLINETYPE COMPLEXTYPE HEADERTYPE COMPLEXTYPE INVOICESTYPE ELEMENT INVOICESTYPE/INVOICE COMPLEXTYPE INVOICETYPE COMPLEXTYPE INVOICEVATINFORMATIONTYPE Page 4
5 XML INTERFACE OVERWIEW WHAT IS IT? The XML Interface is a set of standards which will enable you to understand how to create XML files from your application to be uploaded to WIN UR. The same XML Interface is used to download data from WIN UR to your application. For instance, when you are uploading an XML file for an accounting transaction, the fields of the accounting entry will be automatically filled up using the data within the XML file. XML stands for EXtensible Markup Language XML is a markup language much like HTML XML was designed to describe data XML tags are not predefined. You must define your own tags XML uses a Document Type Definition (DTD) or an XML Schema to describe the data XML with a DTD or XML Schema is designed to be self-descriptive XML is a W3C Recommendation <?xml version="1.0" encoding="iso "?> <note> <to>dove</to> <from>jani</from> <heading>reminder</heading> <body>don't forget me this weekend!</body> </note> WHO IS IT FOR, AND HOW TO IMPLEMENT IT? In a typical implementation, you will need to engage a contractor or acquire the assistance of your organisation s internal IT Department to create a programmatic interface with existing information system. This interface will then create the necessary XML files needed for the upload or the download. Such an interface would alleviate the problem of re-keying of information from an existing accounting information system to a invoicing program. The benefit of such an interface is essentially the time it saves, by reducing the work required in filling out the data fields. DOCUMENTS KIT (ZIP FILE) The XML documentation kit is contained on a compressed zip file. This file contains the following: This master document AccountingXml.xsd AccountingXml.dtd This is the schemas file This is the DTD file Page 5
6 WHAT IS AN XML SCHEMA? A newer XML schema language, described by the W3C as the successor of DTDs, is XML Schema, or more informally referred to by the initialism for XML Schema instances, XSD (XML Schema Definition). XSDs are far more powerful than DTDs in describing XML languages. They use a rich datatyping system, allow for more detailed constraints on an XML document's logical structure, and must be processed in a more robust validation framework. XSDs also use an XMLbased format which makes it possible to use ordinary XML tools to help process them, although XSD implementations require much more than just the ability to read XML. HOW TO EXPORT XML DATA FROM WINEUR SAMPLE: In order to understand the XML file syntax, the easiest way is to create an export from accounting data of an existing company and to look at the result. Creation of a definition format Launch the program from the menu Import /Export XML Press the Create button, This screen will be appears Xml format : File name of the export format. Page 6
7 WinEUR target company : Select the WinEUR company code from which data will be exported. Description : File description After entering the above information, the following screen will appear : Page 7
8 Select File export settings Select the Export tab Directory of export file : Define the directory in which the file will be saved (By default, in the company directory) Element to export : Click data that you wish to export. (entries, GL accounts, clients, etc..) Information in «Options» tab are correctly configured by default Click OK to save the file definition HOW TO EXPORT A FILE In the main menu, choose the definition file you wish to use Page 8
9 Click then on the Export button. The following screen appears : By default, all entries will be saved. If you wish to make a selection ( entries, currencies, etc..) indicate your choice using the corresponding fields. Then click on Export button to launch the treatment. In the result tab, the program will indicate treatments which are executed. At the end of the treatment, you can visualize your file by clicking on the Edit button. (top left). Page 9
10 HOW TO IMPORT XML DATA TO WINEUR CREATION OF A DEFINITION FORMAT Launch the program from the Import/Export XML Press the Create button, This screen will appear Xml format : File name of the import format. WinEUR target company : Select the WinEUR company code in which data will be imported. Description : File description Then click OK. You will have now to define the import settings. You should select the format and click on modify. Then click on file import settings and the following screen will appear : Page 10
11 Select the import tab In the Settings tab, you will find all informations concerning import Directory of import file : Define the directory from which you will read the file to be imported. Page 11
12 File extension : define the file extension. (xml by default). Treatment to perform before import : please do not consider this part as it as been done only for a specific customer. Created Tick actions which should be done during import Update Tick actions which should be done during import Select Default value tab Be aware that default values are used only for creation and not for update During imports, it can happen that information are nonexistent. For instance when you import a client, the language code does not exist in the program from which you import. It means then you can force to have a language code GB Default value for Entry Default currency code : Multiple tax code : General ledger debit line text : General ledger credit line text : Client debit line text : Client credit line text : self explaining self explaining self explaining self explaining self explaining self explaining Page 12
13 Default value for Account Revaluation : Amount to evaluate : Gains on exchange account : Losses on exchange account : Analysis split : Update general ledger : Revaluation method you wish to use. which amount has to be evaluated self explaining self explaining define the analytic breakdown Tick if you wish to update the existing GL accounts. Default value for Clients Client sub ledger account : Supplier sub ledger account : Language code : Payment term : Default tax code : Revaluation : Amount to evaluate : Gains on exchange account : Losses on exchange account : self explaining self explaining self explaining self explaining self explaining Revaluation method you wish to use. which amount has to be evaluated self explaining self explaining Page 13
14 Default value for Analytical account Default analytical general ledger account : Default analytical client account : self explaining self explaining. Conversion tab During import, it can happen that codes are different between two applications. Therefore you have to define conversion between two codes. For instance in the application from which you wish to import the currency code is $ while it is USD in WinEUR. You should use this tab to define conversions. You can establish conversions for the following fields : Account : Anytical account : Client code : Currency : Tax code : Language : Payment term : GL account, self explaining, debtors and creditors code self explaining self explaining self explaining self explaining Partial conversion tab Allows to execute accounts partial conversion. If you wish to choose this of conversion, please contact to get more informations. Page 14
15 Options tab Définitions : Date separator and dates format : should not be used as there is a standard XML format by default. Options Print result : tick if you wish to print import result during automatic treatment. Zip treated files : After automatic treatment, the program will save the XMLfile in the import directory under the form of a zip file. (File name : <year><month>.zip) Process test file : if you tick this box it will only test the file without importing data. Click OK to save the import definition. Page 15
16 HOW TO IMPORT A FILE: In the main menu, choose the definition file you wish to use. Click on the import button. The following screen will appear : Click on «Browse» to select the file, then the following screen will appear : Page 16
17 You can visualize the file when clicking on Edit. If necessary, complete informations on Import. Then click on the verify button. The program will execute a pre treatment to verify the data coherence If there is an error, the program will display the exact problem precising for instance that there is an unknown currency. You will have then to create the new currency in WinEUR or execute a conversion. Be aware that as long all errors are not corrected, you will not be able to import data and the import button is inaccessible. If there is no error, the message : End of check, no errors will appear at the end of verification. The import button is now accessible and you can then import data. Please note that you can see in the new tab all new elements that have been created while you are going to see only errors in the errors tab.. Once the file has been treated, it will be renamed (zipped if the option has been ticked) in order not to import it several times in a row. Page 17
18 Page 18 DETAILED SCHEMA ACCOUNTINGXML.XSD Elements Complex s Account AddressesType AddressLine1 AddressType AddressLine2 AnalyticalAccountsType AddressLine3 AnalyticalAccountType AddressLine4 ClientLineType AddressLine5 ClientsType AmountStoreValue ClientType AnalysisSplit EntriesType AnalyticalAccount EntryType AnalyticalAmount GeneralLedgerAccountsType AnalyticalCurrency GeneralLedgerAccountType AnalyticalType GeneralLedgerLineType Bank HeaderType BankAccount InvoicesType BankAddress1 InvoiceType BankAddress2 InvoiceVATInformationType BankAddress3 BankAddress4 BankAddress5 BccyAmount BccyBalance BccyPayment ClientCode ClientCurrency ClientSubledgerAccount ClientVATNumber Code Commodity Currency CustomerFlag Description1 Description2 Description3 DueDate EntryDate Fax FileName Forex GainsOnExchangeAccount InvoiceBankCode InvoiceDate InvoiceDuedate InvoiceNumber InvoiceText JournalCode Language LossesOnExchangeAccount MasterAnalyticalAccount
19 Name NetMassKg Number OccyAmount OccyBalance OccyPayment Payment PaymentDate Phone PrintCode SubledgerAccount SubType TaxCode Text TextLine1 TextLine2 TranscorBankAccount Type TypeOfInvoice ValueDate VatNumber VATNumberUsedByTranscor Version Voucher WebSite Xml2WinEUR ELEMENT ACCOUNT used by complextypes GeneralLedgerAccountType GeneralLedgerLineType facets maxlength 15 Account number source <xs:element name="account"> <xs:documentation>account number</xs:documentation> <xs:maxlength value="15"/> ELEMENT ADDRESSLINE1 Page 19
20 used by complextype AddressType facets maxlength 40 Client Address line 1 source <xs:element name="addressline1"> <xs:documentation>client Address line 1</xs:documentation> <xs:documentation>client address line 1</xs:documentation> <xs:maxlength value="40"/> ELEMENT ADDRESSLINE2 used by complextype AddressType facets maxlength 40 Client Address line 2 source <xs:element name="addressline2"> <xs:documentation>client Address line 2</xs:documentation> <xs:documentation>client address line 2</xs:documentation> <xs:maxlength value="40"/> ELEMENT ADDRESSLINE3 used by complextype AddressType facets maxlength 40 Client Address line 3 source <xs:element name="addressline3"> <xs:documentation>client Address line 3</xs:documentation> Page 20
21 <xs:documentation>client address line 3</xs:documentation> <xs:maxlength value="40"/> ELEMENT ADDRESSLINE4 used by complextype AddressType facets maxlength 40 Client Address line 4 source <xs:element name="addressline4"> <xs:documentation>client Address line 4</xs:documentation> <xs:documentation>client address line 4</xs:documentation> <xs:maxlength value="40"/> ELEMENT ADDRESSLINE5 used by complextype AddressType facets maxlength 40 Client Address line 5 source <xs:element name="addressline5"> <xs:documentation>client Address line 5</xs:documentation> <xs:documentation>client address line 5</xs:documentation> <xs:maxlength value="40"/> Page 21
22 ELEMENT AMOUNTSTOREVALUE extension of xs:boolean properties content complex used by complextypes ClientType GeneralLedgerAccountType Revalued amounts. source <xs:element name="amountstorevalue"> <xs:documentation>revalued amounts.</xs:documentation> <xs:complextype> <xs:simplecontent> <xs:extension base="xs:boolean"/> </xs:simplecontent> </xs:complextype> ELEMENT ANALYSISSPLIT used by complextype GeneralLedgerAccountType facets enumeration NoAnalyticalBookings enumeration ObligatorySplit Contain the rule of analysis split. (ex Obligartory, optional, no split) source <xs:element name="analysissplit"> <xs:documentation>contain the rule of analysis split. (ex Obligartory, optional, no split)</xs:documentation> <xs:enumeration value="noanalyticalbookings"/> <xs:enumeration value="obligatorysplit"/> ELEMENT ANALYTICALACCOUNT used by complextypes AnalyticalAccountType ClientLineType GeneralLedgerLineType InvoiceType facets maxlength 15 Analytical account source <xs:element name="analyticalaccount"> <xs:documentation>analytical account</xs:documentation> Page 22
23 <xs:maxlength value="15"/> ELEMENT ANALYTICALAMOUNT xs:decimal used by complextypes ClientLineType GeneralLedgerLineType Analytical amount in analytical currency source <xs:element name="analyticalamount" ="xs:decimal"> <xs:documentation>analytical amount in analytical currency</xs:documentation> ELEMENT ANALYTICALCURRENCY used by complextypes ClientLineType GeneralLedgerLineType facets maxlength 3 Iso currency code source <xs:element name="analyticalcurrency"> <xs:documentation>iso currency code</xs:documentation> <xs:maxlength value="3"/> ELEMENT ANALYTICALTYPE used by complextype AnalyticalAccountType facets enumeration Detail enumeration Master Specific field source <xs:element name="analyticaltype"> <xs:documentation>specific field</xs:documentation> Page 23
24 <xs:enumeration value="detail"/> <xs:enumeration value="master"/> ELEMENT BANK used by complextype ClientType facets maxlength 25 Client bank source <xs:element name="bank"> <xs:documentation>client bank</xs:documentation> <xs:maxlength value="25"/> ELEMENT BANKACCOUNT used by complextype ClientType facets maxlength 25 Client bank account source <xs:element name="bankaccount"> <xs:documentation>client bank account</xs:documentation> <xs:maxlength value="25"/> ELEMENT BANKADDRESS1 Page 24
25 used by complextype ClientType facets maxlength 40 Client bank address line 1 source <xs:element name="bankaddress1"> <xs:documentation>client bank address line 1</xs:documentation> <xs:maxlength value="40"/> ELEMENT BANKADDRESS2 used by complextype ClientType facets maxlength 40 Client bank address line 2 source <xs:element name="bankaddress2"> <xs:documentation>client bank address line 2</xs:documentation> <xs:maxlength value="40"/> ELEMENT BANKADDRESS3 used by complextype ClientType facets maxlength 40 Client bank address line 3 source <xs:element name="bankaddress3"> <xs:documentation>client bank address line 3</xs:documentation> <xs:maxlength value="40"/> Page 25
26 ELEMENT BANKADDRESS4 used by complextype ClientType facets maxlength 40 Client bank address line 4 source <xs:element name="bankaddress4"> <xs:documentation>client bank address line 4</xs:documentation> <xs:maxlength value="40"/> ELEMENT BANKADDRESS5 used by complextype ClientType facets maxlength 60 Client bank address line 5 source <xs:element name="bankaddress5"> <xs:documentation>client bank address line 5</xs:documentation> <xs:maxlength value="60"/> ELEMENT BCCYAMOUNT xs:decimal used by complextypes ClientLineType GeneralLedgerLineType InvoiceType Amount in book keeping currency source <xs:element name="bccyamount" ="xs:decimal"> <xs:documentation>amount in book keeping currency</xs:documentation> Page 26
27 ELEMENT BCCYBALANCE xs:decimal used by complextype InvoiceType Balance in book keeping currency source <xs:element name="bccybalance" ="xs:decimal"> <xs:documentation>balance in book keeping currency</xs:documentation> ELEMENT BCCYPAYMENT xs:decimal used by complextype InvoiceType Payment in book keeping currency source <xs:element name="bccypayment" ="xs:decimal"> <xs:documentation>payment in book keeping currency</xs:documentation> ELEMENT CLIENTCODE used by complextypes ClientLineType InvoiceType facets maxlength 15 Client code source <xs:element name="clientcode"> <xs:documentation>client code</xs:documentation> <xs:maxlength value="15"/> ELEMENT CLIENTCURRENCY Page 27
28 xs:string used by complextype ClientLineType Iso currency code source <xs:element name="clientcurrency" ="xs:string"> <xs:documentation>iso currency code</xs:documentation> ELEMENT CLIENTSUBLEDGERACCOUNT used by complextype ClientLineType facets maxlength 15 Sub ledger control account source <xs:element name="clientsubledgeraccount"> <xs:documentation>sub ledger control account</xs:documentation> <xs:maxlength value="15"/> ELEMENT CLIENTVATNUMBER used by complextype InvoiceVATInformationType facets maxlength 15 Not used source <xs:element name="clientvatnumber"> <xs:documentation>not used</xs:documentation> <xs:maxlength value="15"/> Page 28
29 ELEMENT CODE used by complextype ClientType facets maxlength 15 Client code source <xs:element name="code"> <xs:documentation>client code</xs:documentation> <xs:maxlength value="15"/> ELEMENT COMMODITY used by complextype InvoiceVATInformationType facets maxlength 15 Not used source <xs:element name="commodity"> <xs:documentation>not used</xs:documentation> <xs:maxlength value="15"/> ELEMENT CURRENCY used by complextypes AnalyticalAccountType ClientType GeneralLedgerAccountType GeneralLedgerLineType InvoiceType facets length 3 Iso currency code source <xs:element name="currency"> <xs:documentation>iso currency code</xs:documentation> Page 29
30 <xs:length value="3"/> ELEMENT CUSTOMERFLAG used by complextype ClientType facets enumeration no enumeration yes Yes = customer / No = supplier source <xs:element name="customerflag"> <xs:documentation>yes = customer / No = supplier</xs:documentation> <xs:enumeration value="no"/> <xs:enumeration value="yes"/> ELEMENT DESCRIPTION1 used by complextype AnalyticalAccountType facets maxlength 40 Analytical description source <xs:element name="description1"> <xs:documentation>analytical description</xs:documentation> <xs:maxlength value="40"/> ELEMENT DESCRIPTION2 used by complextype AnalyticalAccountType Page 30
31 facets maxlength 40 Analytical description line 2 source <xs:element name="description2"> <xs:documentation>analytical description line 2</xs:documentation> <xs:maxlength value="40"/> ELEMENT DESCRIPTION3 used by complextype AnalyticalAccountType facets maxlength 40 Analytical description line 3 source <xs:element name="description3"> <xs:documentation>analytical description line 3</xs:documentation> <xs:maxlength value="40"/> ELEMENT DUEDATE xs:date used by complextype InvoiceType Invoice due date source <xs:element name="duedate" ="xs:date"> <xs:documentation>invoice due date</xs:documentation> ELEMENT Page 31
32 used by complextype ClientType facets maxlength 60 Client source <xs:element name=" "> <xs:documentation>client </xs:documentation> <xs:maxlength value="60"/> ELEMENT ENTRYDATE xs:date used by complextype HeaderType Entry date source <xs:element name="entrydate" ="xs:date"> <xs:documentation>entry date</xs:documentation> ELEMENT FAX used by complextype ClientType facets maxlength 25 Client faxnumber source <xs:element name="fax"> <xs:documentation>client faxnumber</xs:documentation> <xs:maxlength value="25"/> ELEMENT FILENAME xs:string Page 32
33 used by element Xml2WinEUR Xml file name source <xs:element name="filename" ="xs:string"> <xs:documentation>xml file name</xs:documentation> ELEMENT FOREX extension of xs:boolean properties content complex used by complextypes ClientType GeneralLedgerAccountType Revaluation of exchange rates. source <xs:element name="forex"> <xs:documentation>revaluation of exchange rates.</xs:documentation> <xs:complextype> <xs:simplecontent> <xs:extension base="xs:boolean"/> </xs:simplecontent> </xs:complextype> ELEMENT GAINSONEXCHANGEACCOUNT used by complextypes ClientType GeneralLedgerAccountType facets maxlength 15 Feneral ledger account : Gains on exchange source <xs:element name="gainsonexchangeaccount"> <xs:documentation>feneral ledger account : Gains on exchange</xs:documentation> <xs:maxlength value="15"/> ELEMENT INVOICEBANKCODE Page 33
34 used by complextype ClientLineType facets maxlength 15 Invoice bank code source <xs:element name="invoicebankcode"> <xs:documentation>invoice bank code</xs:documentation> <xs:maxlength value="15"/> ELEMENT INVOICEDATE xs:date used by complextypes ClientLineType InvoiceType Invoice date source <xs:element name="invoicedate" ="xs:date"> <xs:documentation>invoice date</xs:documentation> ELEMENT INVOICEDUEDATE xs:date used by complextype ClientLineType Invoice due date source <xs:element name="invoiceduedate" ="xs:date"> <xs:documentation>invoice due date</xs:documentation> ELEMENT INVOICENUMBER xs:string used by complextype ClientLineType Invoice number source <xs:element name="invoicenumber" ="xs:string"> Page 34
35 <xs:documentation>invoice number</xs:documentation> ELEMENT INVOICETEXT used by complextype ClientLineType facets maxlength 30 Invoice text source <xs:element name="invoicetext"> <xs:documentation>invoice text</xs:documentation> <xs:maxlength value="30"/> ELEMENT JOURNALCODE xs:string used by complextype HeaderType Journal code source <xs:element name="journalcode" ="xs:string"> <xs:documentation>journal code</xs:documentation> ELEMENT LANGUAGE used by complextype ClientType facets maxlength 3 Client language source <xs:element name="language"> <xs:documentation>client language</xs:documentation> Page 35
36 <xs:maxlength value="3"/> ELEMENT LOSSESONEXCHANGEACCOUNT used by complextypes ClientType GeneralLedgerAccountType facets maxlength 15 General ledger account : Losses on exchange source <xs:element name="lossesonexchangeaccount"> <xs:documentation>general ledger account : Losses on exchange</xs:documentation> <xs:maxlength value="15"/> ELEMENT MASTERANALYTICALACCOUNT used by complextype AnalyticalAccountType facets maxlength 15 Specific source <xs:element name="masteranalyticalaccount"> <xs:documentation>specific</xs:documentation> <xs:maxlength value="15"/> ELEMENT NAME used by complextype ClientType facets maxlength 30 Page 36
37 annotation source documentation Client name <xs:element name="name"> <xs:documentation>client name</xs:documentation> <xs:maxlength value="30"/> ELEMENT NETMASSKG xs:decimal used by complextype InvoiceVATInformationType Not used source <xs:element name="netmasskg" ="xs:decimal"> <xs:documentation>not used</xs:documentation> ELEMENT NUMBER xs:string used by complextype InvoiceType Invoice number source <xs:element name="number" ="xs:string"> <xs:documentation>invoice number</xs:documentation> ELEMENT OCCYAMOUNT xs:decimal used by complextypes ClientLineType GeneralLedgerLineType InvoiceType Amount in original currency source <xs:element name="occyamount" ="xs:decimal"> <xs:documentation>amount in original currency</xs:documentation> Page 37
38 ELEMENT OCCYBALANCE xs:decimal used by complextype InvoiceType Invoice balance Amount in original currency source <xs:element name="occybalance" ="xs:decimal"> <xs:documentation>invoice balance Amount in original currency</xs:documentation> ELEMENT OCCYPAYMENT xs:decimal used by complextype InvoiceType Invoice payment Amount in original currency source <xs:element name="occypayment" ="xs:decimal"> <xs:documentation>invoice payment Amount in original currency</xs:documentation> ELEMENT PAYMENT xs:string used by complextype ClientType Payment terms source <xs:element name="payment" ="xs:string"> <xs:documentation>payment terms</xs:documentation> ELEMENT PAYMENTDATE Page 38
39 xs:date used by complextype InvoiceType Invoice payment date source <xs:element name="paymentdate" ="xs:date"> <xs:documentation>invoice payment date</xs:documentation> ELEMENT PHONE used by complextype ClientType facets maxlength 25 Client phone number source <xs:element name="phone"> <xs:documentation>client phone number</xs:documentation> <xs:maxlength value="25"/> ELEMENT PRINTCODE used by complextype AnalyticalAccountType facets maxlength 3 Analytical Print code source <xs:element name="printcode"> <xs:documentation>analytical Print code</xs:documentation> <xs:maxlength value="3"/> ELEMENT SUBLEDGERACCOUNT Page 39
40 used by complextype ClientType facets maxlength 15 Client sub ledger control account source <xs:element name="subledgeraccount"> <xs:documentation>client sub ledger control account</xs:documentation> <xs:maxlength value="15"/> ELEMENT SUBTYPE used by complextype GeneralLedgerAccountType facets enumeration NormalAccount enumeration Sub LedgerControlAccount enumeration InventoryAccount enumeration Class enumeration Group enumeration SubClass enumeration SubGroup enumeration SecuritiesAccount Account sub source <xs:element name="subtype"> <xs:documentation>account sub </xs:documentation> <xs:enumeration value="normalaccount"/> <xs:enumeration value="sub LedgerControlAccount"/> <xs:enumeration value="inventoryaccount"/> <xs:enumeration value="class"/> <xs:enumeration value="group"/> <xs:enumeration value="subclass"/> <xs:enumeration value="subgroup"/> <xs:enumeration value="securitiesaccount"/> ELEMENT TAXCODE Page 40
41 xs:string used by complextypes ClientLineType ClientType InvoiceType Tax code source <xs:element name="taxcode" ="xs:string"> <xs:documentation>tax code</xs:documentation> ELEMENT TEXT used by complextypes GeneralLedgerAccountType InvoiceType facets maxlength 30 Account description source <xs:element name="text"> <xs:documentation>account description</xs:documentation> <xs:maxlength value="30"/> ELEMENT TEXTLINE1 used by complextypes ClientLineType GeneralLedgerLineType facets maxlength 30 Entry line 1 source <xs:element name="textline1"> <xs:documentation>entry line 1</xs:documentation> <xs:maxlength value="30"/> ELEMENT TEXTLINE2 Page 41
42 used by complextypes ClientLineType GeneralLedgerLineType facets maxlength 30 Entry line 2 source <xs:element name="textline2"> <xs:documentation>entry line 2</xs:documentation> <xs:maxlength value="30"/> ELEMENT TRANSCORBANKACCOUNT used by complextype InvoiceVATInformationType facets maxlength 15 Not used source <xs:element name="transcorbankaccount"> <xs:documentation>not used</xs:documentation> <xs:maxlength value="15"/> ELEMENT TYPE used by complextypes ClientLineType GeneralLedgerAccountType GeneralLedgerLineType facets enumeration DEBIT enumeration CREDIT Type source <xs:element name="type"> <xs:documentation>type </xs:documentation> <xs:enumeration value="debit"/> Page 42
43 <xs:enumeration value="credit"/> ELEMENT TYPEOFINVOICE used by complextype InvoiceType facets enumeration CustomerCreditNote enumeration PurchaseInvoice enumeration SalesInvoice enumeration SupplierCreditNote enumeration SupplierDebitNote enumeration CustomerDebitNote Invoice (ex Supplier invoice, custommer credit note...) source <xs:element name="typeofinvoice"> <xs:documentation>invoice (ex Supplier invoice, custommer credit note...)</xs:documentation> <xs:enumeration value="customercreditnote"/> <xs:enumeration value="purchaseinvoice"/> <xs:enumeration value="salesinvoice"/> <xs:enumeration value="suppliercreditnote"/> <xs:enumeration value="supplierdebitnote"/> <xs:enumeration value="customerdebitnote"/> ELEMENT VALUEDATE xs:date used by complextype HeaderType Value date source <xs:element name="valuedate" ="xs:date"> <xs:documentation>value date</xs:documentation> ELEMENT VATNUMBER Page 43
44 used by complextype ClientType facets maxlength 15 Client VAT number source <xs:element name="vatnumber"> <xs:documentation>client VAT number</xs:documentation> <xs:maxlength value="15"/> ELEMENT VATNUMBERUSEDBYTRANSCOR used by complextype InvoiceVATInformationType facets maxlength 15 Not used source <xs:element name="vatnumberusedbytranscor"> <xs:documentation>not used</xs:documentation> <xs:maxlength value="15"/> ELEMENT VERSION used by element Xml2WinEUR facets enumeration A001 Format version : constant should be A001 source <xs:element name="version"> <xs:documentation>format version : constant should be A001</xs:documentation> <xs:enumeration value="a001"/> Page 44
45 ELEMENT VOUCHER xs:string used by complextype HeaderType Entry voucher source <xs:element name="voucher" ="xs:string"> <xs:documentation>entry voucher</xs:documentation> ELEMENT WEBSITE used by complextype ClientType facets maxlength 60 Client Web site source <xs:element name="website"> <xs:documentation>client Web site</xs:documentation> <xs:maxlength value="60"/> ELEMENT XML2WINEUR Page 45
46 properties content complex children Version FileName GeneralLedgerAccounts AnalyticalAccounts Clients Invoices Entries XML Root source <xs:element name="xml2wineur"> <xs:documentation>xml Root</xs:documentation> <xs:complextype> <xs:sequence> <xs:element ref="version"> <xs:documentation>format version : constant should be A001</xs:documentation> <xs:element ref="filename" minoccurs="0"> <xs:documentation>xml file name</xs:documentation> <xs:element name="generalledgeraccounts" ="GeneralLedgerAccountsType" minoccurs="0"> <xs:documentation>contain all definition of general ledger accounts used in entries element</xs:documentation> <xs:element name="analyticalaccounts" ="AnalyticalAccountsType" minoccurs="0"> <xs:documentation>contain all definition of analytical accounts used in entries element</xs:documentation> <xs:element name="clients" ="ClientsType" minoccurs="0"> <xs:documentation>contain all definition of clients (Customers/Suppliers) used in entries element</xs:documentation> <xs:element name="invoices" ="InvoicesType" minoccurs="0"> <xs:documentation>not used for import. Contain all definition of invoices used in entries element</xs:documentation> Page 46
47 <xs:element name="entries" ="EntriesType" minoccurs="0"> <xs:documentation>contain all definition of accounting entries</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT XML2WINEUR/GENERALLEDGERACCOUNTS GeneralLedgerAccountsType properties isref 0 minocc 0 maxocc 1 content complex children GeneralLedgerAccount Contain all definition of general ledger accounts used in entries element source <xs:element name="generalledgeraccounts" ="GeneralLedgerAccountsType" minoccurs="0"> <xs:documentation>contain all definition of general ledger accounts used in entries element</xs:documentation> ELEMENT XML2WINEUR/ANALYTICALACCOUNTS AnalyticalAccountsType properties isref 0 minocc 0 maxocc 1 content complex children AnalyticalAccount Contain all definition of analytical accounts used in entries element source <xs:element name="analyticalaccounts" ="AnalyticalAccountsType" minoccurs="0"> <xs:documentation>contain all definition of analytical accounts used in entries element</xs:documentation> ELEMENT XML2WINEUR/CLIENTS Page 47
48 ClientsType properties isref 0 minocc 0 maxocc 1 content complex children client Contain all definition of clients (Customers/Suppliers) used in entries element source <xs:element name="clients" ="ClientsType" minoccurs="0"> <xs:documentation>contain all definition of clients (Customers/Suppliers) used in entries element</xs:documentation> ELEMENT XML2WINEUR/INVOICES InvoicesType properties isref 0 minocc 0 maxocc 1 content complex children Invoice Not used for import. Contain all definition of invoices used in entries element source <xs:element name="invoices" ="InvoicesType" minoccurs="0"> <xs:documentation>not used for import. Contain all definition of invoices used in entries element</xs:documentation> ELEMENT XML2WINEUR/ENTRIES EntriesType properties isref 0 minocc 0 maxocc 1 content complex Page 48
49 children annotation source Entry documentation Contain all definition of accounting entries <xs:element name="entries" ="EntriesType" minoccurs="0"> <xs:documentation>contain all definition of accounting entries</xs:documentation> COMPLEXTYPE ADDRESSESTYPE children Address used by element ClientType/Addresses source <xs:complextype name="addressestype"> <xs:sequence> <xs:element name="address" ="AddressType" maxoccurs="unbounded"> <xs:documentation>contain one client address</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT ADDRESSESTYPE/ADDRESS AddressType properties isref 0 minocc 1 maxocc unbounded content complex children AddressLine1 AddressLine2 AddressLine3 AddressLine4 AddressLine5 Contain one client address source <xs:element name="address" ="AddressType" maxoccurs="unbounded"> <xs:documentation>contain one client address</xs:documentation> Page 49
50 COMPLEXTYPE ADDRESSTYPE children AddressLine1 AddressLine2 AddressLine3 AddressLine4 AddressLine5 used by element AddressesType/Address source <xs:complextype name="addresstype"> <xs:sequence> <xs:element ref="addressline1"> <xs:documentation>client address line 1</xs:documentation> <xs:element ref="addressline2" minoccurs="0"> <xs:documentation>client address line 2</xs:documentation> <xs:element ref="addressline3" minoccurs="0"> <xs:documentation>client address line 3</xs:documentation> <xs:element ref="addressline4" minoccurs="0"> <xs:documentation>client address line 4</xs:documentation> <xs:element ref="addressline5" minoccurs="0"> <xs:documentation>client address line 5</xs:documentation> </xs:sequence> </xs:complextype> COMPLEXTYPE ANALYTICALACCOUNTSTYPE children AnalyticalAccount Page 50
51 used by element Xml2WinEUR/AnalyticalAccounts source <xs:complextype name="analyticalaccountstype"> <xs:documentation> </xs:documentation> <xs:sequence> <xs:element name="analyticalaccount" ="AnalyticalAccountType" maxoccurs="unbounded"> <xs:documentation>contain definition of one analytical account.</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT ANALYTICALACCOUNTSTYPE/ANALYTICALACCOUNT AnalyticalAccountType properties isref 0 minocc 1 maxocc unbounded content complex children AnalyticalAccount Currency AnalyticalType MasterAnalyticalAccount Description1 Description2 Description3 PrintCode used by complextypes AnalyticalAccountType ClientLineType GeneralLedgerLineType InvoiceType Contain definition of one analytical account. source <xs:element name="analyticalaccount" ="AnalyticalAccountType" maxoccurs="unbounded"> <xs:documentation>contain definition of one analytical account.</xs:documentation> Page 51
52 COMPLEXTYPE ANALYTICALACCOUNTTYPE children AnalyticalAccount Currency AnalyticalType MasterAnalyticalAccount Description1 Description2 Description3 PrintCode used by element AnalyticalAccountsType/AnalyticalAccount Contain all analytical accounts source <xs:complextype name="analyticalaccounttype"> <xs:documentation>contain all analytical accounts</xs:documentation> <xs:sequence minoccurs="0"> <xs:element ref="analyticalaccount"/> <xs:element ref="currency"/> <xs:element ref="analyticaltype" minoccurs="0"> <xs:documentation>specific field</xs:documentation> <xs:element ref="masteranalyticalaccount" minoccurs="0"> <xs:documentation>specific field</xs:documentation> <xs:element ref="description1"> <xs:documentation>analytical desrciption</xs:documentation> <xs:element ref="description2" minoccurs="0"> <xs:documentation>analytical description line 2</xs:documentation> <xs:element ref="description3" minoccurs="0"> Page 52
53 <xs:documentation>analytical description line 3</xs:documentation> <xs:element ref="printcode" minoccurs="0"> <xs:documentation>analytical print code</xs:documentation> </xs:sequence> </xs:complextype> COMPLEXTYPE CLIENTLINETYPE Page 53
54 children Type ClientCode ClientCurrency ClientSubledgerAccount InvoiceNumber InvoiceText InvoiceDate InvoiceDuedate InvoiceBankCode InvoiceVATInformation TaxCode AnalyticalAccount AnalyticalCurrency AnalyticalAmount TextLine1 TextLine2 OccyAmount BccyAmount Page 54
55 used by element EntryType/ClientLine source <xs:complextype name="clientlinetype"> <xs:sequence> <xs:element ref="type"> <xs:documentation>line : DEBIT / CREDIT</xs:documentation> <xs:element ref="clientcode"> <xs:documentation>client code</xs:documentation> <xs:element ref="clientcurrency"/> <xs:element ref="clientsubledgeraccount"> <xs:documentation>client sub ledger control account</xs:documentation> <xs:element ref="invoicenumber"> <xs:documentation>invoice number</xs:documentation> <xs:element ref="invoicetext" minoccurs="0"> <xs:documentation>invoice text</xs:documentation> <xs:element ref="invoicedate"> <xs:documentation>invoice date</xs:documentation> <xs:element ref="invoiceduedate" minoccurs="0"> <xs:documentation>invoice due date</xs:documentation> <xs:element ref="invoicebankcode" minoccurs="0"> <xs:documentation>invoice bank code</xs:documentation> <xs:element name="invoicevatinformation" ="InvoiceVATInformationType" minoccurs="0"> <xs:documentation>not used</xs:documentation> <xs:element ref="taxcode"> <xs:documentation>tax code</xs:documentation> <xs:element ref="analyticalaccount" minoccurs="0"/> <xs:element ref="analyticalcurrency" minoccurs="0"> <xs:documentation>iso currency code</xs:documentation> <xs:element ref="analyticalamount" minoccurs="0"> <xs:documentation>analytical amount in analytical currency</xs:documentation> <xs:element ref="textline1"> <xs:documentation>text line 1</xs:documentation> Page 55
56 <xs:element ref="textline2" minoccurs="0"> <xs:documentation>text line 2</xs:documentation> <xs:element ref="occyamount" minoccurs="0"/> <xs:element ref="bccyamount"/> </xs:sequence> </xs:complextype> ELEMENT CLIENTLINETYPE/INVOICEVATINFORMATION InvoiceVATInformationType properties isref 0 minocc 0 maxocc 1 content complex children Commodity NetMassKg TranscorBankAccount ClientVATNumber VATNumberUsedByTranscor Not used source <xs:element name="invoicevatinformation" ="InvoiceVATInformationType" minoccurs="0"> <xs:documentation>not used</xs:documentation> COMPLEXTYPE CLIENTSTYPE children client used by element Xml2WinEUR/Clients source <xs:complextype name="clientstype"> <xs:sequence> <xs:element name="client" ="ClientType" maxoccurs="unbounded"> <xs:documentation>contain definition of one client</xs:documentation> Page 56
57 </xs:sequence> </xs:complextype> ELEMENT CLIENTSTYPE/CLIENT Page 57
58 ClientType properties isref 0 minocc 1 Page 58
59 children annotation source maxocc unbounded content complex Code Currency SubledgerAccount Name Language CustomerFlag VatNumber Forex AmountStoreValue GainsOnExchangeAccount LossesOnExchangeAccount TaxCode Payment Phone Fax WebSite Bank BankAccount BankAddress1 BankAddress2 BankAddress3 BankAddress4 BankAddress5 Addresses documentation Contain definition of one client <xs:element name="client" ="ClientType" maxoccurs="unbounded"> <xs:documentation>contain definition of one client</xs:documentation> COMPLEXTYPE CLIENTTYPE Page 59
60 children Code Currency SubledgerAccount Name Language CustomerFlag VatNumber Forex AmountStoreValue GainsOnExchangeAccount LossesOnExchangeAccount TaxCode Payment Phone Fax WebSite Bank BankAccount BankAddress1 BankAddress2 BankAddress3 BankAddress4 BankAddress5 Addresses Page 60
61 used by element ClientsType/client Custommer or Supplier source <xs:complextype name="clienttype"> <xs:documentation>custommer or Supplier</xs:documentation> <xs:sequence> <xs:element ref="code"> <xs:documentation>client code</xs:documentation> <xs:element ref="currency"/> <xs:element ref="subledgeraccount"> <xs:documentation>client sub ledger control account</xs:documentation> <xs:element ref="name"> <xs:documentation>client name</xs:documentation> <xs:element ref="language"> <xs:documentation>language</xs:documentation> <xs:element ref="customerflag"> <xs:documentation>yes = customer / No = supplier</xs:documentation> <xs:element ref="vatnumber" minoccurs="0"> <xs:documentation>vat number of the client</xs:documentation> <xs:element ref="forex" minoccurs="0"> <xs:documentation>revaluation of exchange rates. (If client currency different of book keeping currency)</xs:documentation> <xs:element ref="amountstorevalue" minoccurs="0"> <xs:documentation>revalued amounts. (If client currency different of book keeping currency)</xs:documentation> <xs:element ref="gainsonexchangeaccount" minoccurs="0"> <xs:documentation>general ledger account gains. (If account currency different of book keeping currency)</xs:documentation> <xs:element ref="lossesonexchangeaccount" minoccurs="0"> <xs:documentation>general ledger account losses. (If account currency different of book keeping currency)</xs:documentation> <xs:element ref="taxcode"> <xs:documentation>tax code of the client</xs:documentation> <xs:element ref="payment"> <xs:documentation>payment terms of the client</xs:documentation> Page 61
62 <xs:element ref="phone" minoccurs="0"> <xs:documentation>phone number</xs:documentation> <xs:element ref="fax" minoccurs="0"> <xs:documentation>fax number</xs:documentation> <xs:element ref=" " minoccurs="0"> <xs:documentation> </xs:documentation> <xs:element ref="website" minoccurs="0"> <xs:documentation>web site</xs:documentation> <xs:element ref="bank" minoccurs="0"> <xs:documentation>client bank</xs:documentation> <xs:element ref="bankaccount" minoccurs="0"> <xs:documentation>client bank account</xs:documentation> <xs:element ref="bankaddress1" minoccurs="0"> <xs:documentation>client bank address line 1</xs:documentation> <xs:element ref="bankaddress2" minoccurs="0"> <xs:documentation>client bank address line 2</xs:documentation> <xs:element ref="bankaddress3" minoccurs="0"> <xs:documentation>client bank address line 3</xs:documentation> <xs:element ref="bankaddress4" minoccurs="0"> <xs:documentation>client bank address line 4</xs:documentation> <xs:element ref="bankaddress5" minoccurs="0"> <xs:documentation>client bank address line 5</xs:documentation> <xs:element name="addresses" ="AddressesType" minoccurs="0"> <xs:documentation>contain client addresses</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT CLIENTTYPE/ADDRESSES Page 62
63 AddressesType properties isref 0 minocc 0 maxocc 1 content complex children Address Contain client addresses source <xs:element name="addresses" ="AddressesType" minoccurs="0"> <xs:documentation>contain client addresses</xs:documentation> COMPLEXTYPE ENTRIESTYPE children Entry used by element Xml2WinEUR/Entries source <xs:complextype name="entriestype"> <xs:sequence> <xs:element name="entry" ="EntryType" maxoccurs="unbounded"> <xs:documentation>contain definition of one entry</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT ENTRIESTYPE/ENTRY EntryType properties isref 0 minocc 1 Page 63
64 children annotation source maxocc unbounded content complex Header GeneralLedgerLine ClientLine documentation Contain definition of one entry <xs:element name="entry" ="EntryType" maxoccurs="unbounded"> <xs:documentation>contain definition of one entry</xs:documentation> COMPLEXTYPE ENTRYTYPE children Header GeneralLedgerLine ClientLine used by element EntriesType/Entry source <xs:complextype name="entrytype"> <xs:sequence maxoccurs="unbounded"> <xs:element name="header" ="HeaderType"> <xs:documentation>contain all informations of entry header</xs:documentation> <xs:element name="generalledgerline" ="GeneralLedgerLineType" minoccurs="0" maxoccurs="unbounded"> <xs:documentation>contain all definition of general ledger line</xs:documentation> <xs:element name="clientline" ="ClientLineType" minoccurs="0" maxoccurs="unbounded"> <xs:documentation>contain all definition of client line</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT ENTRYTYPE/HEADER Page 64
65 HeaderType properties isref 0 content complex children EntryDate ValueDate Voucher JournalCode Contain all informations of entry header source <xs:element name="header" ="HeaderType"> <xs:documentation>contain all informations of entry header</xs:documentation> ELEMENT ENTRYTYPE/GENERALLEDGERLINE Page 65
66 GeneralLedgerLineType properties isref 0 minocc 0 maxocc unbounded content complex children Type Account Currency AnalyticalAccount AnalyticalCurrency AnalyticalAmount TextLine1 TextLine2 OccyAmount BccyAmount Contain all definition of general ledger line source <xs:element name="generalledgerline" ="GeneralLedgerLineType" minoccurs="0" maxoccurs="unbounded"> <xs:documentation>contain all definition of general ledger line</xs:documentation> ELEMENT ENTRYTYPE/CLIENTLINE Page 66
67 ClientLineType properties isref 0 minocc 0 Page 67
68 children annotation source maxocc unbounded content complex Type ClientCode ClientCurrency ClientSubledgerAccount InvoiceNumber InvoiceText InvoiceDate InvoiceDuedate InvoiceBankCode InvoiceVATInformation TaxCode AnalyticalAccount AnalyticalCurrency AnalyticalAmount TextLine1 TextLine2 OccyAmount BccyAmount documentation Contain all definition of client line <xs:element name="clientline" ="ClientLineType" minoccurs="0" maxoccurs="unbounded"> <xs:documentation>contain all definition of client line</xs:documentation> COMPLEXTYPE GENERALLEDGERACCOUNTSTYPE children GeneralLedgerAccount used by element Xml2WinEUR/GeneralLedgerAccounts source <xs:complextype name="generalledgeraccountstype"> <xs:sequence> <xs:element name="generalledgeraccount" ="GeneralLedgerAccountType" maxoccurs="unbounded"> <xs:documentation>contain definition of one general ledger account</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT GENERALLEDGERACCOUNTSTYPE/GENERALLEDGERACCOUNT Page 68
69 GeneralLedgerAccountType properties isref 0 minocc 1 maxocc unbounded content complex children Account Type SubType Currency Text Forex AmountStoreValue GainsOnExchangeAccount LossesOnExchangeAccount AnalysisSplit Contain definition of one general ledger account source <xs:element name="generalledgeraccount" ="GeneralLedgerAccountType" maxoccurs="unbounded"> <xs:documentation>contain definition of one general ledger account</xs:documentation> COMPLEXTYPE GENERALLEDGERACCOUNTTYPE Page 69
70 children Account Type SubType Currency Text Forex AmountStoreValue GainsOnExchangeAccount LossesOnExchangeAccount AnalysisSplit used by element GeneralLedgerAccountsType/GeneralLedgerAccount source <xs:complextype name="generalledgeraccounttype"> <xs:sequence> <xs:element ref="account"/> <xs:element ref="type"> <xs:documentation>account : assets liabilities, cost, income</xs:documentation> <xs:element ref="subtype"> <xs:documentation>contain the sub of the sublegeder account : Normal account or Sub ledger control account.</xs:documentation> <xs:element ref="currency"/> <xs:element ref="text"> <xs:documentation>account description</xs:documentation> <xs:element ref="forex" minoccurs="0"> <xs:documentation>revaluation of exchange rates. (If account currency different of accounting currency)</xs:documentation> Page 70
71 <xs:element ref="amountstorevalue" minoccurs="0"> <xs:documentation>revalued amounts. (If account currency different of book keeping currency)</xs:documentation> <xs:element ref="gainsonexchangeaccount" minoccurs="0"> <xs:documentation>general ledger account gains. (If account currency different of book keeping currency)</xs:documentation> <xs:element ref="lossesonexchangeaccount" minoccurs="0"> <xs:documentation>general ledger account losses. (If account currency different of book keeping currency</xs:documentation> <xs:element ref="analysissplit" minoccurs="0"> <xs:documentation>contain the rule of analysis split. (ex Obligartory, optional, no split)</xs:documentation> </xs:sequence> </xs:complextype> COMPLEXTYPE GENERALLEDGERLINETYPE children Type Account Currency AnalyticalAccount AnalyticalCurrency AnalyticalAmount TextLine1 TextLine2 OccyAmount BccyAmount used by element EntryType/GeneralLedgerLine Page 71
72 source <xs:complextype name="generalledgerlinetype"> <xs:sequence> <xs:element ref="type"> <xs:documentation>line : DEBIT / CREDIT</xs:documentation> <xs:element ref="account"/> <xs:element ref="currency"/> <xs:element ref="analyticalaccount" minoccurs="0"/> <xs:element ref="analyticalcurrency" minoccurs="0"> <xs:documentation>analytical Iso currency code</xs:documentation> <xs:element ref="analyticalamount" minoccurs="0"> <xs:documentation>analytical amount in analytical currency</xs:documentation> <xs:element ref="textline1"> <xs:documentation>entry line 1</xs:documentation> <xs:element ref="textline2" minoccurs="0"> <xs:documentation>entry line 2</xs:documentation> <xs:element ref="occyamount" minoccurs="0"/> <xs:element ref="bccyamount"/> </xs:sequence> </xs:complextype> COMPLEXTYPE HEADERTYPE children EntryDate ValueDate Voucher JournalCode used by element EntryType/Header source <xs:complextype name="headertype"> <xs:sequence> <xs:element ref="entrydate"> <xs:documentation>entry date</xs:documentation> <xs:element ref="valuedate"> <xs:documentation>entry value date</xs:documentation> Page 72
73 <xs:element ref="voucher" minoccurs="0"> <xs:documentation>entry voucher</xs:documentation> <xs:element ref="journalcode" minoccurs="0"> <xs:documentation>journal code</xs:documentation> </xs:sequence> </xs:complextype> COMPLEXTYPE INVOICESTYPE children Invoice used by element Xml2WinEUR/Invoices source <xs:complextype name="invoicestype"> <xs:sequence> <xs:element name="invoice" ="InvoiceType" maxoccurs="unbounded"> <xs:documentation>not used for import. Contain one definition of invoice</xs:documentation> </xs:sequence> </xs:complextype> ELEMENT INVOICESTYPE/INVOICE Page 73
74 InvoiceType properties isref 0 minocc 1 maxocc unbounded content complex Page 74
Altova XMLSpy 2007 Tutorial
Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage
Altova XMLSpy 2013 Tutorial
Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage
markup language carry data define your own tags self-descriptive W3C Recommendation
XML intro What is XML? XML stands for EXtensible Markup Language XML is a markup language much like HTML XML was designed to carry data, not to display data XML tags are not predefined. You must define
Altova XMLSpy 2014 Tutorial
Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage
Altova XMLSpy Tutorial
Altova XMLSpy 2018 Tutorial All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or
Markup Languages. Lecture 4. XML Schema
Markup Languages Lecture 4. XML Schema Introduction to XML Schema XML Schema is an XML-based alternative to DTD. An XML schema describes the structure of an XML document. The XML Schema language is also
ՕՐԻՆԱԿ XML extensible Markup Language
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
Software Engineering Methods, XML extensible Markup Language. Tutorial Outline. An Example File: Note.xml XML 1
extensible Markup Language Eshcar Hillel Sources: http://www.w3schools.com http://java.sun.com/webservices/jaxp/ learning/tutorial/index.html Tutorial Outline What is? syntax rules Schema Document Object
Schema U4IS_IM_Customer.xsd
Schema U4IS_IM_Customer.xsd schema location: attributeformdefault: elementformdefault: targetnamespace: http://services.agresso.com/u4is/customer/3/u4is_im_customer.xsd qualified http://services.agresso.com/u4is/customer/3
X3D Unit Specification Updates Myeong Won Lee The University of Suwon
X3D Unit Specification Updates Myeong Won Lee The University of Suwon 1 Units Specification ISO_IEC_19775_1_2008_WD3_Am1_2011_04_14 PDAM in ISO progress UNIT statement Defined in Core component UNIT statements
XML. Document Type Definitions XML Schema. Database Systems and Concepts, CSCI 3030U, UOIT, Course Instructor: Jarek Szlichta
XML Document Type Definitions XML Schema 1 XML XML stands for extensible Markup Language. XML was designed to describe data. XML has come into common use for the interchange of data over the Internet.
XML (Extensible Markup Language)
Basics of XML: What is XML? XML (Extensible Markup Language) XML stands for Extensible Markup Language XML was designed to carry data, not to display data XML tags are not predefined. You must define your
MANAGING INFORMATION (CSCU9T4) LECTURE 2: XML STRUCTURE
MANAGING INFORMATION (CSCU9T4) LECTURE 2: XML STRUCTURE Gabriela Ochoa http://www.cs.stir.ac.uk/~goc/ OUTLINE XML Elements vs. Attributes Well-formed vs. Valid XML documents Document Type Definitions (DTDs)
XML Schema. Mario Alviano A.Y. 2017/2018. University of Calabria, Italy 1 / 28
1 / 28 XML Schema Mario Alviano University of Calabria, Italy A.Y. 2017/2018 Outline 2 / 28 1 Introduction 2 Elements 3 Simple and complex types 4 Attributes 5 Groups and built-in 6 Import of other schemes
So far, we've discussed the use of XML in creating web services. How does this work? What other things can we do with it?
XML Page 1 XML and web services Monday, March 14, 2011 2:50 PM So far, we've discussed the use of XML in creating web services. How does this work? What other things can we do with it? XML Page 2 Where
Technical requirements
ANNEX 1: TECHNICAL REQUIREMENTS Technical requirements 1. Introduction... 2 2. Overview of the import formalities section of the market access database... 2 2.1. Architecture... 2 2.2. The dataset... 2
Brief guide for XML, XML Schema, XQuery for YAWL data perspective
Brief guide for XML, XML Schema, XQuery for YAWL data perspective Carmen Bratosin March 16, 2009 1 Data perspective in YAWL YAWL engine files are XML based. Therefore, YAWL uses XML for data perspective
NCLTEC Accounting User Manual
NCLTEC Accounting User Manual Latest Update: Feb 6, 0 For information about customer support, please visit our homepage at http://www.ncltec.com on the World Wide Web. Copyright 05 NCL Energy Technology
Exact General Ledger Setup and Operation
Exact General Ledger Setup and Operation In order to set up the General Ledger in EXACT you need to have already decided on how you want to operate your ledger and the format that the codes for the ledger
Semantic Web. XML and XML Schema. Morteza Amini. Sharif University of Technology Fall 94-95
ه عا ی Semantic Web XML and XML Schema Morteza Amini Sharif University of Technology Fall 94-95 Outline Markup Languages XML Building Blocks XML Applications Namespaces XML Schema 2 Outline Markup Languages
Schema schema-for-json.xsd
Schema schema-for-json.xsd schema location: attributeformdefault: elementformdefault: targetnamespace:..\schema-for-json.xsd qualified http://www.w3.org/2015/exi/json Elements Complex types Simple types
MYOB Exo InterCompany. User Guide
MYOB Exo InterCompany User Guide 2017.3 Table of Contents Features of the System... 1 Setup Overview... 2 Installing InterCompany... 2 Defining the Group Consolidation... 5 Defining Companies... 6 Defining
Introduction Syntax and Usage XML Databases Java Tutorial XML. November 5, 2008 XML
Introduction Syntax and Usage Databases Java Tutorial November 5, 2008 Introduction Syntax and Usage Databases Java Tutorial Outline 1 Introduction 2 Syntax and Usage Syntax Well Formed and Valid Displaying
Chapter 11 XML Data Modeling. Recent Development for Data Models 2016 Stefan Deßloch
Chapter 11 XML Data Modeling Recent Development for Data Models 2016 Stefan Deßloch Motivation Traditional data models (e.g., relational data model) primarily support structure data separate DB schema
ADD/EDIT A JOURNAL ENTRY
ADD/EDIT A JOURNAL ENTRY 1. In Intacct, journal entries are posted into specific journals, which function to categorically separate different types of journal entries. Journal entries can post to any of
The <schema> Element. <?xml version="1.0"?> <xs:schema>... </xs:schema>
DTD: Example
XML Spy Tutorial Lab Contents
XML Spy Tutorial Lab 1 An XML Schema is similar to DTD and created by Microsoft. It describes the structure of an XML document. If an XML document follows the XML Schema, it is said to be valid; otherwise
Restricting complextypes that have mixed content
Restricting complextypes that have mixed content Roger L. Costello October 2012 complextype with mixed content (no attributes) Here is a complextype with mixed content:
XML Format Plug-in User s Guide. Version 10g Release 3 (10.3)
XML Format Plug-in User s Guide Version 10g Release 3 (10.3) XML... 4 TERMINOLOGY... 4 CREATING AN XML FORMAT... 5 CREATING AN XML FORMAT BASED ON AN EXISTING XML MESSAGE FORMAT... 5 CREATING AN EMPTY
Introducing our First Schema
1 di 11 21/05/2006 10.24 Published on XML.com http://www.xml.com/pub/a/2000/11/29/schemas/part1.html See this if you're having trouble printing code examples Using W3C XML By Eric van der Vlist October
SANCRT SANITARY CERTIFICATE
Container positioning for inspection SANCRT SANITARY CERTIFICATE GUIDELINE FOR THE XML SANCRT MESSAGE Version 1.5 Message: SANCRT Version: 1.5 Date: February 2014 Source: Portic Barcelona
XML. Part II DTD (cont.) and XML Schema
XML Part II DTD (cont.) and XML Schema Attribute Declarations Declare a list of allowable attributes for each element These lists are called ATTLIST declarations Consists of 3 basic parts The ATTLIST keyword
Set 2 MCQ
1. ETCS means A) Enable Tax Collected at Source B) Electronic Tax Collected at Source C) Electric Tax Collected at Source D) None of these 2. To get Payroll Reports choose A) Gateway of Tally > Display
OpenTravel Alliance Best Practices
OpenTravel Alliance Best Practices OpenTravel Alliance, Inc. 333 John Carlyle Street, Suite 600 Alexandria, Va. 22314 USA +1 703-548-7005 Fax +1 703-548-1264 opentravel@disa.org http://www.opentravel.org/
Network Configuration Protocol
The (NETCONF) defines a simple mechanism through which a network device can be managed, configuration data can be retrieved, and new configuration data can be uploaded and manipulated. NETCONF uses Extensible
General Interface Control Document
SunGuide TM : General Interface Control Document SunGuide-General-ICD-3.0.1 Prepared for: Florida Department of Transportation Traffic Engineering and Operations Office 605 Suwannee Street, M.S. 90 Tallahassee,
Using the AVImark QuickBooks Interface
June 24, 2013 AVImark Software Support Address: 5 Sugar Creek Road Piedmont, MO 63957 Support Phone: 877.838.9273 Support Fax: 573.223.4306 Corporate Phone: 855.838.7638 Corporate Fax: 573.223.3551 Using
Java EE 7: Back-end Server Application Development 4-2
Java EE 7: Back-end Server Application Development 4-2 XML describes data objects called XML documents that: Are composed of markup language for structuring the document data Support custom tags for data
Oracle Fusion Cash Management Release 11. Solution for Loading Custom Format Bank Statements via XML and XSL
Oracle Fusion Cash Management Release 11 Solution for Loading Custom Format Bank Statements via XML and XSL TECHNICAL STEPS [ONE TIME] 1. Upload the XSL template into the BIP catalog where the ISO20022
TCG. TCG Infrastructure Working Group Security Qualities Schema. TCG PUBLISHED Copyright TCG 2007
TCG Infrastructure Working Group Security Qualities Schema Revision 7 21 May 2007 Published Contacts: admin@trustedcomputinggroup.org Copyright TCG 2007 TCG Copyright 2007 Trusted Computing Group, Incorporated.
Specification of contineo s REST Interface
Specification of contineo s REST Interface Sebastian Stein seb.stein@hpfsc.de 2007-02-07, contineo version 2.5 1 Contents 1 Introduction 3 2 General Concept 3 2.1 REST Web Service Interface..................
SMU Financials Created on April 29, 2011
Created on April 29, 2011 Notice 2011, Southern Methodist University. All Rights Reserved. Published 2011. The information contained in this document is proprietary to Southern Methodist University. This
XML Schema and alternatives
XML Schema and alternatives Patryk Czarnik XML and Applications 2016/2017 Lecture 4 24.03.2017 Some possibilities of XML Schema we have not learnt too much Deriving complex types by restriction restriction
Guide Lines for Offline Tools for Form-C Returns
Guide Lines for Offline Tools for Form-C Returns For Version 8.0 New Formats of Form-C Returns : Preparing Excel Sheets to be zipped using offline tool : 1. Download the Latest Excel Formats for Return
Access Online. Payment Upload
Access Online Payment Upload ABN AMRO Bank N.V. 2017 All rights reserved. Apart from those exceptions stipulated in or by virtue of the 1912 Copyright Law, no part of this publication may be reproduced
PESC Compliant JSON Version /19/2018. A publication of the Technical Advisory Board Postsecondary Electronic Standards Council
Version 0.5.0 10/19/2018 A publication of the Technical Advisory Board Postsecondary Electronic Standards Council 2018. All Rights Reserved. This document may be copied and furnished to others, and derivative
Fall, 2005 CIS 550. Database and Information Systems Homework 5 Solutions
Fall, 2005 CIS 550 Database and Information Systems Homework 5 Solutions November 15, 2005; Due November 22, 2005 at 1:30 pm For this homework, you should test your answers using Galax., the same XQuery
TED schemas. Governance and latest updates
TED schemas Governance and latest updates Enric Staromiejski Torregrosa Carmelo Greco 9 October 2018 Agenda 1. Objectives 2. Scope 3. TED XSD 3.0.0 Technical harmonisation of all TED artefacts Code lists
Infor Enterprise Server User Guide for Triggering
Infor Enterprise Server User Guide for Triggering Copyright 2015 Infor Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential
Messages are securely encrypted using HTTPS. HTTPS is the most commonly used secure method of exchanging data among web browsers.
May 6, 2009 9:39 SIF Specifications SIF Implementation Specification The SIF Implementation Specification is based on the World Wide Web Consortium (W3C) endorsed Extensible Markup Language (XML) which
Evolution M Core Training Contract, Sales & Cash Book Issue 2
Evolution M Core Training Contract, Sales & Cash Book Issue 2 Contents Training............................................................................................ 1 Contract Ledger........................................................................................
MESH client File Interface Specification
Document filename: MESH Client File Interface Specification Directorate / Programme Operations and Project Assurance Services Spine Services/ MESH Document Reference Project Manager Andrew Meyer
2006 Martin v. Löwis. Data-centric XML. XML Schema (Part 1)
Data-centric XML XML Schema (Part 1) Schema and DTD Disadvantages of DTD: separate, non-xml syntax very limited constraints on data types (just ID, IDREF, ) no support for sets (i.e. each element type
Business e-banking Wires User Guide
User Guide Business e-banking User Guide Tables of Contents Entering a One Time Wire Transfer 2 Deleting a Wire Transfer 5 Add Wire Template...8 Wire Money via Templates...12 Wire Money via Multiple Templates.....15
MecWise Accounting Getting Started Kit
MecWise Accounting Getting Started Kit Last updated on: 10/14/2009 Getting Started How do I start enjoying MecWise Accounting? 1.1 Be familiar with the toolbar icons. 1.2 To maintain the company s basic
OpenTravel Alliance XML Schema Design Best Practices
OpenTravel Alliance XML Schema Design Best Practices Version 3.08 March 2010 OpenTravel Alliance Schema Design Best Practices Specification Page 2 Contents 1 OpenTravel XML Schema Design Best Practices...
PESC Compliant JSON Version /04/2019
Version 1.0.0 02/04/2019 A publication of the Technical Advisory Board, 2018. This document is released and all use of it is controlled under Creative Commons, specifically under an Attribution- ShareAlike
XML and Web Services
XML and Web Services Lecture 8 1 XML (Section 17) Outline XML syntax, semistructured data Document Type Definitions (DTDs) XML Schema Introduction to XML based Web Services 2 Additional Readings on XML
1/45. Guidance for the Standard Audit File - Payroll, Version 1.0: Appendix B: SAF-P Schema version element AuditFilePayroll
Guidance for the Standard Audit File - Payroll, Version 1.0: Appendix B: SAF-P Schema version 1.00 1/45 schema location: SAF-P_Schema_v_1.00.xsd attribute form default: element form default: targetnamespace:
OpenTravel Alliance XML Schema Design Best Practices
OpenTravel Alliance XML Schema Design Best Practices Version 3.02 3 December 2004 OpenTravel Alliance Best Practices Specification Page 2 1 OTA XML Schema Design Best Practices... 4 2 XML Standard Specifications...
How to Import Customers & Suppliers into SortMyBooks Online Pt 1.
How to Import Customers & Suppliers into SortMyBooks Online Pt 1. You can import your Customer and Suppliers address & contact details into SortMyBooks online from anywhere that can export them into.csv
Description de tous les champs du fichier de statut de retour pour l échange FATCA - version 0.4
Annexe 3 de la circulaire du directeur des contributions ECHA - n 3 (consolidée) du 18 février 2016 Description de tous les champs du fichier de statut de retour pour l échange FATCA - version 0.4 Introduction
This means that you can create the batch in excel as a.csv file and then import the.csv excel file into Sage Pastel accounting.
In Sage Pastel Accounting while you can import customer, supplier and inventory master information, you can also import certain batches like journals, cashbooks and customer and supplier documents. This
HCSS Accounting Guidance Year End Notes
HCSS Accounting Guidance Year End Notes Page 1 1. House keeping Housekeeping of transactions on HCSS Accounting can take place at any time, but is most important before running Year End. As part of the
BBPS API Sepcifications
BBPS API Sepcifications v11.0 BBPS API Sepcifications v11.0 Page 1 Table of Contents 1 Bill Fetch Request 4 Sample Bill Fetch Request API 4 Bill Fetch Request Tag Details 5 Bill Fetch Request XSD 6 2 Bill
Country-specific update for Belgium
Microsoft Dynamics AX 2009 SP1 Country-specific update for Belgium White Paper This white paper describes the country-specific update released for Belgium in hotfix rollup 7 for Microsoft Dynamics AX 2009
XMLSpy 2005 Home Edition
User Manual XMLSpy 2005 Home Edition All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping,
Last week we saw how to use the DOM parser to read an XML document. The DOM parser can also be used to create and modify nodes.
Distributed Software Development XML Schema Chris Brooks Department of Computer Science University of San Francisco 7-2: Modifying XML programmatically Last week we saw how to use the DOM parser to read
Express365 Accounting User Manual
Express365 Accounting User Manual August 05 Latest Update: 9 th October 08 P a g e 46 For information about customer support, please visit our homepage at http://www.express365.com.my on the World Wide
Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1. September 2017
Oracle Hospitality OPERA Web Self- Service Brochure Web Service Specification Version 5.1 September 2017 Copyright 1987, 2017, Oracle and/or its affiliates. All rights reserved. This software and related
1 9/8/2009 5:05 PM
http://www.pesc.org/library/docs/standards/h... 1 9/8/2009 5:05 PM This XML file does not appear to have any style information associated with it. The document tree is shown below. edited with XMLSpy v2006
<xs:element name="record" type="recordtype" maxoccurs="unbounded" /> </xs:sequence> </xs:complextype>
- -
1
www.clearbooks.co.uk 1 Content Clear Books Demo 1. Customising your Dashboard 2. Setting up for the first time A) Details B) Toggle Features C) Reporting Periods D) Adding a new user E) Invoice Themes
Business On Line File Gateway Guide
Business On Line File Gateway Guide This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document may not be reproduced or further distributed,
XML. Rail Events and Intermodal Ramp Activity
XML Rail Events and Intermodal Ramp Activity Message Implementation Guide Version 1.0.0 Change history Version Date Comments 1.0.0 10-Aug-2016 Initial version Contact our ecommerce team: Hamburg Süd Customer
Overview of the EU ETS Reporting Language (XETL)
Overview of the EU ETS Reporting Language (XETL) General The EU ETS Reporting Language is an electronic ing language supporting EU ETS Monitoring, Reporting and Validation (MRV) activities such as submitting
Download installation package and documentation Installation procedure. Network installation Installing updates
-Manual d-basics I Manual d-basics Table of Contents Chapter I Introduction 1 Chapter II Installation 3 1... Download installation package and documentation 4 2... Installation procedure 4 3... Registration
Oracle isupplier Guide Migrated Suppliers
Oracle isupplier Guide Migrated Suppliers A guide to getting started Version 2 Inside this guide Logging in and Changing your Password Amending your Address Updating your Contact Details Updating your
Session [2] Information Modeling with XSD and DTD
![Session [2] Information Modeling with XSD and DTD](/thumbs/72/67474201.jpg "Session [2] Information Modeling with XSD and DTD")
Session [2] Information Modeling with XSD and DTD September 12, 2000 Horst Rechner Q&A from Session [1] HTML without XML See Code HDBMS vs. RDBMS What does XDR mean? XML-Data Reduced Utilized in Biztalk
INBIZ HOW TO START? QUICK GUIDE
INBIZ HOW TO START? This document was created for you, the InBiz user, for your quick orientation in InBiz and to provide you with a brief and simple guide for using the basic InBiz functionalities. QUICK
HAL E-BANK MANUAL ADDITIONAL TOOLS AND SETTINGS. Hal E-Bank version: 20.X.X.01
HAL E-BANK MANUAL ADDITIONAL TOOLS AND SETTINGS Hal E-Bank version: 20.X.X.01 Content of Manual The manual consists of several content sections. The current section is highlighted on the list. The manual's
Backup / Restore TurboCASH FIXED
Table of Contents Backup / Restore TurboCASH5.0.0.307 FIXED...2 Registration Error on TurboCASH5.0.0.293...2 Help File...2 Updated...2 Updated Books...2 Updated Tutorials...3 Batch Entry Report Added...3
Jeff Offutt. SWE 642 Software Engineering for the World Wide Web
XML Advanced Topics Jeff Offutt http://www.cs.gmu.edu/~offutt/ SWE 642 Software Engineering for the World Wide Web sources: Professional Java Server Programming, Patzer, Wrox, 2 nd edition, Ch 5, 6 Programming
Guide Pagero Invoice Portal Create and send invoices
Guide Pagero Invoice Portal Create and send invoices 1. Log in to your Pagero Online account. 2. Click Create invoice 3. Choose the recipient you wish to send a document to, and the type of invoice you
SET UP A VOUCHER NUMBER STREAM
SET UP A VOUCHER NUMBER STREAM INTRODUCTION: Sun6 uses Voucher Numbering in association with Journal Types and in lieu of the familiar Ref2 Analysis Dimension. The Voucher Number is used as the Journal
XML Schema Element and Attribute Reference
E XML Schema Element and Attribute Reference all This appendix provides a full listing of all elements within the XML Schema Structures Recommendation (found at http://www.w3.org/tr/xmlschema-1/). The
XML and Content Management
XML and Content Management Lecture 3: Modelling XML Documents: XML Schema Maciej Ogrodniczuk, Patryk Czarnik MIMUW, Oct 18, 2010 Lecture 3: XML Schema XML and Content Management 1 DTD example (recall)
:PRIA_DOCUMENT_v2_4_1.XSD
==================================================================
Using and defining new simple types. Basic structuring of definitions. Copyright , Sosnoski Software Solutions, Inc. All rights reserved.
IRIS Web Services Workshop II Session 1 Wednesday AM, September 21 Dennis M. Sosnoski What is XML? Extensible Markup Language XML is metalanguage for markup Enables markup languages for particular domains
Great Plains 8.0 Integration Manager Payables Transaction Integration
Great Plains 8.0 Integration Manager Payables Transaction Integration Required Fields Voucher Number: Document Type: Vendor ID: Document Date: Document Number: Document Amount: The Voucher number of the
GENERAL LEDGER STANDARD JOURNAL ENTRY. 3. Procedure In the Financial Management dropdown, select the Journals function in the Journals submenu.
Procedure # GL - 1 General Ledger Standard Journal Entry Created By Emily Krambs 7/20/09 Revised By Donald Hein 1/8/14 Approved By GENERAL LEDGER STANDARD JOURNAL ENTRY 1. General Journal entries are used
Bank Reconciliation September 2016 P R E F A C E. This is the Bank Reconciliation reference guide for IQ Business & IQ Enterprise software systems.
BANK RECONCILIATION P R E F A C E This is the Bank Reconciliation reference guide for IQ Business & IQ Enterprise software systems. The document will aid in understanding and configuration of the Bank
Sage Live What s New November Release. Sage Connected Apps v1.31 Sage Live v52
Sage Live What s New November Release Sage Connected Apps v1.31 Sage Live v52 Table of Contents 1.0 Lightning 4 1.1 Overview 4 1.2 How to enable the Lightning Experience 4 1.3 Navigating the Lightning
XML. Truck Events and Transportation Carrier Shipment Status Message
XML Truck Events and Transportation Carrier Shipment Status Message Message Implementation Guide Version 1.0.0 Change history Version Date Comments 1.0.0 15-Aug-2016 Initial version Contact our ecommerce
Oracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On
Oracle Utilities Opower Energy Efficiency Web Portal - Classic Single Sign-On Configuration Guide E84772-01 Last Update: Monday, October 09, 2017 Oracle Utilities Opower Energy Efficiency Web Portal -
HAL E-BANK MANUAL REVIEW OF BALANCE, TRANSACTIONS AND STATEMENTS. Hal E-Bank version: 20.X.X.01
HAL E-BANK MANUAL REVIEW OF BALANCE, TRANSACTIONS AND STATEMENTS Hal E-Bank version: 20.X.X.01 Content of Manual The manual consists of several content sections. The current section is highlighted on the
Giro And Rentas & TT Interface From Biztrak to OCBC, By Accstream
Giro And Rentas & TT Interface From Biztrak to OCBC, By Accstream Features Highlight Automate Giro Text File creation from Biztrak Invoice Payment. Automate Rentas & TT Text File creation from Biztrak
AccountsIQ Tips and Tricks. Updated 20/10/2008. Purpose. 1. List and describe what heading and text will be containing in each of the Tip s and tricks
AccountsIQ Tips and Tricks Updated 20/10/2008 Purpose 1. List and describe what heading and text will be containing in each of the Tip s and tricks 2. Outline what FAQ s will be released on the System
Unit: Financials Topic: Manage the Chart of Accounts
Solutions Unit: Financials Topic: Manage the Chart of Accounts 1-1 Transactions Which function do you use to change the properties for a G/L account? Financials Chart of Accounts Which function do you