Previous	Next		Contents	Index	Navigation	Glossary	Library

You load the following transactions (expenditure items) into the interface table. The transaction source of Site1 has expenditure type classes of Straight Time and Expense Reports.

Assuming that all of the transactions in this example are valid, then Oracle Projects creates two expenditure batches--L1 and L2:

Since the transaction source has expenditure type classes of Straight Time and Expense Reports, Transaction Import groups the transactions by employee, expenditure ending date, and expenditure type class when creating expenditures. Therefore, the resulting expenditures are as follows:

Notice that even though transactions 2 and 3 were for the same employee and the same ending date, Oracle Projects created two expenditures. Transactions with different expenditure type classes are imported into different expenditure batches. Different batch names will also result in the creation of different expenditure batches, even if they contain transactions for the same employee and ending date.

Since the ending date of the expenditure batch created is equal to the maximum ending date of the expenditures created within that batch, the batch ending dates for our example are as follows: