1. Recent developments, Product Roadmap & new product launch

2. Nett change from 4.20

3. Version 4.20 (released March 2015)
Infrastructure
Include Date Offsets in all ‘standard’ Purge-it! modules’ Processing Options
Enhance Date Offset functionality to start calculations based on:
System date
Calendar periods/years, or
Fiscal periods/years
General Ledger
Additional validation back to Payroll system (F0618) and Accounts Payable for HR/Payroll
Changed ‘un-processed serviced billing transaction’ validation into a Processing Option
Changed from hard- to soft-coded
Process all transactions in the Master BSFN, for speed and efficiency

4. Version 4.20 (released March 2015)
Accounts Receivable
Process Drafts in the purge and archive routine, and not just mark them as ‘Held’
Inventory
Process all transactions in the Master BSFN, for speed and efficiency
Lot Number and Location can now be summarized out, by a new Processing Option
Ability to process transactions with a zero GL date added via a new Processing Option

5. Version 4.20 (released March 2015)
HR/Payroll
Introduced the HR/Payroll module across all JD Edwards releases
Purge-it! Custom module
Special functionality added for 21 CFR Part 11 audit tables, to cater for their non-unique Primary Keys

6. Version 4.26 (released May 2015)
Infrastructure
Purge-it! for JD Edwards release 9.2 created
Purge-it! Custom module
Can now process from a ‘Join Table’, to improve performance in certain circumstances

7. Version 4.27 (released Jan 2017)
Infrastructure
New application added for automatic Table and OCM generation when installing the software
New application - Purge IT Session Dashboard
Graphical Power Form – Alert, Analyse, Act – used for monitoring individual Sessions
New application - Purge IT Environment Dashboard
Graphical Power Form – Alert, Analyse, Act – used for managing the whole data environment
Audit Data Deletion UBE rewritten for performance improvements and better audit data
Oracle Snapshot issue ‘ORA-01555’ no longer an issue for long running selections
General Ledger
Add new Processing Option to summarize out the Sub Ledger and Sub Ledger Type

8. Version 4.27 (released Jan 2017)
Accounts Receivable
Argentinian Localisation for Table Event Rule processing added
New Processing Option to allow Batch to be archived when no Payment Header exists in F03B13
Performance improvements by restructuring the way the purge and archive routine processes
Accounts Payable
Extend purge and archive processing to include batch type ‘#’ (Payroll Vouchers)
Inventory
New Processing Option to prevent a transaction with a Lot Number from being archived if its Quantity On Hand is not zero

9. Version 4.27 (released Jan 2017)
Sales Order Processing
Change to method used to load audit table with orders to be processed - performance improvement
Purchase Order Processing
New Processing Option to allow Open Amount validation for Transfer Orders to be switched off.

10. Version 4.27 (released Jan 2017)
HR/Payroll
Only archive F4812H if related F4801 Work Order is already archived
Add table F to purge and archive routine
Use SBL / SBLT on Time Entry transactions to check if original Work Order is already archived
Purge-it! Custom module
New Processing Option to disable Table Event Rules on INSERTs and DELETEs

11. Current Purge-it! release
V4.29

12. Version 4.28 / 4.29 (Nov 2017) Infrastructure
New database growth Trend Analysis on Environment Dashboard, to visualise growth over time
Job Costing validation added across all modules via new Processing Options
Ensure Jobs are closed, and all transactions complete, before archiving Job-related data
Date Offsets added to Mass Audit Data Deletion program, so it can be used on the Scheduler

13. New Job Costing validations
(For example)
F0911
F0006
F5108
Purchase Order

14. New Job Costing validations
Purchase Order
<blank>
does not perform any additional validations, over and above those that are already present within the individual Purge-it! module

15. New Job Costing validations
F0006
F5108
Purchase Order
‘1’
Checks the Business Unit(s) on the transactions against the F5108 to determine if they are a Job. If they are a Job, then the F0006 will be validated, for PECC = ‘N’ or ‘P’.

16. New Job Costing validations
F0911
F0006
F5108
Purchase Order
‘2’
Will perform the same check as ‘1’,
and check all G.L. transactions for the Job:
for G.L. Date less than the Cut-Off Date, and
G.L. transactions have been posted to the F0902

17. New Job Costing validations
F5108
Purchase Order
‘3’
Checks the Business Unit(s) on the transactions against the F5108 to determine if they are a Job.
If they are a Job, then don’t archive these documents.

18. Version 4.28 / 4.29 (Nov 2017) Infrastructure
Can now reverse individual transactions from within the audit screens
“Checking for cancellation” process is updated in each module
Mass Audit Data Deletion program now includes ‘total records to be deleted’ counts
Added functionality to purge historical statistical data from the Purge-it! Environment Dashboard

19. Version 4.28 / 4.29 (Nov 2017) General Ledger Inventory
Change to allow SQL Server databases to use Manual Commit mode
Inventory
Added validation to check the Lot status before archiving the IZ transactions (“Lot Hold/Release”)

