Hi Robert,You are correct, the fix should be related to invoices without a PO reference.It should be possible to match an invoice with a PO Receipt even though the Work Task is Finished.If that isn’t possible please raise a support issue on that so it can be looked at.
Direct allocation have no connection back to the resource demand and by that the resource demand is seen as unforfilled and by that the work task will not be automatically set to Work Done.Please see Assign multiple tasks - All resource persons are available to pick | IFS Community for a more extensive explaination.
See Uthpalas response in Task completed in mWO not updating to Work Done | IFS Community.The “Assign Multiple Tasks” and “Direct Allocation” options will create work assignment which doesn’t connect to the resource demand and thus the work task will not automatically be set to Work Done when the work assignment is completed.
This is the functionality and there is no setting to alter this behavior.Either the user should revert the status manually to Work Started if he/she realize that more work needs to be done (= new resource demand is needed) or as Mathias suggests a custom event or workflow could be used to change the status.
Hi,Same type of scenario has been raised here - Stop Time for Cancelled Work Task | IFS CommunityAs Sampath is stating - “If the work assignment has been downloaded to the device (Downloaded Date has a value), you shouldn’t be able to cancel (change the status) the work assignment “.If you can verify that you have a value in Downloaded Date and you still are allowed to cancel the assignment, then please raise a support issue as suggested by Sampath.
Hi,Which version (including SU) are you using?You shouldn’t be able to get into this situation. It is not allowed to cancel an assignment that has a clocking on it (clocked in or clocked out). If a clocking exists the command for cancelling is (should be) disabled. So from where did you cancel the assignment?
No problem, I could have added the Direct Allocation screenshot in the first reply.
I tried to expalain the reason for this in my last reply.We had a requirement to make this a very simple way of assigning same person/tool to multiple Work Tasks (regardless of required resources, maint org etc).See it as a Direct Allocation function where you have automatically set ‘Apply Contraints’ to No.
Hi,As I mentioned the usage of this command would change if it would take Maint Org and/or the Group on the Resource demand. The command would just be available if the user would choose Work Tasks with same setup. The Maint Org would be one thing - that is on Work Task itself and the user could by that filter out the Work Task with the same Maint Org. But the Group on Resource demand isn’t possible to search for in a Work Task context. So suddenly the user might choose multiple Work Tasks with different Groups on the Resource demands and by doing that (without having a clue) the command is not enabled.There is an element of performance question on having such checks on values on Work Task or related tables (Resource demand).But main reason if the functional reason above and the requirement to make this a very simple way of assigning same person/tool to multiple Work Tasks (regardless of required resources etc).I hope this make sense.
Hi,This is the intended functionality (introduced in App10 Upd8).It was introduced as an easy-to-use capability where several work tasks can be marked and assigned to a single person or tool/equipment. Using similar concept as the Direct Allocation capability where this can be done by single work task, but the user interaction here allows for doing it all in one go.The expectation is that the user doing the assignment would know who to assign (if not then the filtration functionality within the drop list can be used).If we were to look at which Resource Group and Maint Org that is stated on the Work Task, then the command would just be available when choosing Work Tasks with same setup. This would go against the easy-to-use idea of this function.
Thanks for the background information @ereslk
Hi,You won’t be able to delete this Task since you have cancelled assignments on it.What you will be able to do is to Cancel the Task.
See responses on same topic: Prority on PM action
Hi,Try to send the Work Order back from mobile and then remove the material line.
Hi,Yes that is possible for a Work Task in status below Released.See post: Move Work Task
Hi, in assign work dialog this is just for information.You can change this on the Work Task itself.
Hi @Elaineebi,If you stand on the an individual PM Action (in your case 346) and from its Maintenance Plan generates the WO then just this PM Action will be generated - hence just one Work Task on the generated WO.You need to run the Calendar Generation with the generation parameters set (wanted generation date range, PM Group ID and anything else you want to use as selection for the PM Actions you want to be generated).Test that out, that should give you the wanted result.
Hi @Elaineebi,What is the result of the PM generation?As I can see the first PM Action has a Work List with to steps, that will prevent the merge to take place.So the expected outcome would be one WO with two Work Tasks (Work Task 1 with object TEST1 and Work Task 2 with object TEST2) - isn’t that what you get?
Hi,The field Work Leader is still there on the Work Order in IFS Cloud. You can use the page Structure for WO as Tony points out to set the value in this field but you can also find the field in Additional Information sub-menu in Prepare Work Order. The Work Leader is something else then the assignee's on the work task.The assignee’s on the work task are the one assigned to perform the work whilst the Work Leader is someone overall responsible that the work is carried out (one direct functionality is that the Work Leader is controlling which Permits that can be connected/used on the Work Order).
Hi,Some feedback around this issue.Me and @Leibnitz Germanio had a Teams session where we tried to figure out what was wrong.We could conclude that the issue was that the Duplicate Work Tasks was in status “Work Started” (if the Master/Duplicate relationship was in place then that status was promoted when the Master Work Task was set to “Work Started”), but they didn’t had a value in Actual Start.That is really strange and should not be possible - when changing the status to “Work Started” the Actual Start is automatically set and the value in this can’t be removed if the status i “Work Started”.We couldn’t figure out why the work tasks had ended up in this situation.We both tried this flow again (taking extra care to set the Master/Duplicate relations before starting any Work Task) - I did it with “normal” Work Order structure and manually entered Work Orders/Work Tasks and Leibnitz did it again with the Work Order structure coming from MO.We ended up not being able to recreate the si
Hi,Out of the box there is no relations between Priority and Latest Start Date and Latest Finish Date.The priority is a user defined basic data and there is no place to put logic in to control the start and finish dates.To achieve this you could perhaps create a custom event that based on priority values gives a latest start based on sysdate and number of days related to the given priority (could be that you need to create custom field in the priority basic data to store the number of days needed to calculate the latest start).
Hi @emilyk8r,If what Asanka answered isn’t what you are looking for, then search for this in the online help.Prepare Materialhttp://docweb.corpnet.ifsworld.com/ifsdoc/Greenhouse/documentation/en/WorkTaskManagement/ProcessPrepareMaterial.htmIssue Materialhttp://docweb.corpnet.ifsworld.com/ifsdoc/Greenhouse/documentation/en/WorkTaskManagement/ActivityIssuePart.htm or if it is purchasing you are referring to then this is a good startActivityEnterPurchaseRequisitionhttp://docweb.corpnet.ifsworld.com/ifsdoc/Greenhouse/documentation/en/WorkTaskManagement/ActivityEnterPurchaseRequisition.htm
Hi,Here is the information from field help:Selection ReleasedIf this check box is selected, only the work tasks in Released status will be displayed. Only one of the check boxes, Selection Released, Selection Started or Selection WorkDone can be selected at a time. If all checkboxes are left unchecked, work tasks in Released, Started and WorkDone statuses will be displayed.Selection StartedIf this check box is selected, only the work tasks in Started status will be displayed. Only one of the check boxes, Selection Released, Selection Started or Selection WorkDone can be selected at a time. If all checkboxes are left unchecked, work tasks in Released, Started and WorkDone statuses will be displayed.Selection WorkDoneIf this check box is selected, only the work tasks in WorkDone status will be displayed. Only one of the check boxes, Selection Released, Selection Started or Selection WorkDone can be selected at a time. If all checkboxes are left unchecked, work tasks in Released, Started
Hi @lisa.gilesAB,Couldn’t you use the ‘Transferred to Mobile’ flag that exists on the Work Task?You could for example open up that column in the work task list on the prepare work order page to let the IEE User now if any work task is still on the mobile device.
Your observations are correct. Technician Portal doesn’t support work order/work task with connection type Tool/Equipment.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
