Transaction sources identify the source of external transactions that you import into Oracle Projects. The transaction source determines how Oracle Projects imports the transactions.
Oracle Projects provides a set of predefined transaction sources that you use to import transactions from other Oracle Applications. For example, the following processes in Oracle Projects use predefined transaction sources to import expenditures:
PRC: Interface Supplier Costs: Uses the predefined transaction sources for supplier costs to import transactions from Oracle Purchasing and Oracle Payables.
PRC: Interface Expense Reports from Payables: Uses the predefined transaction source Oracle Payables Expense Reports to import expense reports from Oracle Payables.
PRC: Transaction Import: Uses predefined transaction sources to import transactions from other Oracle Applications such as Oracle Inventory, Oracle Project Manufacturing, Oracle Time and Labor, and Oracle Labor Distribution.
In addition, Oracle Projects uses predefined transaction sources to import project allocations and capitalized interest transactions that it generates internally.
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. You control the Transaction Import processing by the options that you select for each transaction source.
The following table lists the predefined transactions sources that Oracle Projects uses to import supplier costs from Oracle Purchasing and Oracle Payables and expense reports from Oracle Payables.
Attention: Do not use these transaction sources to import transactions from non-Oracle sources. These transaction sources are intended only for use by the Oracle Projects processes that import supplier costs and expense report costs from Oracle Purchasing and Oracle Payables.
Predefined Transaction Sources for Supplier Costs and Expense Reports
| Transaction Source | Used to Import... |
|---|---|
| Nonrecoverable Tax from Payables | Nonrecoverable tax amounts on item costs and invoice price variance amounts from Oracle Payables |
| Nonrecoverable Tax from Purchasing Receipt | Nonrecoverable tax amounts from purchasing receipts in Oracle Purchasing |
| Nonrecoverable Tax Price Adjustment from Purchasing Receipt | Nonrecoverable tax price adjustment amounts from receipts in Oracle Purchasing |
| Oracle Interproject Invoices | Oracle Projects interproject invoices from Oracle Payables |
| Oracle Payables Expense Reports | Expense reports from Oracle Payables |
| Oracle Payables Invoice Variance | Invoice price and tax variance amounts from Oracle Payables |
| Oracle Payables Supplier Cost Exchange Rate Variance | Exchange rate variances on invoice cost and tax from Oracle Payables |
| Oracle Payables Supplier Invoices | Supplier invoices from Oracle Payables |
| Oracle Projects Intercompany Supplier Invoices | Oracle Projects intercompany supplier invoices from Oracle Payables |
| Oracle Purchasing Receipt Accruals | Receipt accruals from Oracle Purchasing |
| Oracle Purchasing Receipt Accruals Price Adjustment | Price adjustments for receipt accruals in Oracle Purchasing |
| Supplier Invoice Discounts from Payables | Supplier invoice discount amounts from Oracle Payables |
You can define preprocessing and postprocessing extensions to customize the predefined supplier cost transaction sources. For additional information, see: Transaction Import Extensions, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
Additional Information: The process PRC: Interface Supplier Costs only rejects the expenditure items that fail validation. The process interfaces the remaining expenditure items to Oracle Projects. This functionality only applies to predefined transaction sources for supplier costs. It does not apply to user-defined supplier cost transaction sources. For additional information, see: Interface Supplier Costs.
Note: To calculate cross charge amounts for expenditure items with the transaction source Oracle Payables Exchange Rate Variance, you must use either the Transfer Price Determination Extension or the Transfer Price Override Extension. For information on client extensions, see the Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
The following table lists the predefined transactions sources that Oracle Projects uses to import transactions from Oracle Project Manufacturing and Oracle Inventory.
Attention: Do not use these transaction sources to import transactions from non-Oracle sources.
Predefined Transaction Sources for Manufacturing and Inventory Costs
| Transaction Source | Used to Import... |
|---|---|
| Inventory Misc | Inventory issues and receipts entered in the Miscellaneous Transactions window in Oracle Inventory |
| Inventory | Manufacturing material costs for which Oracle Project Manufacturing creates accounting in Oracle Subledger Accounting |
| Inventory with Accounts | Manufacturing material costs with account information for which Oracle Projects creates accounting in Oracle Subledger Accounting |
| Inventory with No Accounts | Manufacturing material costs for which Oracle Projects uses AutoAccounting to derive accounts and creates accounting in Oracle Subledger Accounting |
| Work In Process | Manufacturing resource costs for which Oracle Project Manufacturing creates accounting in Oracle Subledger Accounting |
| WIP with Accounts | Manufacturing nonlabor resource costs with account information that Oracle Projects categorizes as work in process. Transactions are accounted in Oracle Manufacturing. |
| WIP with No Accounts | Manufacturing nonlabor resource costs that Oracle Projects categorizes as work in process, and for which Oracle Projects uses AutoAccounting to derive accounts and creates accounting in Oracle Subledger Accounting |
| WIP Straight Time with Accounts | Manufacturing labor resource costs with account information that Oracle Projects categorizes as straight time. Transactions are accounted in Oracle Manufacturing. |
| WIP Straight Time with No Accounts | Manufacturing labor resource costs that Oracle Projects categorizes as straight time, and for which Oracle Projects uses AutoAccounting to derive accounts and creates accounting in Oracle Subledger Accounting |
Note: For the transaction sources WIP with Accounts and WIP Straight Time with Accounts, the posting option for the inventory organization determines whether Oracle Manufacturing or Oracle Projects generates accounting events and creates accounting for the transactions in Oracle Subledger Accounting. If posting option is Manufacturing, then Oracle Manufacturing generates accounting events and creates accounting. If the posting option is Projects, then Oracle Projects imports the default accounts from Oracle Manufacturing, generates accounting events, and creates accounting. Oracle Projects does not change the default accounts when you generate accounting events. If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting.
The following table lists the predefined transactions sources that Oracle Projects uses to import transactions from Oracle Asset Tracking.
Attention: Do not use these transaction sources to import transactions from non-Oracle sources.
Predefined Transaction Sources for Oracle Asset Tracking
| Transaction Source | Used to Import... |
|---|---|
| CSE_INV_ISSUE | Transactions of the type Issue for non-depreciable items |
| CSE_INV_ISSUE_DEPR | Transactions of the type Issue for depreciable items |
| CSE_IPV_ADJUSTMENT | Supplier cost adjustments for non-depreciable items |
| CSE_IPV_ADJUSTMENT_DEPR | Supplier cost adjustments for depreciable items |
| CSE_PO_RECEIPT | Transactions of the type Receipt for non-depreciable items |
| CSE_PO_RECEIPT_DEPR | Transactions of the type Receipt for depreciable items |
The following table lists the predefined transactions sources that Oracle Projects uses to import labor transactions from Oracle Time and Labor.
Attention: Do not use this transaction source to import transactions from non-Oracle sources.
Predefined Transaction Source for Oracle Time and Labor
| Transaction Source | Used to Import... |
|---|---|
| Oracle Time and Labor | Timecards from Oracle Time and Labor |
The following table lists the predefined transactions sources that Oracle Projects uses to import actual labor transactions and labor encumbrances from Oracle Labor Distribution.
Attention: Do not use these transaction sources to import transactions from non-Oracle sources. These transaction sources are intended only for use by the Oracle Labor Distribution processes. For additional information, see the Oracle Labor Distribution User's Guide.
Predefined Transaction Sources for Oracle Labor Distribution
| Transaction Source | Used to Import... |
|---|---|
| GOLD | Actual costs from Oracle Labor Distribution For additional information, see: Using Transaction Import in Oracle Grants Accounting. |
| GOLDE | Encumbrances from Oracle Labor Distribution For additional information, see: Using Transaction Import in Oracle Grants Accounting. |
The following table lists the predefined transactions sources that Oracle Projects uses to import project allocations and capitalized interest transactions that it generates within the application.
Attention: Do not use these transaction sources to import transactions from non-Oracle sources. These transaction sources are intended only for use by the Oracle Projects processes that import project allocations and capital interest transactions.
Predefined Transaction Sources for Project Allocations and Capitalize Interest Transactions
| Transaction Source | Used to Import... |
|---|---|
| Project Allocations | Project allocations generated in Oracle Projects |
| Capitalized Interest | Capitalized Interest transactions generated in Oracle Projects |
Transaction source options control how Transaction Import processes transactions. Following are the transaction source options:
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.
Select this option to indicate whether transactions imported from this transaction source are already accounted. When you select this option, Oracle Projects processes do not generate accounting events to send the transactions to Oracle Subledger Accounting. See: Loading Items as Accounted or Unaccounted, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
When you select this option, the Import Raw Cost Amounts option is automatically selected.
Examples of transactions for which this option is enabled are manufacturing and inventory transactions with the transaction source Inventory, Inventory Misc, or Work In Process.
When a transaction source has this option enabled, the raw cost amount of the transactions has already been calculated (costed). These are not 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, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.
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.
Note: If Burden Transaction is the default expenditure type class for a transaction source, then you cannot disable the Import Raw Cost Amounts option for the transaction source.
When this option is selected for a transaction source, Oracle Projects expects the external system to provide burdened costs. If the transaction does not have a burdened cost amount, Transaction Import will reject the transaction.
When you select this option, the Import Raw Cost Amounts option is automatically selected.
Note: If Burden Transaction is the default expenditure type class for a transaction source, then you cannot disable the Import Burdened Amounts option for the transaction source.
If you enable this option, the external system can optionally provide an expenditure organization that is different from the employee owning organization. If no expenditure organization is provided, Transaction Import will populate the expenditure organization with the employee owning organization.
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.
This option allows you to modify rejected transactions in the Review Transactions window after the import process is completed.
Note: You must enable this option for predefined supplier cost transaction sources to use the Review Transactions window to modify the expenditure item date for expenditure items that fail date validation during import.
If you select this option, items successfully imported from the transaction source are automatically purged from the interface table when the import process is completed.
If you enable this option, Oracle Projects allows reversals of expenditure batches or expenditure items for the transaction source. When you enable this option, the Allow Adjustments option is automatically enabled.
Note: So that the originating external system can be reconciled with Oracle Projects, you must create corresponding reversals in the external system. In addition, if both this option and the Raw Cost GL Accounted option are enabled, you must generate corresponding reversing cost distribution lines for transactions that you reverse in Oracle Projects.
Note: If Burden Transaction is the default expenditure type class for a transaction source, then you cannot enable the Allow Reversals option for the transaction source.
If you enable this option, then you can adjust imported transactions in Oracle Projects after you load them via Transaction Import.
Note: If you enable this option, Oracle Projects allows adjustments even if you disable the Interface Costs to GL options in Oracle Projects implementation options.
Attention: If you enable the Allow Adjustments option for a predefined transaction source for supplier costs, you must complete at least one of the following setup steps:
Specify the default supplier cost credit account for supplier cost adjustments in Oracle Projects implementation options for each operating unit.
Define a rule in Oracle Subledger Accounting to determine the supplier cost credit account.
This setup is required for the process PRC: Create Accounting to successfully create accounting for supplier cost adjustments. Oracle Projects displays a message asking you to validate the setup each time that you enable the Allow Adjustments option for a predefined transaction source for supplier costs.
Note: If Burden Transaction is the default expenditure type class for a transaction source, then you cannot enable the Allow Adjustments option for the transaction source.
Enabling this option allows you to make adjustments and changes that can result in a new GL account or cost amounts for an item. For example, you can make the following types of adjustments:
Transfer an item to another project or task
Split an item into two or more items
Recalculate raw and burden costs
(Raw cost values for transactions that were already costed when loaded into Oracle Projects are not changed if you mark the item for cost recalculation.)
Reclassify an item as billable or nonbillable
Reclassify an item as capitalizable or noncapitalizable
Change the work type of an item
For additional information, see: Types of Expenditure Item Adjustments.
The default value for this option is No. If the option is set to No, then you can still perform the following adjustments:
Apply a billing hold
Apply a one-time billing hold
Release billing hold
Recalculate burden cost
Note: You can recalculate burden costs only if the Import Burdened Amounts transaction source option is not enabled.
Recalculate revenue
Change comment
Reprocess cross charge
Mark for no cross charge processing
Change transfer price currency attributes
Change the work type (only if the change does not affect the billable status or capitalizable status of the expenditure item)
Note: The profile option PA: Transaction Billability derived from Work Type controls whether the work type determines the billable status of an expenditure item.
If you do not allow users to adjust imported transactions in Oracle Projects, then you can adjust the transactions in the originating external system. After you adjust the transactions, you import adjustments into Oracle Projects.
If you import cross charge transactions that are processed by an external system, enable this option for that system's transaction source. If this option is enabled for a transaction source, Oracle Projects performs cross charge processing for transactions originating from that transaction source.
Enter the name of a PL/SQL procedure to be called before the Transaction Import process runs. You must enter the full name including the package, in the format package.procedure.
This option can be used for loading the Transaction Import Interface table, or for pre-import validations, or for other pre-import processing.
Note: Oracle Projects does not support the use of a Pre-Import client extension with the Capitalized Interest transaction source.
Enter the name of a PL/SQL procedure to be called after the Transaction Import process runs. You must enter the full name including the package, in the format package.procedure.
This option can be used for recording the expenditure and expenditure item IDs generated by the Transaction Import process in the source system. It can also be used for other post-import processing.
Note: Oracle Projects does not support the use of a Post-Import client extension with the Capitalized Interest transaction source.
Enter the size of the processing set. The value entered indicates the number of records to be processed in each set. When interfacing large amounts of data, you can reduce the impact of unexpected errors by processing transactions in sets. The import process issues a database commit after each set is complete. If an error occurs and a rollback is issued, only the transactions in the current set are affected.
To define a transaction source:
In the Transaction Sources window, enter the transaction source, and enter the expenditure type class.
Choose the desired options for the transaction source.
Enter the effective date(s). You must enter an Effective From date. The Effective To date is optional.
Enter a description.
Save your work.
Fremont Corporation defines the following transaction sources to import data from external systems.
| Transaction Source | Expenditure Type Class | Import Raw Cost Amounts | Purge After Import |
|---|---|---|---|
| Faxed Timecard | Straight Time | Disabled | Enabled |
| PBX | Usages | Enabled | Enabled |
Other Sources
Transaction Import, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference