Showing results for 
Search instead for 
Did you mean: 

Change the core - not "stablize" the core the key

Active Contributor
0 Kudos

A common question that falls on deaf ears is how to get those us in a traditional implementation to move over to ESOA. As I was thinking about it, maybe the problem is that the core is stable. My theory on this is that the xapps and every other ESOA solution is nice, but unless I have an absolute for that solution then I am less likely to both with those solutions.

In order to get those who are stuck in traditional land to move, we need to shake-up the core dramatically to make that enticement. In other words why not go to the very foundation, and offer an ESOA version of that foundation. Instead of making the "stable" core compatibile with ESOA. My idea redo the FI module from the ground up as a true ESOA application. Not an old ABAP application that became ESOA enabled. Offer migration tools that takes the old "FI" data and converts into a ESOA FI data so the "existing investment" can be protected.

The risk is much higher here, but the reward is greater. If you use an application that was designed in the ESOA method as your primary application, you are more likely to use ESOA method for other appliations. I just wonder if the ESOA approach is currently more like the ITS approach that was used to offer SAP data in the web browser. You only adapted what you currently have, you did not do the work of re-design to take advantage of everything.

Just my thoughts,


Accepted Solutions (0)

Answers (1)

Answers (1)

Active Participant
0 Kudos

You have my vote, Stephen. And if SAP goes this way, I might even buy some SAP stock.

If, of course, the augmentation of the core as an Enterprise SOA engine built on what has already been done in the core with Business Objects/Workflow ...