How Source, Document, and Document Entry Components Work Together

When you create a transaction source, you select the transaction source options to control the transaction import processing. Transaction source, document, and document entry definitions determine how the application handles validation, import, processing, adjustment, and accounting of project cost transactions.

Example of transaction source, documents, and document entries. — The following figure provides an example of a transaction source called Oracle Fusion Payables, associated documents called Supplier Invoice and Expense Report, and their document entries such as Invoice Price Variance, Exchange Rate Variance, Freight, Item Cost, and Nonrecoverable Tax.

Sources

At the transaction source level, you define the source and the processing set size. When transferring large number of transactions, you can reduce the impact of unexpected errors by processing transactions in sets. Define the set size by providing a value for the processing set size.

Documents

Documents represent the transactions that are imported to Oracle Fusion Project Costing. They are associated to a source. You specify the import and accounting options for transactions. Some of the options are interdependent.

If the document entry is associated with the expenditure type class, Supplier Invoice or Expense Report, you cannot deselect the Accounted in Source Application and Import raw cost amounts options.
If the document entry is associated with the expenditure type class, Burden Transactions, you cannot deselect the Import raw cost amounts or Import burdened cost amounts options.
You can select the Import burdened cost amounts option only when the Import raw cost amounts option is selected.
You can select the Create raw cost accounting journal entries option, if the Accounted in Source Application option is set to No.
You cannot create a document for predefined transaction sources.

Document Entries

Document entries are a further breakdown of the document. They represent different types of transactions that come under a single, specific document. For the Burden Transactions expenditure type class, you specify the Import raw cost amounts and Import burdened cost amounts options at the document level; however, you cannot specify the Allow adjustments and Allow reversals options at the document entry level. Therefore, to allow adjustments and reversals, you either change the document options or select a different expenditure type class. You can define the following document entry options:

Allow modifications to unprocessed transactions: After importing transactions from third-party application sources, you can edit the unprocessed transactions. You can also delete unprocessed transactions from third-party application and Oracle Fusion Projects sources.
Process cross-charge transactions: You can allow cross-charge transactions processing.