Author: admin

WALLDORF — SAP SE (NYSE: SAP) today announced an enhanced release of the SAP Hybris Commerce solution for the telecommunications and media industries.

The telecommunications and media accelerator, developed in collaboration with IBM (NYSE: IBM), addresses industry-specific challenges when engaging, retaining and acquiring customers and selling to them. Consumers are increasingly using the web and mobile channels to research products and services, make purchases and activate or deactivate services. In response, service providers need the ability to quickly offer product and service bundles, as well as personalized customer service and self-service features.

SAP Hybris* and IBM together are offering an agile solution with a ready-to-use framework enabling service providers to engage with customers using feature-rich omnichannel solutions that streamline the purchase process and help to consistently ensure high-quality, dependable customer experiences and journeys.

“Telecom and media consumption is becoming increasingly customizable and is therefore more complicated,” said Matthias Goehler, senior vice president, Industries, SAP Hybris. “SAP is committed to meeting industry business needs by supporting new business models, industry regulations and standards. The telecommunications and media accelerator helps companies achieve and realize their goals all while getting to market as quickly as possible.”

This latest initiative of the 14-year partnership between IBM and SAP is rooted in the companies’ deep industry-specific expertise and understanding of the complex customer journey associated with telecom and media product offerings. SAP Hybris Commerce, telco and media accelerator, combines IBM’s technology integration and services competencies with SAP’s technological capabilities — fostering a continued path of innovation as companies embrace new and evolving business and technology models, such as Over the Top (OTT) and the Internet of Things (IoT).

The enhanced accelerator for SAP Hybris Commerce allows telecom and media providers to:

* Combine digital self-service and assisted forms of interaction with physical channels, such as in-store enablement and in-store pick-up services
* Support complex products and bundles to keep prices and products aligned to industry standards
* Meet modern security and privacy standards as required by global regulations

“The telecommunications industry is experiencing a significant transformation driving companies to invest in capabilities that modernize operations and allow them to differentiate and drive value,” said Bob Fox, Global Industry Leader – Telecommunications, Media and Entertainment, IBM. “Together with SAP Hybris, we offer a unique commerce solution specifically tailored to meet the demands of telecommunication providers and media companies, including add-ons, bundles, promotions, unique checkout flows and more, that enables them to reinvent business processes and deliver more engaging digital customer experiences.”

For more information, visit the SAP Hybris News Center and the SAP News Center. Follow SAP on Twitter at @saphybris and @sapnews.

About SAP Hybris Solutions

SAP Hybris solutions provide omnichannel customer engagement and commerce software that allows organizations to build up a contextual understanding of their customers in real time, deliver a more impactful, relevant customer experience, and sell more goods, services and digital content across every touch point, channel and device. Through customer data management, context driven marketing tools and unified commerce processes, SAP Hybris solutions have helped some of the world’s leading organizations to attract, retain and grow a profitable customer base. SAP Hybris software for customer engagement and commerce provides organizations with the foundation, framework and business tools to create a holistic customer view across channels, simplify customer engagement and solve complex business problems. For more information, visit www.hybris.com.

About SAP

As market leader in enterprise application software, SAP (NYSE: SAP) helps companies of all sizes and industries run better. From back office to boardroom, warehouse to storefront, desktop to mobile device – SAP empowers people and organizations to work together more efficiently and use business insight more effectively to stay ahead of the competition. SAP applications and services enable more than 355,000 business and public sector customers to operate profitably, adapt continuously, and grow sustainably. For more information, visit www.sap.com.

Note to editors:
To preview and download broadcast-standard stock footage and press photos digitally, please visit www.sap.com/photos. On this platform, you can find high resolution material for your media channels. To view video stories on diverse topics, visit www.sap-tv.com. From this site, you can embed videos into your own Web pages, share video via email links, and subscribe to RSS feeds from SAP TV.

For customers interested in learning more about SAP products:
Global Customer Center: +49 180 534-34-24
United States only: 1 (800) 872-1SAP (1-800-872-1727)

For more information, press only:
Michael Baxter, SAP, +49 151 1719 6185, m.baxter@sap.com, CET
SAP News Center press room; press@sap.com

