Wednesday, 13 July 2011

JDE Archiving – a pragmatic approach

Introduction:

Myriad have been involved in a number of JDE related archive projects, they’ve involved using 3rd party software and not. At the end of the day, creating a robust and repeatable archiving solution is simple using both JDE tools and native database products.

Investing time and money into third party tools that are database or ERP specific is not generally a good long term plan. Creating a flexible and repeatable framework that can change with the business, but provide the FASTEST and most ROBUST archiving solution is the best solution.

clip_image002[10]

 

The 90:20 rule:

Generally we find that 90% of a company’s data is found within 20 tables. Depending on which modules you use in JDE and how much you use them will change which tables fill up – and how fast.

F0911 is always going to be a large table, it’s the centre of all financial transactions. Keeping the detail in this file is essential for tracking back problems for customers and suppliers alike. Myriad ensures that all relational integrity is maintained when archiving is performed.

What our solution can do:

We offer you the following:

· Allow you to see ALL archive and ALL existing data as a superset

· Native use of ALL JDE functionality (read-only we suggest) in the archive environment

· Additional environment in JDE, which could have different menus and security to control access to archive information.

· Ability to query (read-only) through JDE web and JDE UBE’s

· Easy to add additional tables to the archive set .

· Ability to use robust database specific functionality to execute the archive process, not be limited to RAT (row at a time) processing.

clip_image002[4]

Specific not Generic:

Most archiving solutions (if not all) do not use the power of your database to perform the archival tasks – we do. The archiving tools are written to support heterogeneous databases and never use the power of the database to perform the task at hand. Many of them process your data row-at-a-time and require a lot of manual configuration anyway.

Myriad ensure that you are using specific SQLServer, Oracle, DB2/UDB or DB2/400 functions to allow you to have seamless access to ALL of your data when you need to. Not just your archived data.

We also ensure that your bespoke modifications are taken into consideration when establishing an archive set. All your F55-F59 data will be moved with the same relational integrity that is maintained with standard tables.

We don’t change the configuration in your production environment - Period. We only remove data, there are NO configuration changes to JDE and therefore no instability problems.

You archive environment is strictly read only. We ensure that the database security profiles that are used in the back end to access you data are ready only. The environment look and feel is also changed to ensure that users know they are in the archive environment.

Myriad ensure that the data stored in your “archive” environment is as efficient as possible. This is an environment used for read only transactions, so Myriad make the most of the latest compression offered to you by your database vendor. The use of VARCHAR as opposed to CHAR fields can cut the size of some tables by a factor of 10!

We’ve seen compression get an amazing 720% reduction in the size of indexes on the F0911 – this is just the beginning!

Finally Myriad know that there is some “heavy lifting” when you first put in an archiving solution, once that has been done the scheduled regular archive operations are relatively innocuous and can occur generally online and “out of hours”.

Want to know more, please fill out your details on our contact page.

No comments:

Extending JDE to generative AI