Oracle® Fusion Applications Project Management Implementation Guide 11g Release 1 (11.1.3) Part Number E20384-03

Contents

Previous

Next

33 Project Costing Configuration: Manage Transaction Sources and Documents

This chapter contains the following:

Transaction Sources: Explained

Source, Document, and Document Entry Components: How They Work Together

Setting Up Transaction Sources: Points to Consider

Transaction Document Import and Accounting Options: Points to Consider

FAQs for Manage Transaction Sources and Documents

Transaction Sources: Explained

Transaction sources identify the source of transactions that you import into Oracle Fusion Project Costing. You control the transaction import and processing by the specifying the source, document, and document entry options.

The transaction sources can be classified into two categories:

• Predefined sources

• Third-party application sources

Predefined Sources

Oracle Fusion Project Costing provides a set of predefined transaction sources that you use to import transactions from other Oracle Fusion applications. The predefined sources and their associated document entries are as follows:

• Oracle Fusion Payables: Supplier costs, expense reports, intercompany invoices, and interproject invoices.

• Oracle Fusion Projects: Time cards, usage expenditures, miscellaneous expenditures, inventory expenditures, burden expenditures, summarized burden expenditures, work-in-progress expenditures, capital interest expenditures, and allocation expenditures.

• Oracle Fusion Cost Management: Purchase receipts and miscellaneous inventory cost.

Third-Party Application Sources

You can define additional transaction sources to import transactions from non-Oracle applications. For example, you can define the transaction source Payroll to identify expenditure items imported from an external payroll system. Similarly, you create documents for a specific transaction source and document entries for a specific document.

Source, Document, and Document Entry Components: How They 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.

Sources

At the transaction source level, you define the source, the processing set size, preprocessing, and postprocessing extensions. The extensions record the internal identifiers of imported expenditure items in the source application or perform other user-defined processing before and at the end of the Import and Process Cost Transactions process. Review and update the transaction sources to call the transaction preprocessing and postprocessing extensions during the import and process cost transactions process.

• 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 the set size.

• Preprocessing extension: Used for transaction validation before importing, uploading the transactions to Transaction Import Interface, or for other processing tasks before importing.

• Postprocessing extension: Used to record the transaction number of the imported expenditure items in the source application.

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 amounts options.

• You can select the Import burdened 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 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 interface modifications: After importing the transactions, you can edit the unprocessed transactions.

• Create related items: When importing the transactions the Create Related Items extension is used to process the related items.

• Cross-charge transaction processing: You can allow cross-charge transactions processing.

Setting Up Transaction Sources: Points to Consider

Transaction sources identify the source of external transactions and determine how you import them into Oracle Fusion Projects.

Consider the following aspects when you set up transaction sources:

• Transaction Source Options

• Document Options

• Document Entry Options

• Predefined Transaction Sources

Transaction Source Options

You specify the following options when setting up transaction sources.

• Processing Set Size

  The number of records to be processed in each set. When processing a large amount of data, you can reduce the impact of unexpected errors by processing transactions in sets. The import process saves to the database after each set is complete. If an error occurs and a rollback is issued, only the transactions in the current set are affected.

• Preprocessing Extension

  Use the Manage Transaction Sources: Preprocessing Extension to perform custom logic at the beginning of Import and Process Cost Transactions process. For example, you can implement custom validation logic before processing the costs.

• Postprocessing Extension

  Use the Manage Transaction Sources: Postprocessing Extension to record the internal identifiers of imported expenditure items in the source application or perform other custom processing at the end of the Import and Process Cost Transactions process.

Document Options

You specify the following options when setting up transaction source documents.

• Import Raw Cost Amounts

  Imports transactions with the raw cost amount of the transaction already calculated. The amount is not modified after the transaction is imported into Oracle Fusion Projects. Designating an imported transaction as costed does not affect burdening or accounting.

  Note

  If Burden Transaction is the expenditure type class for one or more document entries, you cannot disable the Import Raw Cost Amounts option for the document.

• Import Burdened Amounts

  Imports burdened costs for transactions. If selected, transactions that do not have a burdened cost amount are rejected. When you select this option, the Import Raw Cost Amounts option is automatically selected.

  Note

  If Burden Transaction is the expenditure type class for one or more document entries, you cannot disable the Import Burden Amounts option for the document.

