Exporting Sales Transactions from Sage 200
This task will export new, modified or all sales transactions in Sage 200 Transaction XML format. Sales transactions include invoices, credit notes, receipts and payments that have been raised against a customer account.
Note
If you want to export invoices, credit notes, receipts or payments associated with a supplier account, please use the Export Purchase Transactions task.
Settings
Sage 200 Connection
Required
The Sage 200 connection to use. See the Connecting to Sage 200 article if you require more information on how to create/manage connections
Characters To Cleanse
Optional
A list of characters to remove from the output file. Use this if your Sage data contains characters that are not valid for XML documents (e.g. �
).
Export Settings
Required
- Date Created - Used when exporting new records. Only records created after this date will be exported. The date will update automatically each time the task runs.
- Export Modified, New or All Records - Used to choose which records should be included in the export. Note that the 'Modified' setting will also export any new records.
- Op Lock - Used when exporting modified records. Only records where the Op Lock is greater than this value will be exported. The value will update automatically each time the task runs.
- When initially setting up the task, the Op Lock value will default to 0, this will export all records the first time that it runs.
- If you would like the integration to pick up all records modified from now on, enter a value of MAX into the Op Lock setting and press Enter, Zynk will attempt to read the current highest value from Sage 200. Please note that you need to have a connection set up to the Sage 200 company on the task, and the user that Zynk is running as must be able to access the company).
- Page Size - The maximum number of records in each batch read from Sage. Increasing this will speed up the export but use more memory. Defaults to 100.
- Timeout (seconds) - Specify the timeout for the task you're running. Defaults to 30.
- Use Caching - Will cache certain common types which could be referenced in mulitple places, to minimise the amount of database activity, and decrease to overall export time. This will use more memory, if you encounter out of memory issues, then try disabling this setting.
Query Settings
Optional
- Columns - Used to enter the column names to export from the Sage database. Be sure to include the table name eg.
[SLCustomerAccount].[CustomerAccountNumber]
- Joins - Allows data to be exported from other tables in the Sage database. Required when exporting data from tables not included in the standard export.
- Where Clauses - Allows filters to be set to limit the data that is exported.
Output File
Required
The file to save the exported records to, in Zynk XML format.
Zynk Settings
Examples
Sample output file:
<?xml version="1.0" encoding="utf-8"?>
<Company
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Transactions>
<Transaction>
<UniqueId>12944</UniqueId>
<TransactionType>SalesReceipt</TransactionType>
<AccountReference>ONBOARD</AccountReference>
<TransactionDate>2012-03-19T00:00:00</TransactionDate>
<DueDate xsi:nil="true" />
<PostedDate xsi:nil="true" />
<Reference>DXB_000003206C</Reference>
<PaymentReference>101000066426</PaymentReference>
<Details />
<NetAmount>1093.23</NetAmount>
<TaxRate xsi:nil="true" />
<TaxCode xsi:nil="true" />
<TaxAmount>0</TaxAmount>
<ElectronicTransaction xsi:nil="true" />
<OutstandingAmount>1093.23</OutstandingAmount>
<TransactionNumber>1</TransactionNumber>
<BankReference>1202</BankReference>
<Discount xsi:nil="true" />
<ExchangeRate xsi:nil="true" />
<VatInclusive xsi:nil="true" />
<CustomFields />
</Transaction>
</Transactions>
</Company>