MRP trying to parallel TEST to PROD

I'm trying to understand our production MRP messages.

To do so, I've refreshed TEST with PRODUCTION data for the following:
Item Master (4101), Item Branch (4102), Xref (4104),
Cost (4105), Price (4106), Lot Master (4108), Item/Location (41021),
BOM (3002), Routing (3003),
Sales Hdr & Dtl (4201/4211), Purchasing Hdr & Dtl (4301/4311),
WO Master (F4801), WO Parts List (3111), and WO Routing (3112).

I've also compared MRP Calculation Display (UDC 34/MM)
and Supply Demand Inclusion Rules (34004).

We don't use forecasting (3460)(but both environments are blank).

I've ensured that the DW version in TEST matches PROD.

In short, everything LOOKS the same between the two environments.
HOWEVER, when I run MRP, backdating to make sure DATES match, the results do not match.
Not even close.

Can anyone suggest what I've overlooked between PROD & TEST?

Please and Thanks
Gene

(Yet ANOTHER Friday brain cramp !)

(World A7.33)

Are you using the same F0010?

We have a Lib called GRTPLAN in the Library are the files listed below..
It allows us to run MRP and Capacity in a seperate Enviroment but based off of production data.
Perhaps it can help you...
Keep in mind, some of the files are logicals files that must point to the physical file that is in the GRTPLAN library.
Also, a couple of them are custom files and may not exist on your system.

F3311
F3311LA
F3311LB
F3311LC
F3311LD
F3312
F3312LA
F3312LB
F3312LC
F3312LD
F3312XX
F3313
F3313LA
F3313LB
F3313LC
F33133
F3411
F3411LA
F3411LB
F3411LC
F3411LD
F3411LE
F3411LF
F3411LG
F3411LH
F3411LI
F3411LJ
F3411LK
F3411LL
F3411LM
F3411LN
F3411LO
F3411LP
F3411LQ
F3411LR
F3411TEM
F3411Z1
F3412
F3412LA
F3412LB
F3412LC
F3412LD
F3412LE
F3412LF
F3412LG
F3412LH
F3412TEMP
F3413
F3413LA
F3413LB
F3413TEMP
F3413XX

F0010 is in synch between TEST and PROD.
Thanks for the thought.

Gene

Hello,

By Coincidence I'm running through same process myself at moment and have the list of files I am copying in front of me.

This seems to work ok for us but will be setup dependant.

F4101
F4102
F41021

F3002
F3003

F3111
F3102
F4801

F4311 (This takes a while on our system)
F4301

F3411
F3412
F3413

F0007
F3009
F30006
F30026

Would also like to do F4111 but to many records on our system to make justify full copy.

If the files are all in sync I'd double check your
processing options are in line.


Regards,

Paul Thompson

World 7.3 C7

Gene, excellent post in that you give us very specific details of your refresh into your Test environment for MRP run in Test. If others do not give you the names of other files that need to be refreshed from production, I recommend that you do a complete refresh of all files from production. Hopefully that will not overlay others' Test work. I use STRPDM, setting my view to physical files in Test, then a user-defined option to CLRPFM (TESTLIB/&N) all files. Follow up by submitting to batch another PDM option to CPYF PRODUCTIONLIB/&N TESTLIB/&N *ADD

Paul,

TYVM - I have not been copying General Constants (F0009) or WC Master (F30006),
I'll do so and give the wheel another spin.

If you are using lot control, add F4108 to your list.
The code can check for expired lots.

Gene

Eric,

Thanks for the compliment as to my listing file names.
Also thanks for the suggestion however a full data copy would fill our DASD to capacity.

FINALLY, congrats on the upgrade !
Make sure you keep us up to date on your progress.

Gene

Re: MRP trying to parallel TEST to PROD - General MRP question

Our work orders are limited by the size of mixing vats.
MRP keeps trying to cancel/combine work orders.
Where/How would I prevent this?

AGAIN, Please AND Thanks.
Gene
(starting to have brain function this Monday morning...)

Hello Gene,

Thanks for the tip on adding F4108 to my list. It is on there now. We are using lot and location but not expiry dates (in the area we are testing) at the moment but worth adding for future reference.

Regards Paul.

Paul Thompson
World 7.3 c7

WOHOO !

I (finally) wrote the CLP to do the CPYF and submitted it to run after PROD MRP.
Seems that timing can be everything.

Purchased items now match production.
MFGd item seem to match, but need further review.

A noteable exception to this are the "PAST DUE ORDER" msgs,
that are checked real time.

Scott's suggestion of GRTPLAN worked
wonderfully for "updating" MRP from production during the day.

NOW, I'm off to prove the benefit of "having the data filled in consistently AND correctly",
to gently guide them away from "MRP has a mind of its own".

THANKS AGAIN, all!

Gene