1 2 3 81 Previous Next

SAP for Mobile

1,206 Posts

Recently, I was involved in device selection process for one of the utility major in Europe. The common question that was asked being - What is the best device for mobilising SAP? The usual response for this query would be - 'It depends!'. Similarly, there can be a possibility of many other related questions like -  What are all the criteria for this? What are the key selection factors? What will be the ROI on each options? and so on.

In my research based on my previous experiences I have come up with some ideas which I would like to share across.

The first part is to split the device requirements into three and each of these sections has different device requirements:



  1. Business Operations - Normal office employees with daily business operations.
  2. Specialist Operations - Mobile devices used in harsh environments, devices which needs to be rugged, needs different RFID,Barcode and other means of communication.
  3. Customer Facing - These are employees who face customers on sales cycles and it is important to carry a polished device as it says a bit about the company.


Now before defining the criteria, it is important to meet and discuss the key decision makers. Below are the key ones I normally use :


  • Experienced users for each area - Drivers, field technicians, Metering operation partner.
  • Business Lead - The person who is responsible for the program from the Business site.
  • Solution Architect - The person whose duty will be to make sure the device is supported by SAP, solution requirements can be achieved by the form factor and other accessories.
  • MDM Team - Lot of app lifecycle is managed by MDM. The MDM team should understand and make sure the MDM solution can support this device for rollout and provisioning etc. and also that the key device policies are supported by the device.
  • Vendor Selection Manager - The key person who holds all the communication to different vendors.
  • Health and Safety Officer - This person's presence is not required for all meetings but the device has to be approved to cater the Corporate's Health and Safety standards.




Now coming to criteria which needs to be formulated for each operations , a formal document was prepared with all requirements and sent out to different vendors.After a detailed response from vendors a session was run with detailed specification of each device with software installed.



It is very important to understand the life of each devices and its operating system life.  Careful consideration has to be taken care for employees with disabilities. It is always recommended to run a pilot with some selected superusers. From all these select two best devices.


Also I have seen in my previous experiences sometimes it is better to have two devices instead of one as this gives loads of productivity, mainly in heavy vehicles one OBU (onboard unit ) and one handheld are the best options.


Once its down to last two vendors, the ROI is key consideration and costing. After this the app can be deployed to the devices and pilot programme can be started

This afternoon SAP has released a new Android client to the Google Play store for Afaria and Mobile Secure.  The client version is 8412 and the release notes which cover fixed issues are located here:


Current android client release September 2015 -Afaria

There is a new announcement for App wrapping using Mocana in Afaria and Mobile Secure with iOS9.  The changes in iOS9 require changes for Mocana wrapped applications to maintain full support. Therefore SAP does not recommend that Mocana users update their clients to iOS9 until a new update has been issued for Afaria and Mobile Secure.  Please see the details here in this KBA.

Mobile App Protection support and iOS 9

Last year I was the integration/solution architect to expose a custom SAP business process as mobile App. In this posting I want to enumerate the major aspects and challenges we encountered. And with success, the App is in productive use, and the end-result recently won the SAP Quality Award 2015.

Aspects and challenges

SAP business system is a closed system

This actually encompasses 2 different aspects. For one, the functionality of the SAP system is locked internal in the SAP system with SAP proprietary technology and data formats, not exposed nor fit for alternative UI channels. And second, the SAP system is isolated from the evil outside in the company-internal infra.


Users demand a pleasant ‘form-factor’

Users are fed up with the arcane UI, and want a user-experience that feels good. This means it must look good, and moreover that it must have a pleasant behavior that supports the user in doing the work effective and efficient.


The mobile ‘form-factor’ must enable multiple devices and screens

Most noticable is that users expect an App to be usable from tablets and smartphones. And second is that for tablets, but in particular for smartphones, multiple different device formats and OS platforms are in use.


Unknown makes unloved

Since decades the SAP business systems are the stable base on which the organizations rely. Any change to this status quo inhibits the risk of disruption. And then also all that mobile technology and aspects introduces new knowledge. It is human response to be very careful, perhaps even scared, to all that new stuff.


The unknown outside is evil

IT security is not an easy, or even thankful job. They are held responsible in case of issues, and taken for granted otherwise.

