The JD Edwards EnterpriseOne Decustomizer Analysis Report enables customers to identify simple UI customizations to applications that can be replaced by using the more robust personalization and extensibility frameworks. It is recommended that you run this periodically throughout your continuous adoption journey to help you identify the number of customizations that can be replaced by the frameworks. This will continuously reduce the cost of staying current with the latest updates in JD Edwards EnterpriseOne.

The Decustomizer Analysis Report identifies the customizations done to application objects by comparing the application between two path codes. It supports Tools and Application releases 9.1 and 9.2.

Process of Generating the Decustomizer Analysis Report

Generating the Decustomizer Analysis Report is a two-step process. In the first step, the Decustomizer Data Load Report UBE (R9540DC) loads the Decustomizer Data Load Table (F98881DC). In the second step, the Decustomizer Analysis Report UBE (R9540DCR) reads from the Decustomizer Data Load Table to create the report.

Decustomizer Data Load Report UBE

The Decustomizer Data Load Report UBE (R9540DC) loads the Decustomizer Data Load Table (F98881DC) with a list of all of the customized application EnterpriseOne objects.

To run the Decustomizer Data Load Report UBE, navigate to Batch Versions and enter “R9540DC” as the Batch Application. Select the Data Selection checkbox and click “Submit.” The default data selection will be displayed and will load the Decustomizer Data Load Table with the list of customized application objects. Additional data selection can be set up.

If you know the product code that you have heavily customized, you can narrow down the scope of the report by adding the data selection for that specific product code. After setting up specific data selection, click the checkmark icon to save. If the data selection is not specified, the Decustomizer Data Load Report UBE will scan all the application objects that are marked as customized.

The next step is to set the processing options in order to run the Decustomizer Data Load Report UBE. Enter the values for the source and target path codes you want to compare to identify customizations. For example, you may want to compare production and development path codes. You’ll need to ensure that the ESU levels of the source and target path codes being compared are the same levels. It’s important to note that the target path code is where the customizations are expected to be retrofitted.

Next, enter the values for the processing option. Enter “0” or a blank to load the data according to the data selection without deleting the existing records. Enter “1” to delete all existing records from the Decustomizer Data Load Table (F98881DC) and load the data based on the data selection. Setting the processing option value to “1” means that you want to clean up all of the loaded data and reload it with a default data selection or the data selection that you just created. Click the checkmark icon to launch the UBE. The Decustomizer Data Load Report UBE will then load the identified customization information into the Decustomizer Data Load Table.

Decustomizer Analysis Report UBE

After running the Decustomizer Data Load Report UBE, the next step is to run the Decustomizer Analysis Report UBE. The report will produce a combined summary and detail reported. The UBE (R9540DCR) is a read-only report that displays the information available in the Decustomizer Data Load Table in a usable format.

Sections in the summary section of the Decustomizer Analysis Report include:

• Decustomizations Summary: An overview of the impact that customizations have on application objects. It formats embedded values in a sentence that tells how many customized objects there are and how many product codes they are affecting.
• Summary by Path Code: A breakdown of the source and target path code and the number of application objects affected in the target path code.
• Summary by Object Type: A breakdown of object types affected by customizations and number of objects affected per object type.
• Summary by Product Code: A breakdown of product codes affected by customizations, product code descriptions, and the number of application objects affected per product code.
• Customized Application Objects: A breakdown of all application objects that have been customized. It does not show versions for objects. However, this section does show whether the ESU levels for the source and target path codes are a match.

The detailed report section of the Decustomizer Analysis Report is shown in a parent-child hierarchy where the top parent is the object followed by a list of simple UI customizations. A new page is created for each object, and each line in the detailed report identifies one specific change in the object.

The Decustomizer Analysis Report helps customers identify UI customizations made to applications. The report also provides information about the EnterpriseOne application customizations that can be replaced by using the more robust EnterpriseOne personalization and extensibility frameworks.

For demonstrations of what the Decustomizer Data Load Report UBE and Decustomizer Analysis Report UBE look like and how they can be used, check out the video below.

Additional Resources

If you’re looking for more JD Edwards content, join us at INFOCUS 19, the premier deep-dive JD Edwards focused event of the year! The event will take place August 20-22 in Denver, Colorado. Register by July 23 to take advantage of Early Bird prices!