How Project Costs are Processed

Use the Import Costs process to import and process project costs from Oracle Fusion applications or third-party applications. This process imports transactions, derives transaction attributes, validates transactions, calculates cost, checks funds, and creates expenditure items, cost distributions, and accounting events.

This flow chart explains the processing of project cost transactions.

Setup Options: Import Costs

Transaction document and document entry options specify how cost transactions are imported and processed. The following table describes other setup options that determine the processing of project cost transactions.

Option	Setup Level	Description
Burden costs	Project type	Enable burdening, assign burden schedule, and manage burden cost accounting options.
Billable transactions	Work type Project type Project Task Transaction	Indicate whether transactions are billable.
Expenditure organization validation and currency conversion	Business unit	Validate expenditure organization and determine project ledger currency conversion rate as part of your business unit implementation.
Funds check	Business unit Project Financial Plan Type	Business Unit: Enable budgetary control and encumbrance accounting. You must first enable budgetary control for a ledger before you can enable budgetary control and encumbrance accounting for business units using that ledger. Use the Manage Budgetary Control or Manage Encumbrance Accounting task from the Setup and Maintenance work area to enable budgetary control and encumbrance accounting for your ledger and business unit. Procure-to-Pay Business Functions: Enable budgetary control and encumbrance accounting, and select transaction types and transaction subtypes to be included in funds check. Project Accounting Business Function: Enable budgetary control and select transaction sources and documents to be excluded from funds check. Project: Enable budgetary control If a project is enabled for budgetary control. then the transactions are included in the funds check by default. If a project is enabled for budgetary control and the business unit or ledger is also enabled for budgetary control, then a baselined budget version that's created using a budgetary control enabled financial plan type must exist for transactions that must be subjected to project budgetary controls. You can enable budgetary control only if no transactions exist in the project. If cost transactions exist, an error message is displayed. To resolve this error, create a new project that’s enabled for budgetary control, then create a budget and set it to baseline, and then transfer the existing costs to the new project. Financial Plan type: Enable budgetary control Financial plan types and budget versions in Project Control contain attributes that enable you to automatically create control budgets in Budgetary Control. Configuring the budgetary control settings of a financial plan type enable the budget versions that you create from that financial plan type to create control budgets. A project can have only one financial plan type that's enabled for budgetary control. If a financial plan type that's enabled for budgetary control is used by a budget version on a project, then you can't create another budget version with a different financial plan type enabled for budgetary control.
Transaction controls	Project Task	Specify whether transactions are chargeable.

How Transactions Are Processed

The Import Costs process performs the following steps on unprocessed transactions.

Transaction Processing Task	Description
Load transactions	Loads transactions for import into Oracle Fusion Project Costing from other Oracle Fusion applications.
Derive transaction attributes	Derives transaction attributes, such as human resource assignment details for the person, accounting date, project accounting date, and period information. These attributes are used to derive cost rate information and perform accounting.
Validate transactions	Validates transactions for business and transaction control rules. If the Revalidate during import option is enabled at the transaction source document level, the process revalidates the cost transactions imported from other Oracle Fusion applications such as Payables, Cost Management, and Time and Labor.
Create additional transactions	Creates additional transactions if overtime is enabled. This is an optional task.
Calculate costs	Calculates raw and burdened costs, and also converts amounts from the transaction currency to project currency, provider ledger currency, and receiver ledger currency.
Check funds	Validates transactions based on budgetary control and encumbrance accounting rules and computes funds status.
Generate accounting events	Generates cost accounting events, which are used to create cost accounting entries for transactions.
Create expenditure items and cost distribution lines	Creates expenditure items and cost distributions after costs are calculated and validated.
Reconcile transaction details with the source application	Reconciles the transaction processing status with the source application. Third-party applications use a service to update the transaction status and error details. For Oracle Fusion applications, the transaction status is always updated.

You can review the errors for pending and rejected transactions in the Manage Unprocessed Costs page or in the Import Costs Report. After fixing the errors, you can submit the transactions for reprocessing. Instead of reinitiating the process, the application reprocesses transactions from the point of error. For example, if a transaction is rejected while determining the cost rate, the application reprocesses the transaction from the cost rate determination stage and not earlier.

Note:

• You cannot delete expenditure batches that have both processed and unprocessed cost transactions, irrespective of the batch status. You can delete each unprocessed cost transactions in the batch individually, or you can correct the exceptions and reprocess the batch as usual. Once all transactions in the batch are successfully processed, the batch will also be set to Processed.
• If you have a processed expenditure batch that still contains unprocessed cost transactions and is in a status of Exception, you cannot delete the batch itself. You can, however, delete each unprocessed cost transaction in the batch individually, until there are no unprocessed cost transactions left in the batch. The status of the expenditure batch then changes to Processed, and you can then delete the batch if required.