James Meadors
Member
Thanks to all that willing to help me with this question.
I have searched JDEList for what I am asking, and I have found some information. So far, however, I have not been able to find any information on what is "Best Practice" for developing in JDE.
My company is very new to JDE, so we are still in an early learning process. We are currently running EnterpriseOne 9.2.0.
Here is my question:
Using the JDE invoicing proram, R42565, as an example, if I needed to add logic to the UBE at the base level, would it be best practice to add code to R42565 or create a clone/copy, say, R5542565 and make the change there?
What is the best practice for modifying JDE objects such as applications, UBEs, business functions, etc.?
Should I change base JDE code or should I always clone/copy?
What is the best way to handle this for the long haul with regard to ESUs, system upgrades, maintenance, etc.?
Thanks again to anyone willing to discuss this with me. Your time and help is much appreciated.
I have searched JDEList for what I am asking, and I have found some information. So far, however, I have not been able to find any information on what is "Best Practice" for developing in JDE.
My company is very new to JDE, so we are still in an early learning process. We are currently running EnterpriseOne 9.2.0.
Here is my question:
Using the JDE invoicing proram, R42565, as an example, if I needed to add logic to the UBE at the base level, would it be best practice to add code to R42565 or create a clone/copy, say, R5542565 and make the change there?
What is the best practice for modifying JDE objects such as applications, UBEs, business functions, etc.?
Should I change base JDE code or should I always clone/copy?
What is the best way to handle this for the long haul with regard to ESUs, system upgrades, maintenance, etc.?
Thanks again to anyone willing to discuss this with me. Your time and help is much appreciated.