*SAP Hybris is a brand name launched in January 2016 to represent the SAP solutions for customer engagement and commerce as well as the offerings, employees, and business of acquired company hybris AG, which continues to be our legal entity until integration with SAP is complete.
Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as “anticipate,” “believe,” “estimate,” “expect,” “forecast,” “intend,” “may,” “plan,” “project,” “predict,” “should” and “will” and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP’s future financial results are discussed more fully in SAP’s filings with the U.S. Securities and Exchange Commission (“SEC”), including SAP’s most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.
© 2017 SAP SE. All rights reserved.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. http://bit.ly/2icnjXj #SAP #SAPCloud #AI

[Note : This blog would be equally relevant for Lumira Designer 2.x as well as the same migration from SAP UI5 commons controls to sap.m would be required . This blog would focus from the perspective of Lumira discovery.]

With the technology migration from Lumira 1.x to 2.0 , we had taken a conscious call where-in we moved away from supporting the SAP UI5  (including Open UI5 as we) commons library  controls to the sap.m library controls  and its standards . Now, what it means to our developers is if they have developed any visualisation or data access extensions or components using the SAP UI5 commons library for SAP Lumira , then would have to migrate to the sap.m (https://sapui5.hana.ondemand.com/#/api/sap.m) controls . Using  rest of  web  friendly technologies like the HTML , CSS , Javascripts still remains the same and you can continue using it as long as you were following the guidelines suggested for developing 1.x extensions.

An example for how the library controls  between SAP UI5 commons and sap.m would look like is mentioned in the below sample table :

In this blog instead of being theoretical , I will try my best to provide you with a sample data access extension which was built for Lumira Desktop 1.x in SAP UI5 commons library  and we will understand how to move to 2.0 to make it UP and Running.

Instead of just mentioning the the technology changes , I will take the example of an extension which is already available in GitHub : Google chrome network logs data access extension :

The extension is available in the below link which you can download(As of today by this time the blog publishes, the extension is still supported for 1.x line and needs to be upgraded.)

https://github.com/SAP/lumira-extension-da-google-chrome-network-logs

The  UI elements for the current data access extension was built using SAP UI5 commons library and what we would understand from here in this blog is  , how we migrate to SAP UI5 commons library to sap.m library.

At first, i have downloaded the extension available from the GitHub and then imported into the Eclipse IDE.

In the current Chrome network logs extension , the UI is built using the SAP UI5 commons UI controls and the  main UI file which is available as part of the file

ChromeLogsExtensionDialogController.js .

In the below screenshots , you can find on your left side of the code is the 1.x  supported old UI5 commons controls where-as on your right side of the screen , you can  find the changed sap.m controls code.

 

 

 

The complete   changed code with sap.m UI controls is given below : /* Copyright 2015, SAP SE Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ define(function() { “use strict”; var ChromeLogsExtensionDialogController = function(acquisitionState, oDeferred, fServiceCall, workflow) { /* * Create dialog controls */ var dLayout = new sap.ui.layout.VerticalLayout({ }); var datasetNameTxt = new sap.m.Input({ enabled : workflow === “CREATE” }); var datasetNameLbl = new sap.m.Label({ text : “Dataset Name:”, labelFor : datasetNameTxt }); dLayout.addContent( datasetNameLbl); dLayout.addContent( datasetNameTxt); // These paths correspond to the included sample data if the workspace // was unzipped to the C drive var datasetTxt = new sap.m.Input({ width : ‘300px’, value : ‘C:’ }); var datasetLbl = new sap.m.Label({ text : “Logs Folder:”, labelFor : datasetTxt }); dLayout.addContent( datasetLbl); dLayout.addContent(datasetTxt); var metadataTxt = new sap.m.Input({ width : ‘300px’, value : ‘C:metadata.txt’ }); var metadataLbl = new sap.m.Label({ text : “Metadata File:”, labelFor : metadataTxt }); dLayout.addContent( metadataLbl); dLayout.addContent(metadataTxt); /* * Button press events */ this.buttonCancelPressed = function() { oDeferred.reject(); // promise fail dialog.close(); }; var buttonOKPressed = function() { var info = {}; info.logsFolder = datasetTxt.getValue(); info.metadataFile = metadataTxt.getValue(); info.datasetName = datasetNameTxt.getValue(); // info.model = oAccordion.getModel().oData; acquisitionState.info = JSON.stringify(info); oDeferred.resolve(acquisitionState, datasetNameTxt.getValue()); dialog.close(); }; var okButton = new sap.m.Button({ press : [ buttonOKPressed, this ], text : “OK”, tooltip : “OK” }); var cancelButton = new sap.m.Button({ press : [ this.buttonCancelPressed, this ], text : “Cancel”, tooltip : “Cancel” });//.addStyleClass(sap.ui.commons.ButtonStyle.Default); var onClosed = function() { if (oDeferred.state() === “pending”) { oDeferred.reject(); } }; /* * Modify controls based on acquisitionState */ var envProperties = acquisitionState.envProps; if (acquisitionState.info) { var info = JSON.parse(acquisitionState.info); datasetTxt.setValue(info.logsFolder); metadataTxt.setValue(info.metadataFile); envProperties.datasetName = info.datasetName; } datasetNameTxt.setValue(envProperties.datasetName); /* * Create the dialog */ var dialog = new sap.m.Dialog({ width : “720px”, height : “240px”, modal : true, resizable : false, closed : onClosed, content : [ dLayout ], buttons : [ okButton, cancelButton ] }); dialog.setTitle(“Chrome Logs Extension: ” + envProperties.datasetName); this.showDialog = function() { dialog.open(); }; }; return ChromeLogsExtensionDialogController; });

Rest of the code remains unchanged , compile and  build and execute in the Lumira 2.0 Discovery and you should be seeing new the UI as below.

Input the required details and acquire the dataset.

  http://bit.ly/2icnd1T #SAP #SAPCloud #AI

Source: SAP

Source: SAP

The usual legal disclaimer applies; everything in the future is subject to change

Source: SAP

Run (SAP Cloud apps)

Win is Leonardo

“Innovate core processes to innovate” by going to the cloud

Use intelligent applications to automate

In a few years, 80% apps will be automated

Source: SAP

External market; business trends and technology trends

Global growth – increase globalization

Cost pressure to do “more with less”

Source: SAP

Train the machine to run on its own

Predictive and cognitive computing adding intelligence to the finance functions

Blockchain and connected value networks

Source: SAP

Focus in future to lessen the effort to “keep the lights on”

Part of the vision – employee logs into finance system, sees KPI’s important – system is leading

Source: SAP

1708 – 2017, August published

Above shows the current solution

See in the middle the “core finance areas” covered

New area is contract and lease management

Core finance is part of the optimized “order to cash” and invoice and payables management

Integrates with SAP Cloud Platform applications on the left shown above

Delivered on same code line as on-premise software

Benefits of universal journal

Source: SAP

Features of 1708

Contracts are in compliance with accounting standards

“reminder rules” to check the contract conditions, renewal options

Accelerate lease processes

Integration with SAP Analytics Cloud planning; in 1705 integration with embedded BPC

Subsidiary integration for central finance

Source:SAP

Search in innovation discovery for more details on the innovations

1711 – cost controlling for IoT scenarios – extend data structures for cost object controlling to allow “greater insights” – cost to work center – improve production cost analysis – cost for each operation

Cost assignment to WBS, and link to supplier

Contract Accounting (FI-CA) – basic scenario for credit card payments only (no collection processes)

1802 – includes some plans for prediction accounting

1805 – budgeting – enter and report on universal journal

Source: SAP

Bank analysis and fees (1711)

Consolidation of plan data is already available in 1708

Source: SAP

Key connectivity innovations with SAP Cloud Platform

1708 – enabled credit card payment

1711- enable PayPal payments

1802/5 – IR/GR monitor to leverage machine learning, next step for “autonomous” enterprise

Source: SAP

Cloud has a quarterly release to customers

On premise is released once a year

Continuous innovation for autonomous ERP

Plan to deliver more self-service configuration UI’s

Q: What does the “Y” stand for in hybris?

A: hybris

Q: FI-CA

A; cleared items planned for 1711

Open items planned for 1805

Q: Funds management/Public Sector?

A: non-Public sector customers can use 1711 – not yet planned for external roadmap – how to handle industries

  http://bit.ly/2idFA6P #SAP #SAPCloud #AI