Assign Tasks for WIP Material Issues Using Task Auto Assignment Client Extension
You can configure how to assign the task for WIP material issues using the Task Auto Assignment (TAA) client extension. By default, TAA uses the Material rule defined by the user in the TAA workbench to derive the task for the issued material. The client extension provides the flexibility to override this default logic and derive the task using the WIP Material rule instead.
In a WIP Material issue transaction, there are two tasks involved: the task of the transaction and the task defined in the discrete job. These tasks correspond to the “Task” and “Source Task” respectively in the Material Transactions form. During Cost Collection, TAA needs to assign both the “Task” and “Source Task” for each transaction. In the default logic, TAA uses the Material rules for assigning the “Task”, and WIP Material rules for assigning the “Source Task”.
Consider the following example of TAA rules:
Material Rule
| Task Number | Item Number |
|---|---|
| 1.0 | CM4200 |
WIP Material Rule
| Task Number | WIP Prefix |
|---|---|
| 3.0 | WO1001 |
Based on these rules, when “CM4200” is issued to discrete job “WO1001”, TAA assigns “1.0” to the “Task”, and “3.0” to the “Source Task” of the transaction. This means that the material is issued from task “1.0” to task “3.0”. In terms of costing, the cost is moved from task “1.0” to task “3.0” for the WIP material issue.
This has a limitation when the same component needs to be issued from different tasks for different discrete jobs. For example, if the component is issued from task “1.1” for discrete job “WO1001” but issued from task “1.2” for discrete job “WO2001”.
Now consider the following example of TAA rules:
WIP Material Rule
| Task Number | WIP Prefix | Component | Transaction Type |
|---|---|---|---|
| 1.1 | WO1001 | CM4200 | Issue |
| 3.0 | WO1001 | Completion | |
| 1.2 | WO2001 | CM4200 | Issue |
| 4.0 | WO2001 | Completion |
When the client extension has been used to override the default logic, the TAA will apply the WIP Material rules as follow:
- TAA assigns the “Task” based on the rules applicable for WIP material issue.
- TAA assigns the “Source Task” based on the rules applicable for WIP assembly completion.
As such, based on the above rules:
- when “CM4200” is issued to discrete job “WO1001”, TAA assigns “1.1” to the “Task”, and “3.0” to the “Source “Task” of the transaction,
- when “CM4200” is issued to discrete job “WO2001”, TAA assigns “1.2” to the “Task”, and “4.0” to the “Source “Task” of the transaction.
This means that, the same component can now be issued from different tasks for different discrete jobs.
Steps to Enable
The new PL/SQL package PJM_TASK_AUTO_ASSIGN_EXT has been provided to override the default logic in TAA. The corresponding files can be found in the Project Manufacturing patch/115/sql directory.
- Package Specification File – PJMTKAXS.pls
- Package Body File – PJMTKAXB.pls
In the above package, override the function RULE_FOR_WIPMAT_TXN_TASK as follow:
- Uncomment the following line in the function body:
RETURN pjm_task_auto_assign.g_wipmat_rule; - Comment out the following line in the function body:
RETURN NULL;
This means that TAA will use WIP Material rules, instead of Material rules, for assigning the “Task” for WIP material transactions. In other words, TAA will then use only the WIP Material rules for assigning both the “Task” and “Source Task”.
Note that the default logic for RULE_FOR_WIPMAT_TXN_TASK is RETURN NULL, which means TAA will use Material rules for assigning the “Task” for WIP material transactions.