• Allow Duplicate Reference

  Allows this document to have multiple transactions with the same original system reference. If you select this option, you cannot uniquely identify the item by source, document, and original system reference.

• Allow Override of Person Organization

  Allows the external application to provide an expenditure organization that is different from the owning organization of the person. If no expenditure organization is provided, the import process populates the expenditure organization with the owning organization of the person.

• Reconcile with Source

  Ties transactions from this document back to the transaction source application.

• Archive After Import

  Automatically archives successful imported transactions when the import process completes.

• Accounted in Source Application

  Controls the accounts that are imported and the fields that are required from the transaction source application.

• Create Raw Cost Accounting Journal Entries

  Interfaces cost accounting journals for the raw cost to the general ledger.

  Note

  Settings on the project type determine whether accounting journal entries for the burden cost and burdened cost are sent to the general ledger.

• Create Adjustment Accounting Journal Entries

  Interfaces adjustments to the general ledger.

Document Entry Options

You specify the following options when setting up transaction source document entries.

• Allow Adjustments

  Allows adjustments to imported transactions in Oracle Fusion Projects after the import process.

  Note

  If Burden Transaction is the expenditure type class, you cannot disable the Allow Adjustments option.

• Allow Reversals

  Allows reversals of expenditure batches or expenditure items for the document entry.

  Note

  So that the originating external application can be reconciled with Oracle Fusion Projects, you may need to create corresponding reversals in the external application. In addition, if both this option and the Import Raw Cost Amounts option are selected, you may need to create corresponding reversals in the external application for the transactions that you reverse in Oracle Fusion Projects.

  Note

  If Burden Transaction is the expenditure type class, you cannot select the Allow Reversals option.

• Allow Interface Modifications

  Allows modifications to rejected transactions after the import process completes. Allows modifications to pending transactions after they are loaded to the interface table and before the import process is submitted.

• Create Related Items

  Indicates that the Related Transaction Extension is used to create related transactions for expenditure items charged to projects.

• Process Cross-Charge Transactions

  If this option is selected for a document entry, Oracle Fusion Projects performs cross-charge processing for transactions that originate from the source, document, and document entry.

• Expenditure Type Class

  Expenditure type class used for this document entry.

Predefined Transaction Sources

Oracle Fusion Projects provides a set of predefined transaction sources that you use to import transactions from other Oracle Fusion applications. In addition, Oracle Fusion Projects uses predefined transaction sources to import project allocations, capitalized interest transactions, and summarized burden transactions that are generated internally.

You can define additional transaction sources to import transactions from third-party applications. For example, you can define the transaction source Payroll to identify expenditure items imported from an external payroll application. You control the Transaction Import processing by the options that you select for each transaction source.

The following table lists the predefined transaction sources that you can use to import transactions from Oracle Fusion Payables:

The following table lists the predefined transaction sources that you can use to import transactions from Oracle Fusion Cost Management:

The following table lists the predefined transaction sources that you can use to import transactions from Oracle Fusion Projects:

Transaction Document Import and Accounting Options: Points to Consider

Specify the import and accounting options in the transaction document to define the way in which the transactions are imported and processed.

Transaction Import Options

The import options that you define for documents impact how the application imports transactions for that document. You specify the following import options for each document:

Transaction Accounting Options

The accounting options that you define for documents impact how the application accounts transactions for that document. You specify the following accounting options for each document:

FAQs for Manage Transaction Sources and Documents

Can I assign a document to multiple sources?

You can have a document with the same name in multiple sources but you cannot share documents across sources. For example, a corporation with multiple time capture systems can associate a time card document with Oracle Fusion Projects and a non-Oracle application as sources. The rules on how these transactions are treated may differ depending on how they are processed in the source applications.

Can I create documents and document entries for predefined transactions sources?

No.You can create documents and document entries only for third-party transaction sources.

Can I delete transaction sources, documents, and document entries?

You can delete third-party transaction sources, documents, or document entries only if no cost transactions exist. However, you cannot delete the predefined transaction sources, documents, or document entries.

Can I allow adjustments and reversals for all transactions in the document entry?

No. You decide whether to allow transaction adjustments and reversals for each document entry that you create during implementation. However, you cannot define document entries to allow adjustments and reversals for transactions that are generated by the application such as allocation transactions, capital interest expenditure transactions, summarized burden transactions.

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.

Previous Next

Copyright ©  2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Contents Contact Us