parent/child


C

Craig

I was thinking about utilizing parent/child to order my products that come
in cases. The problem I'm running into is that currently I have these items
set up with reorder points lower than the case quantity. Ex. product comes
in a case of 48, my reorder point is 8. When item quantity goes below 8 it
reorders a case of 48, I then have 56 on hand of that item. Then, since I
have MPQ set to 48, 48 gets printed on PO instead of 1, hence I have to
manually change the quantity on the PO to 1 so that I don't receive 48
cases. If I set up parent item, when child goes to 0 it takes a case from
parent and parent reorders a case of 48. I then have 96 of that item on hand
instead of the 56. If I don't want to reorder until the child quantity goes
down to 8 I have to delete it manually from purchase order until items
quantity goes down to 8 and I want to reorder. Is there any way to put off
having the parent item get ordered until child quantity gets down to a
certain point. In this example 8?
 
Ad

Advertisements

J

Jay

Craig said:
I was thinking about utilizing parent/child to order my products that come
in cases. The problem I'm running into is that currently I have these items
set up with reorder points lower than the case quantity. Ex. product comes
in a case of 48, my reorder point is 8. When item quantity goes below 8 it
reorders a case of 48, I then have 56 on hand of that item. Then, since I
have MPQ set to 48, 48 gets printed on PO instead of 1, hence I have to
manually change the quantity on the PO to 1 so that I don't receive 48
cases. If I set up parent item, when child goes to 0 it takes a case from
parent and parent reorders a case of 48. I then have 96 of that item on hand
instead of the 56. If I don't want to reorder until the child quantity goes
down to 8 I have to delete it manually from purchase order until items
quantity goes down to 8 and I want to reorder. Is there any way to put off
having the parent item get ordered until child quantity gets down to a
certain point. In this example 8?
I would hope Microsoft has a good answer for you as I also have numerous
items like this. I believe the correct way for any program to handle
this is the reverse of how RMS handles it. When you receive 1 case the
program should convert it into the smallest selling unit. In your case
it would be very easy to set your ROP at 8 and then order 1 case.
The idea (theory) of selling by unit and breaking down 1 case at a time
is nice. In reality it never happens like that in a retail environment.
When was the last time you saw a cooler with just 1 can of soda waiting
for someonne to buy it so that they could open another case?
Jay
 
S

Steve Cookinham

I'm astounded the reordering is this primitive...I kept fumbling around
thinking I must be stupid, because I can't get the system to order the way
you are also trying for...if this is really as good as it gets isn't there
some sort of way to ask Microsoft programmers to address this as a critical
improvement requirement, if not an outright bug? (I'm new to the system and
the discussion group) I would never have bought this software if I had
realized this limitation in ordering flexibility
 
K

Ken K.

Hi Craig, we have an RMS add-on module that supports case-based purchasing
with out the use of parent/child. It you don't normally sell by the case,
you can avoid creating and maintaining the p/c relationships.

The module uses the MPQ to convert units to case quanities. It prints cases
& case cost on the PO. You can enter/edit PO detail lines using case
quantities & costs directly without first converting to unit quantities &
costs. You can add items using the supplier's reorder number directly
without creating aliases. You can control the item FIND function and
restrict items shown to the PO supplier or any group of suppliers. You can
copy an existing PO. If you have a partial receipt, you can close the
current PO and automatically carry forward the backorders to a "child" PO.
You can add new items on the fly directly from the PO edit window.

A download demo will be available soon. In the meanwhile you can e-mail me
for the demo.

Ken Kosnik
Computer Analytics Corporation
kkosnik at cacorp dot com
 
R

Roxanne

This is all well and good as far as pulling the next case quantity. What I
think should happen is that you order the case by case price - even though
you are selling by each price. That way on PO you order one case for $48.00
and sell each one for $1.00 without having to have a calcualtor to figure out
the pricing. Am I understanding the pricing to be this way correctly and has
anybody found a fix for this? Rob are you out there??
 
Ad

Advertisements

R

Roxanne

I have just read this post...after writing mine requesting this feature.
So...ignore the next post unless someone out there has written a solution to
this without having to purchase an add-on??
 
Ad

Advertisements

C

Craig

Hopefully MS will rectify this problem. Manufacturers/distributers compound
this problem by requiring some items be ordered as 1 = case, and other times
they want the amount thats in the case to = case. It would be nice to be
able to specify in the items properties how you would like to order that
item. Either as 1 = case or MPQ = case.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Child & Parent 1
Parent Child 1
Parent and Child Setup 0
Parent Child report 2
Parent child breakup? 1
Parent vs Child 2
child of poor parents? 13
Parent Child Relationships 1

Top