Splitting DRP Orders between 2 Facilities

<vendor>



Hi Tom ...

Conceptually speaking .... might be worth experimenting with this:

Let's say the sold item has item code M300. Create a final assembly bill for
M300 with two phantom children (M300-A and M300-B). Set up the math so that
(quantity needed of M300-A) + (the quantity needed of M300-B) equals one.
Source M300-A out of facility A and source M300-B out of facility B. Arrange
the child math to split the volume 50/50 or 40/60. I suppose you could use
effectivity dates to manage movements from 50/50 to 40/60.

I'm not confident you can define a child as a phantom in a final assembly
bill. If not, you could experiment using a plain Jane BOM.

Gotta be careful with cost of sales ... part of the experiment requires
examination of cost of sales effect. And ... you already knew this ... the
accounting policy person has to be involved to make sure that the
inter-facility transactions sustain inventory valuation according to GAAP.

Seems like it would be more fun and less maintenance than using firm planned
orders. Let me know if you can get it to work.

Peace to you,
Milt Habeck
Unbeaten Path International
(888) 874-8008
+262-681-3151



</vendor>







From: Molyneux, Tom
Sent: Thursday, October 06, 2011 6:08 AM
To: BPCS-L@xxxxxxxxxxxx
Cc: Beever, Mike
Subject: Splitting DRP Orders between 2 Facilities

The exact requirements of this are a bit vague yet, but I've been asked to
investigate possibilities.

We have a selling facility which takes products from 2 of our manufacturing
facilities. Is there any way for BPCS planning to split requirements for the
parts between the 2 facilities, so that 50% of the requirement would be
loaded on a DRP order to facility A and 50% would be loaded on facility B. Or
60% on one, 40% on the other.

Not sure if the splitting would be done at individual part level, or on a
consolidation of parts for each due date, or whatever....

Just wanting to get some idea if anyone else does anything similar.

We are on ERP Lx 8.3.2

Thanks in advance
Tom Molyneux

NOV Mono
MIS Department