1 2 3 73 Previous Next

SAP for Mobile

1,086 Posts

It is finally here!

The SAP HANA Cloud Platform mobile services  (HCPms) trail that we all have been waiting for has just been released just in time for the Holidays like a big shiny gift to our Mobile community.

 

The product Manager for HCPms, Martin Grasshoff has just posted a great blog taking you trough all the needed steps and makes it very easy for you to get started.

 

Join the rest of us and take mobile for a spin in the cloud and share your experiences with us.

 

and Happy Holidays to you all as well !

 

trail.png


/ Jenny Lundberg

As part of UX service offering, SAP held an on-site workshop with OpenText to go through the entire development lifecycle within one week: from multiple, iterative steps in design to development & deployment of a Fiori app. With this blog I would like to share both, the structure and content of this workshop offering as well as a role model mindset and behaviour of OpenText as the partner which made this particular workshop very successful.01OpenText.jpgDay 1 – Persona, pain points, ideate and story board

We kicked off the workshop with an overview of what Fiori is (concept, design & technology) as well as SAP’s UX strategy to create a common knowledge level within a diverse group as a basis to build upon. With 17 participants of very diverse background (UX designers, product managers, developers) and different knowledge levels reaching from experts to people who get in contact with the Fiori UX for the first time every participant was enabled to be ready for the workshop to start.

 

Before the actual hands on part of the workshop started, the basic design process was explained in order to set the stage and expectations for the first and second day.

Within these 2 days, the goal was to get through the full process of designing (see discover and design stages below) Fiori apps for personas who need to solve one specific business task in their job.

 

02Design.png

 

After teaching and discussing the first 6 steps of the design process, it was time to roll up the sleeves: 3 groups were created where each group started with the first step to define the actual scope of the business task each group wanted to tackle. Supported by a design coach, the first step was to create a persona. With a persona it is easy to keep focus on the business problem by also creating empathy for the user during the design process.


03Persona.jpg


Each group then presented their persona within the workshop to share and openly discuss their results and experience of the group work.

 

To prepare the next round of hands on work again the theoretical background was presented and discussed about the concept for the next step, the “current user experience journey” which is a mechanism to identify the today’s process steps, system interactions and the users’ reaction and experience on each of the steps.

04UserJourney.JPG

After getting back together in groups the groups had 1 hour to finalise this exercise which increased the coverage of the walls in the large workshop room.With the analysis of the status quo and ground work done, the groups now were ready to move to the next level: Improving the experience! In the first step, the groups generated ideas with the most possible diverse and therefore comprehensive output. In order to achieve these brainstorming goals, a few basic rules were provided:

05BrainstormingGuidelines.png

With many ideas generated, the next challenge was to narrow the scope. The groups did achieve this by clustering the ideas. A final round of voting helped to prioritise the different clusters in addition.

 

Following this exercise, the day was already well advanced; however, before wrapping up the first day, the groups came together one last time to connect the ideas with the persona and the persona’s business issue. The groups accomplished this by creating a user story. In this user story a typical scenario out of the persona’s normal business day was drawn on paper / i.e. large post its. In this way it was possible to distribute the single steps, draw a story and put it up on a wall. The final user story was created quickly and ready to be easily told to others in a comprehensive way.06UserStoryWritten.gif07UserStoryVisual.gif

With the creation of the user story we wrapped up the day with a feedback round. The feedback was very positive to bring together people with different expertise like UX, product management and development to identify a persona, the persona’s daily challenges and design the user story which will make the persona’s life simpler and better. The process was perceived to be both efficient and provide valuable results.

 

Day 2 – creation of low and high fidelity prototype

After rejuvenating overnight, we kicked of the second day with each group to present their user story. The presentation was interactive because questions were raised to understand or refine the user story. This in turn helped the presenting group to sharpen the user story based on the feedback and do another iteration to refine the design. This was the base for the next step: The creation of a low fidelity prototype. The low fidelity prototype is the next step of the iteration to become more precise and evolve the user story to the actual application which can make the persona’s life simpler. With this iteration the cost is still low as the low fidelity prototype is realised with post its of various sizes. They are used to construct an application which meets the persona expectations by flexibly sticking them to the wall. In group work and discussion it is still very easy to discuss, rearrange or discard proposals which in turn encourages everyone involved to contribute with better ideas or additional thoughts. This effect is not equivalent when investing into pixel perfect design where changes are expensive and therefore more difficult to achieve. The photo below illustrates how a low fidelity prototype can look like, you can tell that it is easy to redo single cards & post its which the group actually did as new ideas came up once it was possible to relate to an actual application with a first look and feel.

 

08LowFidelityPrototype.JPG

 

In between these intense sessions we also enjoyed formidable coffee at OpenText during breaks, a big compliment – the coffee was as good as it gets!

 

09Coffee.gif

 

The final step of the design phase left to be mastered was the creation of a high fidelity prototype. The goal at the end of this 90 minute session was for the groups to present their final design of the Fiori app where other participants would now be asked to in detail challenge the design before it is taken over by development to realise the application. Firstly the participants got an introduction and a quick tour over SAP’s design stencils, a set of UI images as part of a Fiori stencil template which can be used to compile complete Fiori app mockups. Secondly the groups got familiar with the stencils and started their work. Groups divided the entire scope form the low fidelity prototype into sub screens and assigned them to group members. Each person used available stencils from the template to create screens which exactly look like a real Fiori app screens. With each group member finishing their part, the overall design was put together piece by piece until the final presentation was done. Quick feedback within the group & direct action enabled the groups to actually manage to finish the high fidelity prototype within the given time frame.

 

From start to finish every button click was mockup up, e.g. see the Fiori Launchpad tile where the persona starts:

10Tile.png

 

to the detail of the application:

 

11HighFidelityPrototype.png

 

Day 3 – Technical kick-off & first hands on

On day three the goal was now to kick off the development of the Fiori app and create a skeleton version of the app where views & navigation exist but the content of views is still open. Naturally the workshop attendees changed a bit to reflect the technical focus: UX designers & product managers stepped out, but not before sharing their interest in the results at the end of the week which was a nice proof point of the engagement level and enthusiasm by the results achieved in the first two days.

 

The day started with a technical overview of the current architecture, system landscape & deployment for Fiori apps on the on premise suite.

Following the overall architecture we gave an overview of SAPUI5 by explaining basic SAPUI5 concepts with the Fiori Sample / Reference applications which are available with the SAP Web IDE. To name a few examples we covered topics like the purpose of the Component.js file, explained how the MVC pattern is realized in Fiori apps, how test data handling (mock capabilities) or translations are realized. Of course we also dove deeper in particular topics of interest which were raised in this interactive form of initial enablement.

 

Next the group discussed how to best get started with the actual development. The agreed working mode was to have one team of two developers to focus on the OData service development where one SAP coach would sit at their side to walk them through the development process. The OData service development team decided to use the SEGW capabilities and used a step-by-step blog to build an OData service on existing APIs.

 

12ODataTeam.jpg13ODataDev.jpg

 

14ClientTeam.jpg

 

 

 

 

 

 

 

 

 

 

 

 

The remaining developers started with the Fiori app development with a code dojo like approach. Due to different knowledge levels in the team (expert to novice) the team felt this is the best approach to get started as it had the effect of having discussions & questions as well as getting everyone on the same page. A SAP UI5 coach assisted and guided the team when required.

 

 

The passion in both groups was very high, even so high that the OData team stayed some extra hours until the OData read service was ready to be consumed by the Fiori app the next day.

 












Day 4 – effective team work to finish the application

On day 4 the team got back together at 9 am and started with the discussion how to tackle the 4th day. Since the OData service was mature enough for the app to serve the read scenario, and the focus was to enable every developer to develop Fiori apps, it was decided to have the entire team to focus on the UI developments.

 

To get started, one developer shared his screen with the entire team which then started development. As a whole group, the team developed the connection to the available OData service through HCP capabilities and bound OData service attributes to the UI. More precisely the team used the metadata.xml of the built OData service as a base and developed the actual data binding to existing UI elements. After successfully calling the OData service and after seeing actual backend values on the UI, the pattern was clear to the team members, which was the base for scaling up the development. The team then took a few minutes to discuss the various work packages which needed to be developed: e.g. the master list, the detail header and footer as well as 4 different tabs for which the content needed to be developed.

 

15ClientTeamPlanning.jpg

 

