Zaki Ahmed
Well Known Member
We are going through new implementation of JDE and IT is strong about NOT making any changes to standard JDE applications. They want to set a precedence that std applications shouldn't be modified as it is high cost of retrofitting for IT during ESU updates and upgrades and such.
However, there's a big push from business to include some functionality that doesn't exist in std. application. Some developers have opted for cloning standard applications such as P4210 to P554210 - even for minor modifications such as adding a URDT field to Grid. But I personally think it is a very bad idea cloning applications such as P4210 due to following factors
1. Get processing option business function has hard coded value of "P4210" to retrieve PO. That means, if I clone P4210 to P554210 and create a version against P554210 and link it to other applications, then those apps wont' be able to retrieve PO of P554210. So I will then have to create a similar version against P4210 to refer to that. Messy!
2. Cloning to P554210 doesn't fulfill the desired result of reducing retrofitting effort. As if a fix/esu comes from Oracle, that ESU will have to merged into P554210 if there's a desire. And it's more difficult to merge ESU code into P554210 than to merge our custom code into P4210 after ESU is applied
I am all for creating new applications, but it impacts user experience, as they have to toggle between applications to do different things, that would otherwise be done in one screen.
I guess, what I am asking here is, how do you guys make a decision of Modify std app VS. Clone std app VS. Create a new app. Do you have any corporate strategy around this? Or it's all under the domain of JDE developer - how he/she seems fit. What drives your decision making in the respect.
However, there's a big push from business to include some functionality that doesn't exist in std. application. Some developers have opted for cloning standard applications such as P4210 to P554210 - even for minor modifications such as adding a URDT field to Grid. But I personally think it is a very bad idea cloning applications such as P4210 due to following factors
1. Get processing option business function has hard coded value of "P4210" to retrieve PO. That means, if I clone P4210 to P554210 and create a version against P554210 and link it to other applications, then those apps wont' be able to retrieve PO of P554210. So I will then have to create a similar version against P4210 to refer to that. Messy!
2. Cloning to P554210 doesn't fulfill the desired result of reducing retrofitting effort. As if a fix/esu comes from Oracle, that ESU will have to merged into P554210 if there's a desire. And it's more difficult to merge ESU code into P554210 than to merge our custom code into P4210 after ESU is applied
I am all for creating new applications, but it impacts user experience, as they have to toggle between applications to do different things, that would otherwise be done in one screen.
I guess, what I am asking here is, how do you guys make a decision of Modify std app VS. Clone std app VS. Create a new app. Do you have any corporate strategy around this? Or it's all under the domain of JDE developer - how he/she seems fit. What drives your decision making in the respect.