Hello @all I have created a graph on how I think the workflow between sales, support and project could be. I have marked existing “Make-buttons” in green. Semi working ones in orange and all missing in red.
I’m not entirely sure what you mean by “do not need Project”…
I agree on that Project is something bigger. I figure the ERPNext design uses this as something smaller though, as this can be created from a Sales Order.
If I where to chose I would have a “Make Task” from Sales Order and have the project, as you say as something bigger conjoining all sorts of things that aren’t in ERPNext at the moment. Like e.g. Quotations. I figure a project can start even befor a Lead has become a customer…
Also what I forgot to mention…we work with Issue a lot. We are in IT services. Most things come in as an issue. For example if a computer is slow we will trouble shoot and find out, that a hard drive needs to be replaced. From this there is a Sales cycle to be started wich can only be starten manually for the moment.
In another case it is a software issue and we need to start replace a whole IT Solution or server system which has several dependencies. In that case we wan’t to escelate an issue right up toward a project and have the “process-trail” tracked…
I’m sure this is also a use-case outside my trade?!
yeah, I have also seen this. But isn’t Cost Center already sufficient for the accounting and controlling purpose?
Also I feel, that the moduul Projects needs a little polishing here and there. For example I can not bill a single Task inside Project. This is something we would like to work towards. Let’s take you construction business as example. I thing we should be able bill the Task “Foundation” befor the project is finished. Also “Roof” should not necessarily be on the same invoice. At the moment I can only bill whole projects and then need to remove all time sheets from the invoice that I don’t need. This a prone for mistakes.
How do you use Projects in your system?
Yes, that will work. We have tried that also. The trouble is, it will still fetch all other open timesheets to that Invoice as soon as the project field is filled.
Also the option to bill a whole task (from several time sheets) won’t work.
My trouble is not, that it is not possible to do (it is) but there is no clean process which makes it prone for errors which are at this point really annoying as we a booking things for good after which we are not able to correct anything as we would have to cancel sales invoices etc
all good, I am aware of that. It’s about billing small portions of a project. There is no trouble linking everything together. Though some times it would be nice to have a higher resolution so beeing to be able to link Material Request, Purchase Order etc. at Task level…and then bill just that Task.
Take the “Roof” stated earlier as an example. Have the tiles etc. linked to just that task. If I#m building a house the house is the project split into tasks like, roof, baseplate, woodwork, electrics etc. Or would you put them in separate projects? (there is no sub-project in ERPNext as far as I know)
that is true, yes. But that’s not my point here. The point is 1. billing 2. workflow
I can not bill the task Roof or one of your suggested subtasks like tiles. Not as one click oder via “make/create” but only by creating a sales invoice and then remove all the timesheets that I don’t want to bill. That is a whole lot of manual work.
working on the roof you might come across issues which would probably lead to creating excactly that. Or your customer could come over to the cunstruction site and have an issue with something that he would raise towards your office. They would the be able to link that to the project but not to the specific task. Like if he saw the pallet on which the tiles are delivered and is worried, that the color of those is not right…