Oracle Project Manufacturing Implementation Guide Release 12.1 Part Number E13685-05 | Contents | Previous | Next |
This chapter covers the following topics:
This chapter explains the use of Oracle Project Manufacturing's Task Auto Assignment feature. Task Auto Assignment gives you a flexible way to specify how to track material and resource costs by tasks within your project rather than manually specifying tasks on your manufacturing transactions. Task Auto Assignment dynamically assigns tasks to manufacturing transactions based task assignment rules you define.
The Task Auto Assignment allows you to specify a set of rules for assigning tasks to inventory, WIP, and WIP material transactions. Based on these rules tasks are automatically assigned to project material and resource transactions.
Task Auto Assignment - Schematic diagram
Task Auto Assignment has different criteria for creating rules. These are:
Material task assignment criteria:
Item Number
Procure Flag
Purchase Order Number
Category Code
Subinventory
Resource task assignment criteria:
Operation Code
Job Number or Job prefix
Assembly
Department
WIP Material task assignment criteria:
Transaction Type
Assembly
Component
Item Category
Subinventory
WIP prefix
Department
Operation
For a given project, you can use any combination of the above mentioned criteria to define a rule for a particular task.
Whenever a project related material or resource transaction is recorded, Task Auto Assignment compares the conditions for that transaction with the pre-specified rules for the project and automatically assigns the task. For example, if you want to monitor the usage of certain critical raw material for a project, define a rule that links a task to that material. Wherever a transaction for this material occurs, it is charged to that task.
A similar rule on the resource side would assign a critical operation to a separate task in the project work breakdown structure.
A rule on the WIP material side would assign the issue of a common component to multiple parent assemblies.
The following sections explain how to use this feature, the benefits of the Task Auto Assignment feature and illustrate some examples where this feature could be effectively deployed.
The Material tab region of the Task Auto Assignment window lets you associate a task with an item, procure flag, PO number, item category, and subinventory. Task Auto Assignment looks at the item, whether the item is procured, or the PO number, 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, the Task Auto Assignment feature looks for the rule that corresponds to the highest-priority field, which is the field that appears on the left. For example, suppose you've defined two rules for Project P1:
Project | Task | Item | PO Number | Category | Subinventory | Procure |
---|---|---|---|---|---|---|
P1 | T1 | A | 101 | - | - | - |
P1 | T2 | A | - | - | Stores | - |
When you deliver PO#101 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 PO number has a higher priority than Subinventory which is displayed on the left of the Subinventory column on the window. You can also define the priority of these fields. For more information, refer to the section on Defining the hierarchy of Task Assignment Criteria.
The Resource tab region of the Task Auto Assignment window enables you to associate a task with an operation code, job (or job prefix), 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 left. For example, suppose you've defined two rules for Project P1:
Project | Task | Operation code | Job Number / Prefix | Assembly | Department Code |
---|---|---|---|---|---|
P1 | T1 | Assembly | R% | - | - |
P1 | T2 | Assembly | - | - | AS2 |
When you perform a resource transaction for job R222 for a resource belonging to 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 which is displayed on the left of the Department Code column on the window.
You can define the priority of these fields to suit their needs. For more information, refer to the section on Defining the hierarchy of Task Assignment Criteria.
The WIP Material tab region of the Task Auto Assignment window enables you to associate a task with a transaction type, assembly, component, item category, subinventory, WIP prefix, department, or operation. Task Auto Assignment looks at the values entered in these fields and finds a rule that matches a WIP material 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 left. For example, suppose you've defined two rules for Project P1:
Project | Task | Transaction Type | Assembly | Component | Subinventory |
---|---|---|---|---|---|
P1 | T1 | Issue | SB27 | CM20 | - |
P1 | T2 | Issue | - | CM20 | Stores |
When you perform a WIP Material Issue transaction for component CM20 to the Assembly 27 from the Subinventory 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 Assembly has a higher priority than Component or Subinventory.
You can define the priority of these fields to suit their needs. For more information, refer to the section on Defining the Hierarchy of Task Assignment Criteria.
You can change the hierarchy of the task assignment criteria if the default hierarchy does not meet their requirements. The task assignment forms regenerate using the hierarchy you specified. The criteria with higher priority appears to the left of the ones with a lower priority.
Task Auto Assignment is intended to provide a flexible way to determine how you want to track the material (inventory) and resource (WIP) costs by different tasks. It enables you to define rules to associate different tasks for inventory, WIP, and WIP Material transactions. When the inventory and WIP transactions are being costed in the Oracle Inventory and WIP, the Task Auto Assignment assigns a task to the transaction based rules you define. When the transaction cost is transferred to Oracle Projects, the cost is collected under the desired task.
The following process diagram shows the Cost Collection flow of a transaction through the Cost Worker and Cost Collector.
Related Topics
Oracle Project Manufacturing User's Guide
The Task Auto Assignment feature provides you with greater control over how project work breakdown structures are linked to manufacturing activities. Some of the key benefits are listed here:
Provides complete flexibility in defining project work breakdown structure.
Consider a simple bill of material that is intended to be manufactured as a project.
Bill of Material for a Project Item
In order to achieve better cost control, it is identified that costs of items LongLT (a long lead time item) and item HiValue (expensive item) need to closely monitored. It is also necessary to track the costs of critical welding and prefabrication resources used in building the end assembly. In order to meet these objectives, a project work breakdown structure is prepared that tracks these costs under separate tasks. The work breakdown structure is shown in the figure above.
Proposed Project Work Breakdown Structure
Without the Task Auto Assignment feature, it would not be possible to support such a project work breakdown structure. This is because the task number for manufacturing activities (requisitions/purchase orders and WIP jobs) would have been either:
Suggested by the planning system
Manually entered
In either case, the procurement and assembly activities of all the component items would have the same task as their parent. As a consequence, all the material and resource costs would be bundled up under one task and it would not be possible to monitor the costs of critical items and resources used in the project.
Task Assignment Without Task Auto Assignment
For example, if Task 1 is assigned to the end assembly on a MDS (or MPS or Forecast), the same task would appear on all the transactions for items HiValue and LongLT and also on all the resource transactions required in building the end item.
You have greater flexibility in designing the work breakdown structure. Apart from separating the costs of items LongLT and HiValue under different tasks, the usage of critical welding resources (Task 3.1) and prefabrication resources (Task 3.2) can also be tracked. This is accomplished automatically and hence consistently for a given project.
It is evident from the example that task assignment with the Task Auto Assignment feature is not restricted by (and to) the product structure. You have the option of defining the work breakdown structure the way manufacturing activities are undertaken. This provides you with unlimited flexibility in defining their work breakdown structures.
Allows cost collection on a much finer level.
Task Auto Assignment enables cost collection at a much finer level. Without Task Auto Assignment, task assignment (and cost collection) can happen only at the work order level. ALL the resource costs are charged to the task specified on the work order. With Task Auto Assignment, cost collection can be pushed down to the department level or even to the individual operation level. A comparison of the standard functionality and the additional functionality imparted by Task Auto Assignment is shown below.
Cost Collection Without Task Auto Assignment
Cost Collection with Task Auto Assignment
As indicated in the figure above, Task Auto Assignment gives you considerable flexibility in cost collection. You can choose the granularity of cost collection based on the specific requirements.
Eliminates manual task entry.
You do not worry about entering tasks on any project related transactions. This eliminates all the errors associated with manual task entry.
Cost accountants control the allocation of manufacturing costs to a project instead of manufacturing personnel assigning tasks to a transaction.
You can still choose to manually enter a task for any of the transactions. Task Auto Assignment does not override this task.
You must plan, execute and track manufacturing activities at a project level instead of a more granular task level if Task Auto Assignment is used.
Enables standardization of project work breakdown structure and manufacturing costing.
The task assignment rules for material and resource transactions guide the process of task assignment. Once the rules have been defined, the process of task assignment takes place with no human intervention. This facilitates creation and maintenance of organization-wide standards for defining Project work breakdown structure and manufacturing cost collection. This is an added advantage over all the other benefits mentioned earlier.
This section briefly describes some typical examples using the Task Auto Assignment feature. The given list is just an indicator of things that could be accomplished with the Task Auto Assignment feature.
Budget and Track critical resource consumption for a project
On many occasions it is necessary to budget and closely monitor the usage of a critical manufacturing resource for a project. This could be a resource using expensive piece of machinery or a resource with unstable process/high rejection rates or a resource that uses highly skilled manual labor. The Task Auto Assignment feature allows you to budget for and monitor these critical resources by project.
This ensures better visibility of critical or money loosing resource costs and enable better control over such resources.
Collect costs by department
Using Task Auto Assignment, costs can also be collected by the manufacturing departments involved. The resource consumption in a particular department for the project is always be charged to a user-specified task. This enables budgeting for projects by the individual departments involved. Simultaneously, it also enables project progress monitoring/performance evaluation by department.
The following figures show two different approaches in which you could setup Project Work Breakdown Structure in relation to the Organization Breakdown Structure. Without Task Auto Assignment, such a link between Project Work Breakdown Structure and Organization Structure would not be possible for manufacturing departments.
Inventory Organizations as Project Expenditure Organizations
The figure above shows an example where Inventory Organizations (INVORG1, INVORG2, etc.) have been modeled as Project Expenditure Organizations.
These Expenditure Organizations have been referenced on the Manufacturing departments. For example, MFGDEPT1 and MFGDEPT2 have been assigned the same Project Expenditure Organization INVORG1. Task Auto Assignment rules (TAA Rule1, TAA Rule2, etc.) have been setup such that resource costs incurred in each of the manufacturing departments are collected under a separate task. The disadvantage of this approach is you loose visibility of manufacturing department level costs in a Project Expenditure Organization. i.e. Costs in Project Expenditure Organization INVORG1 commingles the resource costs for MFGDEPT1, and MFGDEPT2 along with other expenditures (including material costs) for INVORG1.
Another approach shown in the figure models manufacturing departments as individual Project Expenditure Organizations. Here each Manufacturing Department represents one Project Expenditure Organization and there is no commingling of costs.
Manufacturing departments as Project Expenditure Organizations
Collect resource costs for a particular job or assembly.
Another application of the Task Auto Assignment feature is seen in a case where you intend to monitor the resource usage for a particular assembly or a particular WIP job. You can assign a task assignment rule for this assembly or WIP job and can monitor the resource usage for that assembly or WIP job. If there is a need to control a specific resource for a job or an assembly, it can also be accomplished using Task Auto Assignment. You can associate only unreleased jobs with a resource task assignment rule.
Collect resource costs for a specific group of WIP jobs.
You can generate jobs in Oracle Work In Process with a particular prefix. Task Auto Assignment allows you to define resource task assignment rules with partial WIP job numbers as one of the criteria. This enables monitoring resource usage for a specific group of jobs that carry a certain prefix. This enables grouping of project costs for a specific work (e.g. rework, repair, etc.) under separate tasks automatically.
Note: You can choose to enter any number of characters before entering the wildcard character (%). For example, if RW is the chosen prefix for rework type jobs, you can enter R% or RW% or RW100% as the task assignment criteria to refer to a specific group of jobs. The rule applies to a broader or narrower group of WIP jobs.
Track procurement activity.
A task assignment rule that uses Procure Flag as one of its conditions facilitates tracking of the procurement activity. When purchased material is received for a project, the value of the receipt (plus any applicable overheads) are charged to the task that corresponds to the rule. This helps to monitor the progress of project procurement activities. This can be used for monitoring procurement of project items that have a very long lead time or are very expensive.
Tracking of procurement against a specific purchase order is accomplished by entering the PO Number as one of the task assignment criteria or by entering the task directly on the PO distribution line.
You cannot enter partially received purchase orders as task assignment criteria.
Track cost of critical items for a given project
A task assignment rule that uses an item number as one of the criterion (with the PO field blank and the procure flag unchecked) can be used to track the cost of that item for a given project. This set of rules keeps a track of all the inventory transactions for that item and keeps an account of the value of material consumption for the project.
Capture the cost of BOM in the Work Breakdown Structure
The block diagram shows the work breakdown structure and how the costs are captured for various material and resource transactions in the system. The table below lists the rules setup using Task Auto Assignment. In this example, only Resource and WIP material rules have been used to achieve the cost allocation results as displayed in the work breakdown structure.
Resource | WIP Material | ||||
---|---|---|---|---|---|
Task | Assembly | Department | Transaction Type | Assembly | Component |
1.1.3.1 | - | - | Issue | Main Controls Build | - |
1.1.3.1 | Main Controls Build | - | - | - | - |
1.1.3.2 | - | - | Issue | Sync Unit Build | - |
1.1.3.2 | Sync Unit Build | - | - | - | - |
1.1.3.3 | Controls Build | - | - | - | - |
1.1.3.3 | - | - | Issue | Controls Build | - |
1.1.3.3 | - | - | Completion | Main Controls Build | - |
1.1.3.3 | - | - | Completion | Sync Unit | - |
1.1.1 | - | - | Issue | Fan Build | - |
1.1.1 | Fan Build | - | - | - | - |
1.1.2 | Turbine Build | - | - | - | - |
1.1.2 | - | - | Issue | Turbine Build | - |
1.1.4 | Transformer Build | - | - | - | - |
1.1.4 | - | - | Issue | Transformer Build | - |
1.1.5 | Test Unit Build | - | - | - | - |
1.1.5 | - | - | Issue | Test Unit Build | - |
1.1.5 | - | - | Completion | Fan Build | - |
1.1.5 | - | - | Completion | Turbine Build | - |
1.1.5 | - | - | Completion | Transformer Build | - |
1.2 | Gearbox Build | - | - | - | - |
1.2 | - | - | Completion | Test Unit Build | - |
1.2 | - | - | Issues | Gearbox Build | - |
This section describes the basic steps involved in the implementation procedure of the Task Auto Assignment feature.
Set the Project Control Level organization parameter to Project. This enables you to have project-only identity to supply and demand orders. You can then use Task Auto Assignment to assign task for the transactions. Project Cost Collection should be enabled.
You need to define the hierarchy of material, resource, and WIP material task assignment criteria. You should ensure adequate security for this window.
Define the profile option in WIP to generate WIP jobs with a certain prefix. This step is optional.
You need to determine how you want to budget and track your project expenditures first. Then you create the work breakdown structure for your project.
You need to assign your project to a cost group, a default WIP accounting class, optionally a planning group, a default material task and a default resource task in the Project Parameter window. The window automatically creates a default material task assignment rule in the Material Assignment table using the default material task, and a default resource task assignment rule in the Resource Assignment table using the default resource task you specify in this window.
Enter your task assignment rule(s) in the Material tab region of the Task Auto Assignment window. You should make sure that you enter all the rules before you start transactions.
If you desire to use PO numbers as a part of task assignment rules, you must create the corresponding purchase orders.
Enter your task assignment rule(s) in the Resource tab region of the Task Auto Assignment window. You should make sure that you enter all the rules before you start transactions.
Enter your task assignment rule(s) in the WIP Material alternate region of the Task Auto Assignment window. Make sure that you enter all the rules before you start transactions.
Note: If you desire to use WIP Job number as a part of the task assignment rule(s), the corresponding WIP job has to be created before it could be entered in this window.
The Task Auto Assignment feature brings a lot of flexibility in defining Project work breakdown structure and collection of manufacturing costs. Given below are some key aspects that you should be aware of while using the Task Auto Assignment feature.
Coverage of the entire spectrum of Material and Resource Transactions is essential
While defining the task assignment rules for a project, it is necessary that all conceivable material and resource transactions are accounted for. If this condition is not satisfied, some transactions would not be assigned the desired task and the costs for such transactions would be transferred to the project on the default task.
A default task assignment rule is a rule that has the project and task fields populated and all the other task assignment criteria are null. You define the default tasks when you define Project Parameters.
Changing the hierarchy of task assignment criteria after cost collection can distort facts
Exercise extreme caution in modifying the hierarchy of task assignment criteria after some project transactions have been processed by the cost collector. Project expenditures would be distorted when the logic is changed. You must be aware of the consequences of such a change if the changes are decided to be implemented.
Using partial WIP job numbers as criteria
Task Auto Assignment allows you to enter only unreleased WIP jobs as task assignment criteria. This ensures that all the WIP resource transactions for the jobs are assigned appropriate tasks and costs are transferred to Oracle Projects.
This validation does not apply for partial WIP jobs numbers entered with a wildcard. So when partial WIP job numbers with wildcards are entered as task assignment criteria, you should ensure that no previously cost collected project WIP resource transactions that satisfy the task assignment rule exist.
The tasks assigned by Task Auto Assignment for Inventory and Resource transactions can be viewed in the following windows:
Viewing Tasks assigned by Task Auto Assignment
Transactions | Window | Zone | Field |
---|---|---|---|
All Project Inventory transactions | View Material Transactions | Transaction ID | Task Number |
Common Material Issue to Project WIP | View Material Transactions | Transaction ID | Source Task Number |
All Project Resource Transactions | View Resource Transactions | Project | Task Number |
Viewing Errors in the task assignment process
The errors in the task assignment process for material transactions could be viewed in the View Material Transactions window in the Cost Management or Inventory responsibility. The alternate zone Transaction ID has columns Error Code and Error Explanation that show the errors in task assignment process.
Copyright © 2000, 2014, Oracle and/or its affiliates. All rights reserved.