ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Sales >> Requested vs. Estimated Due Dates
http://www.istechforum.com/YaBB.pl?num=1078589350

Message started by perrinmfg on 03/06/04 at 08:09:10

Title: Requested vs. Estimated Due Dates
Post by perrinmfg on 03/06/04 at 08:09:10

We are looking for a good way to keep our estimated ship dates separate from customer requested ship dates when entering sales orders.

When we enter a sales order, we enter our estimated ship date and confirm that date back to our customer. Often we finish the order before our estimated date and the order ends up in storage until the estimated date causing our customers needless waiting and causing us to carry finished inventory longer than we need.

Does this cause anyone else any problems? and if so, how do you work around it?

Title: Re: Requested vs. Estimated Due Dates
Post by aricon on 03/06/04 at 09:11:30

Why don't you ship immediately upon completion? As soon as the work order is finished it should be forwarded to S/R for shipping and once shipped forwarded to the office for invoicing.

Title: Re: Requested vs. Estimated Due Dates
Post by perrinmfg on 03/06/04 at 09:52:51

In many cases our customers will not accept early deliveries so when possible we enter the estimated ship date to concide with the customers schedule. The problems occur when we have have to confirm a ship date later than the request date; if the item is finished early it sits until the ship date rolls around.

I'd like to find a way to be able to identify those orders that could be shipped early. Many systems handle by taking two dates at order entry: requested and scheduled. I suspect that it would require a major overhaul to add the two dates to DBA so I'm looking for ways other users handle this situation.

Title: Re: Requested vs. Estimated Due Dates
Post by aricon on 03/06/04 at 19:58:22

Well....this could be done without a major overhaul. If ISTS was to create a new report that simply produced a variance listing from Est. Ship Date in the SO as compared to Act. Finish Date from WO-I that should give you what you are looking for. ;D

Title: Re: Requested vs. Estimated Due Dates
Post by perrinmfg on 03/10/04 at 08:31:18

I guess I'm not quite following how this would solve my problem. The way I understand you, you're talking about about an on time shipment report. I am looking for a way of recording a customer's request date but at the same time entering a realistic ship date for confirmations and production scheduling. At a minimum I'm looking for a way to record on an order by order basis whether a customer will accept early shipments.

Title: Re: Requested vs. Estimated Due Dates
Post by Lynn Pantic on 03/10/04 at 09:10:36

There are 2 date fields in the Sales Order line item file (which becomes the invoice line item file) - the Estimated Ship Date and the Actual Ship date. When the order is in the Open SO file as opposed to the posted invoice file, the Actual Ship Date field is not used becasue it is not shipped yet. We could use that date as a second date relating to the projected shipment so you could have both the customer request date and your realistic projected ship date. Other people might use the same capability to differentiate between a customer required "On Dock" date as opposed to a ship date, thus allowing for transit time. Given that scenario, all currently existing orders have a date in the "Est Ship Date" field. If we added the capability to update both date fields in SO-A, all existing reports look at that currently populated field so I would think the new logic should continue to use that date as the Ship Date so MRP and the Shipping Schedule and other reports don't need to be changed and we can call the other date the "Customer Due Date". Comments or suggestions? What kind of reports would you want using the new date? Besides the obvious "Late Shipment" report listing orders with a Ship Date greater than the customer due date.

Title: Re: Requested vs. Estimated Due Dates
Post by aricon on 03/10/04 at 09:21:45

You're aware I'm sure that Ezijobz has this capability already?

Title: Re: Requested vs. Estimated Due Dates
Post by perrinmfg on 03/10/04 at 10:25:40

Yeah, thats what reminded me how bad I wish DBA had the capability.

Title: Re: Requested vs. Estimated Due Dates
Post by Karen Mason on 03/10/04 at 12:24:28

A slight help in the due date area: We use the work order to help identify due dates.

We wipe out the description and use it for a variety of info on the work order. In our case we use it to identify the heat code of the parts, the due date to customer, and the estimated date the raw material (steel) is due: it looks something like this:
B-5 D:03/30/04 S:03/15/04
This tells us the customer wants parts on March 30th and the steel is due in March 15. We release the order when the steel is received and change the steel date to IN.

Title: Re: Requested vs. Estimated Due Dates
Post by perrinmfg on 03/12/04 at 13:02:59

Good Idea! thats better than anything I was able to come up with. I'll give it a try and see how it works for me

Title: Re: Requested vs. Estimated Due Dates
Post by Lynn Pantic on 03/12/04 at 13:54:39

Next post (I hope this weekend) has an additional Customer Due Date field in the Line item entry of SO-A so you can enter both the Estimated Ship Date (your date) and the Customer Due Date (their date).

Title: Re: Requested vs. Estimated Due Dates
Post by aricon on 03/12/04 at 14:39:51

But what is the program doing with those dates? Or is the due date strictly notational? And is it going to be on the forms and/or reports? If so, which forms/reports?

Title: Re: Requested vs. Estimated Due Dates
Post by perrinmfg on 03/12/04 at 15:17:53

AWESOME!!! I never imagined you'd be able to make an addition like that, especially so quickly.

Just being able to store the data in the SO will help alot. If, and when, possible it would be nice if the additional date could show on SO-O-E Shipping Schedule and if it could display on the SOs screen in IN-A.

Thanks so much for making this happen Lynn!

Title: Re: Requested vs. Estimated Due Dates
Post by sharon krewson on 10/12/04 at 05:57:21

I am making a custom on-time delivery report using Crystal. But, I cannot find the customer's "dream date" once the order has shipped (from BKARHIVL). I see from Lynn's response that the unused ASD in the current BKARINVL is being used for this date. Does it just go away once the order ships? Or, can I retrieve the info from another file?

Thanks

Title: Re: Requested vs. Estimated Due Dates
Post by Lynn Pantic on 10/12/04 at 10:09:25

Turn on the On Time Delivery tracking and it is stored in ISARHCHG

Title: Re: Requested vs. Estimated Due Dates
Post by sharon krewson on 10/13/04 at 09:49:43

Thanks, Lynn.

Title: Re: Requested vs. Estimated Due Dates
Post by sharon krewson on 10/28/04 at 09:59:08

Thanks, Lynn. We did this but we kept getting the following error when we go into SO-A:

"A record was not found in FILELOC for file - ISARCHG.B-2 . The must be a record for each file opened."

I'm also not seeing this table to select in Crystal Reports.

What are we doing wrong?

Title: Re: Requested vs. Estimated Due Dates
Post by Lynn Pantic on 10/28/04 at 13:32:30

Since you have Evo, after you run the UPDFILE in classic DBA, you also need to download the file and follow the instructions at www.istechsupport.com/datadict.asp