(Module) > Utility > Data Interfaces ... (applicable interface) > View export error log
This utility displays the details of any errors that occurred when performing one of SpendMap's "direct integrations" (where SpendMap "pushes" data/transactions directly into another system). For more details, see Direct vs. Batch File Integration.
If a transaction could not be successfully sent to the other system, SpendMap will hold onto the transaction so that you can correct the issue and try again. Transactions that were successfully sent to the other system will NOT be listed here.
The list of unsuccessful transactions listed here is cumulative. If you continue to run the interface and errors continue to occur, the number of transactions shown here will increment.
This utility displays details of why the error occurred, which might include a problem with the data in the transactions themselves (e.g. an invalid supplier code, account code, etc.), or perhaps the target system is not configured properly to accept the applicable transactions. Once the issue is corrected (perhaps by correcting the invalid data in SpendMap, or perhaps by adjusting the settings in the target system, etc.), you can re-run the applicable interface to send the transactions that had failed (along with any new transactions that were processed since the last time the interface was run).
For more information on the integration tools in SpendMap, see Data Interfaces - Overview and General Information.
Transaction Error Summary Screen
This screen displays a cumulative list of transactions that could not be successfully sent to the target system. Depending on the type of transaction/interface, suggestions/tips for possible way to correct the issue(s) will be listed at the top of the screen.
To see additional details of a transaction, double-click on the transaction or use the [Details] button to go to the Transaction Error Details Screen. On the Details Screen, among other things you will see a description of why the error occurred, which would typically include error information that was fed back to SpendMap from the target system during the interface attempt. You can click on the error message to see additional details.
