Distribute and Install Desktop Integrator Client

Project Transactions: How They Are Imported to Oracle Fusion Projects

Collect and import all types of project costs
from Oracle Fusion and third-party applications. During this process
you can validate transactions to reduce corrections and rework. Before
you import the transactions to Oracle Fusion Projects, you can review
the exceptions for third-party transactions and correct the errors.

Settings That Affect Transactions Import

The setup options in the transaction document and
document entry specify how the transactions are imported and processed

How Transactions Are Imported

You create, validate, and transfer the transactions
to Oracle Fusion Projects interface as specified in the following
table.

Transactions Type

Creating Transactions

Validating Transactions

Importing Transactions

Oracle Fusion Projects Costs

Uncosted labor transactions

Uncosted nonlabor transactions

Initially only in Excel templates.

You can later edit or add transactions in the Manage
Unreleased Expenditure Batches page.

Validation is compulsory and is performed automatically
during transaction entry.

Transactions are exported using the Export button in Excel templates.

Third-Party Application Costs

Uncosted labor transactions

Uncosted nonlabor transactions

Costed or accounted labor or nonlabor
transactions

Excel templates or Source applications

You can also create transactions in the Manage Unprocessed
Transactions page.

Validation is compulsory but can be performed at various
phases.

Note

If the validations are not performed in the source
applications, you can validate them when you enter and export them
from Excel templates to Oracle Fusion Projects. Else they are validated
when you run the Import and Process Cost Transactions process.

You can use any of the two methods:

Transactions are exported using the Export button in Excel templates.

Transactions are transferred to the
Oracle Fusion Projects interface through Web services.

Costs from Other Fusion applications

Source applications

Validation is compulsory.

As transactions are validated in their source applications,
they are not validated again during the Import
and Process Costs Transactions process.

Transactions are transferred to Oracle Fusion Projects
by running the Import and Process Cost Transactions process.

All transactions are validated but at various points,
transaction entry or transfer, or processing. If you are exporting
transactions from Excel, you can release the transactions directly
from the spreadsheet itself by selecting the Process Costs option. Costs are submitted for Import and Process Cost Transactions process
avoiding the need to do it from the application.

Restriction

The Process Costs option is not available in the Excel template, when you have separate
duties for entering and releasing Oracle Fusion Projects expenditure
batches. You can review the expenditure batches in the Manage Unreleased
Expenditure Batches page and submit them for processing.

After the transactions are imported to Oracle Fusion
Projects, the application tracks transactions with errors including
the details for the cause of the error and the action to be taken
to fix the error. While the successful transactions are ready for
cost processing.

You can define the transaction document and
document entry options for transactions that originate from predefined
sources and third-party applications sources. However, there is a
limitation in editing these options. The options that you can edit
for each source depend on whether the document entry is predefined
for use with Oracle Fusion Applications or defined during implementation
for use with third-party application sources.

Document Edit Options

The following table provides a list of document options
that you can edit for predefined and third-party application source
transactions.

Note

For third-party application source transactions, the
following table details whether the options are editable after you
have created and imported transactions for the source.

Document Options

Predefined Sources

Third-Party Application Sources

Archive After Import

Editable

Editable

Allow Duplicate Reference

Not editable

Not editable

Allow Override of Person Organization

Not editable

Not editable

Import Raw Cost Amount

Not editable

Not editable

Import Burdened Amount

Not editable

Not editable

Accounted in Source Application

Not editable

Not editable

Create Raw Cost Accounting Journal Entries

Not editable

Not editable

Create Adjustment Accounting Journal Entries

Editable

Editable

Reconcile with Source

Not editable

Editable

Document Entry Edit Options

The following table provides a list of document entry
options that you can edit for predefined and third-party application
source transactions.

Note

For third-party application source transactions, the
following table details whether the options are editable after you
have created and imported transactions for the source.

Document Entry Options

Predefined Sources

Third-Party Application Sources

Expenditure Type Class

Not editable

Not editable

Allow Adjustments

Editable

Editable

Allow Reversals

Not editable

Editable

Allow Interface Modifications

Not editable

Editable

Process Cross-Charge Transactions

Editable

Editable

Create Related Items

Editable

Editable

FAQs for Distribute and Install Desktop Integrator
Client

Can I change the source and document for transactions after exporting them to Oracle
Fusion Projects?

No. You cannot change the source, document,
and document entry after creating a transaction.

What's the difference between the export and work in spreadsheet options?

Use the Export button or menu option to download data to view or analyze. You get
a Microsoft Excel file, of any type that Excel supports, containing
selected or all records from the corresponding table. If row selection
is disabled, then the export would include all rows. When all rows
are exported, that includes all the rows that are not visible on the
page. However, any search criteria, filters, and Query By Example values applied
to the table can exclude rows from the export. Data from hidden columns
are also not included in the export.

Use the option to work in spreadsheet to create
or edit records in a Microsoft Excel file and upload the records back
into Oracle Fusion Applications. This feature is helpful for mass
updates or working outside of Oracle Fusion Applications. The file
is based on a predefined template, which you download in most cases
from a link in the regional area, for example the Create
Expense Items in Spreadsheet link, or from a table, for
example using the Prepare in Spreadsheet button. The spreadsheets downloaded from a link can include rows
of data, or empty rows except for default values in some columns.
From a table, what is included in the spreadsheet is determined the
same way as for the export option. If no rows are selected,
however, the spreadsheet does not include any records from the table.

Note

If you are using a feature integrated with Oracle
Fusion Applications that presents a set number of rows per page or
view, then exporting or downloading all rows might not include all
the data you want. You might need to navigate to subsequent sets of
rows to export or download.

When do I validate
transactions in Excel templates?

You can validate transactions from third-party
applications in Excel templates when you export them to Oracle Fusion
Projects. Costs from Oracle Fusion Projects are automatically
validated when you export them.

Why can't I find the business unit I want to select in the downloaded Excel templates?

If your access is revised, then you have to
download the Excel templates again. For example, if you initially
have access to Vision Operations business unit, then you view only
this business unit listed in the Excel template. If new business units
are assigned or removed, you must download the templates again to
view the business units according to your access in the Excel template.