From: Olwen W. <ol...@ha...> - 2004-05-29 22:37:29
|
I've been sitting and thinking about the requirements and was starting to think along similar lines. I have to spec and quote the first stage. I'll spend some time today looking at the contract area. Theres several new tables to be created. Steve wants to partially validate product (for repair) info to get better reporting, and because many repairs are third party warranty repairs. Phil Daintree wrote: > Olwen, > > Been thinking about the requirments of the service company. I thought that in > fact when a customer calls them, they are not so much placing an order as > initiating a job. The tables for jobs already exist - albeit that some > alterations may be required and they are called "Contracts" not jobs. The > thinking here is that the details of the job are taken and the person for the > job allocated. The service-person doing the job would add the materials etc > that are required or have been consumed on the job together with a dummy part > for her time at whatever chargeout rate, once the job is fully defined and > the work is done it is converted to a sales order and invoiced. > > I am thinking that creating a sales order without a part on it may not be > exactly what they are after - I think the scenario above might suit them > better - clearly Steve is the one to decide that. > > Currently, a job (contract) requires a customer and branch to be selected and > in many cases the set up of a new customer would be required first. It > doesn't currently have a person responsible for follow up - this would need > to be added. Thought initially this might go together with work centres but > think maybe this is a separate table now? > > It might be better to default some of the customer/branch input in a special > customer initiation screen that leads on to the (yet to be created) job set > up screen, to populate the job details (contracts table). > > > Phil > > |