I’d like to invite some discussion on an interesting topic.
Our implementation, developed with SAP, is heavily leveraged on a custom namespace (ABC) which sits between the normal CRM implementation and our enhancements. Rather than working with the component BP_HEAD, we have /ABC/BP_HEAD as our base. So, for example, /ABC/BP_HEAD would be enhanced under enhancement set ZES1.
Our implementation has many dozens of enhanced components and 200+enhanced views, with a multitude of context and method changes under them.
Here is the current task:
We will be migrating to a new box and new system, NEW, with a shiny, new, SAP delivered namespace, XYZ. XYZ implements the ABC functionality and then some. The ABC namespace goes away. XYZ does not implement our enhancements. We need to reestablish our enhancements on the NEW box (making code changes, etc to point to the new namespace where needed).
I’d like to explore efficient ways to re-create our enhancements in the new environment.
I’m sure there are many options. Here’s one, brute force. Two side by side windows – one in the OLD system and one in the NEW. Starting with a component, manually enhance, one for one, from the component controller down to each window, view, and the associated contexts, getters, setters, and controller methods…. . Use the same naming conventions for enhancements. Cut, Paste, Change Code as necessary. Repeat 50 times. And I know it will work.
In a nutshell, this highlights that we need to a) ENHANCE certain IDENTIFIED items, providing new implementing classes along the way, and b) provide code to these new items and c) update the code where necessary.
I’m wondering if there are better, more programmatic/cts/technical ways to perform these tasks, particularly the ENHANCEing and IDENTIFYing .
I could add a lot of our musings, but rather would prefer to engage the community.
The discussion is open. Thanks...