You answered your own question when you said "there seems to be a disconnect".
There are no simple useful data relationships between the Make To Stock supply orders and the orders (or jobs) generating the requirements - because the supply orders are Make To Stock.
Unless you are a 100% engineer (from scratch) to order environment, it probably isn't practical to manually link your requirements (as they arise) to MTS supply orders.
If it is practical/manageable - that is your answer.
If it is not, it is possible (but probably would result in achingly slow report performance that might bog the whole system down) that, if you run Pegging (with MRP or standalone) daily, you might have an outside shot of using the resulting Supply and Requirement table data to essentially do an on-the-fly MRP run on every unlinked open requirement. The goal would be to attempt to determine which pending supply order (at that instant in time) will likely fulfill it.
...Makes me shiver just thinking what a CPU cycle & memory eating monster a report like that would be.
Rob Brown
melissa hietala <kevmel822@...> wrote:
I'm looking at tying information between jobs, orders, and quotes. Jobs that are directly tied to an order (made-to-order) seem to tie in with the corresponding orders and quotes relatively well. However, jobs that are indirectly tied to an order (made-to-stock) are creating problems when trying to tie in the corresponding orders and quotes. There seems to be a disconnect. Wondering if there are any suggestions on how to tie made-to-stock jobs with the appropriate orders and quote tables without creating duplications?
Thanks,
Melissa Hietala
UMC, Inc.
melissah@...
__________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
[Non-text portions of this message have been removed]
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
[Non-text portions of this message have been removed]
There are no simple useful data relationships between the Make To Stock supply orders and the orders (or jobs) generating the requirements - because the supply orders are Make To Stock.
Unless you are a 100% engineer (from scratch) to order environment, it probably isn't practical to manually link your requirements (as they arise) to MTS supply orders.
If it is practical/manageable - that is your answer.
If it is not, it is possible (but probably would result in achingly slow report performance that might bog the whole system down) that, if you run Pegging (with MRP or standalone) daily, you might have an outside shot of using the resulting Supply and Requirement table data to essentially do an on-the-fly MRP run on every unlinked open requirement. The goal would be to attempt to determine which pending supply order (at that instant in time) will likely fulfill it.
...Makes me shiver just thinking what a CPU cycle & memory eating monster a report like that would be.
Rob Brown
melissa hietala <kevmel822@...> wrote:
I'm looking at tying information between jobs, orders, and quotes. Jobs that are directly tied to an order (made-to-order) seem to tie in with the corresponding orders and quotes relatively well. However, jobs that are indirectly tied to an order (made-to-stock) are creating problems when trying to tie in the corresponding orders and quotes. There seems to be a disconnect. Wondering if there are any suggestions on how to tie made-to-stock jobs with the appropriate orders and quote tables without creating duplications?
Thanks,
Melissa Hietala
UMC, Inc.
melissah@...
__________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
[Non-text portions of this message have been removed]
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
[Non-text portions of this message have been removed]