Está en la página 1de 5

Multi-Project Configurations

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.

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

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

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.

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.

También podría gustarte