Summary

The Re-export Related Data tool is used to re-export data from committed batches to the related database. This export tool is only enabled for organizations set up to use Multi-Muni relational databases.

This tool can help Multi-Muni organizations re-export any data that failed to import into the related database. For example, if an AP Invoices batch was committed in the child database, that batch data import could fail in the parent database because of a reference GL account not being active for the current fiscal year. In this situation, the issue with the GL account could be resolved and then the AP Invoices batch data could be re-exported through this process. This process does not create any new data in the database running the tool.

Step by Step

1     Open the Re-export Related Data window (SS> Utilities> Re-export Related Data).

2     Configure the export.

• The Batch Type drop-down menu is used to select the type of batch you would like to export.
  • In the parent database, this tool can export data from the AP Computer Checks, AP Void Checks, and AP Void Invoices batch processes.
  • In the child database, this tool can export data from the AP Invoices, CR Cash Receipts, PR Computer Checks, PR Manual Checks, PR Retro Pay, PR Void Checks, PR W-2s, and PR W-2 Adjustments batch processes.
• The Batch Number field is used to select the batch number you would like to include in the export.
  • Enter a batch number or click the field search button   to select one from a list. Only the batch of the type selected in the Batch Type field above will display in the window.
• The Batch Month, Batch Year, and Batch Name fields can also be used to filter the results displayed in the data grid below.

3     Export the data.

• Click the RE-EXPORT BATCH button when complete to generate the export data.
  • You can view the progress of the export on the Job Viewer window (SS> Utilities> Show Scheduled Jobs).
  • In order to prevent duplicate transactions, a validation message will be displayed and the batch in question will not be exported if it already exists in the target database.