ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Sales >> Building to forcast
http://www.istechforum.com/YaBB.pl?num=1089326061

Message started by BillB on 07/08/04 at 14:34:21

Title: Building to forcast
Post by BillB on 07/08/04 at 14:34:21

My largest customer has started a new system that we must work to.

We are to build to a forcast and he will issue a P.O. only 10 days from ship date. Our problem is that if we issue a sales order number, and create internal job folder tied to that sales order number, how do I ship against his P.O. number, and his next P.O. etc. but still retain the orginal sales order number.

Title: Re: Building to forcast
Post by aricon on 07/08/04 at 15:00:43

Why do you need to maintain just one sales order number? The invoice numbers will be different anyway as you generate them on an on-going basis. So what is the desire/requirement to keep the SO number constant driven by?

Title: Re: Building to forcast
Post by BillB on 07/13/04 at 06:17:42

Because of job folders. We require inspection records, cert's etc, this folder can be involved to create. With new sales order number - new folder required.

Title: Re: Building to forcast
Post by sharon krewson on 07/13/04 at 06:27:12

Can you tie your job folder to a work order instead of a sales order? You could build your stock with a work order that has your certs, records, etc associated with it. Then when your customer's PO arrives you just create a new sales order and ship from stock.

Title: Re: Building to forcast
Post by BillB on 07/19/04 at 11:29:13

Don't think I can to it. We make various assemblies and when a work order is created from a sales order a dash number is created for the assembly and also a number of various dash numbers for the compounts are created.
I don't know of a way to do that other then a sales order conversion?

Title: Re: Building to forcast
Post by Lynn Pantic on 07/19/04 at 11:52:38

You can manually create a 12345-1 work order for the top level assembly, then use WO-K-D to create the subassembly work orders which will all be the other dash numbers of 12345. So all the subassembly work orders will still have the same base number and therefore be filed together as for certs etc.

Title: Re: Building to forcast
Post by aricon on 07/19/04 at 11:53:50

You can create multi-assembly work orders in WO-K-D.

Title: Re: Building to forcast
Post by cathyh on 07/19/04 at 12:13:12

Can you use a job number for your job folder? You can enter this on each sales order and it can be the same for all the sales orders. It will print on the work order also when you convert sales order to work order. You can sort by job number in sales order also.

Title: Re: Building to forcast
Post by aricon on 07/19/04 at 12:49:40

Cathy,

The problem with that is that the job number is not auto-generating. It is a UDF rather than a system field.

Title: Re: Building to forcast
Post by cathyh on 07/19/04 at 13:43:49

I guess I don't see a problem with that since I would create an alphanumeric job number unique to that blanket order ( for instance the customer code and date). The important thing in my view is that you can sort by job number in various lookups and reports. I have to admit that so far all we use the job number for is to add the serial number to a work order header (since we assign these early on in production), but that's what I like about the forum-- it gets you thinking about other ways to do things.

Title: Re: Building to forcast
Post by BillB on 07/26/04 at 13:21:14

Tried suggestions, but don't work.
Move tickets when brought to inspection show a sales order number, but no job number. inspection cannot associate to proper folder since move ticket has a new sales order number , no job number.

Title: Re: Building to forcast
Post by cathyh on 07/27/04 at 11:30:34

Yeah, Bill, I didn't look at the move tickets (we don't use them; instead we use routing numbers to print each sequence on its own page) but the field is missing from them. . Maybe Lynn would consider adding the job field to the move ticket??
The job number assigned in the sales order shows up on the aknowledgement, traveler of work order generated from the sales order, and invoice though.

Title: Re: Building to forcast
Post by Lynn Pantic on 07/27/04 at 14:22:08

What are you using for a Move Ticket? WO-E?

Title: Re: Building to forcast
Post by BillB on 07/29/04 at 10:44:41

We are using a custom program that is a "Move ticket"
It gives a Move from operation to a Move to operation.
I could have it added to it.