Audit Service
Our Audit service explained
Once approval to proceed has been given, we proceed to convert the initial list of possible upgrade objects to the optimum list of upgrade objects identifying decommissioning opportunities and various anomalies along the way. Typically this process can identify a reduction of 35-64% in objects requiring upgrade.
This service involves DWS and the customer (typically a lead developer or lead CNC) working together to create the optimum list of objects. Dimension will uncover
-
Definition
-
Initial List
This is the list of modified objects extracted by Dimension during the Extract runOptimum List
This is the agreed list of modified objects that will be taken up to the target release
Value Proposition
- Caters for releases B7333 to 9.0.1
- Automatically identifies reports and versions that have not run for more than X months or a user defined period of time
- Automatically identifies ‘design’ time changes to Versions. Standard JDE does not provide this capability. If left unidentified, this can have a significant impact on testing at the higher release level as the testers would not be seeing the results they expected as per original release
- Automatically identifies every modification in your E1 system over and above standard JDE enquiries and reports
- Automatically identifies all objects that are flagged by JDE as modified, when in fact they are not modified at all
- Automatically identifies objects that are actually modified, but have not been flagged as modified by JDE
- Helps to identify objects that were copied from a standard JDE object and identifies which standard JDE object they were copied from
- Identifies ESU code differences between the customer’s Prod and Prist environments
- Automatically allow base object comparisons of objects between JDE releases to determine standard level of JDE net change to a very low level of detail
- Automatically identifies and reports on all Client Only Business Functions
- Automatically identify objects with unusual or non-standard naming conventions
- Clearly identifies ‘hack’ objects & 3rd-party objects as well
- Automatically provide intelligence that allows customer to decide whether to retain an object as a copy or move back to making changes to standard again
- Automatic ability to ignore minor pixel-movements of report/screen fields
- Automatic ability to factor in JDE’s Net Change to JDE-std objects called by custom code.
- Determine “standalone” objects that should not need upgrading – enabling testing staff to begin immediate functional testing
- Automatically determine and remove orphaned objects (objects not called by other objects)
- Service can be delivered remotely – no requirement for on-site visit