When functionality is exposed via additional channels, also the security vulnerability increases. It is only rightful that security is very cautious, and demands proofing that the changes do not result in unacceptable security and thus business risks.


Secure and reliable authentication from App into SAP

Like all business systems, SAP internal processing is permission-based. What one is allowed to do depends on authentication (who you are) and authorization (what your allowed to do). In mobilizing the business process, the authentication part is primary delegated to the App, while the authorization part remains in the business system.

Typical the App-identity is different from the SAP identity, and a credential-mapping is required (Single Sign-On).



Although performance is also an aspect of the pleasant app-experience, the importance of this topic for user acceptance on itself warrants dedicated focus. Business-users are just as intolerant against bad-performing business-apps as they are in the personal context against non-performing consumer-apps. Also note that a major motivation for mobilizing SAP business process is to facilitate shorter time to handle, and a performant ui-experience is in that sense an absolute requirement.


What if…

...in <x> time insights or business situation has changed, and the delivered App is no longer sufficient? Such uncertainty about future developments (business and technology) is often misused as excuse to halt, and make no changes. And users are withheld from improvements in operation of the daily business actions that can be delivered to them today.


Infra aspects highlighted

1. Interoperability

Connectivity from App to the SAP business system
Expose the SAP proprietary data and functionality for outside consumption in the App
Data mapping of SAP proprietary data model in a standards-based, and optimized dataformat
Integration endpoints

2. Identity Management / IAM
Authentication (SSO across diverse authentication administrations)
Permission management

3. Security
Data loss ( through Device loss)
Data integrity (inspection, to prevent via encryption)
Unmanaged devices / BYOD
User and Device onboarding

4. Performance
Network throughput + latency

5. Auditing / Audit Trails
Health monitoring


Architectural decisions:

  1. Deliver the App as a web-app; and rely on platform browsers to make sure the App runs on the multiple devices
  2. Deploy as PhoneGap hybrid App that can directly be started from the device (relieving the user of need to retype the url in browser)
  3. Expose the required functionality to outside as an API, with endpoints that are invoced via integration and data standards.
  4. Use Gateway as middleware to deliver the service API: develop + runtime
  5. Use SAPUI5 as html/javascript platform to deliver Responsive Design UI, and in look&feel that users are getting more familiarized with via the expanding SAP Fiori apps
  6. Architect the App as loosely-connected UI-part and Processing part. This allows to exchange the UI-part for another UI-format when the situation has changed, while the processing part can be reused.
  7. Architect the service API for an optimized integration surface. Avoid excessive call behavior of the App into the service API resulting in network latency, and design ‘chatty’ interface methods instead of data-minimized service methods.
  8. We did NOT utilize SAP Mobile Platform, but hook into mobile platform that is already in use. Providing device onboarding, reverse proxy, transfer security.
  9. Rely on proven SAP-technology of Java Authentication Server + LogonModule to convert customer-internal credential into SAP Logon Ticket (MYSAPSSO2, used in the SAP system).


Project approach

  1. UI-design the ‘mobile experience’: build mock-ups together with stakeholders to quickly arrive at an App-experience that will truly help the business users.
  2. Take the initial unknowledgable at the customer side on the tour to teach the new mobile concepts, and as such take away their uncertainties and anxiety that are due the unknown
  3. Team up with SAP as supplier, and convince IT stakeholders at the customer on the support level of standard software (Gateway, SAPUI5). Call in on well-known SAP expertise (Andre Fischer, Holger Bruchelt) for solid advice and/or crosschecking.




Some relevant references:

Disclosure: I am the CTO the company that delivered the underlying software for this implementation.


This week the Norwegian Government Agency for Financial Management (DFØ) released their new app for 40 000 employees in the Norwegian public sector and they plan to roll it out to 40 000 more.


In addition they won an award in the competition called «time thieves» - an incentive to promote reduction in non-productive time that was issued by the Ministry of Local Government and Modernization.



For me, the most interesting thing about this project is the fact that it had an implementation cost of around 300 000 $, the app is super user-friendly and runs directly on their existing SAP systems. It enables the 40 000 users to register time and create leave requests on-the-go with travel expense being added in the next release. The initial tests show up to 80% reduction in time performing these tasks compared to using the existing desktop portal. That ROI is self- explanatory but I am certain they will see other huge benefits such as real-time input of data, greatly reduced back-office work and most importantly - happy users.