Having identified the work packages, each developer picked up one of the topics and developed in parallel. Using the Web IDE and a central GIT repository, it was great to see with which speed every developer was able to provide his contribution to the overall Fiori app. During the parallel development, two SAP UI5 coaches helped whenever developers got stuck or had a question.

 

By the end of the development on that day there were 106 commits in the repository and the result was remarkable. It was pretty impressive to see how much of the design has been realized as a Fiori app and certainly the goal of enabling the team to develop Fiori apps had been achieved. To reward ourselves we had a great night out with the team to enjoy some local Bavarian food.

 

Day 5 – final presentation and time for more…

On the 5th day product managers & UX designers joined the development team which then presented its results. People were impressed on the progress to have a Fiori app that can read data from the internal test system with a UI that is responsive, simple and delightful to use. The Fiori app was close to the initially designed high fidelity prototype and proved the workshop to be a great success.

 

16GroupPresentation.jpg
17FioriAppResult.jpg

 

Due to the fact that the team was making such great progress, we spent some more time to present and demo capabilities of Fiori Smart Business applications and their power to cover insight to action use cases. After lunch we wrapped up the day with the next steps to take the Fiori app mobile by providing an overview into SAP Mobile secure and SAP Mobile app protection.

 

With a final positive feedback round, we wrapped a very successful week of passionate work and a great learning experience.

Introducing the SAP Web IDE Hybrid App Toolkit Add-on

 

In my last post, I wrote about our plans to implement hybrid development capabilities in the Web IDE. I hinted at some capabilities that were coming that allow Web IDE to interact with a local Cordova development environment. Well, the tools have been released, so it’s time to tell you about them.

 

What we have released is the SAP Web IDE Hybrid App Toolkit Add-on; the toolkit only works today with Web IDE running on the Trial Edition of the HANA Cloud Platform. The software is available for download from SCN (https://store.sap.com/sap/cp/ui/resources/store/html/SolutionDetails.html?pid=0000013586) and documentation for HAT is available as well at https://scn.sap.com/docs/DOC-60529. This is an early preview of the software, that’s why it’s running in the trial environment, and it cannot be used in production environments (for now).

 

The Hybrid App Toolkit (HAT) consists of three components:

  • Web IDE plugin
  • Hybrid App Toolkit Connector
  • Web IDE Companion Application

 

The toolkit supports hybrid application development for Android and iOS, support for Microsoft Windows is on the roadmap for a potential future release.

 

The remaining sections of this post will describe each of the components and how they work.

 

Web IDE Plugin

The Web IDE Plugin adds mobile hybrid application awareness to Web IDE; capabilities that allow a developer to set mobile properties within an application. With those properties are settings that define the target mobile device platforms for the application as well as the Cordova or SMP Hybrid SDK (Kapsel) plugins that are used by the application. Developers use Web IDE to add Cordova plugins to the project then code the application’s interaction with those plugins adding code as needed to deliver whatever capabilities are required by the application. The plugin also provides code completion for the hybrid plugin APIs and a catalog of code snippets a developer can use to quickly inject plugin code into the application.

 

When it comes time to test the web application, Web IDE provides several options. Web IDE already has live preview capabilities, the Web IDE plugin will add capabilities that allow Web IDE live preview to simulate the native capabilities exposed by the plugins (and code) added to the project (through mock data or perhaps someday some alternate mechanism).

 

A Web IDE developer may also want to test the application on a physical device or on a device emulator or simulator (Google provides Android emulators and Apple iOS simulators; yes, there is a difference). Web IDE can display a QR code a developer can use to launch the web application in a mobile device browser – simply point the device camera at the QR code and use a code scanning application to load the application URL wrapped in the QR code. To test the web application on a device emulator or simulator, a developer can simply copy the web application URL and paste it into the browser on the simulated device or into the SAP Fiori Client’s configuration and test away.

 

Hybrid App Toolkit Connector

If the web application is a hybrid application and makes use of native APIs, then testing the web application in the browser may not be enough. The application may utilize mobile device-specific hardware (such as the camera, accelerometer or compass) or make use of a mobile-specific native API (such as the Contacts application or network information APIs) that are not available in the browser or inside Web IDE’s Preview mode. The Web IDE may be adding capabilities in the future that can make some of this testing easier, but for right now for some things you just need a mobile device.

 

To accommodate this, the Hybrid App Toolkit provides the Connector (In the initial release, this component is called Communicator, this name will change to Connector in the January update of the toolkit so I’m going to use the new name here), a locally installed module that allows Web IDE to communicate with a local Cordova development environment. A developer installs and configures a local Apache Cordova development environment (installing Git, node.js then platform-specific tools such as Java, Ant (or Gradle) & ADT for Android or Xcode and some Xcode command-line tools for iOS development) before installing HAT.

 

With that in place, the developer simply right-clicks on a project in Web IDE and selects Deploy --> Deploy to local Hybrid Toolkit. Web IDE opens a connection to the Connector and passes it the Web IDE project configuration file and associated content. The Connector parses the project’s configuration file then uses the local Cordova development environment to create a new project, adds the selected mobile device platforms and Cordova or Hybrid SDK plugins then copies the web application content into the new Cordova project.

 

Developers can also select Run on --> Android Emulator/Device or Run on --> iOS Simulator/Device. With this option, the Connector will initiate the Cordova build process for the selected platform and launch the compiled application on a connected device or the appropriate device emulator or simulator.
The Connector is written in JavaScript and executed using Node.js, just like the Cordova command-line tools, so what we’ve implemented fits cleanly within the Cordova development approach.

 

Two of the drawbacks of the current implementation of this is that the Connector creates the full Cordova project every time, so there’s no incremental update nor is there any way to upload any changes you’ve made to the local project back to the Web IDE. My expectation is that we’ll fix these two limitations in a future release.

 

Hybrid App Toolkit Companion App

If you think about the process I just described, you may have noticed that there’s a lot going on there and it will take a while to create, build and deploy the native project to the device or simulator. You’re right and we don’t expect developers to use this approach for the majority of their testing. The deploy to device option is for final testing, once you’ve worked through all of the kinks in your application and are ready to deploy the application to alpha or beta testers. For iterative testing, we have another approach you can use.

 

Included with HAT is a native application project we’re calling the Hybrid App Toolkit Companion App. The Companion App is a native application developers can use to streamline testing of hybrid applications created using Web IDE on a mobile device. Instead of packaging the web application content into a Cordova application as described in the previous paragraphs, the Companion App allows a developer to make changes in Web IDE and see those changes reflected immediately in the Companion App. The source code for the Companion App is included with HAT and eventually we hope to have a version of the application available in the public app stores.

 

Let me explain how it works.

 

A developer working in Web IDE creates an application and publishes it on the Hana Cloud Platform. Then, within the Web IDE, the developer can initiate a live preview through the Companion App. Web IDE will push the web application URL through the Connector to the Companion app. With the URL in place, the application can be instantly viewed within the Companion App and refreshed whenever the content on the server is changed.

 

We hope to simplify this process in a future release by enhancing the Companion app with the Kapsel Barcode Scanner plugin. With this in place, a developer will be able to populate the web application URL in the Companion App using the QR code capabilities already included in Web IDE.
The Companion App contains all of the Cordova core and Hybrid SDK (Kapsel) plugins, so any code within the web application that utilizes the plugin APIs will work within the Companion App.

 

This approach dramatically reduces the cycle time when iteratively coding and testing changes to a hybrid application, especially when native plugins are involved. The Companion App is similar to the PhoneGap Developer App or the AppGyver Scanner application, but has direct integration with Web IDE and supports the SMP Hybrid SDK (Kapsel) plugins as well.

 

Wrap-Up

As you can see, the Web IDE team has been busy and taking a serious look at the hybrid developer use cases. The toolkit is free, available to anyone with a Web IDE license. What’s available today is a trial version of the toolkit; we will continue work on solidifying the toolkit’s capabilities and make it available for productive use soon.

 

Note that these tools are for Apache Cordova development scenarios. It’s easy to think that this toolkit was created specifically for SMP Hybrid SDK (Kapsel) developer, but that is not the case. The Hybrid SDK (Kapsel) is a set of plugins for Apache Cordova, but there are many Web IDE developers that won’t be using the Hybrid SDK. That’s why HAT supports Cordova developers as well as SMP Hybrid SDK developers.

 

As we continue to enhance the toolkit, I’ll post updates here. Stay tuned!

 

In my next post, I’ll show you how to install and use the Hybrid App Toolkit; hopefully before the end of the year.

SAP Mobile application for Inventory Management and Warehouse Management

 

 

Some of the Key features of SAP Inventory Manager 4.1 are:

 

  • Bundling of issue transactions to create a combined Material Document
  • ASN (Advance Shipping Notification) support
    • Download and view details on device
    • Perform goods receipt of material The IM

• Create IM physical Inventory document and perform cycle counts

• Receipts against Purchase Order and Production Order

• Adhoc goods receipts without Purchase order and Production order

• Create returns for Purchase order

• Perform goods issue against Work Order and reservations

• Perform goods issue for cost center

• Perform transfer 1 step (plant to plant) and SLOC to SLOC.

• Create WM physical Inventory document at quant level

• Download WM physical Inventory documents and perform cycle counts

• Perform Transfer Order Confirmation for picking and put away scenarios

• Perform Bin2Bin transfer

• Look –up Warehouse stock on-demand basis

•  Single sign-on support (Authentication against Enterprise portal and Active directory)

• Additional language support

•  Released on SMP 3.0  Platform

 

Documentation

For the latest version of the installation guide, see the SAP Service Marketplace at service.sap.com/instguides → SAP Mobile → SAP Inventory Manager-> SAP Inventory Manager 4.1

SAP Inventory Manager 4.1 Configuration Guide

SAP Inventory Manager 4.1 Installation Guide

SAP Inventory Manager 4.1 Java Docs

SAP Inventory Manager 4.1 User Guide

 

SAP Inventory Manager important notes

 

2096292 - Software Release Note - SAP Inventory Manager 4.1

2096260 Release Restrictions Note - SAP Inventory Manager 4.1

 

2016828 SAP Inventory Manager ABAP Add-On Installation Master Note

 

SAP Inventory Manager Software Pre Requisites for SAP ERP System:

SAP ERP 6.0 (SAP ECC 6.0) with SP15

SAP EHP2 FOR SAP ERP 6.0 or

SAP EHP3 FOR SAP ERP 6.0 or

SAP EHP4 FOR SAP ERP 6.0 or

SAP EHP5 FOR SAP ERP 6.0 or

SAP EHP6 FOR SAP ERP 6.0 or

SAP EHP7 FOR SAP ERP 6.0

 

 

Customer can only choose one scenario for the deployment:

1) Base SAP Inventory Manager 4.1 with only IM Inventory functions

