Re: [Strategies for populating Test Data in a Development Environment]

b_gilmore

Well Known Member
Re: [Strategies for populating Test Data in a Development Environment]

Many times clearing records out a few tables will free up 50% or more of the
space allocated for the PRODDTA data set.

It depends on what modules you run but check these tables.

F42199 Sales Ledger
F43199 PO Ledger

[Messaging tables]
F01131M
F01131T
F01133
F01131
F00165 where GDOBNM = GT01131

Be sure and do a RGZPFM on each file you resize or clear to release the white
space in the files to the OS.

Good luck.




KBintz <[email protected]> wrote:

thought I would ask any way)What strategies are people using to create "good"
test data in the hundreds and hundreds of tables in JDE/OW in a development
environment?We had been copying full production data but the size of the
production data library is making that unacceptable. It has been suggested
that we extract only the data we need for testing but that is easier said than
done. We have a half a dozen programmers working on a couple dozen projects
at any one time. So, it is very complicated to select a subset of data,
maintain referential integrity, and keep eveyone happy and productive. Are
there any JDE/OW tools to extract a representative subset of data or do we
need to attempt to create our own? Are there any common strategies for
skinnying down data?Thanks in advance for any assistance.
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OWDEV&Number=60293
these messages, login to http://www.jdelist.com/forums, click Control Panel,
then click Edit by "Subscribe / Unsubscribe from receiving board posts by
email, change message notifications, etc." and adjust your subscription
preferences. JDEList is not affiliated with JDEdwards®
 
Back
Top