Purging Strategies with JD Edwards Software Northern California OAUG Training Day 2007 January 17, 2007
Agenda Purging the old fashioned way Overview Prep Process Purging today Using ArcTools by DCSoftware Overview Prep Process Case Study
The Old Fashioned Way Overview of Purge Process Purge Preparation Perform Integrity Tests Process Purges Archive Data Reorganize Files Re-do Integrity Tests
Purge Preparation Verify DASD Availability Required Setup Steps Review Program Helps DreamWriter Versions Processing Options Data Summarization File Backups
Perform Integrity Tests General Ledger Integrity Tests Batch Integrity Tests Accounts Payable Integrity Tests Accounts Receivable Integrity Tests
Process Purges Process with No Users on the System Time Considerations # of Records Being Purged Start Time of Process File Backup Timing
Archiving Data Preparing Data for Archiving File Names Library Locations Archiving Options Tape Separate Environment Imaging Data Retrieval Future Release Considerations
Reorganize and Re-Test JDE Reorganization Program Decide Which Files Timing Re-Do Integrity Tests
From Old to New… JDE - Existing Purge Functionality Some purge programs (ex: AP, AR, GL) Existing purge programs have issues… P00Purge Handy, but limited functionality… Purge schemas High level design a ‘step in the right direction’. Schema presents purge approach at the ‘document level’… Schemas provide the ‘road map’ – the high level design and the approach to the purge of various functional areas. In many cases, higher level considerations, such as batch integrity, can further complicate the requirements.
From Old to New… Problems with Standard JDE Purge Programs: 1.Narrowly focused, resulting in too much data purged and integrity problems in the live environment (ex: GL purge) 2.Programs do not purge related files, also leading to integrity problems in the production database (ex: AP purge) 3.Archived data does not come close to becoming an environment, so archived data is difficult to use. 4.Extended file locks, inability to stop/restart 5.Inability to purge other files Problems with P00Purge or SQL: 1.Too simple… not capable of building enough intelligence into the logic 2.Performance, stop / restart
“Data Integrity” Textbook: -headers and details – the easy part JDE Specific – the hard part: -Batch – GL/AP/AR batches – purge partial batches… purge unbalanced -Cross functional area – AP/GL integrity, orders/cardex,PO/AP… -Integrity reports JDE programs are often expecting certain data to exist in other modules.
Beyond Purge Schemas Purge Schemas – a start, but… –Standard purge approach, very basic –Mirrors those (few) purge programs that exist –Files, joins, selection criteria But… beyond the schemas: –Related files considerations –“JDE Integrity” –“Gotchas” –Batch considerations –Which date field(s)? –Bad data? –Example – Accounts Payable
Intro to ARCTOOLS/400 ™ and JDE Module™ Purge and archive files without programming – any AS/400 database Create purge routines as easily as writing a query RPG code generator processes data safely and in the native database – no UBE’s ‘Stop-by’ functionality allows purges to be run in increments Throttle feature controls resource utilization. oAnalyze complex JDE data relationships using simple queries (AS400 query and/or SQL), run purges using menu driven user interface oTop-down, bottom up, process of inclusion, process of elimination, iterative approaches oKeep related data together in both live and archive (a.k.a. JDE data integrity) oNumerous functional area purges pre-defined oOver 170 JDE customers on six continents oRecommended by Denver as part of A9 upgrade strategy
Demo screens Insert screen shots or live demo here…
Purge Results Analysis JobPurge Job File # Records (Millions)Run Hours # Purged% Purged F % F % F % F (Invoices) % (Receipts) % (Total) % F % F % F %
Purge Results Analysis JobPurge Job File # Records (Millons)Run Hours # Purged% Purged F N/A % F % F % F % F N/A % F % F % F % F n/a % F %
Purge Results Analysis JobPurge Job File # Records (Millions)Run Hours # Purged% PurgedNotes F G/D/N/P/T/#/ %900k of 1771k batches V/K/M/W %283k of 525k batches I/R %191k of 333k batches Z/X/E %11k of 19k batches TOTAL %1385k of 2648k batches
Reorg after PurgingReorgWizard™
Intro to ARCTOOLS Enterprise Manager™ Based on ARCTOOLS/400 and JDE Module – same methodology, same approaches to analyses Java front end PL/SQL code generator (Oracle) or TL/SQL code generator (SQL Server) fastNot a UBE. Runs in the native database fast Completely parameter driven – front end feeds inclusion, exclusion, iterative approaches Useful for any other application on Oracle or SQL Server, simply through configuration
Overview of the solution AEM modules for JDE E1 DSTMFGFIN Archive Database Production Database AEM Engine Driving File Archive Purge Outlines data to be archived or purged
Demo screens Insert screen shots or live demo here…
Purge Results Purge Module TableDescription Total Records Archived Records Purged Records Archive Time Purge Time Gigabytes Gained ReceivablesF03B11Invoice1,481,130597,614 5m 40s45m0.50 F03B13Receipts293,701191,256 40s5m0.15 F03B14Receipt Detail2,146,3351,190,682 7m1h 45m0.90 F0911G/L10,087,2573,680,649 1h 7m3h 15m2.60 PayablesF0411Vouchers371,442172,634 4m10m0.15 F0413Payments195,372128,035 1m3m0.20 F0414Payment Detail326,721164,073 2m2m 20s0.05 F0911G/L6,406,608349,558 20m45m0.25 GLF0911G/L6,057,050750,788 19m1h0.60 PurchasingF4301PO Header532,480193,466 1m9m0.15 F4311PO Detail922,263382,657 4m21m0.60 F43121PO Receptions1,189,718752,654 3m 30s35m0.75 F43199PO History858,243235,774 3m15m0.30 InventoryF4111Cardex5,694,074503,611 5m 30s1h0.40 Sales OrdersF42019SO Header History247,682245,849 2m14m0,30 F42119SO History4,056,8531,871,622 16m1h 25m1.50 F49219SO Tag History2,692,5541,179,491 8m1h 5m0.50
Purging Strategies Co-ordination With Files Within Each System (i.e. G/L) With Other Systems Timing of Process Backups Users on the System Deletion of Records (copy to alternate media) Reorganization of Files Future Release Considerations
Questions ?????? Steve Colgrove, Platinum 21: David Shea, DCSoftware, Inc.: x200