2) Base SAP Inventory Manager 4.1 with Warehouse Management functions

 

Base SAP Inventory Manager 4.1 with only IM Inventory functions

Install the following ABAP Add-ons in ERP System:

SMFND 610_700 with Support Package 04

SMERP 610_700 with Support Package 04

 

Base SAP Inventory Manager 4.1 with Warehouse Management functions

 

Install the following ABAP Add-ons in ERP System

SMFND 610_700 with Support Package 04

SMERP 610_700 with Support Package 04

 

Ugrade from existing Inventory Manager 3.X,4.0  to Inventory 4.1

 

SAP ABAP Add-On’s

SMFND 610_700 Installation Package

SMFND 610_700 Upgrade Package

 

Reference note: 1936049- How to upgrade ABAP AddOn SYCLO 3XX_700 to SMCRM 610_700  (Steps are similar for Inventory Manager 4.1)

 

SAP Knowledge Base Articles

1957056 How to install or upgrade to Mobile Syclo AddOn 600_700 or 610_700

 

Note: - Both .SAR files should in same queue before importing.

 

 

SAP Mobile Add-on download link

  1. service.sap.com /SWDC

https://support.sap.com/swdc -> Installation & Upgrade -> SAP Mobile Solutions

-> Mobile Add-On for SAP -> MOBILE ADD-ON FOR ERP -> MOBILE ADD-ON FOR ERP 6.1

 

POST Installation BC SET activation

Depending on your requirement activate appropriate BC set

 

/SMERP/SAP_INVENTORYMGR_41_REF : SAP Inventory Manager 4.1 BC Set - Reference

/SMERP/SAP_WAREHOUSE_MANAGER_11_REF : SAP Warehouse Manager 1.1 BC Set - Reference

 

 

Additional reference SAP notes for Inventory Manager 4.1

  • 2105225 - Enable field selections to include batch field for Purchase Order fetch
  • 2104636 - Conversion Exit Missing - Inventory Documents - UOM Field - Class /SYCLO/CL_WM_INVENTORYDOC_DO

SAP Web IDE is a browser based IDE for developing SAPUI5 based applications. It lets you to rapidly design, build and deploy Fiori like apps based on SAPUI5. droid@screen-1.pngWeb IDE started supporting development of hybrid applications, the hybrid apps are based on Cordova framework. So you are free to add any Cordova plugins to your SAPUI5 project to access the native features of the phone in few clicks. In this UI5 based mobile app example I am accessing camera of my phone.

Prerequisites

Java Development Kit (JDK)

Apache Ant 1.8 or later

Android SDK - Set system environment variable ANDROID_HOME to the location SDK. Add Android tools (C:\adt-bundle-windows-x86_64-20140702\sdk\tools) and platform-tools to your path.

Node.js

Cordova - Recommended version is 3.6.3-0.2.13

Git

Hybrid App Toolkit Add-on

SMP 3 SP05 SDK

Verify Hybrid App Development Environment

To verify the development environment extract Hybrid App Toolkit Add-on and open the hybridapptoolkit.communicator-1.0.0\installation folder and run check_env.bat.

ScreenHunter_12 Dec. 15 11.52.jpg

Setting up Hybrid Toolkit Communicator

Hybrid Toolkit Communicator invokes the Hybrid App toolkit from Web IDE over HTTPS.

Navigate to the folder ..hybridapptoolkit.communicator-1.0.0/installation, right click setup.bat and Run as Administrator.

In this step you are prompted for your Web IDE host URL and set a keystore password.

ScreenHunter_13 Dec. 15 11.59.jpg

Next, open the hybridapptoolkit.communicator-1.0.0 folder and start Hybrid App Communicator by double clicking run.bat.

ScreenHunter_16 Dec. 15 16.18.jpg

Build Hybrid Companion Container App

The companion app is used to preview the hybrid app developed using Web IDE.

To build companion app, open command promt, change path to ..hybridapptoolkit.communicator-1.0.0\WebIdeCompanion\companionapp and run the command npm install.

 

Edit config.json file present in the folder ..hybridapptoolkit.communicator-1.0.0\WebIdeCompanion\companionapp as given below.

pluginDir refers to the SMP SDK installation path.

ScreenHunter_13 Dec. 15 12.51.jpg

 

Then, run command:

node create_companion_app.js

ScreenHunter_16 Dec. 16 19.53.jpg

Create Hybrid Project

From Web IDE, create a Mobile Kapsel Project and replace the intex.html with intex.html.

ScreenHunter_16 Dec. 16 18.36.jpg


Open .project.json and append the word Hybrid with the templateId. It activates required toolkit menu for the project.

ScreenHunter_16 Dec. 16 18.44.jpg

 

Configure Device and Run the App

To configure device right click on project> Project properties> Device configuration and choose a mobile platform, camera plugin and Save.

ScreenHunter_16 Dec. 16 18.53.jpg

To preview the app right click on the intex.html> Run> Preview on> Android device.

 

 

CC:

UI Development Toolkit for HTML5 Developer Center

SAP Mobile Platform Developer Center

 

Happy Coding !

Midhun VP

@midhunvptwit

Over the past couple of years, people have asked me both publically and privately if I thought SMS was dying or is a non-viable communications channel.  My answer has always been emphatically that SMS is and will continue to be a viable choice for text-based communications – both for enterprises and brands as well as person-to-person (P2P).


As 2014 winds to a close, I want to direct the focus of this posting toward the use of SMS for enterprises and brands. First off, certainly I acknowledge that Person-to-Person SMS usage has declined, with many subscribers around the world opting for non-SMS messaging solutions from WhatsApp, Line, WeChat, and others.  In other markets such as the United States and Canada, Apple iMessage has taken a bite out of SMS volumes; however, overall traffic volumes in 2014 have remained steady and have even increased one or two percentage points.

 

Brands and enterprises are increasingly turning to the SMS channel for a variety of solutions to reach all subscribers – not just subscribers with smart devices. But, in many cases, it is these very smart devices that can benefit from increased enterprise/brand usage of SMS.  And, I’m really talking about A2P or Application to Person SMS.SMS Advantage Quote 1.jpg


