Gene,
I'm suggesting that instead of attempting to modify the BOM database to
accommodate the warehouse (which would be a very nice feature for INFOR to
add to the product!)
I'm suggesting that the BOM be changed to create the related BOM's. Let me
illustrated.
Let's suppose I have a BOM and associated routing that looks like the
following:
ENDITEM
-PART123
-PART456
-PART789
OPERATION 0010 MEXICO USES PART123 AND PART456
OPERATION 0020 BOISE USES PART789
If I represent the "Item Process" as follows:
ENDITEM
-0010 ASSEMBLY (MEXICO)
--PART123
--PART456
-0020 FINAL ASSEMBLY (BOISE)
--PART789
Then I would change it to the following:
ENDITEM
-PART789
OPERATION 0010 BOISE USES PART789
WIPITEM
-PART123
-PART456
OPERATION 0010 MEXICO USES PART123 AND PART456
I can then represent the indented "Item Process" as follows:
ENDITEM
-0010 ASSEMBLY (BOISE)
--PART789
--WIPITEM
---0010 ASSEMBLY (MEXICO)
----PART123
----PART456
You could then define in the warehouse a relationship type like follows:
Demand Warehouse: 1 (Boise) Relationship: 1(*DEF) Item: ENDITEM
Demand Warehouse: 1 (Boise) Relationship: 3(*ITEM-OUT) Item: WIPITEM
Demand Warehouse: 2 (Mexico) Relationship: 2(*ITEM-IN) Item: WIPITEM
When MRP runs for each warehouse, you will generate plan to build ENDITEM in
Boise and make it dependent upon supply of WIPITEM from Mexico. Here are
the steps.
1. You will generate an MO for WIPITEM in Mexico (Can use Auto-Release)
2. Receive WIPITEM to the warehouse in Mexico from the MO
3. TW Transfer from Warehouse 2 (Mexico) to Warehouse 1(Boise) (Note: you
need to have a reconciling location for "in transit", if you have R7.8 this
is automatic)
4. Receive WIPITEM into warehouse 1 Boise)
5. Issue WIPITEM to another MO that makes ENDITEM
6. Receive ENDITEM into stock in warehouse 1 and ship
In practice, this is very easy to do as all the MRP logic works normal, and
the transactions that each warehouse executes are also normal transactions
that are easily understood and implemented.
Where my clients get this messed up is when they think "hey let's automate
it and reduce the number of transactions". This of course is usually done
BEFORE they have control of the system. My experience has been that if the
transactions are done "as required" and then good six-sigma practices are
used to define improvements, that automating the transactions very rarely,
if ever, rise to the point that it justifies automating them. (Excluding bar
coding of course.)
Just note again, R7.8 has the "automatic" features built in.
Good Luck!
Kevin
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Gene lampe
Sent: Thursday, September 17, 2009 3:02 PM
To: MAPICS ERP System Discussion
Subject: Re: [MAPICS-L] (no subject)
Thanks for the information.
When you refer to splits, do you mean doing a manufacturing order split?
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx
[mailto:mapics-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Fox
Sent: Thursday, September 17, 2009 3:03 PM
To: 'MAPICS ERP System Discussion'
Subject: Re: [MAPICS-L] (no subject)
Gene
Correct, the MO assumes all material comes from the warehouse for the
finished item.
1 solution and 1 work around.
Solutions: Intersite Logistics is a XA (MAPICS) application designed to
resolve just this issue.
Work around: Split your bills such that the Mexico WIP is complete to
an
item level. Then this can be interplant shipped to Boise. Then a
separate
bill for the wip in Boise with the Mexican WIP production item as one of
the
components. This appears to cause some extra steps, but in reality
someone
is doing these steps offline now anyway. Also, with R7.8 you have the
ability to automate the transfer between the warehouses have an "in
transit"
location to answer the question "where is it now?".
Kevin Fox
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx
[mailto:mapics-l-bounces@xxxxxxxxxxxx]
On Behalf Of Gene lampe
Sent: Thursday, September 17, 2009 1:54 PM
To: mapics-l@xxxxxxxxxxxx
Subject: [MAPICS-L] (no subject)
I have a question for the group about multiple warehouses.
We are a job shop with two locations. One is in Boise, Idaho and the
other is in Mexico. We carry inventory in both of these locations and
are
in the process of separating this inventory into its own warehouse.
Right now the inventory is combined. Warehouse #1 is in Idaho and
Warehouse
#2 is in Mexico. We have some part numbers that need to be built in
Mexico
and then sent to our Boise location to be finished and vice versa. I
would
like to use the warehouse number as an indicator to where the inventory
is
supposed to go, but I have some problems.
1) Is there any way on a BOM to put a warehouse number on where the
material is going to be used from? For example, we have one process
that
starts in Boise and then is sent to Mexico to be finished. The only
materials used are at the Boise facility and the WIP then gets sent down
to
Mexico to be completed. The problem is when we create a Manufacturing
order
for warehouse #2, the BOM says all the material is going to be used from
warehouse #2, when in reality it is going to be used from warehouse #1.
I
know you can change this BOM at the M0 level, but I was hoping that
someone
had a fix for this at the routing level.
2) We are entering are orders in COM to ship from the preferred
warehouse based on a set of rules. As per my previous question, when we
have WIP being sent from Mexico to Idaho, the customer order has been
entered to ship from warehouse #1, but will be processed in Warehouse #2
and
then sent to warehouse #1 to be completed. I enter the manufacturing
order
to warehouse #1 and change the components on the BOM to warehouse #2
which
works fine except that MRP seems to only recognize the warehouse number
on
the header and not the BOM level. Is this correct? Is there anything
that
can be done to fix this?
We currently are running PDM in an XA environment, release 7.7.
Any feedback on this is greatly appreciated.
Thanks,
Gene
Gene Lampe > Director of Operations > Quality Thermistor Inc > 2108
Century
Way > Boise, ID 83709
O|208|377|3373 C|208|891|2319 F|208|376|4754 > glampe@xxxxxxxxxxxxxx
<mailto:glampe@xxxxxxxxxxxxxx> > www.thermistor.com
<
http://www.thermistor.com/>
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/mapics-l.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/mapics-l.
midrange.com