20. Version 4.28 / 4.29 (Nov 2017) HR/Payroll Purge-it! Custom module
Can now process F0719 records that do not have matching F0618 records
Automatically handled, within the purge and archive routine
Purge-it! Custom module
Allow ability to purge and archive tables that are also archived in the standard Purge-it! modules
Add Purge-it! Custom module Extension Pack functionality (premium feature)
Pre-defined template configurations within the Purge-it! Custom module, covering multiple common processes in multiple JD Edwards modules

21. HR/Payroll enhancement
F0618 19
Payroll transactions
Employee
Master
F0719 9
Tax History / Summary 6
Employee Leave 1
HR History 2
‘Z’ Tables 2
Journal tables

22. HR/Payroll enhancement
F0618 19
Payroll transactions
Employee
Master
F0719 9
Tax History / Summary 6
Employee Leave 1
HR History 2
‘Z’ Tables 2
Journal tables

23. New Product Launch

24. Soon

25. Manage-it!

26. Jump into system

27. Slides

28. Manage-it!

30. The most important thing with Dashboards is the colour !

31. What Database Data Sources are we going to gather data for, and display in what colour?

32. Link Database Data Sources to an Environment, so that we can inquire at that level

33. What thresholds shall I get notified at?
Configure your alerts – at Database Data Source and/or at Table level

34. Gather those statistics !

35. Don’t worry about smaller tables, if you don’t want to
Also, “clean house” whilst you are gathering the statistics

36. Manage-it! will accurately estimate the record sizes, based on the table specifications

37. The dashboard is born !

38. What has broken the Database Data Source thresholds that I set ?
Table
thresholds that I set ?

39. See the triggers that you set from within the dashboard

40. Build your own time machine to look into the past !
Choose how you view the results, and change your mind whenever you want!
Build your own time machine to look into the past !

41. Now I’m looking by record counts!

42. Ooh, those Database Data Sources had size triggers on them
Here’s the trigger, and it has been exceeded !
Here’s another one!

43. Good news - the record counts are OK 

44. Ooh, look at all of that history 
But what’s it going to be like in the future ??

45. Well with the Database Data Source forecast, you can predict the future!
No more crystal balls …

46. And what about that individual table??
Ah, that’s how big it will get …
Maybe it’s time to archive

47. All of these statistics are built from data, and here it is.
First, it is sorted by record counts, and how much data is in each table as a percentage of the whole …

48. And when we change the radio button, it is sorted by size, again, with the percentage split

49. And if we click on any of our alerts …

50. We then see the analysis of that table, in all of the Database Data Sources that it exists in

52. How do we get to the next new product released within Manage-it! ??
Well, via this Dashboard, of course !

54. Test-it!

55. Test-it! structure 1 2 3 4 5 6 Tables in a Table Group Definition
Groups 1
Definition
Runs
Data
Selection
(optional) 2 3 4 5
“IN”
Join
(optional) 6

56. All new products need dashboards !

57. Here are the tables in our Table Group …
… if Data Selection has been set up …
… what is going to be done with the tables …
… and if we have joined to another table.

58. Here’s that Data Selection, just like you are used to in the Purge-it
Here’s that Data Selection, just like you are used to in the Purge-it! Custom module

59. What actions can we take ?
Just delete everything that is in the destination.
Copy data into the destination, and keep what is already there.
Clear the destination, then copy the data in.
Add the data to the destination, if a record exists in the Join table.
Replace the data in the destination, if a Join record exists.
An auditable conscious decision to not do anything.

60. Copy the F42019TX, where we have already copied the F42019
Joins
Copy the F42019TX, where we have already copied the F42019
And keep the data integrity at the individual transaction level, by linking on Primary or Foreign keys

61. So we have defined our Table Group, what is next?

62. Well, why don’t we use another dashboard to manage that 

63. All the Table Groups that I have defined …

64. … and here is where we join the Table Groups together into Definitions
If you have multiple projects ongoing at any one time, just refresh the data needed for a specific project, and not everything, like you used to

65. Here’s where we create a Definition

66. And we add one or more Table Groups into a Definition

67. Also, from here, you can look at all of the times you have run a Definition

68. Here they all are !

69. Here’s the big Dashboard – let’s look at all of that useful information …

70. Basic configuration of the Definition
A default action for all those other tables that you might want to copy, but didn’t set up in a Table group

71. And details about any Joins that you set up
Each table that is going to be, is being, or has been processed in the Definition Run
And details about any Joins that you set up

72. How is it going, on a table by table basis ?

73. And what was it that I was copying for that table again?
Oh yeah, just the recent data for Company 200

74. Sheesh, that’s a lot quicker than my SQL scripts used to be !
How long did it take me?
Sheesh, that’s a lot quicker than my SQL scripts used to be !

75. OK, let’s run it !

76. Is that all I have to specify ?
Sweeeeeeeet !