The media is full of failed governmental IT projects that costs millions, are way over budget and fail to deliver the expected results. So what did they do different and better in this project that made them hit the media because of success rather than failure? (Which is the most common reason journalists cover public projects)

Here are a few points I believe was vital in their success

Use of existing back-end system and landscape


The Managing Director of DFØ Øystein Børmer said during the press conference: “The alternative would have been to replace the underlying ERP system, a 100 million dollar project”


I believe he is right.


DFØ have been using SAP for a long time. They handle financials and HR for over 200 organizations under the various Norwegian ministries. In addition to different requirements among these, there are strict national regulations making an off-the-shelf solution impossible. Also, few other ERP systems can handle such a setup (Needless to say they have a lot of clients in their system)  


By implementing the solution into their existing SAP landscape the reuse of existing SAP transactions reduces complexity, the need of back-end testing is almost obsolete and costly integration is avoided.


Agile methodology and modern UI framework


Ingvild Nygaard  the DFØ project manager stated that during the project they frequently tested the app on real users. They realized that what project members considered user-friendly was not true for the actual recipients of the App. Delivering a solution to such a large and diverse group regarding digital maturity, demands simplicity and if the App is not intuitive you have failed.

They decided to use interaction design principles, change the SAPUI5 theme and add quite a bit of custom styling. The design is following Google’s Material Design guidelines and even includes the ripple effect to highlight user actions (See Robin van het Hof I actually admit to you guys being useful )


I think they did a good job! (It is in Norwegian but you get the idea)


2.png   3.png


A traditional waterfall methodology where more time would be spent on arguing over change-requests than fixing the actual problem would have been disastrous in this situation.



Easy but secure logon


The surest way of losing user adoption for apps is to have a complex logon routine. You wouldn’t use your Facebook app very frequently if you had to provide your credentials every time you opened the app and neither will users of your enterprise app.


Still DFØ required a very secure solution and it was solved in the following way:


When users logon to the app for the first time, they are required to on-board via “ID-porten”, a common national solution for authentication to public services.  “ID-porten” supports multiple two-factor authentication solutions and covers all Norwegian citizens and expats.


As part of the on-boarding they choose a personal PIN-code which is then used for subsequent logins to the app from the specific device. After 90 days the security credentials have expired and a new login to “ID-porten” is required.





The right team


I had the pleasure of hosting training for the internal DFØ team members together with my co-founder Ole-André Haugen. They are great people and very capable ABAP developers, but more importantly they were extremely enthusiastic. The opportunity to finally work on a project that would enhance their SAP system with a state of the art look and feel and hopefully happy users made a big difference.


DFØ decided on using the SAP SI and Neptune Partner Bouvet. Leading this team was Alumni SAP Mentor and UX enthusiast  Dagfinn Parnas . This team has deep SAP and ABAP knowledge coupled with Design and UI experts. The fact that they very early on acquired SAPUI5 skills was also vital.


Finally I have to include a picture of the Norwegian Minister of Finance Siv Jensen getting a demo of the App by Project Manager Ingvild Nygaard. Cool to have members of the Norwegian government as Neptune users




To read more on my views on SAP Enterprise Mobility you can read this blog

SP6 for Afaria 7 is available for download at support portal from SAP. It comes with some significant changes, like support for Windows 2012/2012 R2 and Android for Work. As SP5 is from September 2014, it makes 100% sense to update to SP6 as soon as you can. If you are wondering how to do that and what to expect during the update process, I have published some blogs on my website showing the procedure and a simple validation of the installation. The blogs contain a lot of screenshots: 84 in total. You can see it as a walkthrough.


The blogs are:

  1. Afaria 7 - Update to SP6
  2. Install Afaria Server
  3. Install Afaria API Service and Administrator
  4. Install Self Service Portal
  5. Install Enrollment Server
  6. Install Package Server
  7. Validation of Afaria 7 SP6


The update is an easy task to do, basically you “reinstall” Afaria 7. Luckily all the previously configuration data is read by the setup program, no need to enter everything again!