In the early days, A2P SMS was mainly about acquiring mobile content from the operator’s walled gardens as well as heavy usages of premium SMS.  Then the use-cases for SMS-based alerting came into being and this has helped fuel the growth of A2P SMS ever since.  Premium SMS is all but gone, save a few Asian markets, and mobile content is now almost exclusively downloaded from app stores. The mobile operator walled gardens are gone and a new, social-savvy, IP-centric ecosystem has grown up. How can there be any room for simple SMS?


The answers are quite clear.  In the survey that we (SAP Mobile Services) conducted early this year, called The SMS Advantage, we surveyed smartphone users aged 18 – 65 years in the USA, UK, France, Germany, Spain, Italy, Australia, Hong Kong, China, Malaysia, Singapore and UAE, and came up with some surprising answers.  One of them was that 81% believe sometimes that a simple SMS is preferable to mobile app usage.  Let’s drill into that conclusion a bit.

 

If you are a smartphone user and I assume the majority of my readers are, you probably have dozens of apps installed. Don’t you sometimes find that many of these apps along with the various push alerts that they provide, sometimes seem overwhelming?  If you are like me, in many cases, you simply turn off push alerts.  The problem with that is that sometimes, I can miss important updates or benefits. True, for a game that I might periodically play, I don’t need a push notification reminding me to “come back and feel the frenzy.”  I’ll feel the frenzy when I am good and ready and not until then.  Those notifications are definitely off.  But think about all of the various store apps you download. Sometimes, just sometimes, there are notifications that you’ll ultimately miss because, along with “feel the frenzy” notifications, you’re just overwhelmed with little numbers all over your app icons. We call this “Icon overload.”


Our survey also noted that “consumers are acclimatized to frequent, habitual interaction with smartphones. 68% of respondents check handsets at least every hour, with 20% checking devices every 10 minutes or more often.”  And what do they check?  If they (and you) are like me, I prioritize my smartphone checks:  SMS, Email (work, personal), then and only then might I look at social media such as Twitter, finally and only finally, I’ll review my notification center.   Note what was #1 – at least for me – SMS (or iMessage in my case – which certainly includes SMS).  Our survey also implies that respondents likely agree noting that: “81% also agree with the statement that ‘sometimes I just need a simple text message rather than complicated and varied apps.’”

 

A2P SMS (or the “simple text message”) is a key channel across a number of industries. Think about shipping logistics – especially as it pertains to engaging consumers.  Do we really want a separate app for each of the shipping vendors to notify us about shipment statuses via push notifications or for that, a simple A2P SMS can suffice in our in-box from any or all of the shippers (UPS, Post Office, FedEx, DHL, etc.)?  The survey noted that “the use of SMS is serving to enhance customer relationships with 83% of consumers saying that its use makes them feel as if ‘they care about my delivery / parcel’ and 81% saying it improved their experience of the organization overall.” This result suggests that for various types consumer-oriented logistics (shipping, order handling/processing, confirmations, status changes, etc.), SMS remains a very capable channel and logistics solutions should highly consider SMS as the primary delivery channel for consumer notifications.

273892_l_srgb_s_gl.jpg

Another industry that benefits from SMS is the area around social networks.  Yes, those social networks: Twitter, Facebook, as well as WeChat, Line, and many, many other vertical social networks (those dedicated to a particular subject matter such as fashion/shopping or automotive).  I know what you’re thinking:  Why would social networks benefit from SMS?  In reality, SMS is used heavily in a number of ways by social networks: identity management (2-Factor Authentication, One-Time Passwords, Registration Codes, etc.), notifications of new events, receipt of news as well as helping in acquisition of new social network participants.  Our research noted that 74% of consumers think that SMS can help social networks improve the way they communicate with them and 67% also indicated that SMS can help social networks differentiate themselves from others.

 

Have you ever used a social network application where you wanted to send a notification to a friend to try to get them to also join that social network?  Chances are, you sent them an SMS from the social network app – that is a heavily used capability. The message originates from you – from your device,  from your phone number, to one or more people in your address book. While not strictly A2P – this is more P2P in nature – it still is a common usage of SMS for ecosystem that are not necessarily SMS-centric. This is just one of the many ways that SMS actually complements with competing social networking ecosystems – some of which offer competing types of P2P messaging.


Social networks, logistics, transportation, financial as well as brand awareness and more are some of the industry that are benefiting from SMS. Businesses and brands should remember that mobile subscribers are becoming savvier about which apps they install and how they engage with the enterprise or brand through them. One of the most telling results of the survey was that only 17% saw SMS messages from companies as intrusive. This means that consumers want to receive SMS – not more push notifications. Like me, they attach a high priority to SMS messages.  SMS is a very wise choice and should remain so for the foreseeable future, even as the operator implementations may evolve - the ubiquity and reach will not decrease; therefore the benefit will remain.

 

Download the SAP report:  The SMS Advantage

 

Please follow me on Twitter: @wdudley2009

According to Gartner’s Strategic Planning Assumption, 70% of mobile professionals will be working on their own smart mobile devices using at least one kind of application containment by 2017.


In order to ensure that mobile device and app usage continues to grow exponentially to meet this statistic, it is important to be aware of technologies that meet security criteria yet don’t negatively impact the user experience. If you ever confused when security capabilities in EMM, MAM, and MADP technologies then read on!

 

Gartner analyst Jason Wong recently published a research note titled “How to Choose Among MADP, MAM and EMM Security Controls for Mobile Apps”. The research note provides great summary of the security capabilities in each product and also features a case study on an SAP customer who went through great measures to revamp their mobile app security strategy. The strategy needed a facelift when the company switched from BlackBerry to iPhone and Android devices (as many companies have). In order to meet all of their security guidelines yet keep the apps simple, they selected a combination of products to meet their needs.

I encourage you to download and read the full research note, available here. I’ll give you some of the highlights. First, the company used Mobile Device Management (SAP Afaria) alongside app wrapping (SAP Mobile App Protection by Mocana). They met device level security requirements and also eliminated the need for penetration testing for mobile apps, which were becoming costly and time consuming. The company also used Mocana Atlas to eliminate the multiple authentication steps necessary to access many enterprise mobility applications.  This case study is a great example of how to use SAP Mobile Secure, SAP Mobile Platform, and SAP Mobile App Protection by Mocana and Mocana Atlas platform to cover all the bases. In the end, the company has achieved stellar results and rock solid security.

 

This particular case study shows how multiple technologies including MADP, EMM/MDM, and MAM can be combined for optimal security and usability. Gartner gives excellent advice and clarifies when and why different approaches are relevant for different use cases. So click through the form and get your copy. It is well worth a read – I hope you enjoy it!

At SAPPHIRE NOW back in June, we announced the SAP Web IDE. At the time it was called SAP River RDE, but I expected that the name would change to be more in line with the product’s capabilities. (and it did). Web IDE is a browser-based IDE for designing and coding UI5 applications. Fiori apps are also based on UI5, so Web IDE is the tool SAP uses to create Fiori apps and we expect customers will want to do so as well.

 

If you were at the event and you know me (or met me there) then you probably knew that I was stationed at the Web IDE table (under the old name, of course). I was there because the SMP team has a lot of interest in Web IDE and what it means for hybrid application developers.

 

Before Web IDE, there was a product called SAP AppBuilder that was built by members of the PowerBuilder team. We connected with them during the development process and started working with them to build in awareness of the SAP Mobile Platform (SMP) Hybrid SDK (Kapsel) into AppBuilder. AppBuilder had the ability to create a Kapsel application from a web application built using the designer and that was pretty cool stuff. We’ve since stopped work on AppBuilder; the AppBuilder team worked on Web IDE and is now focused on adding mobile awareness to Web IDE.

 

With that background in place, I wrote this post to address a common question: What hybrid development capabilities are planned for Web IDE?

 

When you’re finished reading this, please give me some feedback on what we’re doing. I know what we want to build and what we’re building, but I would love to hear from you what features and capabilities you want for hybrid development, whether it’s for Web IDE or the SMP Hybrid SDK – either way, I’d love to hear your thoughts.

 

Hybrid Development

