Chuck,
Regarding your desire for your DSP to use shorter blocks of time when calculating a stockorder, thus enabling a more accurate and rapid response to sales, I agree 100%. I have wished for just that many a time (when I lost a sale or had a stockout that I believe would not have happened with weekly time units). Weekly "time buckets" are common in manufacturing software packages designed for material (parts!) requirements planning. I have "dreamt" of bypassing our ADP system's STK routine and instead importing daily sales data into some custom program that would use weekly buckets. I would then design my own ordering algorithms using standard deviation and other weighting criteria for each source. Then I wake up. The phone is ringing. I've got to get back to work!
NS stocking status syndrome
42 posts
• Page 2 of 5 • 1, 2, 3, 4, 5
NS stocking status syndrome
by Mike Nicholes » Wed Feb 23, 2000 7:28 pm
Regarding AP and NS. Depending on the system you are using, changing AP to NS to retain sales history (whatever of there may be) must also include a change in the entry date to the current month and year. Otherwise, the system will read the identical parameters that take a part from stock to AP to delete, or from NS to AP to delete.
- Mike Nicholes
NS stocking status syndrome
by mbowers » Thu Feb 24, 2000 8:37 am
Thanks to Mike Nicholes for jumping in and reviving this topic.
This is a pretty sophisticated aspect of inventory management and deserves more attention than we've been giving.
Chuck Hartle`-- Any comments?
This is a pretty sophisticated aspect of inventory management and deserves more attention than we've been giving.
Chuck Hartle`-- Any comments?
- mbowers
NS stocking status syndrome
by Chuck Hartle » Thu Feb 24, 2000 11:21 am
Well.....
As usual, I do have something to add to this. Mr. Nicholes just gave an answer to a flaw that both ADP and ERA have with their system. When you do put parts back to "NS" test status after they have been on "AP" status or if you all of the sudden sell a part (or have a demand for the first time) that was on "NS" status, the system will put it to "AP" status and if you don't review these parts they will drop off of the system at the end of the month.
We have written custom programs to offset this bug for our clients so that we don't lose valuable sales history. We couldn't get an answer from anyone as to why this was occuring from either of the computer vendors. Now I know why it has this flaw, because it is triggered by the 'ENTRY DATE' of the part on the system.
My question is, Mike, what would it take for ADP and Reynolds & Reynolds to change the logic for the
As usual, I do have something to add to this. Mr. Nicholes just gave an answer to a flaw that both ADP and ERA have with their system. When you do put parts back to "NS" test status after they have been on "AP" status or if you all of the sudden sell a part (or have a demand for the first time) that was on "NS" status, the system will put it to "AP" status and if you don't review these parts they will drop off of the system at the end of the month.
We have written custom programs to offset this bug for our clients so that we don't lose valuable sales history. We couldn't get an answer from anyone as to why this was occuring from either of the computer vendors. Now I know why it has this flaw, because it is triggered by the 'ENTRY DATE' of the part on the system.
My question is, Mike, what would it take for ADP and Reynolds & Reynolds to change the logic for the
- Chuck Hartle
NS stocking status syndrome
by eweirick » Mon Mar 20, 2000 9:46 pm
Fist time reply.
After reading this topic I thought I might add a caution to using the "SP" special status in ADP.
The SP status as defined by ADP: "SP for special purchase. The part has been special ordered for a customer. If future demand meets your stocking criteria before the sale is posted for the customer, the status is removed and the part becomes active. If insufficient demand occurs, the part is automatically deleted after the on-hand and on-order drop to zero."
As you can see, this special status can totally defeat the testing of new parts. If you were to add a new part to your system this month with a status of SP and sell it this month, it would drop off the system at month end (if 0 on order). SP would be a great way to code non-factory onetime purchases (parts for a different make used car, etc.). The history is maintained in PDA and you would not be cluttering up your system with one-time purchases.
To Chuck Hartle - ADP does allow the changing of the entry date. We are running release IN635B and it allows entry date changes in function PM. I've just recently gone to work for an ADP dealer (been with an ERA dealer for the last few years) and can't remember being able to do this way back when. Must be something new.
A general note: from what I've read today this is a great forum. I'm going to pass this web site on the every parts manager and factory representative I know.
------------------
Ed Weirick
After reading this topic I thought I might add a caution to using the "SP" special status in ADP.
The SP status as defined by ADP: "SP for special purchase. The part has been special ordered for a customer. If future demand meets your stocking criteria before the sale is posted for the customer, the status is removed and the part becomes active. If insufficient demand occurs, the part is automatically deleted after the on-hand and on-order drop to zero."
As you can see, this special status can totally defeat the testing of new parts. If you were to add a new part to your system this month with a status of SP and sell it this month, it would drop off the system at month end (if 0 on order). SP would be a great way to code non-factory onetime purchases (parts for a different make used car, etc.). The history is maintained in PDA and you would not be cluttering up your system with one-time purchases.
To Chuck Hartle - ADP does allow the changing of the entry date. We are running release IN635B and it allows entry date changes in function PM. I've just recently gone to work for an ADP dealer (been with an ERA dealer for the last few years) and can't remember being able to do this way back when. Must be something new.
A general note: from what I've read today this is a great forum. I'm going to pass this web site on the every parts manager and factory representative I know.
------------------
Ed Weirick
- eweirick
NS stocking status syndrome
by Chuck Hartle » Mon Mar 20, 2000 10:06 pm
Hi Ed,
Thanks for the posting. You are correct that ADP allows you to alter your entry date in program "PM" (the second prompt under option "C"). The ERA system shows it to you in the 2101 and 2102 screens, but you cannot alter it at all.
The point I guess I am driving at Ed is that you would think that ADP and Reynolds and Reynolds both could easily change the "MNS Testing Criteria" to look at the last sale date rather than the entry date. If you alter your entry date to "20MAR00" and you have two sales in 1999 it is going to look funny and it could throw off some of the reports that are generated. Again, this is just one of those 'faults' the system has and you have to alter it yourself.
You are absolutely correct about "SP". The good news is I have done over 100 analysis on ADP systems in the last year and no one has used the "SP" status code that I have seen. You bring up an interesting point about using this code for non-factory related material and I like it. Are you using this code now for that purpose?
Chuck Hartle'
Thanks for the posting. You are correct that ADP allows you to alter your entry date in program "PM" (the second prompt under option "C"). The ERA system shows it to you in the 2101 and 2102 screens, but you cannot alter it at all.
The point I guess I am driving at Ed is that you would think that ADP and Reynolds and Reynolds both could easily change the "MNS Testing Criteria" to look at the last sale date rather than the entry date. If you alter your entry date to "20MAR00" and you have two sales in 1999 it is going to look funny and it could throw off some of the reports that are generated. Again, this is just one of those 'faults' the system has and you have to alter it yourself.
You are absolutely correct about "SP". The good news is I have done over 100 analysis on ADP systems in the last year and no one has used the "SP" status code that I have seen. You bring up an interesting point about using this code for non-factory related material and I like it. Are you using this code now for that purpose?
Chuck Hartle'
- Chuck Hartle
NS stocking status syndrome
by jdpetey » Mon Mar 20, 2000 11:21 pm
Hello Chuck & Ed,
All of the observations that have been noted about many of the status' that have been mentioned, I have also recognized.
I haven't been using the SP status. I tried to find a use.
I would like to know if there is any purpose for this status at all!!!!
My desire would be that special order parts could be added to our system with an automatic status (temporarily) indicating that the origin of entry was a special order, and, until the part reached the desired phase in, no matter what source, the SS status, which is in my display field, would indicate the part was special ordered.
The immediate delete with "0" O.H. is a little too hasty.
This would eliminate the need to separate special ordered parts into a special source in order to track their sale or MNS. The MGR report monthly would automatically calculate SP values.
Sourcing is great for some purposes, but, all in all, I think we can get carried away with it too much.
Make any sense?
jdpetey
All of the observations that have been noted about many of the status' that have been mentioned, I have also recognized.
I haven't been using the SP status. I tried to find a use.
I would like to know if there is any purpose for this status at all!!!!
My desire would be that special order parts could be added to our system with an automatic status (temporarily) indicating that the origin of entry was a special order, and, until the part reached the desired phase in, no matter what source, the SS status, which is in my display field, would indicate the part was special ordered.
The immediate delete with "0" O.H. is a little too hasty.
This would eliminate the need to separate special ordered parts into a special source in order to track their sale or MNS. The MGR report monthly would automatically calculate SP values.
Sourcing is great for some purposes, but, all in all, I think we can get carried away with it too much.
Make any sense?
jdpetey
- jdpetey
NS stocking status syndrome
by eweirick » Tue Mar 21, 2000 9:42 pm
Hi Chuck,
I get the point. Using last sale date in place of entry date is obvious. I'm going to email my ADP rep. and see if we can get the ball rolling. The dealer principal at my current location recognized this problem years ago and developed a user program to correct it. The program is run after month end and looks for parts set to DEL with a YRSL greater than zero. It then resets the special status to NS. Now, because the entry date has not been changed these parts cycle right back to DEL but since we run it every month it doesn't matter. Once the part has a YRSL of zero it deletes. I like this approach because it also resets AP parts, giving those parts another shot at phasing in. I've been with Mercedes-Benz dealers for a number of years and we see a good number of parts phase in a second or third time. This program can save an extra hit when looking at phase in.
Hello jdpetey,
The SP status in ADP. Is there is any purpose for this status? Yes, it was designed for ONE-TIME purchases. I do not currently use it but I did back in the late 80's. I was with a dealership that did a large volume of alternate make used car refurbishing. We had no desire to track these purchases so we used the SP status to keep our system clean.
Another thing you might be interested in. When we started using the SP status we also started using our purchase order number for the part number on all one-time or non-factory purchases. This really helped us out in warranty situations. No more trying to figure out who you bought the darn thing from. The purchase order number was right there on the repair order. I'm sure hundreds of parts managers do this, but at the time I looked at it as a revelation from heaven.
I'm a little unclear on your desire to track special order parts without utilizing a separate source. It sounds to me like you might be having trouble separating special orders from parts you have knowingly forced into stock. In our system the only parts that have a special status of NS are in fact special order (or lost sale) parts. When we see NS in our display line we know it is a non-stocking part. I know that you don't like the idea of having too many sources, but we set up a separate source for items we force into stock (service parts for a new model year vehicle) and we bring them into inventory with a blank status. This separate source allows setting the phase out criteria so that the part doesn't go away after it finally starts selling. Once it starts selling we move it to a normal stocking source. Let me know if I didn't fully understand your needs.
Hope this helps.
Chuck, I know this was a little long winded and these topics may have been covered in the past so feel free to edit as needed.
------------------
Ed Weirick
I get the point. Using last sale date in place of entry date is obvious. I'm going to email my ADP rep. and see if we can get the ball rolling. The dealer principal at my current location recognized this problem years ago and developed a user program to correct it. The program is run after month end and looks for parts set to DEL with a YRSL greater than zero. It then resets the special status to NS. Now, because the entry date has not been changed these parts cycle right back to DEL but since we run it every month it doesn't matter. Once the part has a YRSL of zero it deletes. I like this approach because it also resets AP parts, giving those parts another shot at phasing in. I've been with Mercedes-Benz dealers for a number of years and we see a good number of parts phase in a second or third time. This program can save an extra hit when looking at phase in.
Hello jdpetey,
The SP status in ADP. Is there is any purpose for this status? Yes, it was designed for ONE-TIME purchases. I do not currently use it but I did back in the late 80's. I was with a dealership that did a large volume of alternate make used car refurbishing. We had no desire to track these purchases so we used the SP status to keep our system clean.
Another thing you might be interested in. When we started using the SP status we also started using our purchase order number for the part number on all one-time or non-factory purchases. This really helped us out in warranty situations. No more trying to figure out who you bought the darn thing from. The purchase order number was right there on the repair order. I'm sure hundreds of parts managers do this, but at the time I looked at it as a revelation from heaven.
I'm a little unclear on your desire to track special order parts without utilizing a separate source. It sounds to me like you might be having trouble separating special orders from parts you have knowingly forced into stock. In our system the only parts that have a special status of NS are in fact special order (or lost sale) parts. When we see NS in our display line we know it is a non-stocking part. I know that you don't like the idea of having too many sources, but we set up a separate source for items we force into stock (service parts for a new model year vehicle) and we bring them into inventory with a blank status. This separate source allows setting the phase out criteria so that the part doesn't go away after it finally starts selling. Once it starts selling we move it to a normal stocking source. Let me know if I didn't fully understand your needs.
Hope this helps.
Chuck, I know this was a little long winded and these topics may have been covered in the past so feel free to edit as needed.
------------------
Ed Weirick
- eweirick
NS stocking status syndrome
by Rex » Wed Mar 22, 2000 12:39 am
Ed,
I don't like the approach of changing the entry date because I like knowing what the true entry date is. Somehow it just doesn't look right to see month-by-month sales with an entry date of last week.
I too have a special program that runs in the job stack and changes anything with AP or DEL status and with YRSL greater than 0 back to NS.
ADP users can email me to get it.
------------------
www.powerprograms.com
I don't like the approach of changing the entry date because I like knowing what the true entry date is. Somehow it just doesn't look right to see month-by-month sales with an entry date of last week.
I too have a special program that runs in the job stack and changes anything with AP or DEL status and with YRSL greater than 0 back to NS.
ADP users can email me to get it.
------------------
www.powerprograms.com
- Rex
NS stocking status syndrome
by Chris » Thu Mar 23, 2000 11:21 am
Hi Chuck,
Whew, long winded thread here but very interesting and informative.
I'm on a UCS 7000 system (Ford) pthew.
I would like your input reguarding the fact that anytime I special order a part via their special order system it generates sales history. Lost sales they say but non the less, sales history that is reviewed by their stock order process.
Example: I order one of part xyz and generate a sale history. 30 days later I move the part from the special order shelf and software database to the normal stocking shelf and normal stocking database (hoping to sell or return to vendor). Customer comes in 10 days later and wants the part. Now I have a sales history of 2.
Attempting to be a proactive dealer the stock order process spots 2 sales in 60 days and burps up a suggested order.
Bottom line, my question is what are your thoughts reguarding a system that automatically assigns sales history to a special order?
------------------
Chris Bledsoe
Pts Mgr
Pulliam Ford
Columbia, SC
sysop@clynx.com
Whew, long winded thread here but very interesting and informative.
I'm on a UCS 7000 system (Ford) pthew.
I would like your input reguarding the fact that anytime I special order a part via their special order system it generates sales history. Lost sales they say but non the less, sales history that is reviewed by their stock order process.
Example: I order one of part xyz and generate a sale history. 30 days later I move the part from the special order shelf and software database to the normal stocking shelf and normal stocking database (hoping to sell or return to vendor). Customer comes in 10 days later and wants the part. Now I have a sales history of 2.
Attempting to be a proactive dealer the stock order process spots 2 sales in 60 days and burps up a suggested order.
Bottom line, my question is what are your thoughts reguarding a system that automatically assigns sales history to a special order?
------------------
Chris Bledsoe
Pts Mgr
Pulliam Ford
Columbia, SC
sysop@clynx.com
- Chris
42 posts
• Page 2 of 5 • 1, 2, 3, 4, 5
Who is online
Users browsing this forum: Google [Bot] and 10 guests