Previous	Next		Contents	Index	Navigation	Glossary	Library

You load the following transactions into the interface table; the transaction source of Usage has an expenditure type class of Usages. The grouping logic is slightly different for usage items, because usage expenditures can be created for an employee or an organization.

Note: You do not need to enter an employee number for usage transactions.

Since all of these transactions have the same batch name, Oracle Projects creates only one expenditure batch. For usage items, Transaction Import groups transactions by employee, organization, and expenditure ending date when creating expenditures. Therefore, the resulting expenditures after import would be as follows:

Notice that transactions (1) and (2) appear in the same expenditure because they were for the same employee/expenditure ending date, even though the organization name specified for both is different. If a transaction specifies an employee number, Transaction Import ignores any value for Organization and derives the organization value based on the employee's assignment.

Also note that even if employee 1000's organization assignment were West, the resulting expenditures would still be the same. Transaction Import never groups usage transactions for an employee into the same expenditure as usage transactions for an organization.