Migrate SAP BO to Looker with a real semantic layer

Migrate SAP BO to Looker (Google)  - Rebuild a real semantic layer! "  To misname things is to add to the world's misery  ," said Albert Camus. Naming things well can also help ensure the success of a business!   This was the great success of SAP BO, which, with its "Objects", translated very abstract IT concepts into business information that could be manipulated by the greatest number of people.   This is a long time ago now, and many companies are moving away from SAP BO, which is starting to become obsolete and is poorly suited to the Cloud.   Leaving BO also means separating from its "Objects", organized in its very popular semantic layer, the "Universes".    But not necessarily. Especially if the migration takes place to Google's Looker, which natively provides a semantic layer.   We explain how.  Step #1:   A migration from Universes to Explores Looker  Our {openAudit} migration engine will divide the BO (Business Objects) Universes based on each context and fact table actually used in the BO reports used. Our migration engine is based on the actual usage of the BO platform as source.  Each BO Universe will be transformed into multiple Explore Lookers based on a star model centered on the fact table. {openAudit} will only take what is used in SAP BO.   Each Explore Looker will allow users to create ad hoc queries, explore and visualize data. It is a faithful resumption of the semantic layer, but it will remain quite far from the original Universes due to the technical specificities of Looker vs SAP BO.    To make life easier for the profession, we felt it was necessary to add a device to our migration engine.  Step #2:    Adjust this migration to make it more usable by the businesses  We have enhanced our migration engine by dynamically providing a "control table." This will allow for simple configuration of the output, moving toward an ideal semantic layer, potentially very close to that of SAP BO.    The first run of our migration engine will feed the control table and produce the LookML (Looker modeling language).  The processing will thus be "controllable", which will allow the profession to "play" to modify the Explores as it sees fit.  The LookML will be versioned.    Conclusion   The release of SAP BO is perilous, particularly because the semantic layer is generating strong support. Google's Looker is a solution that will allow you to rebuild a very functional semantic layer.    To make this semantic layer as "experiential" as it was in SAP BO, our migration engine will build a control table to produce output that is very usable by the business lines, almost instantly.