Previous	Next		Contents	Index	Navigation	Glossary	Library

For each valid transaction, Transaction Import imports the transactions and creates corresponding expenditure records in the Oracle Projects expenditure tables; expenditure records include expenditure batches, expenditures, and expenditure items. For each invalid transaction, Transaction Import rejects the transaction and updates the transaction in the interface table with a status of Rejected and the rejection reason. You should update rejected items in the interface tables or your external system and import the transactions again.

If the transaction source for the Transaction Import is purgeable, Transaction Import deletes the corresponding transactions from the interface table. If the transaction source is not purgeable, Transaction Import updates the status of the corresponding transaction in the interface table with a status of Accepted.

For detailed information on importing data into Oracle Projects using Transaction Import, including interface table descriptions, refer to the following essay: Overview of Transaction Import.

Process Submission

Process Parameters

Batch Name. Enter the name of a specific batch of transaction that you want to import into Oracle Projects. You can choose only batches having the transaction source specified for the Transaction Source parameter.

Suggestion: For increased performance, submit several concurrent Transaction Import requests specifying different batch names rather than submitting one request for a particular transaction source.

Output Reports

• The Transaction Import Exception Report. Lists all transactions that were rejected during the Transaction Import process. For each rejected transaction, this report displays the key field values of the transaction in the interface table. It also displays the rejection reason code that identifies the cause of the transaction's rejection. For reference, the last page of this report prints a key of rejection reason codes and their meanings.

Attention: If any one expenditure item in an expenditure fails validation, Oracle Projects rejects the entire expenditure and updates each expenditure item in the expenditure with a status of R (Rejected). You can locate all of the related rejected transactions within an expenditure batch by using a SQL*Plus select statement on the EXPENDITURE_ID column using the expenditure id of the rejected item; then update the TRANSACTION_ STATUS_CODE column to remove the R status. Or you can re-import the corrected items, Oracle Projects creates a new record for the expenditure items instead of updating the existing records that were rejected.

• The Transaction Import Report. Displays a summary of the expenditure successfully imported into Oracle Projects by the Transaction Import process. This report lists the name of each expenditure batch created during the import process, the expenditure batch ending date, and the total number of expenditures created in the expenditure batch. This report also includes a total count of the expenditure batches created during the import process.

Suggestion: If you want to view more detailed information about the expenditures created in Oracle Projects, submit the AUD: Pre-Approved Expenditures Entry Audit report.