Possible archiving methods, and using them to resolve data quality issues

Methods of purging and archiving your JD Edwards system Leaving the JD Edwards system alone, and not purging and archiving Upgrading the hardware to increase performance Standard JD Edwards purging and archiving routines Building a home-grown purging and archiving solution in-house Purchasing a generic purging and archiving tool The benefits of purging and archiving with Purge-it! And how it solves these problems

Leaving the JD Edwards system alone, and not purging and archiving

Leaving the JD Edwards system alone, and not purging and archiving The situation does not get any better The data grows exponentially over time There is a higher risk of unwanted effects The data footprint gets larger – more records equals more space The system performance decreases – more records equals more processing time

Leaving the JD Edwards system alone, and not purging and archiving The Production system is holding old non-operational data The legal exposure gets greater – you may be holding data that you legally no longer need to, which would need to be provided to a court of law, if ordered to The data can get dirtier, increasing the amount of open, incomplete, or unprocessed transactions There is no business improvement through identification of historically open transactions The data growth is not actively managed and there are no ongoing improvements or benefits because of this

Leaving the JD Edwards system alone, and not purging and archiving Upgrades tend to be slower, longer, and less confident, due to a larger dataset resulting in fewer testing cycles You have longer backup times, and larger backup and replication requirements Users are less efficient due to the longer processing time of activities User satisfaction is decreased due to an ever decreasing performance of the system Third-party applications and interfaces are also affected with poor performance

Leaving the JD Edwards system alone, and not purging and archiving Overall, it is harder to perform day-to-day maintenance and project work, such as re-indexing of tables and performing data refreshes to other environments

Upgrading the hardware to increase performance

Upgrading the hardware to increase performance It is a very costly exercise. New hard disc drives might be relatively cheap, but increasing performance with higher specification processors and memory, and/or switching out to solid-state disk drives, is a very expensive option It can be a time-consuming exercise. If you have to wait until the next hardware upgrade cycle in order to increase the performance of the system, then you might be waiting a long time. Upgrading hardware just masks the underlying problem. The volume of data is still there, and it is still growing, in the Production environment. Increasing performance through hardware upgrade, does not tackle any of the other problems such as data growth management, incomplete transactions, legal exposure, etc

Standard JD Edwards purging and archiving routines

Standard JD Edwards purging and archiving routines There is a completely inconsistent approach for purging and archiving across the standard JD Edwards system A mixture of different terminology is used, including the words History, Ledger, Purge, and Archive, with no consistency throughout The majority of the UBE or Table Conversion processes actually purge the data, i.e. permanently delete the data with no chance of retrieval For the little data that is archived, there is no interactive access to that data from archive applications Some routines also delete the associated Media Objects

Standard JD Edwards purging and archiving routines There is no audit trail for any of the standard JD Edwards purging and archiving routines, so when the auditors ask who deleted the records, there can be no answer For data that is purged, i.e. deleted, there is no possibility of reversal, but even for those few routines that actually archive the data, there are no reversal routines There is very little validation in any of the purging and archiving routines, which could cause serious data integrity problems in the Production environment

Building a home-grown purging and archiving solution in-house

Building a home-grown purging and archiving solution in-house There is a much higher cost for creating an in-house purging and archiving solution, when considering the whole development life-cycle: design, development, testing, documentation, and support Because the software has to be developed from scratch, there is a much longer time to achieve any return on investment Comprehensive knowledge of data integrity across the JD Edwards system is required in order to maintain the correct referential data integrity when purging and archiving, and it can be the case that the validations employed in a home-grown solution are insufficient The documentation of the solution tends to be of poor quality, incomplete, or even non-existent Detailed knowledge of the development is generally held with only one person in the entire world

Purchasing a generic purging and archiving tool

Purchasing a generic purging and archiving tool Generic purging and archiving solutions are generally marketed as being "fully flexible" to cater for any possible situation, with JD Edwards modules. Because of this, it tends to take more time to achieve the desired solution, involving potentially more risk due to the “fully flexible” nature, and requiring more upfront consultancy in order to configure the purging and archiving routines.

Purchasing a generic purging and archiving tool They tend to be complex database-level tools that require coding in SQL-style scripts. This restricts the number of potential users of the software within an organisation to a limited set, and/or requires ongoing consultancy in order to create, maintain, and use the purging and archiving solution.

Purchasing a generic purging and archiving tool Because of the "fully flexible" nature, and the SQL-style configuration, the user inherently requires a field-by-field knowledge of the data integrity within a JD Edwards system so that the solution can be used effectively.

