PA Transaction Upload  Help

PA Transaction Upload loads pre-approved expenditure items into Oracle Projects from Excel – timecards, usages, expenses, supplier costs and other cost transactions – by staging them in the Projects Transaction Import interface and then running Transaction Import. It creates new transactions; it does not change posted expenditure items.

When to use it

• Import costs from external or legacy systems (third-party payroll, timekeeping, usage, expense feeds) as project expenditure items.
• Load miscellaneous, usage or supplier-cost transactions in bulk against projects and tasks.
• Bring in accounted transactions that already carry their GL debit/credit accounts.
• Post negative or accrual/reversal transactions for period-end adjustments.
• Re-load and correct a batch of rows that previously failed import.
• Stage and import in a single submission, or stage only for a later manual import.

Before you start

• Blitz Report is installed and you are signed in to a responsibility with access to the operating unit and the right to run Transaction Import.
• A Projects-enabled operating unit, an active Transaction Source, and a Batch Name.
• The project and task exist, are chargeable to expenditures, and are active on the expenditure item date.

Step 1 – Choose a mode, set the parameters and download

In Blitz Report, open PA Transaction Upload, choose an Upload Mode (Create for an empty template, or Create, Update to retrieve transactions still in the interface), and set the parameters:

Run the upload to download and open the Excel file.

Step 2 – Enter the transactions

On each row enter the Operating Unit, Transaction Source, Expnd Type Class, Batch Name, a unique Original Trans Ref, the Expenditure Ending Date, the Project Number, Task Number and Expnd Type, the Expnd Item Date and the Quantity. Add cost, currency, employee, GL accounting or vendor/PO columns as the transaction type requires.

Step 3 – Validate and Save

Click Validate and Save. This checks for missing required values and runs the upload’s validation (week-ending date, duplicate reference, costed/accounted rules, currency rules), then saves the file. Correct anything it flags before continuing.

Step 4 – Upload and view the result

Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which stages the transactions and (unless you chose not to) runs Transaction Import. When it finishes, a result report opens showing each row as success or error.

What’s produced

• Pre-approved expenditure items in Oracle Projects (or staged interface rows when import is deferred).
• A result report listing every row with a status (success or error) and a message.

Common questions

Does this create the final expenditure items directly?
No. It writes to the Transaction Import interface and then runs Transaction Import, which creates the expenditure items. You can defer the import by setting Import Transactions = No.

Can I update or delete an expenditure item that already imported?
No – this upload only stages new transactions. Adjust already-imported items through standard Projects functionality.

What stops duplicates?
Each transaction carries an Original Transaction Reference. If the Transaction Source disallows duplicates, a row whose reference already exists is rejected.

Why must the Expenditure Ending Date be a specific date?
It must be a valid week-ending date for the operating unit’s expenditure cycle; the template defaults the correct value.

When are GL accounts and exchange-rate fields required?
Only for an accounted Transaction Source (GL date + debit/credit accounts) and for foreign-currency transactions (rate type/date, and a rate for a User rate type).

Troubleshooting