Verifying an export

You can verify the exported system data from these sources:

  • If the export interface uses the WBINT_EXPORT staging table, you can view the Export Transactions page to verify the records in the staging table.
  • If the export interface produces a report, you can view the report for data validation.
  • After running the export task, view the Job Scheduler log for information about the export task run.

Verifying the export using the Export Transactions page

After the Job Scheduler runs the export task, you can determine the task status by viewing the Export Transactions page. The Export Transactions page displays each export transaction that uses the WBINT_EXPORT staging table. A status of either SUCCESS or FAILURE is indicated in the Export Transactions page for each export transaction. You can view the details of each transaction by clicking the Edit link next to the transaction entry to display the Export Transactions Detail page.

The Export Transactions Details section displays each export record in the WBINT_EXPORT table. After the export task is executed, a status of either APPLIED or ERROR is displayed for each entry in the Export Transactions Details section.

  • APPLIED: Indicates that the entry has been successfully exported to the external text file.
  • ERROR: Indicates that an error occurred during the export process.

See Viewing import or export transactions.

Verifying the export using reports

For payroll exports, after the Job Scheduler runs the Payroll Export task, you can validate the export data by viewing the report that the Job Scheduler task generates.

See Setting up Payroll Exports.

Verifying export data through Job Scheduler logs

After the Job Scheduler runs the export task, you can validate the task run details through the Job Scheduler export task log. The log contains Job Scheduler task run details including task runtime, task status, and any error activities that may have occurred during the actual run. If the Job Scheduler task status is FAILED, the status is always accompanied by an error message and exception stack trace details.