• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Data Refresh - List of E1 tables not to include

johndanter

Legendary Poster
Hi list,

I've been asked my opinion on a data refresh down from PD to UT PY etc.

Apart from the tables we currently have in mid SDLC, is there a E1 definitive official list of tables that should not be refreshed?

I'm thinking things like F983051 etc. They maybe different in terms of the versions that exist. That's just without even thinking too hard about it.

So is there such a list in place?

Thanks

John
 

brandonkirsch

Active Member
We always use R98403 to refresh non-Production environments. I don't know much about it except that it handles the dirty work for you, and since it's never been a problem I've never really had to look at it.
 

sselman

Well Known Member
if you have a "standard" JDE designed environment, you should be able to just do a database backup and restore of the data datasource. Update the schema and the security.

If you use BI publisher, you will need to watch for BI templates that are in the middle of promotion since those are stored in the data databases.
 

peterbruce

Legendary Poster
John,

I've never heard of a "E1 definitive official list of tables that should not be refreshed", but then again I've never looked for one either.

However, when we refresh, we only refresh business and control data schemas in the PY environment. We don't touch the PY or DV path codes or DV environment.
 

glen7x

Active Member
John, Typically Business data and control tables are the ones that gets refreshed. And we do this entirely. The table you mentioned, F983051 is part of central objects. For a data refresh, that does not come in to the picture.
And as mentioned, if there are any XMLP templates / Menu's etc that are in the works and exclusively in the lower environment, make sure that you back it up, else that will be lost.
 

David Robertson

Reputable Poster
Hi list,

I've been asked my opinion on a data refresh down from PD to UT PY etc.

Apart from the tables we currently have in mid SDLC, is there a E1 definitive official list of tables that should not be refreshed?

I'm thinking things like F983051 etc. They maybe different in terms of the versions that exist. That's just without even thinking too hard about it.

So is there such a list in place?

Thanks

John
Easiest is to copy or backup/restore PRODDTA and PRODCTL, which contain all of the business data.
The only real considerations are for sensitive information and large tables that you may not want or need in a testing environment, but that is dependent on your own data and available space.
F983051 should not be in there, as it is not business data, and should be considered part of the path code, and is a whole different thing to refresh.

An example, I generally clear these tables after refreshing a test environment (I would actually like to move them out of PRODDTA):
TESTDTA.F01131
TESTDTA.F01133
TESTDTA.F01131M
TESTDTA.F01131T
TESTDTA.F00165
 
Last edited:

Adrian_Chimirel

Legendary Poster
One caveat! IF YOU HAPPEN TO ADD any SQL View or MODIFIED any table in CRP (like adding a field or an index) and use the backup method, you will LOSE those modifications :D
 
Top