Import Costs Process

You can import transactions from Oracle Cloud and third-party applications, validate them, and process them to create project costs and cost distributions.

You can track exceptions for invalid transactions on the Costs > Overview page, and in the Import Costs report.

To import the costs using file based data import, you must:

1. Prepare your data in the Import Costs macro-enabled Excel workbook template.

2. Click Generate CSV File in the template to create a comma-separated values file.

3. Navigate to the Scheduled Processes page or Tasks pane on the Overview page in the Costs work area.

4. Submit the Load Interface File for Import process to load the project costs from your CSV file into the Project Costing open interface table.

5. Submit the Import Costs process and select the CSV file to upload.

You can load data to interface tables using predefined templates and the Load Interface File for Import scheduled process, which are both part of the External Data Integration Services for Oracle Cloud feature. For more information, see the File Based Data Import guide for your cloud services.

You can schedule the Import Costs process to run at a predefined frequency and process project costs through the date on which the run is being performed. For example, if you schedule the process to run daily, then the value of the parameter Process Through Expenditure Item Date is set to the system date of the day on which the run is executed so that all project costs till that date are processed.

Note: If the project expenditure batches are eligible to undergo approval, the Import Costs process will only process transactions that belong to approved batches.

Parameters

Business Unit

Business unit that owns the project transaction.

Process Mode

Mode for processing imported transactions or adjustments.

Transaction Status

Status of transactions identified for processing: For example, All statuses, Not previously imported, or Rejected during processing.

Transaction Source

Name of the transaction source application.

Document

Document associated with the transaction.

Expenditure Batch

Expenditure batch for which transactions are processed.

From Project Number

Initial project number in the range of projects provided for importing and processing cost transactions.

To Project Number

Final project number in the range of projects provided for importing and processing cost transactions.

Process Through Expenditure Item Date

Expenditure item date of transactions through which transactions are processed and imported, which may include future dates. You can enable the option to increment the value of this parameter to match the system date if the job is scheduled. You can leave the default date as blank to import all pending costs for a specific source. This lets you import transactions from other modules, such as Payables, providing the project team with full visibility on the project actual cost.

Output Report

After the process completes, review the Import Costs report for the successful transactions and exceptions, if any. Review and resolve the issues and resubmit the process. There are 2 exception reports:

• The first report is an Excel spreadsheet that tracks exception transactions without valid names and numbers. For example, an invalid project name or project ID. Correct the issue in the source spreadsheet and export the transactions again to the staging table PJC_TXN_XFACE_STAGE_ALL.

• The second report is a portable document format (PDF) that tracks the business validation exceptions, which can be corrected in the Manage Unprocessed Costs page.