To support hybrid development, the Web IDE team has been hard at work implementing a set of mobile capabilities to Web IDE. These capabilities are enabled through a project setting and adds the following capabilities to Web IDE:

  • Hybrid application properties such as identifying target mobile device, supported device orientations and so on.
  • Support for Cordova and Kapsel plugins – with mobile properties enabled, the Web IDE user can enable one or more Kapsel or core Cordova plugins for the project.
  • Cordova and Kapsel API code completion and code snippets – Web IDE eases hybrid development by providing developers with in-IDE guidance on usage of the hybrid APIs.
  • API reference documentation for the mobile capabilities can be viewed in Web IDE and provides links to more detailed online documents.
  • Hybrid application project templates to get you started quickly – a basic starter application template, and also a Master Detail template that makes use of Kapsel plugins. A project wizard will guide you through the steps in configuring the project. Note that although the templates we provide now make use of the Kapsel plugins, you are free to create apps that are not using the Kapsel plugins.

These capabilities will initially be released through the Web IDE Trial and will work with the cloud and local build tools described below to create a robust environment for hybrid application development using Web IDE.

 

Cloud Build

At TechEd 2014 in Las Vegas and Berlin, Bjoern Goerke demonstrated an end to end demo of a Business Analyst’s request for a specific application for his end users. The demo included exposure of an API via some API management capabilities available with the HANA Cloud Platform (HCP), creating, designing and coding a UI5 application using Web IDE and delivery of the application as a native application to mobile devices through SAP Mobile Place. As end-to-end demos go, this was pretty end-to-end.

 

The process of creating the native application from Web IDE was accomplished through a Cloud Build Service (CBS) being implemented by the SAP Mobile Secure team. In the demo, the web application built using Web IDE was deployed to the HANA Cloud Platform. Then, the URL for the application was passed to the build service which packaged the URL into the configuration of a SAP Fiori Client application, built and signed the application then made it available for deployment through SAP Mobile Place.

 

When it’s released sometime next year, the CBS will allow Web IDE developers to build a Fiori Client application like was shown in the demo. Later, we want to enhance the service so it can allow a Web IDE developer to deploy a UI5 application or one or more Fiori applications directly into a hybrid application. The SAP Fiori Client runs Fiori in online mode, pulling Fiori assets and data from the Fiori Front-end Server or through an SMP Server. You can also run Fiori applications packaged inside of an Apache Cordova application (along with Launchpad and UI5) using Cordova or the SMP Hybrid SDK (Kapsel). This packaged approach is another way SAP customers are deploying Fiori apps to their end users.

 

Ultimately where we’d like to go with the CBS is to provide general purpose cloud build capabilities for hybrid applications. A developer would package a web application, most likely into a zip archive, upload it to the service and receive native application binaries for multiple mobile device platforms. I expect the CBS to be a bit like the PhoneGap Build service, but more tightly integrated with Web IDE and other SAP tools plus will provide access to the SMP Hybrid (Kapsel) plugins.

 

I’ll tell you more as we get closer to launch and I’m able to share more details.

 

Local Build

OK, so with what I’ve described so far, I’ve covered the cloud-based development process. A developer can create, design & code a web application and deploy it to a mobile device as a native application without using any local development environment or tools. What if I do want to use my local development environment with Web IDE?

 

There are many use cases for using a local development environment with an application created using Web IDE. The Web IDE is a powerful tool, but if you’re working with custom (home-grown or third-party) plugins or a modified Cordova container, you may need to use native debugging tools that aren’t available in the cloud. Additionally, if you are developing applications for a Government agency or work in an environment where security restrictions are greater, you simply may not be able to utilize a cloud service to package and sign your native mobile applications.

 

To accommodate these use cases, the Web IDE team is working on a toolkit that will allow the Web IDE to deploy a web application to a local Cordova project. The team is making some final updates to the product which will be published soon. I’ll update you with more details in my next post. Stay tuned.

This fall season there has been a flurry of activity involving SAP product experts, partners and customers around the topic of Mobile solutions for Enterprise Asset Management and Field Service. As we officially welcome Winter later this month, you can access updated information, product launch details, and recorded replays of webinars from the comfort of your warm office and or home. I suggest warming up a cup of your favourite winter drink, such as hot cocoa or apple cider, and use the following resources to catch up and plan for your 2015 plans to transform your enterprise asset management and field services practices.

 

SAP Deliver 's New Workforce Mobile Apps Running on SAP® Mobile Platform

In October at the DSAG conference, being held October 14-16 in Leipzig, Germany, SAP announced plans to release new versions of the SAP® Enterprise Asset Management (SAP EAM) solution and SAP Field Service mobile app leveraging the Maximo® back end, to help workforce customers simplify their mobile business. The planned continual investment in these industry-specific solutions demonstrates the strategic relevance and future for SAP EAM and SAP Field Service. This announcement was made at the . Full newsbyte available here.


Manju Venkatesha has posted detailed information about the new relerases, use the links below to learn more about these apps running on SAP Mobile Platform.


SAP Work Manager 6.2

SAP CRM Service Manager 4.2

SAP Inventory Manager 4.1

SAP Work Manager for Maximo 8.0.0

SAP Inventory Manager for Maximo 8.0.0

 

(more coming soon...)

 

In addition to these mobile apps, the SAP Mobile team  has released two Augmented Reality apps: SAP AR Service Technician (extension for the SAP Work Manager mobile app) and SAP AR Warehouse Picker.


The SAP AR apps that are now generally available are SAP AR Warehouse Picker and SAP AR Service Technician. Here are some handy resources to learn more about these innovative solutions. For more information about these apps and SAP Augmented Reality solutions for the Enterprise visit www.sap.com/augmented-reality.

 

SAP AR Warehouse Picker

SAP AR Service Technician

Product Brochure
AR Warehouse Picker Brochure Thumbnail.JPG

Product Brochure

AR Service Technician Brochure Thumbnail.JPG

 

Customer Webinar: Air Liquide - Empowering Field Service Through Mobility

To run smarter, asset-intensive companies must implement bold strategies to take production and service to the next levels. Mobile and GIS solutions offer unlimited potential to transform maintenance operations. For over a decade, paper work orders have been a thing of the past to nearly 100 Air Liquide field service workers. You can access a replay of the educational Webinar and hear from SAP Mobile EAM expert Brian Nelow and Corey King from Air Liquide discuss the evolution of SAP mobile solutions for Maximo and how Air Liquide is using mobile apps to gain a competitive advantage.

Link to Slides & Replay

 

ASUG Take Enterprise Asset Management Where It Matters Most with Mobile Webinar Series

The SAP Mobile EAM group teamed up with ASUG to produce the Take Enterprise Asset Management Where It Matters Most with Mobile - ASUG Webcast Series. The information shared by SAP Mobile EAM product experts and customer will enable you to understand how to use mobile technology, including the latest devices and wearables, to drive innovation in your enterprise asset management and field service operations.


Here is a summary of the four part series with links to speakers, slides and replays.

 

SAP Mobile Enterprise Asset
Management (EAM)
Today, Roadmap and Future
Untether Field Workers with
Augmented Reality
Mobile EAM Customer Spotlight:
Marathon Oil & Aquarion Water
Plan now for the Future of

Mobile EAM

Field workers and maintenance technicians are always on the move. They require real-time access to information about assets, inventory and work orders in dynamic environments. Asset intensive industry leaders are looking to mobile and other innovative technologies for process improvement and execution, enhanced safety and compliance, and real-time collaboration among operations, maintenance, logistics, service and support. Attend this webinar with Patrick Flaherty, SAP Mobile Field Service & EAM Expert to learn about SAP’s current solutions, roadmap and future of mobile EAM.

 

Link to Slides & Replay

The opportunity to untether field workers is here. With augmented reality, field service technicians are enabled with a “hands free” experience through visual enterprise models, gesture or touch events, voice recognition and remote expert calling to perform their tasks and operations. Attend this webinar with SAP Augmented Reality Experts to learn what Augmented Reality is all about, SAP’s current solutions for field workers, and customer use cases and co-innovation stories.

 

Link to Slides & Replay

Over 600 customers around the globe have deployed Mobile EAM solutions from SAP to streamline asset management and realize dramatic operational efficiencies in the workplace. According to SAP Performance Benchmarking and Customer Reference studies, mobile EAM customers have increased labor productivity by up to 50% and reduced production down-time and delays by as much as 30%. Attend this Mobile EAM Customer Spotlight session to learn about real SAP Mobile EAM customer deployments and best practices.

 

 

Link to Slides & Replay

