Source Documents

The transaction source determines how Transaction Import processes transactions. Some
transaction sources are system-defined, and you can create others to fit your business needs.
When you create a transaction source, you control the Transaction Import processing by the
options that you select.

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.

Inventory with No Accounts

Work In Process
WIP with Accounts
WIP with No Accounts
WIP Straight Time with Accounts
WIP Straight Time Manufacturing labor resource costs that Oracle Projects categorizes as
with No Accounts straight time, and for which Oracle Projects generates accounts and
interfaces transactions to General Ledger

If you import transactions from another manufacturing system, you must define your own
transaction source.

Transaction Source Options

Transaction source options control how Transaction Import processes transactions. Following
are the transaction source options:

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.

Raw Cost 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 cost 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, 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.
Import Raw Cost Amounts

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

When you enable this option, you indicate that transaction amounts in your functional
currency and each associated reporting currency are provided by the external system. For
transaction sources using this option, you must populate the
PA_MC_TXN_INTERFACE_ALL table with the currency conversion rates and converted
amounts for all transactions.

For transaction sources that do not have this option enabled, Oracle Projects calculates
reporting currency amounts based on the rates stored in the GL_DAILY_RATES table.

For more information about multiple reporting currencies, see: Multiple Reporting
Currencies Oracle Applications.

Import Employee Organization

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.

Allow Duplicate Reference

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.

Allow Interface Modifications

This option allows you to modify rejected transactions in the Review Transactions window
after the import process is completed.

Purge After 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.

Allow Reversals

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.

Allow Adjustments

If you enable this option, you can adjust imported transactions in Oracle Projects after you
load them via Transaction Import.

Note: This flag allows adjustments even if the implementation options Interface Labor Costs
to GL and/or Interface Usage Costs to GL are disabled.

Adjustments that are enabled by this flag include any change that could result in a new GL
account or cost amounts for an item, such as:

o Transferring an item to another project or task

o Splitting an item into two or more items

o Recalculating 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.)

o Reclassifying an item as capitalizable or non-capitalizable

If you do not allow users to adjust imported transactions in Oracle Projects, you can only
make changes in the imported transactions as follows:

o First, adjust the transactions in the originating external system.

o Then, import the adjustment into Oracle Projects.

Process Cross Charge

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.

Pre Processing Extension

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.

Post Processing Extension

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.

Processing Set Size

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.

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). You must enter an Effective From date. The
Effective To date is optional.
4. Enter a description.
5. Save your work.

Fremont Corporation Transaction Sources

Fremont Corporation defines the following transaction sources to import data from external
systems.

Transaction Expenditure Type Import Raw Cost Purge After

Source Class Amounts Import

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.

Predefined Transaction Sources

Oracle Projects predefines several transaction sources. The following table lists some of the
predefined transaction sources:

Transaction
Used to Import Records From ...
Source
Oracle Payables Oracle Payables (supplier invoices)
Supplier Invoices WARNING: Do not use this transaction source when you run the PRC:
Transaction Import program. It is intended only for use by the Oracle
Projects processes to import Oracle Payables invoices.
Oracle Self-Service Oracle Self-Service Time
Time
Time Management Oracle Time Management
Oracle Time and Oracle Time and Labor
Labor

Predefined Transaction Sources for Manufacturing and Inventory Costs

Oracle Projects predefines the following transaction sources for importing expenditures from
Oracle Project Manufacturing and Oracle Inventory:

Transaction
Used to Import ...
Source
Inventory Misc Inventory issues and receipts entered in the Miscellaneous Transactions
window in Oracle Inventory
Inventory Manufacturing material costs for which Oracle Project Manufacturing
interfaces transactions to General Ledger
Inventory with Manufacturing material costs with account information for which Oracle
Accounts Projects interfaces transactions to General Ledger