Purchasing a generic purging and archiving tool Generic purging and archiving solutions are marketed that they can access any database and any application, which thus requires them to be built in their own unique coding structure. This introduces proprietary terminology and interfaces into the process, which can be a significant barrier to archiving

Purchasing a generic purging and archiving tool Some generic solutions might store the archived data in non-JD Edwards table formats, disabling any possibility of accessing the data from with JD Edwards

Purchasing a generic purging and archiving tool System downtime is generally required to purge and archive with generic purging and archiving tools, due to their high intensity direct access to the database. Once the JD Edwards system is taken off-line, purging and archiving can occur during a “downtime weekend”, but archiving cannot occur at any other point throughout the year.

The benefits of purging and archiving with Purge-it The benefits of purging and archiving with Purge-it!, and how it solves these problems

The benefits of purging and archiving with Purge-it The benefits of purging and archiving with Purge-it!, and how it solves these problems Purge-it! is the only JD Edwards specific purging and archiving solution, and is designed within the JD Edwards Toolset for simplicity and for maximum data integrity Purge-it! is an off-the-shelf solution with nearly 200 users worldwide, backed up by dedicated Support and R&D teams, and with comprehensive end-user documentation Purge-it! is designed, built and supported by JD Edwards experts, with a holistic design approach across the entire system

The benefits of purging and archiving with Purge-it The benefits of purging and archiving with Purge-it!, and how it solves these problems The average JD Edwards experience of the Purge-it! specialists at Klik IT Ltd is over 25 years per person The data processed by Purge-it! is archived by default, with easy access to that archived data Purge-it! can be used to purge data from the archive, when your Data Retention Policy requires it Data is archived with Purge-it! at the document level, maintaining the data integrity of whole Orders or whole Batches Purge-it! activities are fully audited down to the individual transaction level, recording success or failure of purging and archiving, with full error reporting at the individual transaction level

The benefits of purging and archiving with Purge-it The benefits of purging and archiving with Purge-it!, and how it solves these problems There are hard- and soft-coded validations within Purge-it!, to protect the data integrity of the documents, but also to provide flexibility in configuration The standard JD Edwards method of bulk processing data is used by Purge-it!, i.e. UBE processes that run under the hood of JD Edwards Standard JD Edwards Batch Versions, Processing Options and Data Selection are used for easy configuration - Purge-it! does the hard work so that you don't have to There is a single job for each of the Purge-it! purge and archive routines, coded with C Master BSFN's for speed and efficiency

The benefits of purging and archiving with Purge-it The benefits of purging and archiving with Purge-it!, and how it solves these problems Purge-it! is a programmed solution that can make intelligent decisions at individual transactional level, i.e. it is not bulk SQL SELECT and DELETE statements Purge-it! runs and is managed within Work with Submitted Jobs, with summary PDF output Purge-it! can run 100% of the time that the JD Edwards system is online and operational, enabling full 24/7/365 operation of your Purge-it! purging and archiving solution Purge-it! error reporting shows why individual transactions were not archived, with full cause and resolution help text Purge-it! is a low risk solution, with static UBE and C code

The benefits of purging and archiving with Purge-it The benefits of purging and archiving with Purge-it!, and how it solves these problems Purge-it! has controlled flexibility via the specifically designed Processing Options Summarisation occurs within the Purge-it! purge and archive routines, on a record by record basis Un-summarisation occurs within the reversal routines, on a record by record basis Purge-it! has the ability to cancel mid-‘purge and archive routine’, whilst still maintaining full data integrity of all documents

Purge-it! requires no manual data integrity checking of documents after processing The standard JD Edwards installation method is used for Purge-it!, i.e. ASU's and ESU's Standard JD Edwards security also applies to Purge-it!

The benefits of purging and archiving with Purge-it The benefits of purging and archiving with Purge-it!, and how it solves these problems Standard JD Edwards Database Data Sources and OCMs are used to archive between locations and platforms when using Purge-it! Purge-it! has a choice of using either a separate archive environment, or accessing the archived data from within the Production environment Standard JD Edwards Task Views and Tasks are used to access Purge-it! from within the JD Edwards system Purge-it! has the ability to join purge and archive routines together in order to archive complete business process, e.g. Procure to Pay The standard JD Edwards Scheduler can be used to run the Purge-it! purge and archive routines in "unattended mode" Purge-it! Date Offsets allow dynamic calculation of archiving dates, providing a "fire and forget" solution on the JD Edwards Scheduler Standard JD Edwards Power Forms are used to create Purge-it! Dashboards, for Alert- Analyse-Act operations, and for active data management