Mobile solutions have already changed how people work and assets are managed to drive operational excellence. The next generation of mobile technologies including devices, wearables, and augmented reality will create opportunities to increase asset performance and reliability. Attend this session with Erik Schrampf, Mobile Solution Management for EAM/Field Service (Syclo) Mobile Apps, to learn about the future of Mobile EAM including product roadmaps and customer co- innovation plans.

 

Link to Slides & Replay

Speakers: Patrick Flaherty,

Carolyn Coad

Speakers: Pascal Lessard,

Josh Waddell

Speakers:

Carolyn Coad, SAP

Jason Moore, Marathon Oil

Sarina Miller, Marathon Oil

John Pondiccio, Aquarion Water Company

Speakers: Erik Schrampf, Carolyn Coad


Innovation Examples from 2014 Fall SAP TechEd && d-code Events

SAP Mobile EAM experts shared innovative examples of how to extend SAP Work Manager from a mobile experience into a contextually aware and augmented reality experience. Check out these replay videos to learn more.

 

The Future of Field Workers: SAP Work Manager with iBeaconsUntether Field Workers with SAP AR Service Technician
Field workers operate in dynamic environments with many assets that have specific maintenance requirements and detailed life histories. Using opensource technology such as iBeacons, workers can benefit from real-time updates to optimize asset performance. In this interview Carolyn Coad, SAP TechEd && d-code Reporter, and Jonathan Zufi, SAP Director of the Mobile Innovation Center, walk through a concept app, SAP Work Manager with iBeacons.Field workers require hands free technology to properly maintain assets. Using Augmented Reality solutions this requirement can be met. In this interview, Carolyn Coad, SAP TechEd && d-code Reporter, experiences SAP AR Service Technician, an AR extension of the SAP Work Manager mobile app, with Pascal Lessard, SAP Product Manager through smart glasses.

Welcome to the third part of a story started in two other posts about using business resources in mobility, here's the first and the second post. Here, we talk about compliance. More precisely, about solutions that can help us to be compliant in our daily operations

 

The story, in short:

 

>>> "...ok here you are, but pay attention to the confidentiality policy, that's very confidential stuff and I am responsible for this... OK???"

 

<<< "Yeah sure, ... wait, what exactly? well nevermind, need to go! Bye!"

 

>>> "..."

 

The problem

 

The problem in essence is that specific information classification policies exist and define well how to protect a piece of information. However, in many cases the adequate implementation of such terms depends solely on information consumers. Not only deliberate policy violations or theft, but also human factors like stress, fatigue or sometimes even little oversights may lead to breaching the confidentiality of a data asset.

 

For instance, if we receive a critical and urgent request to perform a task while on a connection in an airport, are we compliant with our confidentiality policy when accessing a customer's private data on our tablet and discussing them in a confcall?

 

What if we could have a simple tool to store data securely but that supports a compliant information consumption, assisting users especially when in mobility?

 

To do so, we would need:

  • Requirement #1: to describe confidentiality policy terms in a machine-understandable manner in a computer artefact
  • Requirement #2: to enforce policy terms considering contextual information captured by mobile sensors
  • Requirement #3: to harmonise such enforcement mechanism with the mobile user experience

 

At SAP ASCOT Product Security Research group, we are working on this problem and we will show you the earliest findings (for a bit of background, here is the first and the second post).

 

Important: Please note that the following work stems from research activities and has prototypical character. It does not correspond to functionality offered by official SAP products

 

Let's start with Requirement #1.

 

Obtaining a machine-understandable policy for achieving compliance

 

This task can easily become very hard, for instance: regulations and standards use high-level terms, expressions and indirect references; require ordered temporal action sequences that can span on long periods; does not always define explicitly forbidden actions or operations, and so on.

 

Let's consider a simple example: what are the requirements for a mobile application that consumes Personal Identifiable Information of EU citizens? Look at this this table:

 

DataRegulationDraft-table.png

This table is currently proposed as part of the new EU Data Privacy Regulation, in one of the drafts discussed by the European Parliament. If the proposal will get accepted, every software will present this table to its users in order to explain in a nutshell its privacy policy terms. Application developers have to declare whether their software complies or not with the terms proposed, it is only mandatory to say "yes" to rows 1-3.  We chose this example as it allows to synthesize few relevant privacy requirements that could be of general interest for many application developers.

 

So, as application developers, we may want to define a policy to comply with these privacy requirements. A simple approach can be to elaborate on each of the rows in the previous table, thus defining some lower-level requirements like in the following example:

 

regulation-to-policy.png

 