SAP TechEd held in Las Vegas is approaching, and Barcelona is following in November. Since we released SMP 3 SP9 and HCPms 1.2 we will have a lot of new stuff to show and talk about.


If you want to learn more about the new features we bring and join us at, I would like to help you planning your agenda by pointing to the following sessions. You will find them in the mobile track for which Sue Berry and I are responsible for the content.  Check out the session catalog for your location.

For those of you who visited my Lecture MOB 205 last year on the event or watched it online, you will be interested to hear that we continue on our offline story. In the Session MOB 360 and MOB 108 we will share our latest features and capabilities of our offline features.

The latest and greatest tools are getting presented by my

My colleague Matthias De la Roche is going to present our latest and greatest tooling in his Sessions MOB160 and MOB 100 have a preview in his video.


Looking foreword seeing you in Vegas or Barcelona.




since Afaria 7.0 SP6 is now supporting Windows 2012 (64bit) and 2012 R2 i wrote an Wiki Article about updating the Windows 2008 R2 Server to the latest Operating System.


You will find the Wiki here: CLICK


Best Regards

Andreas Kuhn

To All SAP Agentry/SMP 3.0 users,


SAP Global Services and Support (GSS - One Service) tries to be proactive in giving an announcement to the customers prior to more issues to show. We value your time in using our products and we always try to fix issues and give the best solution out to the customer.


Unfortunately based on some internal and external installation of SAP Mobile Platform/Agentry Products in iOS 9, the SAP Agentry team believed that upgrading the Agentry client to iOS 9 will see a serious performance degradation running Agentry-based applications.


As part of the target delivery, an official Agentry iOS client that supports iOS 9 is scheduled to be released for SMP 3.0 SDK SP10 and later. The plan was to get it ready by end of September to be given to the iOS App store to be available 1 week later unless there are new issues seen that may delay the delivery (An update will be posted).


More internal SAP testing is being done at the moment and it is possible that we may see more issues that would require an SAP SMP 3.0 SP10 patch.


If we get more information we may update this Broadcast Announcement or update the official release notes.


Thanks for all your patience as we strive to improve our software. We also thank each of the customers in the community who brought this to our attention.


As an action: Please share right away to your users and team of developers.


Best Regards,

Mark Pe
SAP Platinum Support Engineer

Once again September 9th was the date for the announcement of a new slate of Apple iPhone devices – this year gives us the iPhone 6S and iPhone 6S Plus with more new exciting features including 3D Touch and an upgraded 12 Megapixel camera.


While all these new features are certainly important, let’s once again look at the Apple iPhone 6s and 6s Plus LTE support. This year, the iPhone 6s and 6s Plus models bring us either 22 or 23 LTE bands (depending on the model - Click the table in this posting to view a larger image)  I’ve covered Apple’s LTE support thrice before: Last year, my September 15, 2014 post detailed the 20 LTE bands available on the Apple 6 and 6 Plus.  In my September 12, 2013 post, I took a detailed look at LTE support for the iPhone 5c/5s models and finally back 3 years ago, in my September 14, 2012 post, where I was excited to see that the iPhone 5 support 5 LTE bands!


For 2015’s iPhone 6s and 6s Plus, Apple’s LTE Advanced supports downlink speeds up to 300 Mbps, under ideal conditions with 23 LTE bands. Last year’s iPhone 6/6 Plus only tentatively supported LTE-Advanced to 150 Mbps and that was not fully realized. This year, various leaked sources indicated that the iPhone 6s/6s Plus would host the Qualcomm MDM9635M chip -- also referred to as the "9X35" Gobi modem platform. This supports LTE Cat6 (peak data rate of 300 Mbps), carrier aggregation (40 MHz support with 20 + 20 MHz in downlink) among other specifications.  This means that the 6s and 6s Plus will likely work in networks where the mobile operator is deploying LTE Advanced through carrier aggregation as this chip set (and its associated RF chip set) will support virtually all carrier aggregation band combinations in deployment or planning. This will certainly help Sprint iPhone 6s/6s Plus users as they are leveraging carrier aggregation technology (using 1900 [Band 25] and 2500 [Band 41] bands for download carrier aggregation) and the PCS band for uploads to provide more capacity and better speeds.  See more in this Reddit discussion.iPhone 6s LTE Bands.png


