Modifications to JDE

When making modifications to JDE what is the best approach to take? Should you rename the object and put it into the client reserved product code 55-59 or should you make the change to the JDE source code? I have heard different solutions to this. I know if you make changes to JDE source code that you risk losing those changes when updates are done. I have also heard that you have the ability to monitor the updates to see which applications it will touch. If the application is one which has been changed it can be skipped. The changes will then need to be merged in. Thanks for your thoughts.

Hi David,

That's a huge topic that you raise today... Hopefully, it will get even
more replies than "Cranky hadn't ..."

My advice here:
Keep your mods in systems 55-59 as much as possible.
Alter the standard JDE objects as a last resort only, you will save a
lot of headache!

In most cases, it is possible, although you will probably end up knee
deep in P4210 and a few others...


Cheers

Philippe

Hi David,

It is really a very huge topic and unfortunatley you missed to describe your system configuration, mainly your OW release level. In some of the aspect it could be relevant.
I haven't to much time to decribe all aspect that I know but I try to add my two cents. Hopefuly the others will added their owns to help you in this issue. Let see:

1.) You can not copy all type of objects (differs from release to release).
2.) Updates, but mainly ESUs will not affect your copied objects, further JDE do not support to apply ESUs on copied objects. You have to figure out the changes and apply them to the copied object if it is really requiered. It could be sometimes a great challenge.
3.) APPLs/UBEs/BSFNs sometimes call each others and they won't know about your copied and customized object and will call the original one. In some cases it could be also an issue.
4.) If you change (generally minor changes) the original objects then you have to re-work the changes after an ESU install if the object was effected, but many times it is the minor disadvantages and you can document the changes and can use Visual ER Compare (on XE and on B7332 if you installed the rolled back solution on B7332).
5.) I do not advise you to skip an object when it affected by an ESU. You can never know the logic of the changes and it is possible that you will install only one part of the changes which will cause faults.

That's all for now.

Good luck anyway,
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)

Üdvözöljük Zoltan, and greetings to all others on the List.

It was my understanding that after the Xe upgrade,
all new releases, (including ESU's and SP's), would merge
the new specs with the modified original JDE objects.
If this is not

(Sorry List, my previous response did not go through prpoperly.
Let's try again.)

Üdvözöljük Zoltan, and greetings to all others on the List.

It was my understanding that after the Xe upgrade,
all new releases, (including ESU's and SP's), would merge
the new specs with the modified original JDE objects.
If this is not