Ok this seems useful but... Which conceptual foundation could we use for implementing the finer-grained requirements and conditions? Well, for instance, Access Control and one of its refinements, Usage Control, may be of use: for instance, to describe whether personal data are disseminated to commercial third parties (point #6 of the table on the right in the previous picture). Let's see how do they work.

access_and_usage_control.png

In a nutshell, Access and Usage Control permit to control and monitor how protected resources are accessed and processed. In  particular, it is possible to use conditions and obligations for access and usage control, so that, for example, a notification email must be sent if a piece of data is consumed  outside of a secured building. We use XACML and PPL as policy languages to transform compliance directives in machine-readable policies, and we enforce them using a specific engine (see here and here for more details). In fact, now we are starting to address also Requirement #2.

 

Enforce policy terms

 

Using XACML and PPL, it is possible to define a machine-readable policy that describes all the finer-level requirements. Let's see how:

 

policy-to-ppl-v2.png

OK, but what does it mean in practice??? where's the code??? Here you are!

 

ppl-snippet-v2.png

Therefore, it is possible to define machine-readable policies following EC Data Privacy Draft Regulation (or the existing Directive). Of course, many other policies, like corporate confidentiality policies, may be implemented in the same way.

 

Lastly, considering Requirement #3, we tried to develop some proof-of-concepts that are smoothly integrated in everyone's mobile UX.

 

Integrate enforcement in UX

 

Let's see some results:

 

It is possible to render where and when a piece of data was consumed.
gps-log.jpg
It is possible to render a policy to end-users in a simple and clear manner.

policy-rendering-mobile.png

It is possible to enforce automatically the policy terms.

enforcement-app.png

Conclusion

 

In this post, we saw how it is possible to achieve compliance in information distribution and consumption by means of machine-understandable policies and specific policy enforcement solutions.

 

We defined XACML+PPL implementations with enforcement mechanisms for cloud and mobile, defining context-specific triggers, conditions and obligations. All the previous screenshots come from our mobile enforcement engine.

 

We are involved in the EU-funded Coco Cloud collaborative research project that investigates on compliance and confidentiality issues connected to information exchanges on cloud and mobile, for inquiries, suggestions or just for more details feel free to get in touch with us:

 

Francesco DI CERBO, Slim TRABELSI or Laurent Gomez from SAP ASCOT Product Security Research group.

 

Special Thanks to Stuart SHORT for the precious help.

DISCLAIMER: SAP does not have an 'Official' toolset to achieve this. ** Though I am an SAP employee, SAP does not endorse the methods, toolset or the codes that I have used in this guide.

 

Hi Fiori Friends,

 

I am sure when one tried to build first few custom Fiori like applications in SAPUI5 you have encountered a problem regarding Component-preload.js.

Especially if you tried to figure out the which files are required to run the application via Chrome debugger tools, most probably you have encountered the following error -

/sap/bc/ui5_ui5/sap/..../Component-preload.js 404 Not found


This is an error due to the absence of such a file from the custom Fiori like app directory. To avoid this some of us add a dummy Component-preload.js file in the eclipse working folder and commit the changes to the Gateway server. While it is sufficient to stop the error by this way, we fail to achieve the intent of Component-preload.js file.

 

The purpose of Component-preload.js file is to load all the project resources in one single file. This resolves multiple problems for the online app - it reduces loading time and maintains single source for project resources. It also reduces the total payload of resource files.


The component-preload file is a minified and uglified combination of all javascript and xml resources. How to achieve this?


Well while this is not rocket science , it is a multi-step process. When I started the process myself, I could not find many reusable resources which will enable me do achive what I wanted. Following is the step-by-step guide which will help you to create such a file.


Note: I assume you use Windows. The reusable files are created accordingly. If you use OS X or Linux, you may need to change the batch file and node installations. Also gulpfile.js needs to changed include unix style separators from '/' to '\'.


The reusable files are at sjsaha/Fiori-Reusables · GitHub 


Step 1: You have finished your Eclipse based SAPUI5 development  and your project looks like this:

eclipse-start.PNG

Step 2: Download Noad.js installer and install in your OS. Source: http://nodejs.org/download/

Node.PNG


Step 3: Install the node and confirm the node installation from command prompt, by checking the Node.js version

node-installed.PNG

Step 4: Please close Eclipse and go to the workspace folder in Windows Explorer and navigate to the WebContent folder of your Fiori UI project

folder-start.PNG


Step 5: Download the files (gulpcmd.bat and gulpfile.js) from github - https://github.com/sjsaha/Fiori-Reusables and copy the files  in WebContent folder. After copying the directory structure should look like this -


folder-mid.PNG


Step 6: Modify the 'gulpfile.js' to suit your project name and structure. At minimum, please modify your application name. You may need to change individual gulp tasks according tour project structure and needs.


gulpfile-modify.PNG


Step 7: Review the gulpcmd.bat file. If your computer is behind a corporate network proxy you might need to delete the REM from the following lines and change to the proxy servers IP or domain name.


gulpcmd-proxy.PNG



Step 7: Execute the gulpcmd.bat file by double clicking or open the command prompt at WeConetent folder. This script should work in a verbose mode and if there is no error, will silently create a Component-preload.js file in the WebContent folder.


folder-end.PNG


Warning: The script does download a lot of Node plugins. So network connectivity is required. Also it will create a 'node_modules' folder in the working directory, where Node is installed (check PATH in environment variables).


node-modules.PNG


Step 8: Rest of the tasks are standard development tasks. Open Eclipse, Format the project folder to import the generated files, delete the gulpfile.js and gulpcmd.bat from eclipse.


eclise-refresh.png  right.jpg  eclipse-format.png  right.jpg eclipse-final.PNG


Step 9: Commit the new project into NetWeaver Gateway server.

Step 10: Run the new Fiori app.


Do not forget to read the documentation at Extending and Testing SAP Fiori Apps before you modify / build your custom app.


To know more about the problem and solution you may refer to the following forum posts.

component-preload.js not found  (404 not found) In SAP fiori like UI5 APP

Inline XMLViews into component-preload.js 


John Patterson's confidence on Gulp.js helped me to create the reusable tools.



As I said this is an indicative how-to, may not work 100% for your project implementation. I hope it gives a good starting point, on which you can build your own successful Fiori app.


Let's get fast and fiori-ous.


____________________________________________________________________________________________________________________________________


** SAP now has an official method to package SAPUI5 into Component-preload at SAP/grunt-openui5 · GitHub. The Fiori specific tools had to be reused from there.

This methods still remain valid, - especially for those who like gulp.js more than Grunt.



To All SAP Work Manager users,

 

SAP Global Services and Support (GSS - One Service) tries to be proactive in giving resolutions out to the customer to be readily available before the need arises.

 

Based on some internal and external installation of SAP Work Manager Products, the following KBA articles will help users deploy and troubleshoot performance issue successfully. This article can be use as a check point prior to deployment to production that key KBA articles and SAP notes were applied.

 

Please review each article with their corresponding SAP Work Manager versions under environment.

 

For SAP Backend:

 

  1. SAP KBA # 2095696: Troubleshooting Performance Issue: SAP Work Manager - Workorder/Notification Fetch taking too long.
  2. SAP KBA # 2095707: Performance Issue: SAP Work Manager SAP Mobile Add-On for ERP - Bad Performance after activation of BC set.
  3. SAP KBA # 2106336: Troubleshooting Performance Issue: SAP Work Manager - Measurement Point creation - update task is slow.

 

 

For IBM Backend:

 

  1. SAP KBA # 2095626: Performance Issue: SAP Work Manager for IBM - Workorder fetches taking too long and causes deadlocks and error 13.

 

Agentry Clients

 

We appreciate all the customers/developers/consultants who gave all the field report about our SAP products performance and where to improve. We value your feedback to help make our product best in class. In this blog, please see some of the troubleshooting or key KBA articles to improve performance issues for your production environment.

 

You may bookmark this article as we plan to update this article with new SAP notes/resolution later.

 

Best Regards,

Mark Pe

SAP Senior Support Engineer

Overview:

SAP CRM Service Manager is designed to automate workflow and improve service. It connects technicians with the data stored in the SAP CRM system so they can better manager customer service requests. With SAP CRM Service Manager mobile app, you can maximize efficiency and effectiveness of your field technicians by providing them access to relevant and real-time information and tools. The app connects to the SAP Customer Relationship Management (SAP CRM) applications and enables status updates, last minute changes, and accurate data capturing to help achieve higher first-time fix rates.

 

This release includes new functionality and features like:

  • Create Service Order
  • Edit Service Order
  • Confirmation enhancement
  • Ibase/reference object at item level
  • Counter reading at header and item level
  • GIS integration – ESRI
  • Manage service orders and create confirmations in real time
  • Record status, materials, problems, actions, expenses, and customer signatures
  • Generate account factsheets and create service confirmation for serialized products and add surveys
  • Get 360 degrees customer view using Account factsheet
  • Display customer and contact information in regional formats
  • Support all note types created on SAP CRM Service backend
  • Upload and Download Attachments for Service Orders and Confirmations
  • Display equipment or install base listings.
  • Display entitlements and contract or service history
  • Display Assignments on Calendar
  • Create / Edit non-order ibase for Service confirmation
  • View Serial number for iObject / Equipment
  • Backend integration with MRS
  • Support on SMP 3.0 Platform

 

 

Vehicle Stock Component

The Vehicle Stock add-on component for SAP CRM Service Manager is an optional component that allows technicians to view current stock for their vehicle as well as external stock. They can transfer stock to and from their vehicle in preparation for field services. The Stock component integrates into ECC.

  • It enables the Service Technician to view stock within their Vehicle as well as stock with other users.
  • Technicians can control his own vehicle/trunk stock like look-up/search products for current inventory,
  • Technicians can transfer from his vehicle stock into another technician
  • Transfer stock from external trunk/technician.
  • Search and receives STO's.

 

Deployment scenarios:

  1. 1. SAP CRM Service Manager 4.2
  2. 2. SAP CRM Service Manager 4.2  with Vehicle Stock component

 

Service Manager 4.2 release notes

 

2084248 - Software Release Note - SAP CRM Service Manager 4.2

2084285 - Release Restrictions Note - SAP CRM Service Manager 4.2

 

Prerequisites

For SAP CRM Service Manager 4.2

SAP CRM 7.0 Ehp 0 SP11 (SAP_ABA 701 SP11+,  SAP_BASIS 701 SP11, BBPCRM 700 SP11+, WFM core 2.0 SP16+, MRS 9.0 SP01)

For optional Vehicle stock component

SAP ECC 6.0 Ehp 0 SP15 (SAP_ABA 700 SP18+, SAP_BASIS 700 SP18+,SAP_APPL 600 SP15+)

 

Mobile Add-On for CRM 6.10 contains the following ABAP Add-On software components:

 

Mobile Add-on for CRM 6.1  can be found in the Service Marketplace at: http://service.sap.com/swdc -> Installation and Upgrades - > -Browse our Download catalog -> SAP Mobile Solutions->Mobile Add-On for SAP -> MOBILE ADD-ON FOR CRM -> MOBILE ADD-ON FOR CRM 6.1.

 

SMFND 610_700 - Mobile Integration Framework Foundation

SMCRM 610_700 - Application Add-On for SAP CRM 7

 

Upgrade from existing Service Manager 3.X or 4.0 SAP ABAP Add-On

SMFND 610_700 Installation Package

SMCRM 610_700 Upgrade Package

 

Service Manager Documentation

For the latest version of the installation guide and documentation, see the SAP Service Marketplace athttp://service.sap.com/instguides -> SAP Mobile -> SAP Service Manager -> SAP Service Manager 4.2.



Device Support

    • Windows 7 and above
      • Windows 8 Pro tablets
      • Windows 8 RT tablets is not supported
      • Windows 8 Phone is not supported
    • Windows Mobile 6.0, 6.1, and 6.5
    • Apple iOS versions 7.0 and above
    • Android Tablet minimum version is 4.0 and above
    • Android Phone minimum version is 4.0 and above

 

Reference Notes:

 

2014454 - MRS Integration with CRM Service Manager 4.1

1935387 - For SAP CRM Service Manager ABAP AddOn Installation

1962949 - Release Information Note - Mobile Add-On for CRM 6.10 Support Packages

1936049- How to upgrade ABAP AddOn SYCLO 3XX_700 to SMCRM 610_700

1828657 - To get more information about planning the installation and upgrades of the ABAP add-ons SMFND, SMERP, SMISU, and SMCRM.

Mobile Work Order Management for SAP Systems

Key Features of SAP Work Manager 6.2


Current release of SAP Work Manager offers a great range of functionality:

 

  • Access to asset location, repair history, work order details and materials needed in real time
  • View and Create Work Orders, Operations, Measurement Documents , Material Confirmations and Set Order Status
  • Create Notifications, Tasks, Items and Activities
  • View and Execute Inspection rounds with PRT, Wizard driven Measurement Points reading
  • View Linear Asset Data for Orders, Operations, Notifications, Functional Locations, Equipment’s, Characteristics and Measurement Readings
  • Create and Assign Linear Assets to Orders, Operations, Notifications and Items.
  • Upload and Download Attachments to Work Orders, Notifications, Equipment’s and Functional Locations
  • View equipment, functional locations, characteristics, measuring points, measurement readings.
  • View equipment and functional location unrelated to orders and notifications
  • Create/update equipment and functional location master data
  • Install/dismantle equipment
  • Enhancements to Meter Management component (periodic meter readings and disconnections/reconnections)
  • Enhancements to geographical information system features (offline map support, feature layers, and additional geometrics like poly-lines and polygons )
  • Report Time & Attendance (CATS)
  • Integration with ESRI GIS
  • Integration with SAP 3D Visual Enterprise
  • Support on SMP 3.0 Platform


Work Manager 6.2 components


Please note that all of listed components below are optional.


1Meter Management Component

When Meter Management Component add-on component is implemented

It adds the following functionality to the core Work Manager application:-

  • Install meters (technical and full installations)
  • Remove Meters (technical and full removal)
  • Replace meters (full replacement)
  • Meter repair
  • Non-periodic meter readings
  • Disconnection / Reconnection orders
  • Periodic meter readings (MRU)

2)  Customer Service Component

