Codis APIs
- Demand the minimum data required, but optionally allow other data to be provided
- Default values are calculated when required
- Validate entered data, including cross-referencing to existing Sage data
- Provide optional transaction size at batch or item level
- Provide a set of methods to validate data fields independently of posting
Codis Table Import Facilities
- Not all column names need to be defined - the APIs generate default values
- A log file is updated (user selected name) showing details of the import and any errors encountered. Five different logging levels are available
- Updates to the Sage database can optionally be made only using complete and coherent transactions* ensuring items are not half written
- Processed flags can be used on the source table. Records are only marked as processed once the relevant Sage transaction is validated and successfully written to the Sage database
- Immediate validation whilst still in Excel (invalid data highlighted)
- For example, if an individual line of a Sales Invoice contains an invalid posting code, then the entire invoice update to Sage will be rolled back, and none of the input records will be marked as processed
- The import facilities are available as Microsoft DTS components, allowing integration into Microsoft DTS scripts
APIs Available Include
- Sales Invoices/Credit Notes
- Sales Cash (and allocations against invoices)
- Purchase Invoices
- General Ledger Journals
- Payroll Timesheets
- Customer Create
*Where the target Sage database provides this possibility (i.e. NT, Informix online, Oracle)
|