A modification is a Tools-based change to an object in the system, which alters it from the way Oracle has delivered it. Modifications can have an impact every time you go through an upgrade. Customers are encouraged to create their own objects or make copies of Oracle objects, but the reality is that almost everyone has made direct changes to objects in the system. An approach that is laid out in a recent presentation shows the no-mod way to make JD Edwards easier to use.

Get an Overview

Why Customers Modify JD Edwards

There are several reasons that Oracle customers make modifications to their JD Edwards system. A few reasons include:

• Simplifying the User Interface
• Streamlining/controlling processes
• Enhancing functionality
• Integrating other systems

In reality, the reasons behind these modifications can be addressed through other processes or Tools within JD Edwards. You just have to know how.

Top 4 Challenges with Modifications

People make modifications to their systems to make it easier to use, but there are still major challenges that come with modifications.

1. They are expensive to do. It takes up to three times the development effort to deploy a modification.
2. They are expensive to own. It takes up to twice the original effort to own a modification.
3. They are expensive to undo. It takes at least the same amount as the original effort to remove a modification after it’s done.
4. They make you inflexible. Modifications impair your ability to adapt and be competitive.

There are several tools with JD Edwards that can help you avoid modifications or at least reduce the amount that you have. The presentation focused on three to get started: Forms Personalization, Form Extensions, and Orchestrator.

Form Personalizations

Personal Forms were first introduced in Tools 9.2.1 and has been updated in more recent Tools releases since then. They allow users to change the appearance, not its functionality. With Personal Forms, users can rearrange fields, hide or delete fields, rename forms or fields, and rearrange the sequence of tabs. Personal Forms also allows users to personalize row and form exits. Personal Forms are enabled in Security Workbench and are managed as a User Defined Object (UDO). Users can have multiple Personal Forms for a single application. They are currently only available in a few form types. Personal Forms are easy to use and allow users to create mobile applications and minimize the screen footprint of Cafe One Composite applications.

Form Extensions

Form Extensions were introduced in Tools 9.2.2.4. They allow you to add fields to a form, but the fields must exist in Business View in order to be added. Similar to Form Personalizations, Form Extensions are managed as a UDO. However, Form Personalizations and Form Extensions are two separate features that users can enable. Users can only have one Form Extension per form, so users cannot edit the name of the Form Extension. Once new fields are added to a form, users can resize and rearrange them. Users can also edit the properties of a field by setting filter fields. It is possible to add fields to a grid the same way they are added to a form. Form Extensions are currently only available for certain form types.

Orchestrator

Orchestrator is a great tool for integration and automation. It connects JD Edwards with external systems and machines, both inbound and outbound. It can also automate processes that connect JD Edwards to JD Edwards. It connects with JD Edwards at the application level. Orchestrator’s functionality has continued to increase over recent Tools releases. It requires AIS Server and an ADF component. One limitation to Orchestrator is that it is “headless,” meaning it has no User Interface. Users would have to build a UI using Web, JAVA, or another tool. One of the perks of Orchestrator is that a Business Analyst can easily build an Orchestration without having to understand the underlying code. Orchestrations are developed within the Orchestrator Studio.