Why are multiple bands so important? The more bands provide more and better coverage within your own network as well as greater possibility of roaming.  Fierce Wireless noted:  “Apple's iPhone 6s and 6s Plus support LTE Band 12 in the 700 MHz A Block, which T-Mobile has been rapidly deploying where it has such spectrum. That should give T-Mobile a lift because customers who get the new iPhone 6s/6s Plus models will have access to broader coverage, especially in suburban and rural markets. T-Mobile said last month that its 700 MHz LTE deployment now covers 130 million POPs and that the company will get close to 190 million POPs by the end of the year.”


The GSA now indicates that as of September 4, 2015, there are 422 commercially launched LTE networks in 143 countries with 187 LTE1800 and 59 LTE TDD networks. With the iPhone 6s/6s Plus increased number of supported LTE bands, these devices continue to become true world phones.  Our own research shows around 170 LTE networks are supporting roaming, powered by ours and a number of mostly mobile operator group IPXs.


For LTE-Advanced, GSA notes there are now 88 commercially launched systems across 45 countries with 73 commercial networks supporting Cat 6 (supporting maximum speed of 300 Mbps). That too, is good for the iPhone 6s/6s Plus as the evidence fully supports an LTE-Advanced Cat 6 implementation.LTE-Advanced networks - 07.2015.png


iPhone 6s/6s Plus are not revolutionary in terms of their support for Cat 6 LTE-Advanced; however, they are within the first groups of 50 or so devices (as of this writing) that support LTE-Advanced.  other notable devices with similar support, include Samsung’s Galaxy S6 and a number of devices from Huawei, Sony, ZTE, Nokia, LG, and Motorola.


Coming soon and under discussions across the industry is 5G. At this point, I cannot realistically explain what the 5G technology will be, as many of the specifications are still being finalized.  I am worried; however, that some marketers will refer to LTE-Advanced as “5G.” Between 3GPP, ITU, and marketing arms across the industry, the terms 4G and 5G are quite obfuscated. For example, in the US market, an iPhone will display “4G” when connected to an HSPA+ (which is really 3.5G network).  Fortunately, they display “LTE” when connected to LTE networks.  Will we see “LTE-A” for LTE-Advanced networks?  Stay tuned.  The next few years will be entertaining.

Whether you’re a developer in a large enterprise, small or medium enterprise, or even a start-up or you’re a freelancer, you can create mobile applications in the cloud and develop secure mobile apps. Developing Mobile Apps with SAP HANA Cloud Platform focuses on developing mobile apps with SAP HANA Cloud Platform to allow developers to extend, build, and run business applications on mobile devices in the cloud. The course will focus on using SAP Fiori client to host content and build mobile qualities, such as push notifications, lifecycle management, application security, offline use, and much more.

“But I’ve already learned to build an SAP Fiori app?”, I hear you say. Then you’re one step ahead of the rest as you’ve already gained experience with SAP Web Integrated Development Environment (IDE). With this course, you can further extend your SAP Fiori app into a mobile app and learn to use SAP HANA Mobile Services, add plug-ins, and much more! The course will show you how to mobilize an SAP Fiori app but you can apply the knowledge you learn to build native apps for both Android and iOS devices.

To complete the exercises, you will need to be an administrator on your computer to ensure you can configure and set up the system correctly. Although the course begins on October 27, there will be videos available from October 13 to enable you to get your system configured so you will be ready to hit the ground running once the content is released from October 27. The course will run for six weeks with 4-6 hours per week required to complete the content.

Sign up today and get your business transactions as mobile as your employees and customers!

I had an experience on an error which encountered when entering Labortime (not CATS). You may encounter this error on WM 6.1 or WM 6.2 versions.


When you add an activity labortime on a workorder you may face following error while sych;

/SMERP/PM_DOWORKORDERCONF_CRT): Number 0,0 cannot be encoded as a BCD. Invalid digit ',' encountered

SAP has a fix on this error : Note 2163538

