From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key things to factor in...” by Sarah Mack of TeamCain (April 23, 2012), this presentation highlights the 6 factors to keep in mind when approaching a JD Edwards data purge project.

1. Are You About to
Embark on a
Data Purge
Project?
Here Are 6 Key Things to Factor In
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here
are 6 key things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain

2. Have you tried a purge before, or considered
a purge, but were held back by concerns
about integrity or completeness?
You are not alone...
Our surveys show that this is one of the main reasons why
organizations don’t purge their JD Edwards data.
Our experts recommend purging and archiving every couple
of years at a minimum, and for sure if you have at least 7+ years
of data.
The thought of a purge project can be daunting. Here are six key
questions to ask yourself when about to embark on a data
purge project to make sure that your project goes smoothly.
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key
things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain

3. Question #1
What “date horizon” should be used?
• Consider your timeframe
This is based on the data retention policy that is set up in
your organization
• Factor in legislative, business, and legal
requirements
What information have you needed in the past that is
important for the future?
• Approach your application users
They know what they need from the data
*A total of 7 years on your system is sufficient to making
sure you are adhering to any requirements and keeping
your system up to date
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key
things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain

4. Question #2
Which modules should you purge, and
how will you decide?
Not all modules are equal and lots of applications run in JD Edwards, so...
STEP ONE
Look at the most heavy transaction files (AP, GL, Work Orders etc.) - which of
those modules are critical to your business?
STEP TWO
Analyze how much space each application uses and which one uses the most.
STEP THREE
Look at your custom files – how do they work with JD Edwards, how are they
linked with JD Edwards, will you need to purge these files along with the JDE files?
*Help from experts in analyzing your data files and determining
where to get the most “bang for the buck” often is a good idea.
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key
things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain

5. Question #3
Do you have custom tables and/or add
on applications?
Having add-on applications and custom tables is very common among
JDE customers – these are usually the F55 – F59 series files and
applications.
Many have custom development for specialized purposes like extended
SOP or specialized CRM.
You need to keep these in
mind when approaching
your purge project.
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key
things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain

6. Question #4
Who will need to be involved?
Those who work with the applications need to be involved so they can say yes this is okay to purge and make
sure that which has been purged and archived is correct. There are 3 main levels of staff and external
involvement:
Level 1: We want to do it all ourselves as much as possible.
This is a great approach if you have the staff and time - you are up to speed and have the
internal knowledge then to carry on subsequent purge and archive projects. Remember, the
business users are the
Level 2: We want to be involved but don’t have the time to do most of it real owners of the
data!
ourselves.
This is likely the most common scenario we encounter. You set up the project so that you
get the knowledge you need to be self sufficient but don’t cramp your staff time.
Level 3: We want to get it done, but don’t have the time ourselves.
Bringing in a partner who understands JD Edwards, your needs, and purging can make this
a simple project. BUT your business users still need to review and sign off on what will be
purged (and archived).
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key
things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain

7. Question #5
How will you maintain the data
integrity inherent in JDE?
Be careful that if you are taking data out of one application, that it is looking at all
the files relevant to that application and not leaving anything behind. If it did
leave items behind, your data integrity could be compromised.
You want to make sure that the users are verifying the integrity of the data that is
being purged, so make sure to run JDE integrity before and after the purge project.
Avoid the “Domino Effect”!!!
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key
things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain

8. Question #6
What will you do with the archived
data?
In order to answer that question, consider these questions:
• Is a team going to go back and look at the archived data?
• Do you want to take the data right off your system right
away?
• Will keeping some of the data on your system be sufficient
enough in case you need to access it?
• Do you want to keep the archived data until that next purge
project?
• How often will you purge, who will be on that future project
team, what is going to be purged and how far back you are
going to go?
You can always purge the archived data at a later date if you wished.
Having simple access to archived data makes your users a whole lot happier.
From the TeamCain Blog Post “Are you about to embark on a data purge project? Here are 6 key
things to factor in...” by Sarah Mack, April 23, 2012 © TeamCain