Case for Action

• In JDE Upgrade, documentation is typically inadequate or simply missing in some cases, that lists program modifications that have been performed to “Base JDE Objects”. Implementation of a new versions are difficult due to the business processes that need to be supported. Comparing new functionality to replace the mods is impossible.

Objective of Application

• The new application will provide a detail list of modified “Base JDE Object” programs to be tested and validated against enhancements in the new version creating Project Setup and User Documentation.

Benefit

• This will provide a detail list of programs that can then be compared to new functionality that may be able to replace the modification. This will also serve as the documentation of the “Old vs. New” programs to help in retrofit processes.

• JDE debug log files grow to an unmanageable size very quickly. Most of the information in the logs is not necessary for researching errors. For developers, the majority of the time this log has more information than needed. Either, the log has information for dates and times not within the research window or the extra logging information is obscuring the real business logic. This parser will allow a more focused inspection of the debug logs.
• The process to split a file has many advantages. Split the file to include only a designated date and time range for review of system issues. Split the overlarge file into smaller files so that the log can be opened in a plain text editor. The log split operation will retain all business logic and system process logging. This enables focused reviewing of the logs for system issues.
• The process to parse the file for Business Function logic enables a quicker review of the log file. There are hundreds of lines between steps in the business logic. The requirement to scroll through hundreds of log lines to get to a table fetch after the function is called can lead to overlooking the issue highlighted in the log.

• Saves precious time for the IT staff to investigate how many custom/modified objects you really have. Use as a change control process
• Low cost solution – If you had to build an extension of the current JDE report would it would be cost prohibitive
• Tools are not just used for upgrades but can be used for various reasons:
• Baseline type ESU’s
• Change Control
• Business Process Changes