By applying this note solved the problem but we got another one which related to the time unit problem. The activity duration and work duration time unit has been  set statically "MIN"(Minutes) in the standart TimeEntryCreateBAPI class.

Screen Shot 2015-09-07 at 22.55.19.png

This works if localization and implementation are in english on ERP side. In other cases if use localization any other than english so you have to enhace the BAPI class to change value.

In my scenario i changed to "DAK" in terms of Turkish.

Mark Pe , Bill Froelich i want to take this in your consideration. Setting of these two values dynamically would be better so that no need for enhancement.


Tahir ÖZ

To my surprise, I recently received an email that one of sessions I did at Teched was last year was going to be featured on SCN. I didn’t even recall that they had recorded it. MOB203 – Enable Data For Mobile Consumption was the session, and if I recall correctly the session went well (at least in my mind). Anyway, I was coerced to write a blog revisiting the subject and update everyone on where things stand today in regards to enabling data for mobile consumption. So here goes…


MOB203 focused on three things: Integration Gateway, Delta Query Support for OData, and getting real time business event notifications by integrating Push Notification support into your business systems. So it makes to tackle these one at a time.


Integration Gateway (IGW) – this is a component of the SAP Mobile Platform 3.0. You might have heard that SAP is a huge supporter of OData and that much of our Mobile Platform SDK as well as Mobile Platform both on-Premise and Cloud (HCPms) requires it’s use (think offline odata). So it is extremely critical we have a component that is able to translate other service formats (SOAP, Simple REST, JDBC) into OData and make it as simple as possible for our customers. When I did this session last year, IGW only supported SOAP (with many constraints), JDBC, JPA (which no one used), and ODC (backend SAP OData Services). Since then, we now support exposing Simple REST services and many of the constraints have been lifted on SOAP services (though some remain). Much of the new functionality requires scripting which can be done in JavaScript or Groovy…you can pick. We do have graphical mapping tools but these can only do so much, with some things you just gotta get you hands dirty and do some coding/scripting. Anyway, a lot is still being done in this area. Things are moving to the cloud and this IGW functionality should be showing up there soon. You can find lots of blogs, and how to guides on this IGW subject here.


Implementing Delta Query Support in SAP Gateway OData – this was the name of the section in MOB203. The scope has widened quite a bit. Not all OData comes from SAP Gateway, we need to understand how to enable this from an OData backend. First some back ground, OData delta queries allow you to query an OData service with a timestamp, the OData service should then use that timestamp to query for all new entities, changed entities and deleted entities. This functionality is key for Offline OData that is possible with HCPms and SMP3. You can imagine when you offline data onto a device that when your refresh that data you don’t want to have to query the entry result set…you want to be able to get the changes/deltas. To get the best offline performance supporting delta queries is key. We have many how to guides on this subject. My colleague Kenichi Unnai did a great webinar on how to get the best performance out of Offline OData. You can watch his webinar here. You can also find how to guides, blogs and more on the Integration are of our Mobility Enablement page on SCN.


So that leaves us now with Push Notification support and tying that in with business events on your backend. To me this is the apex of mobility…push notifications enable so much efficiency…their use is so wide spread from chats, to games, to now business applications. If you can inform your employees of important events the instant they happen, you can imagine that this can drive a lot of efficiencies and at the same time get your users actually using your app. Not too much has changed with how this is done since I did the presentation. That said, I would like to see more companies implementing this feature, it will surely be cost effective to do so. You can find a how to guide written by my colleague Jin Shin that takes you through the process of setting it all up and triggering the push notification from an SAP Gateway system.


Anyway, I hope you enjoy the MOB203 revisited session:




If you have any questions please let me know!

To All SAP Mobile Platform and Agentry application 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 6.2 from the Google Play Store there are installation issues that were seen tied to devices that have specific built-in functionality (ex: No GPS,With Camera and Others).









Please refer to SAP Knowledge Base Article # 2213381 - Agentry / SMP 3.0: Android cannot install - Your device isn't compatible with this version from the Google Play Store - SAP Work Manager 6.2 for more details of the cause, workaround and resolution.


Thanks to all customers and/or partners who have reported this issue with the Google Play Store. We in SAP have found the root cause and will work the details with Google Play as documented in 2213381.


