Using Electronic Data Collection Transactions
Data collection transactions received through XML messages, batch oriented flat files, and the transaction pages are loaded into the transaction log. Background processes pick up these transactions, validate them, and then update the appropriate PeopleSoft application tables. If an error is found, the system does not process the transaction. The transaction's status on the transaction log is changed to Error, and the system inserts a row into the error table for each error message.
The BCt Errors Workflow process (IN_WFBCTERRS) checks for electronic data collection transactions that have an error status and generates a worklist entry. Once you process the worklist entry, the PeopleSoft system displays the Transaction Maintenance page, where you can view the errors and fix them.
Once you have modified the transaction and saved the Transaction Maintenance Detail page, the transaction can be reprocessed. Transactions that have been processed to the Complete status or that have been canceled in the Transaction Maintenance page can be archived and purged from the transaction log using the transaction purge process.
The background processes validate all information before performing any updates. However, when you enter the transactions through the data collection transaction pages, selected pieces of information on the page have edits to verify the data that is entered.
For technical details about individual EIPs, use the Interactive Services Repository (ISR) in the My Oracle Support website located at https://support.oracle.com/CSP/ui/flash.html.