Whatever the action, an audit trail report is usually printed. This may include every action taken by the XML processor (if Report in Full was ticked for input applications) or just show errors and any entries forced for output to the audit trail report, such as any total values checked, whether correct or incorrect. The audit trail report should always be examined after an XML process, to check for any error conditions. If any errors are found, then decisions must be taken about how to handle them.
An example of an audit trail report (for input XML purchase invoices) is shown on the following page. The Report in Full option had been ticked, and many actions are reported here. There were a couple of invoices for which the purchase order was not recognised — so the invoices were ignored — and an invoice line where the order line wasn’t recognised. Ignored invoices were almost certainly the cause of the batch total errors.
The only occasion when an audit report will not be created is for an output XML process where no errors were encountered, or if output errors were marked to be ignored. In these cases the on-screen summary report tells you all you need to know.
Article ID: 1755 Created On: Thu, Jul 5, 2012 at 3:46 PM Last Updated On: Thu, Jun 22, 2023 at 4:38 PM