It is beautiful!

Work Order solutions are very similar to sales order solutions. It almost seems there is a generalized structure to most operations systems. It [also] seems the first to consider is just how the cost centers would be transacted to the work order.

A cost center control file would be central. Data to maintain standards, like units or type of cost code [etc] would also be needed. The question [always, well almost always:)] is how the cost is expressed and what kinds of automation would be required to service costing. For example, labor could be costed on a per hour basis. Stock inventory may use FIFO costing. Attaching X number of labor hours to a work order would not affect that hourly cost on subsequent work orders. However, attaching Y number of units from stock inventory, could affect the cost of that item on future work orders (FIFO averaging).

Sometimes, items are adjusted or removed from the work order (returned to inventory). There are costing consequences here also.

The good news is that the end user, the administrators and clerks that feed the data to your software, usually have a pretty good idea of what the system needs to do, and how it needs to do it. The center of the system you are working on is the place that the cost (and/or profit) centers transact with your work order. Get an understanding of how that guy works and then design and build outwards. You are going to have a lot of fun!


>thanks for your help terry, cali is beautiful please see this url www.caliescali.com
>am looking form schemas or something that let me make an idea to build my version of abc software..