La-Z-Boy makes use of most modules in JD Edwards EnterpriseOne, and makes heavy use of the distribution and manufacturing modules in particular. With over 2TB of data and multiple sites coming on to JDE, there was a definite need to be able to keep their JDE tables clean and crisp. Too much data would impact their data copies, backups, and batch jobs - they wanted to get on top of this before it became a problem. Being risk adverse, they needed a rock solid solution. Originally presented at JDE INFOCUS 2013 (December 03, 2013)

1. La-Z-Boy keeps JDE humming with clean data using
Purge-it!
Presenter (remote) :
Andy Weidenbach, ERP Program Director
La-Z-Boy Incorporated
Presented at InFocus 2013 –Session ID 1001870
Facilitator
Mike Guerin, President, TeamCain

2. Agenda

Introduction to La-Z-Boy


Our JDE set up and environment
Why we decided to purge and archive our JDE data
Selection, decision and implementation process
Current process JDE purge and archive
Summary of benefits and lessons learned

JDE Purge and archive best practices, courtesy of Mike Guerin

Wrap up and Questions




3. About La-Z-Boy





Established in 1927 –first recliner sold by “
Floral City
Furniture”(our original name)
First upholstered recliner –1929, and with it the new
name of La-Z-Boy
First Reclina-Rocker –1961, propelled growth
immensely
Went public March 1961
Revenue exceeded 1 billion in 1997

4. Our JDE set up, environment and upgrade




Went live initially on JDE 8.9 in 2007, staged module go live
Migrated to JDE EnterpriseOne with 9.0 in 2011 (still there)
1775 users, 600 concurrent average
JDE Modules Used at La-Z-Boy:
•
•
•
•


Financials (AP, AR, GL), Fixed Assets
Distribution / other (PO, SOP, IN)
Manufacturing –heavy usage (bread and butter)
Fair number of custom tables
JDE support staff size is about 12 in total, total IT is just shy
of 100
Running Intel / SQL Server at present, VMWare, etc.

5. Why we looked for a purge and archive solution





Data files growing rapidly and needed to get a handle on the
growth –currently 2.2 TB
2009 implementation in Mexico added immensely to records
2010 –up to 200 million mfg transactions
Made system changes, down to ~ mfg 100 million
Performance impact

6. Why we looked for a purge and archive solution

7. Solution selection and implementation
Alternatives reviewed, decision factors




Looked at JDE “
tactical”purge processes –would have needed
to customize
Determined needed “ of the box”solution / JDE specific
out
Looked at several solutions out there –end 2011
Decided to go forward with Purge-it! –less of a technical
solution, more user friendly, more like JDE

8. Solution selection and implementation
Decision factors





We are risk averse, and wanted a solution the business users
could have control over (not IT)
Ability to largely implement the solution ourselves, and have
“
ownership”of it going forward.
Purge-it! worked within EnterpriseOne –easy for users and IT
to set up, manage and work with
Ability to view archived data within PROD without separate set
up / sign on / environment
Audit reports and capabilities; reversal

9. Solution selection and implementation

10. Solution selection and implementation

11. Solution implementation

Decisions and process:
•
•
•
•
•
•
•
•
Purged from the “
outside in”in terms of modules, so MFG PO Sales
and Inventory AP AR and GL in pretty much that order
Allowed us to purge related transactions and work down to the final
“
resting spot”of GL
Thought GL would be the “ one”but turned out MFG was instead
big
Keep 16 months in PROD for MFG, determination in process for how
much to keep in archive
Purge for other modules to come, business discussions happening
Ran in the usual proof mode then final mode
Currently –about 10 million transactions per year in GL and IN, about
23 million in MFG
Light on SOP right now, but will grow as we expand use of it

12. Solution implementation

13. Solution implementation

Our experience:
•
•
•
•
•
•
•
Installed the ASU, package build and deploy
Got a couple of hours training from Klik IT for config and
processing options / jobs
Started late 2012 after installing / testing in 1st half of 2012, then did
the sequence of purges.
Completed proof and final modes within a couple of months –series
of purges.
Beg of June –over 200 million records in MFG modules; by second
week of July were down to about 100 million (50% reduction)
Validated records counts between production and archive
We are using the “
FYK”set up –easy access to archive data in
production; thinking of changing to standard table name option for
reporting and BI processes and setup.

14. Our Purge / Archive process now





Doing purge on a rolling basis –monthly now for MFG side
Move to archive, just letting the archive grow for now
Do it all ourselves
Have the “
custom”module –use it for MFG add on / tag
files
Have tested out and are ready for the PD purge / archive for
other modules … just a matter of timing with other higher
priority projects going on (hopeful spring / summer 2014)

15. Purge-IT: features we liked
•
•
•
•
•
Uses JDE menus for access and set up –what we and our users are used
to
Single job runs the whole process
Archive access –choice available for how to do this with latest release
is helpful for us going forward
Installed as ASU –in our comfort zone
As we upgrade, will just get the new Purge-it! version for the JDE
release and move forward; new Purge-it! releases include updates to
archived FYK tables for new release

16. Our payback …
We received the following payback from implementing Purge-IT!:





With the PROD access to archived data, users have easy access to
this data –not widely used, but very helpful
We started (pre purge) with 200 million MFG table records and
ended up with half that after the initial series of purges
Data copies are less time consuming now (partially due to PurgeIT!, partially due to processor / horsepower changes) –from 8
hours to 4
Virtually no consulting “
drag”for implementing
Upgrade assistance will be minimal

17. What we like about it
User Perspective:
– Works, looks and acts just like JDE
– Access to the archived data, although not huge, is helpful
IT Perspective:
–
–
Simple to install and use
Works just like JDE –contributing to the ease of use: processing options,
data selection, JDE menu access, inquiry screens for archived data

18. Our “
lessons learned






Easy to get busy and leave purge and archive as a “
somewhere
down the road”project –don’ do this!
t
Don’ be a “
t
data hoarder”
Involve business users –for course of actions, what stays in
prod and what goes
Stay on top of it –purge and keep clean
Consider reporting / data retrieval side of things –
should
impact what you end up doing for archived data
Select the right tool

19. Questions ?

20. Purge and archive best practices
Courtesy of Mike Guerin / TeamCain

21. Purge and archive best practices
Why purge and archive?
• Performance
• JDE is a batch system and transactional … performance can drop significantly
• Upgrade
• Most common reason of late … purge before upgrade can reduce risk and
speed things up (can always migrate archived data later). Gets rid of “
dirty
data”too
• Business change
• LOB sold off, plant / location closed
• Disk and backup
• Disk is “
cheap” but not never ending. Backup implications
,
• Spin off impact
• BI Data loads, disaster recovery …
• If you have more than 10 years –it is probably just time to get it done.
• Did you realize? 10 minutes per day for 50 people = 1 Full Time Equivalent

22. Purge and archive best practices
What to purge and archive?
• Look for the “
heavy hitters”–larger transaction files (typically GL, AP,
AR, PO, IN, SOP
• Run reports to show disk usage in descending order –record counts too
• Watch for tag files –often these are heavy disk use as well (F55 –F59)
• Add on systems?
• Master files? Often not (other implications) and often not large usage /
performance implications
• Old / dead / dirty data that can be swept away?

23. Purge and archive best practices
When to purge and archive, and how far back?
•
•
•
•
•
•
How much to keep –question for the business
Most common –current plus 2 in PROD; another 2 in Archive tables
Can be up to 7 in PROD depending on industry
Legislative –what MUST you keep and how accessible does it need to be?
Reverse also holds true –if the data is there you will have to produce it (exposure)
Users will almost always want more –ask the “
why”question. Often can be
satisfied in other ways
• Consider go-forward plans as well –how often (monthly, quarterly, annually) as a
best practice

24. Purge and archive best practices
Who is involved?
• A purge and archive project is a business project supported by technical
staff
• Users own the data, IT owns the process to manage it and deal
appropriately with storage and technical aspects
• Business staff decide on purge and archive cut-off dates, companies / units
to carve off, legal interpretations, etc.
• Business users should sign off on test purge results and validate the data
• Outsourcing can make sense depending on schedules … but not the sign
off by users

25. Purge and archive best practices
Watch out for / other points
• Integrity
– Normal to keep, but sometimes need to break
• What to do with archived data
– Who needs access / how often
• If upgrading
– Benchmark time needed for data conversion
• Pre or post upgrade?

26. Our recent customer survey –selected details
• Top features
– Ease of use
– No table locks or system down time
– The option to self install / self train / self operate
– How Purge-it! looks, feels and works just like JD Edwards
– The out of the box access to archive data within Production (only for
EnterpriseOne clients)
– Single process for purge, summarize and archive
• Top Reasons for choosing Purge-IT!
– Ease of use
– Ability to access archived data from within production directly
– Price / investment
– How it worked just like JD Edwards
– Product presentation

27. Our recent customer survey –selected details
• Over 95% said they would purge as part of their upgrade, and 85% said it
would be before the upgrade
• About 60% do annual purges, another 25% as required
• Current + 2 most common retention policy
• About 83% use custom tables
• 58% purged in less than a month, none were more than 3 months elapsed
time
• About 25% had used JDE purge routines before, just under 50% had done
nothing, 12% had used ARCTOOLS

28. P - Purpose built
JDE, release, module, no hardware, no MTR's
U - Update or proof
Comfort and confidence
R - Reversible
Whole, part
G - Get access to data
Archive data in PD, safe, secure, no new Environments
E - Extendable
Modular, Custom module, ASU install and updates, multi-server
I - Integrity
Hard- and soft-coded, preserves data integrity
T - Toolset
Middleware, CNC, easiest to configure and run

29. How can we help??








Come chat at our booth
Get a copy of this presentation
Arrange to speak with Andy at La-Z-Boy (or others)
File review for recommendations on what to purge
One page “
Benefits of a JDE purge and archive”document
Recorded solution webinars on our site
Specific presentation for you?
Happy to provide investment estimate

30. How to reach us…
Andrew Weidenbach: andrew.weidenbach@la-z-boy.com
www.teamcain.com
Michael_guerin@teamcain.com President | TeamCain
John_Hein@teamcain.com Director of Sales | TeamCain