We appreciate the partnership that SAP customers and users have given us in the SAP Community Network (SCN) mobile space: http://scn.sap.com/community/mobile


Best Regards,

Mark Pe
SAP Platinum Support Engineer (Mobility)

To All SAP Agentry/SMP 3.0 users,


SAP Global Services and Support (GSS - One Service) tries to be proactive in knowledge sharing to the customers.


Based on some internal and external discussion with customers, partners and SAP consultants, general knowledge on what is known may be needed to be provided to prevent additional wasted work being done by customers or system integrators or users to prove that an issue exists.


  • The goal of the Agentry Support News (X-Month Year) is to make the customer know what issues and fixes are in the pipeline based on the given date
  • By knowing what is known, this proactively helps the customer or users of Agentry (in SMP 3.0) know what are the known issues to mitigate the time spent on analyzing and proving to SAP that an issue exist as the issue is already known and the fix forthcoming
  • There is no need to let SAP know of the issue (or no need to open an incident) - this will save precious time for both user/customer/partner and SAP
  • The forthcoming fix will be targeted on a newer release based on the specified current release below. It may be the next Patch Level or Patch Level +N or SP Level)


Current Date: 09/01/2015 (September 1)

Current SP Release Runtime: (Agentry Server - SMP): SMP 3.0 SP08

Current SP Release SDK: (Agentry Editor and Clients): SMP 3.0 SP09


Disclaimer: The data in here may change without notice and due care is required when referencing it. Do not use the data in here as reference when purchasing software, hardware or services in SAP or external parties. Some of the data may be purposely removed as it may be tied to new features that are not readily to be shared publicly and may only be shared in major announcement or official documentation. An actual date of release will not be provided to safeguard SAP in presenting a date. Not all known issues and fixes will be presented in this news article.


SAP Global Support proactively tries to partner with SAP users/customers/partners to generate information that can be shared to improve our software and services. We as the community of SAP users need to help each other by sharing the known fixes and knowledge to help strengthen the bond and speed of innovation.

Reactive to proactive, SAP support is best in class.


Before: Customers have a problem (issue) and need to ask SAP - Is this a known issue?



Now (Agentry Support News - Month - Year): Helping the customer not to report an issue when the fix is forthcoming



Blog Rule: Any question about more details on the data below, you may respond to this blog. Keep it only to the subject header presented (do not ask for dates or version numbers as those can change or anything outside what is listed). For example, if you need more information on a line item specify the reference number and title, the author of this article may respond when available. Any other details you may refer to the disclaimer above.

Data as of September 1, 2015:



Issues with forthcoming fixes

[REFERENCE-3366] - Successful Login Action

[REFERENCE-3843] - Document Selection screen size is too small on iOS client

[REFERENCE-3859] - Complex Table Tree picker selects values too early and no way to cancel - WPF client

[REFERENCE-3938] - [Editor] Unable to get values from Response Header using OData Back-end

[REFERENCE-4075] - WPF Tile Inline Add Creates Ghost Tile at End of List

[REFERENCE-4242] - WPF-Scrolling down and then up on Complex Table Search dialog causes the "-NONE-" entry to have values in fields that were initially (and supposed to be) blank

[REFERENCE-4245] - Complex Table Drop Down controls are empty on WPF

[REFERENCE-4359] - WPF client button label by rule does not refresh

[REFERENCE-4364] - Typing into Android string field is not reflected on the screen

[REFERENCE-4546] - Incorrect screen animation invoked by OpenUI

[REFERENCE-4733] - Tile edit button not showing on WPF client

[REFERENCE-4789] - Google Maps in an HTML control on WPF client does not display special characters

[REFERENCE-4867] - Hyperlink Style on WPF Client

[REFERENCE-4922] - Half-width Japanese characters are only partially displayed

[REFERENCE-4923] - Android Branded client crashes when switching networks

[REFERENCE-5209] - Transactions unnecessarily orphaned during collection replacement

[REFERENCE-5218] - Close stale sockets after server timeout value is met

[REFERENCE-5231] - Backend-initiated lockouts don't work

[REFERENCE-5233] - User is able to delete main screen set via Compare view

[REFERENCE-5319] - Add Support for Teamshare Session Logging