When Customer Service Component add-on component is implemented

it adds the following functionality to the core Work Manager application:-

Basic customer information, including contact and address information

  • Details of technicians’ service engagements with the customer
  • Details of business partners for the customer
  • Provides technicians access to contract and warranty information for the customer
  • Related work order information
  • Install base information on core components consisting of infrastructure information relevant to the work order
  • Mapping functionality for both customer address and partner address

 

3) Crew Management Component

When Crew Management Component  add-on component is implemented

it adds the following functionality to the core Work Manager application:-

It allows supervisors and team leaders to manage their crew

  • Add, remove, and select crew technicians
  • Add, remove, and select vehicles
  • Track vehicle usage through vehicle odometer readings
  • Report, review, and approve time for crew

 

SAP Work Manager 6.2 release notes

2093621 - Software Release Note - SAP Work Manager 6.2

2084941 -  Release Restrictions Note - SAP Work Manager 6.2 

1936034 - SAP Work Manager ABAP AddOn Installation Master Note


Deployment options:-

  • Work Manager base without LAM
  • Work Manager base with LAM
  • Work Manager base with Crew Management
  • Work Manager with Meter Management
  • Work Manager with Customer Service

 

SAP Work Manager Software Pre Requisites


1) Work Manager 6.2 Base Version (Without LAM)

Install the following ABAP Add-ons in ERP System:

  • SMFND 610_700 with Support Package 04
  • SMERP 610_700 with Support Package 04

BC set to activate:

/SMERP/SAP_WORK_MANAGER_62_REF: SAP Work Manager 6.2.0 BC Set - Reference


2) Work Manager 6.2 with LAM & Inspection Rounds (SAP ERP 6.0 System with EHP5 or above)

Install the following ABAP Add-ons in ERP System:

  • SMFND 610_700 with Support Package 04
  • SMERP 610_700 with Support Package 04

BC set to activate:

       /SMERP/SAP_WORKMGR_62_EHP5_REF : SAP Work Manager 6.2.0 for EHP5 with LAM BC Set - Reference


3) Base SAP Work Manager 6.2 with Meter Management Component 1.5  ( SAP ERP 6.0 Component IS-UT 600 Support Package 15 (or higher) with Enhancement Package 0 (or higher) )

 

Install the following ABAP Add-ons in ERP System:

  • SMFND 610_700 with Support Package 04
  • SMERP 610_700 with Support Package 04
  • SMISU 610_700 with Support Package 04

BC set to activate:

     /SMISU/SAP_METER_MGMNT_20_REF : SAP Meter Management 2.0 BC Set - Reference

 

4) Base SAP Work Manager 6.2 with ERP Customer Service Component 2.1 (Customer Service Component 2.1)

 

SMFND 610_700 with Support Package 04

SMERP 610_700 with Support Package 04

 

BC set to activate:

       /SMERP/SAP_CUST_SERVICE_21_REF : SAP Customer Service 2.1 BC Set - Reference

 

NOTE: Linear Asset Management (LAM) is not supported by SAP Customer Service 2.0 application.

 

5) Base SAP Work Manager 6.2 with Crew Management

Install the base SAP Work Manager 6.2 Add-On as mentioned above and there is no special BC Set required for Crew Management component. Please go through the documentation "SAP Work Manager Add-on component installation version 6.2" for additional details and configuration panel changes required for Crew Management Component.

 

 

 

 

 

SAP ABAP Add-On download link

 

service.sap.com/SWDC

 

Installation and Upgrades - > Browse our Download catalog -> SAP Mobile Solutions
-> Mobile Add-On for SAP -> MOBILE ADD-ON FOR ERP -> MOBILE ADD-ON FOR ERP 6.1


POST Installation switch activation

Activate switch /SMERP/EPH5_EAM_BUS_FUNC if you’re using LAM -  (SFW5)


Work Manager 6.2 Documentation

 

For the latest version of the installation guide and documentation, see the SAP Service Marketplace at http://service.sap.com/instguides -> SAP Mobile -> SAP Work Manager-> SAP Work Manager 6.2.

 

Additional SAP notes for Work Manager 6.2:-

1962948 -   Release Information Note - Mobile Add-On for ERP 6.10 Support Packages
1828657 -   To get more information about planning the installation and upgrades of the ABAP add-ons SMFND, SMERP, SMISU, and SMCRM.

2085946 -   Additional Mobile configuration panel changes for SAP Work Manager 6.2 application

1982598 -   GIS Integration Support for Mobile Add-On 6.10 for further integration details

Quick Start Guide: SAP Work Manager 6.X with SMP (Agentry)

Hi All,

 

We came across a such scenario in our project. After doing a lots of exploration we found the solution, So thought of to share with you all.

 

Problem Statement: - Sometimes we come across a scenario where we need to apply multiple filters at the same time on a complex table.

Scenario: - Suppose we have a complex table ZCTEmployee with the following structure.

                    Employee Structure.PNG

                   

                  Let's say we have a requirement to display the employees in a drop down on a Transaction screen, who matches a certain criteria.

 

                 E.g. The employees need to be populated in the drop-down, who belongs to X department and with grade A.

Assumptions: -

      1. The complex table ZCTEmployee is already created and required Java and ABAP codes are in place for the complex table.
      2. The transaction screen is ready with three UI elements.
        1. Grade-string
        2. Department-string
        3. Employee- Complex Table Drop Down

Solution:-

      1. We need to create 4 indexes for the complex table ZCTEmployee.
        1. EmpIDIndex(Unique)
        2. DepartmentIndex
        3. GradeByDepartmentIndex
        4. NameByGradeByDepartmentIndex
    • Please make sure the field and parent index are mapped properly as per the below screen shot.

                    CT-Index.PNG

 

                    2.  Make sure the transaction screen is designed as below and corresponding transaction is bound properly.


                             Screen.PNG

                    3.      Now our main intent is to pass the Grade & Department screen field values to the index of the complex table through cascade parent.

                                   CT-Field.PNG

                   4.     Now we will write a rule to pass both the screen field values(Grade & Department) to the index of the complex table, which is very interesting.

                             Rule-x.PNG

        • Here NEWLINE plays a major role.

 

Conclusion :- NEWLINE allows to return more than one value from a rule.

 


I hope this article will helpful.

Have a nice day!!


Thanks,

Sudhir.

  


Actions

Filter Blog

By author:
By date:
By tag: