Transaction Sources
Transaction sources identify the source of external transactions you import into Oracle Projects using Transaction Import. For example, you can define the transaction source Payroll to identify expenditure items imported from an external payroll system.
Transaction Sources for PTE
Oracle Projects predefines two Oracle Personal Time and Expense (PTE) transaction sources:
- PTE EXPENSE for expense reports
- PTE TIME for timecards (expenditure type class of Straight Time)
Oracle Projects uses these transaction sources to import expenditures from Oracle Personal Time and Expense.
Transaction Sources for Manufacturing and Inventory Costs
Oracle Projects predefines three transaction sources for Oracle Manufacturing and Oracle Inventory costs:
- Inventory for manufacturing material costs
- Inventory Misc for inventory issues and receipts entered in the Miscellaneous Transactions window in Oracle Inventory
- Work In Process for manufacturing resource costs
Oracle Projects uses these transaction sources to import expenditures from Oracle Inventory and Oracle Manufacturing.
If you import transactions from another manufacturing system, you must define your own transaction source.
Transaction Source Options
Transaction Import processes transactions based on the options that you select for their transaction sources.
Default Expenditure Type Class
Oracle Projects uses the default expenditure type class that you assign to a transaction source if an expenditure type class is not specified in the interface table. Oracle Projects provides this option to facilitate the migration of data from earlier releases of Oracle Projects.
Costed
When a transaction source is specified as having costed transactions, this means that the raw cost amount of the transactions has already been calculated and will not be modified after being imported into Oracle Projects. None of the Oracle Projects processes will calculate raw cost amounts for these transactions. See: Loading Items as Costed or Uncosted.
The designation of a transaction as costed does not affect burdening, accounting, or interfacing to GL or AP. These processes are still performed on the transaction as they would be if it were imported as a non-costed transaction.
Cost Burdened
If you enable this option, all transactions originating from this transaction source must have burdened costs. If the transaction does not have a burdened cost amount, the burdened cost amount will default to the transaction's raw cost amount.
GL Accounted
Select this option to indicate whether transactions imported from this transaction source have already been accounted for in GL. Oracle Projects expects that the external system has already posted the raw and burdened costs to the appropriate debit and credit accounts. None of the Oracle Projects processes will transfer these costs to GL or AP. See: Loading Items as Accounted or Unaccounted.
This option is enabled for manufacturing or inventory transactions with a transaction source of Inventory, Inventory Misc, or Work In Process.
Allow Duplicate References
Enable this option to allow multiple transactions with this transaction source to use the same original system reference. If you enable this option, you cannot uniquely identify the item by transaction source and original system reference.
Modify Interface
If Transaction Import rejects transactions from a particular transaction source, this option allows users to modify the rejected transactions in the Review Transactions window in Oracle Projects after the import process is completed.
Allow Adjustments
If you enable this option, you can adjust imported transactions in Oracle Projects after you load them via Transaction Import. Adjustments that you can allow include any change that could result in a new GL account or cost amounts for an item, such as:
- Transferring an item to another project or task
- Splitting an item into two or more items (not allowed for burden transaction items)
- Recalculating costs (raw and burden)
- Reclassifying an item as billable or non-billable (or capitalizable or non-capitalizable)
Note: Raw cost values for transactions that were already costed when loaded into Oracle Projects will not be changed if you mark the item for cost recalculation.
If you do not allow users to adjust imported transactions in Oracle Projects, you must adjust the transaction in the originating external system and import the adjustment into Oracle Projects.
Purgeable
If you select this option for a transaction source, items successfully imported from this transaction source are automatically purged from the interface table when the import process completes.
MRC Amounts from External System (only in MRC environments)
If you have implemented Multiple Reporting Currencies, this option appears only in the Transaction Sources window for your primary set of books. Checking this option indicates that transaction amounts in your primary currency and each associated reporting currency are provided by an external system. Otherwise, Oracle Projects calculates reporting currency amounts based on the rates stored in the GL_DAILY_RATES table. If you enable this option, you must populate the PA_MC_TXN_INTERFACE_ALL table with the currency conversion rates and converted amounts for all transactions originating from that transaction source. For more information about reporting currencies, see: Multiple Reporting Currencies in Oracle Applications.
Defining Transaction Sources
To define a transaction source:
1. In the Transaction Sources window, enter the transaction source, and enter the expenditure type class.
2. Choose the desired options for the transaction source.
3. Enter the effective date(s) and a description.
See Also
Effective Dates
Overview of Oracle Personal Time and Expense
Project Manufacturing
Transaction Import
Transaction Import Interface
Transaction Sources Listing