[REFERENCE-5523] - iOS client opens HTTPS URLs externally instead of HTML Control

[REFERENCE-5628] - Team Share - Export by tag does not import all changed values

[REFERENCE-5699] - Team Share - Updated images overridden after publish

[REFERENCE-5714] - WPF crashes when displaying tile list (disconnectedItem)

[REFERENCE-5715] - WPF platform caption doesn't update on screensets

[REFERENCE-5717] - Android client crashes with an overlay view in landscape mode

[REFERENCE-5784] - Team Share - Renamed property treated as new property after update

[REFERENCE-5843] - GPS coordinates are inconsistently available on iOS

[REFERENCE-5904] - WPF ATE Stability Issues

[REFERENCE-5912] - Background sending in transmit hangs WPF client

[REFERENCE-5928] - "Close the screen set that the user is leaving" is working inconsistently

[REFERENCE-6017] - Android toolbar disappears after rotating device with Agentry in the background

[REFERENCE-6041] - Multi-screen tile display still shows object though no item is selected in Tile List

[REFERENCE-6043] - WPF External Data Field file browser filters on image types only

[REFERENCE-6046] - Editor - Sometimes the properties tab for an object doesn't open

[REFERENCE-6047] - List Tile filter on WPF client is not refreshed following an object update

[REFERENCE-6048] - Android screen is showing check boxes when it should be clickable images

[REFERENCE-6053] - User Credential conflict when using multiple Agentry clients on iOS

[REFERENCE-6054] - List Selection field in iOS shows "is required" error

[REFERENCE-6058] - Keyboard header remains on screen after SlideOver activation in iOS 9

[REFERENCE-6059] - Location control not getting validated

[REFERENCE-6065] - Communication Error when using Turkish localization (Android Dev)

[REFERENCE-6066] - WPF client crash when running .bat file via Windows Command Action Step

[REFERENCE-6068] - Agentry buttons on iOS input controls are not picking up application tint style

[REFERENCE-6099] - "Swipe to Navigate" broken on Android

[REFERENCE-6100] - Clicking Scan button sometimes crashes the client

[REFERENCE-6142] - Team Share - Unable to complete Update

[REFERENCE-6144] - Action buttons and action menus overlap on iOS9

[REFERENCE-6357] - Unable to edit JavaScript Text rule terms via the middle rule editor pane

[REFERENCE-6359] - WPF client crash running an action following a canceled transaction

[REFERENCE-6393] - Team Share - Rule duplicated in tree after update

[REFERENCE-6401] - Agentry client text field allows only half of max length for Russian characters

[REFERENCE-6402] - Core - Creates database tables with invalid names

[REFERENCE-6403] - Android toolbar draws incorrectly following rotation

[REFERENCE-6441] - Fortify "Use after free" regression from WPF Client crashes when trying to end shift fix

[REFERENCE-6448] - Android client crashing with java.lang.OutOfMemoryError

[REFERENCE-6449] - Android client crashing intermittently with java.lang.IllegalStateException

[REFERENCE-6463] - WPF & iOS Rule based screens in a screenset does not get refreshed

[REFERENCE-6501] - Double click action results in "Collection not found" error on WPF client

[REFERENCE-6599] - Team Share - Editor freezes during update

[REFERENCE-6626] - Interacting with SP10 WPF ATE repeatedly crashes Eclipse

[REFERENCE-6702] - WPF client allows blank signature after the clear button is pressed for a required Signature Field

[REFERENCE-5504] - Client Crashed After selecting Exit button in Server URL selection dialog

[REFERENCE-5505] - client crashed after input invalid URL in server selection dialog

[REFERENCE-6002] - Image with 2 state or 4 state doesn't work on toolbar button

[REFERENCE-6011] - Overflow toolbar doesn't work on action button support

[REFERENCE-6579] - Error when executing batch build command for wpcordova client





We hope by sharing this knowledge, you the customer may be able to save time and effort and continue to innovate to speed up configuration and deployment.


We may blog another Agentry Support News in the future with new data. Please stay tune.


Have a great day.


Mark Pe

SAP Platinum Support Engineer


Filter Blog

By author:
By date:
By tag: