Grouping Transactions into Expenditure Batches
This section describes how Transaction Import groups transactions into expenditure batches and expenditures.
When you load transactions into the interface table from an external system, Oracle Projects requires that you specify the following information for each transaction:
- Employee name or Organization
- Expenditure type class (if this information is not provided for the transaction, the value defaults to the expenditure type class assigned to the transaction source during implementation)
Transaction Import groups all of the transactions processed during an interface run into expenditures and expenditure batches in the following manner.
Attention: For all transactions, if the employee number is specified, Transaction Import ignores any value for the organization and derives the organization value based on the employee's assignment.
Straight Time and Expense Reports
If the transaction source of the transactions being processed is defined with an expenditure type class of Straight Time or Expense Reports, the key information in the interface table used in grouping transactions into expenditures and expenditure batches is as follows:
Each unique batch name becomes an expenditure batch, and each unique expenditure type class, employee number, and expenditure ending date combination becomes an expenditure within the expenditure batch. The ending date of the expenditure batch is set to the maximum ending date of all the expenditures created within that batch.
An employee number is required for all transactions with an expenditure type class Straight Time or Expense Reports. Transactions with any other expenditure type classes do not require an employee number.
All Other Expenditure Type Classes
If the transaction source of the transactions being processed is defined with an expenditure type class of Usages, Miscellaneous Transactions, Burden Transactions, Inventory, or Work in Process, the key information in the interface table used in grouping transactions into expenditures and expenditure batches is as follows:
- Employee number (optional)
- Expenditure organization name
Each unique batch name becomes an expenditure batch, and each unique expenditure type class, employee number, organization, and expenditure ending date combination becomes an expenditure within the expenditure batch. The ending date of the expenditure batch is set to the maximum ending date of all the expenditures created within that batch.
See Also
Example 1: Labor and Expense by Employee Number
Example 2: Usage
