Purge & Archive

We are looking to implement a purge and archive solution before we upgrade to INFOR 10. We have looked at NTT Data & TeamAbsolute's solutions. Any insight you are willing to share on either? Are there any other solutions that work with INFOR/Lawson?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

moellerg

You could always run the purge programs... (300 series) We've elected to not do that, because they don't get everything, and the only history that you have is the csv files produced by the different jobs.
We have actually looked at NTT Data & TeamAbsolute's solutions as well, and I'm personally leaning towards TeamAbsolute's solution. I've seen it at Inforum, and it really looks sweet!

unknown

We run PR300, then use Informatica to move the CSV files into an Oracle data warehouse where they are available for reporting if ever needed.

srijas

Roseann, we too are looking into a solution for the same reason. I've had some discussions with Lawson on their backoffice solution and it's crazy expensive. Can you share how much Absolute's solution is? We want something that we'll be able to continue to use so mostly want a tool to be able to do this every year. Do they have that or is it a one time deal?

unknown

We are going with the home-grown solution. We've created a new data instance that contains a copy of all the production data for smaller (e.g. employee) tables and "purged" data from large tables (e.g. prtime, prdistrib) pre-dating 2010. We now have an "archive" data instance. Next steps: create a new archive productline within the PROD environment (so authorized users can switch between productlines or queries can be written with joins between the two PL's) and implement Lawson Security rules so that the archive productline is inquiry-only. Finally, all the "old" data needs to be purged from the production PROD PL. What could possibly go wrong? Anyone care to comment on what we should watch out for when a) creating a second PL in our PROD environment and b) what our Lawson Security profiles and security classes should look like when we are done? Has anyone out there attempted anything remotely like this?

unknown

I'm finding this post quite interesting. I do like your proposal:). I'm curious though as to how you will continue to implement future env. and app. upgrades. Will you 'upgrade' your archived data and the applications; in addition to your 'current' data and apps? When you say 'purge' old data from prod, will you use lawsons programs (300 series) to do that? Greg says 'they don't get everything'; what exactly does that mean? Purging from production ... wow ... you sound adventurous. Any idea how long that might take; hours, days? Will your end users still be able to work while you're performing the purge?

CloudSuite Financials & Supply Chain Mgmt - Optimized Invoice Appr.mp4

unknown

Dennis--

Did you get my email? Donald.grochocinski@us.mcd.com

unknown

Donald:

In regards to your solution, a few things come to mind.
- Is your solution able to handle future application upgrades and customizations? Would you have to create a new PL for a future archive/purge cycle, or just add to the existing PL? Or replace the entire PL?
- Would the purge/archive PL basically contain 1-to-1 records from the source, or would it incorporate some kind of consolidation?
- What system codes does your solution incorporate? Payroll? Financials? Materials? Everything?
- How does your solution ensure that future archives beyond the 1st archive contain unique data from the 1st archive?
- How do you compare the archived PL numbers/reports against the archive?

unknown

We are interested in doing some clean up of old data prior to the v10 upgrade as well. We are currently on 9.0.1.10 for apps but the only systems we use here are the Purchasing and Financial Suites. When using the purge programs, are there parameters that need to be followed legally? For example - keeping 7 yrs worth of XYZ data. We've never done any purge/archiving in the past so just wondering what we really need to know.

unknown

The IRS web site has legal information about records retention. In my humble opinion, their guidelines should be considered a _minimum_ and going way beyond is okay. The real reason to clear out data is to keep data files down to a reasonable size; archiving data rather than deleting it is a very good way to have it when you need it.

Here's one of their pages: www.irs.gov/.../How-long-should-I-keep-records

bob-heitzman

With regards to how much data needs to be kept online we put that decision in the hands of our business units and left it up to them to determine how many years of data to keep on the live system for routine business access and how many years to keep on the archive system for historical needs. They had solid ideas on how many years of data could be needed for any court issues (which are typically HR data related) or audit requests (which are often Financial data related).

Copyright © 2025 Infor. All rights reserved.