Defining Resource Task Assignment
The Resource Task Assignment window lets you associate a task with an operation code, job, assembly, and department. Task Auto Assignment looks at the values entered in these fields and finds a rule that matches a resource transaction. It then assigns the 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
| Assembly
| 222
|
|
|
| P1
| T2
| Assembly
|
|
| AS2
|
When you perform a resource transaction for job 222 in the Assembly operation in the AS2 department, 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 that Job Number has a higher priority than Department Code.
To assign WIP labor and overhead tasks:
2. Enter a Project Number.
This is the number of the project for which the tasks are being auto-assigned.
This number corresponds to a task defined in Oracle Projects.
4. Optionally, enter a value for one or more of the following fields:
This is a code defined in Oracle Bills of Material that refers to a specific standard operation.
This field is for a job number created in Oracle Work In Process.
If you want to assign the task to a particular assembly, enter the assembly item number in this field.
This code is defined in Oracle Bills of Material.
Note: You cannot enter values in both the Job field and the Assembly field for the same rule.
See Also
Defining a Department
Creating a Standard Operation.
Defining Discrete Jobs Manually
