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.
Suggestion: When interfacing large volumes of data, you can reduce the risk of unexpected errors by committing records after a specified number of transactions are processed. A Processing Set size is defined for each transaction source. As transactions are imported, a database commit is issued after each set is complete. If an error occurs and a rollback is issued, only the records in the current set are affected. See Processing Set Size, Oracle Projects Implementation Guide.
For detailed information on importing data into Oracle Projects using Transaction Import, including interface table descriptions, see: Overview of Transaction Import, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
You submit the PRC: Transaction Import process from the Submit Request window. See: Submitting Requests.
Transaction Source. Enter the transaction source for the transactions that you want to import into Oracle Projects.
Attention: Do not use the AP INVOICES transaction source when you run the PRC: Transaction Import program. This transaction source is intended only for use by the Oracle Projects processes to import Oracle Payables invoices.
Batch Name. Enter the name of a specific batch of transactions 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.
The following reports show you the results of this process:
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.
Note: If any expenditure item fails validation, Oracle Projects rejects the entire expenditure and updates each expenditure item with a status of R (Rejected). To locate all rejected transactions within an expenditure batch, use a SQL*Plus select statement on the EXPENDITURE_ID column and specify the expenditure id of the rejected item. Then update the TRANSACTION_ STATUS_CODE column to remove the R status. Or you can import the corrected items again, so that Oracle Projects creates a new record for the expenditure items instead of updating the rejected records.
The Transaction Import Report. Displays a summary of the expenditures successfully imported into Oracle Projects and the total number of expenditure batches created. For each expenditure batch, the report lists the name, the expenditure batch ending date, and the total number of expenditures created.
Suggestion: To view detailed information about the expenditures created in Oracle Projects, submit the AUD: Pre-Approved Expenditures Entry Audit report.
Other Sources
Using Transaction Import, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference
Transaction Import Interface, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference