Blueprinting and Enterprise SOA
Unless things have changed in the past few years, the core of the blueprinting process is still identification of the transactions that a customer will use and the tailoring of these transactions within the permitted bounds. If a brand-new SAP customer is really really committed to an implementation of Enterprise SOA, how will the blueprinting process be different for such a customer? It would seem that a transaction-oriented blueprinting approach is essentially inimical to an Enterprise SOA approach, inasmuch as the former relies on a predetermined dicing of business functionality into “transactions” delivered with stovepipe apps – the antithesis of Enterprise SOA cross-app tapestry. If this has been discussed anywhere in the various SDN locales by SAP staff or others (particularly the former), I apologize for missing it. But not having seen anything on this specific question, I’m wondering if SAP strategists have given it any thought.