Defining Material Task Assignment
The Material Task Assignment window lets you associate a task with an item, P.O. number, item category, and subinventory. Task Auto Assignment looks at the item, P.O. number (if any), category, and subinventory of a material transaction and finds a rule that matches the transaction. It then assigns a task to the transaction. If more than one rule matches the values of some of these fields, Task Auto Assignment looks for the rule that corresponds to the highest-priority field, which is the field that appears on the window first. For example, suppose you've defined two rules for project 1:
| P1
| T1
| A
| 101
|
|
|
| P1
| T2
| A
|
|
| Stores
|
When you deliver a P.O. for item A into Stores, Task Auto Assignment matches the transaction with the first rule (and therefore assigns task T1 to the transaction). The reason it picks the first rule rather than the second, even though both contain matching fields, is because the P.O. number has a higher priority than Subinventory.
To assign tasks to material transactions:
2. Enter a Project Number.
This is the number of the project for which the tasks are being auto-assigned.
This number must correspond to a task defined in Oracle Projects.
4. Optionally, enter a value for one or more of the following fields:
This number refers to the item number defined in Oracle Inventory.
This is the Purchase Order number to which you might want to assign the task.
This is the category in the Category set belonging to the Inventory functional area defined in Oracle Inventory.
This is the destination subinventory used in a transaction.
Note: You cannot enter values in both the Item Number field and the Category field for the same rule.
