![]() With each new SAP Visual Business release we are coming closer to achieve the goals. But combining functional requirements with the above described architectural background, we believe that we are on track. Functional limitations.Īnd whenever an issue came up, the first questions I got was: Why didn’t you use plugin if vendor G*? Did you check the product of vendor E*? Of course taking a single requirement and matching the best product against it, it always looks like a no brainer. Limitation regarding operating systems and browser. Of course there was no component available fulfilling our major goals ad-hoc, but out of SAP research SAP Visual Business evolved into the top candidate position.ĭid we have to make compromises in the beginning? Yes, quite a lot. Back those days and in the following years after it was not always easy. My vision was to have a middleware between the SAP external geo-map content and our applications taking on all of those GIS specific challenges. Goal 3: SAP T&L applications shall use a geo-map component that could become the SAP standard geo-map. And very seldom there are really requirements demanding a GIS vendor proprietary solution. Taking a closer look very seldom something really application specific remains in this area. And I wondered why…In the end all want to display business application specific information / objects on geo-map content. It seemed like any application somehow did it differently. When starting to investigate this topic internally, I was amazed how many different solutions we have SAP internally. We wanted to use a component with the potential to become the SAP standard geo-map. Goal 2: SAP T&L applications shall use a top-class geo-map plugin regarding usability, stability, and flexibility. But nevertheless, we need for our applications a high quality geo-map component. And each hour we spend on converting geo-coordinates, navigating through content, displaying legends, keeping WebService calls up-to-date, speaking with legal departments, and so on is a lost hour for our core business processes. But that for sure would not have fulfilled our and our customer expectations. (Well, actually I have some GIS background…) Of course we could have taken something and somehow get it to work with the restricted capacity we can spend on that topic. Hey, we are developing software for transportation and logistics! We are no GIS experts. I say potentially as it was not a must have for a first rollout, but the tool should be from a technology point of view able to grow into such an open component. Goal 1: SAP T&L applications shall use a tool potentially capable of integrating any geo-map content. Also, we have foreseen requirements driven more by politics taking a look at Chinese customers (locally hosted, local content,…). So even if we would have integrated a GIS vendor specific product capable of using different data sources and having global content, we would kind of run into issues with those customers as they would not like to have a new contract with just another GIS vendor. In addition, we saw that most of our customers and known prospects in some way already had business contracts with one or another GIS vendor. This means it should be able to display high quality maps anywhere, even respecting local specifics. When starting with this topic for Transportation Management 7.0 it was clear that we wanted to deliver a solution as global as possible. It has sooooo many features! Or why we don’t in standard integrate all vendors you could possibly think of! Maybe after reading this it becomes clear. It’s free!!! Or why we don’t use the product of vendor E*. Often I am asked why we don’t integrate a plugin of vendor G* directly. 19:48:10,393 - CRITICAL - I would like to answer the question why SAP’s Transportation and Logistics applications SAP Transportation Management, SAP Extended Warehouse Management, and SAP Event Management use SAP Visual Business to integrate geo-maps. init : self._network_(self._onPrinterDiscover圜hanged) init : File "C:\Users***\AppData\Roaming\cura\4.4\plugins\MKSWifiPlugin\MKSWifiPlugin\MachineConfig.py", line 48, in startDiscovery init : Traceback (most recent call last): 19:48:10,245 - DEBUG - : Starting printer discovery. 19:48:10,166 - DEBUG - MKSWifiPlugin.MachineConfig._createAdditionalComponentsView : Creating additional ui components for tft35.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |