RELATED IDEAS
Project work order
We would like the button “Opprett Arbeidsordre (“Create Work order”) not to be available in sub-projects with project group “ANLBID”. This is because the work orders inherits this project group and the registered cost is then allocated to the wrong accounts in the ledger. ANLBID is a project group that is dedicated to handle income, and thus has account setup relating ti the income int he general ledger. An idea ca be to create at posibility to choose which project groups that's allow on the work order type (the same way as attributes og work order types)
@Guest Many thanks for your feedback and concerns.
The way it is implemented, you are able to limit for which project groups you are allowed to create work orders. If there are no project groups set up, then you can create work order for all projects.
It is optional if you want to set up limitations.
I have a concern with this based on the proposed solution. We utilize the 'Create Work Order' from the project at both the parent and sub-project level as this is simpler for our planners and project managers. We utilize a subproject structure based on the project, to break out different aspects which may be grouped differently than the parent. The parent is kept in 'Initiate' status while we transact against the sub-project or work order sub-sub-project. We have several work order types due to billing, maintenance, construction, etc. so this makes using the 'Work order project setup' more error-prone to the planners than simply using the functionality to create a work order from the project. This is used less than creating work orders through the EAM but is important to us, nonetheless.
Planned for release in 2501.1.1