1 2 3 79 Previous Next

SAP for Mobile

1,178 Posts

SAP Mobile application for Inventory Management and Warehouse Management



Some of the new key features of SAP Inventory Manager 4.2 are:


This release includes new functionality and features like :

  • Stock transport order
    • Ability to search/download STO
    • Ability to view STO details
    • Ability to perform goods issues and receipt against a STO
  • Support consignment stock
  • Purchase requisition
    • Ability to create/edit/delete purchase requisition
  • Outbound delivery process
    • Ability to download outbound delivery document
    • Perform confirmations against outbound delivery document
  • Ability to change bin quantity during bin to bin transfer




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.2

SAP Inventory Manager 4.2 Installation Guide

SAP Inventory Manager 4.2 Configuration Guide

SAP Inventory Manager 4.2 Installation Guide

SAP Inventory Manager 4.2 Java Docs

SAP Inventory Manager 4.2 User Guides

SAP Inventory Manager 4.2 Sizing Guide


SAP Inventory Manager important notes


2158268 - Software Release Note - SAP Inventory Manager 4.2

2158270 - Release Restrictions Note - SAP Inventory Manager 4.2

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









Customer can only choose one scenario for the deployment:

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

2) SAP Warehouse Manager 1.2


Base SAP Inventory Manager 4.2 with only IM Inventory functions

Install the following ABAP Add-ons in ERP System:

SMFND 610_700 with Support Package 05

SMERP 610_700 with Support Package 05


SAP Warehouse Management 1.2

Install the following ABAP Add-ons in ERP System

SMFND 610_700 with Support Package 05

SMERP 610_700 with Support Package 05


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



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.2)


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

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



POST Installation BC SET activation

Depending on your requirement activate appropriate BC set


/SMERP/SAP_INVENTORYMGR_42_REF : SAP Inventory Manager 4.2 BC Set – Reference 

/SMERP/SAP_WAREHOUSE_MANAGER_12_REF : SAP Warehouse Manager 1.2 BC Set - Reference


Customer Support

For any support related inquiries for SAP Inventory Manager 4.2 please open an incident using component MOB-SYC-SAP.


Additional reference SAP notes for Inventory Manager 4.2


2175488 - SAP Inventory Manager - Outbound Issue List missing columns on WinCE Client.


Demo Inventory Manager 4.2 Apps  can be downloaded from   Appstore for iOS platform or from Google play for Android platform.

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: 7/20/2015

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 July 20, 2015:


Issues with forthcoming fixes
[Reference-3366] - Agentry Successful Login
  Action does not work in SMP 3.0
[Reference-3859] - Complex Table Tree
  picker selects values too early and no way to cancel - WPF client
[Reference-3936] - Error in Message
  Action Step (Using OpenUI)
[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-4789] - Google Maps in an HTML
  control on WPF client does not display special characters
[Reference-4867] - Hyperlink Style on WPF
[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-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-5208] - Unable to delete
  Agentry Production versions from SMP
[Reference-5256] - Sending Client Info
  message takes a very long time on initial transmit [Timer Implementation]
[Reference-5421] - (Linux Server)
  Simultaneous login results in double deletion of TimeZone data
[Reference-5869] - Agentry server fails
  to communicate with SQL backend on SUSE
[Reference-5909] - Server instability
  with a particular SAP customer implementation

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

All Agentry 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 Mobile Platform/Agentry Products, the following KBA articles will help users troubleshoot issues tied to SMP 3.0 (Agentry) Invalid user name or password successfully. This SCN blog/article can be used as a check point for this type of issues in SMP 3.0 and Agentry.


Some of the issues may be tied to a specific product (Work Manager SAP or Work Manager IBM).


Please review each listed Knowledge Base Article (KBA) below based on your use case (proper SAP access required):


Knowledge Base Articles (KBA):


  1. 2193329 - SMP 3.0 "Invalid user name or password" that occurs when a Transmit session is restarted after an Error 14 - Agentry and SAP Work Manager 6.1 (This error is popular in Work Manager 6.1 installation - unknown error why the client disconnects - Related to KBA 2165411).
  2. 2110369 - SMP 3.0 SP04: Not able to connect via Agentry - The UserID or password is Invalid. Try Again - getEndpoint#No endpoint with name SAPXXXX was found #null (Additional tip: The quick answer to this is you used an ID in creating an Agentry node in the SAP Cockpit that is not the expected official Editor name or ID or production name ex: Application\SAPWM-v1-0-0.app.agpz - where SAPWM is the official ID).
  3. 2165411 - SMP 3.0: The user ID or password is invalid. Try Again. - Exception caught: Destination custom User AUTH does not exist - Agentry



Other older references (for older installation - kept for reference as it may be important for older installs):


  1. 1853847 - Invalid user and password error upon log in and Failed to acquire cryptography context and key container - Agentry
  2. 2015194 - Getting "Invalid Password for <User>" error during Work Manager login to Production Agentry Server
  3. 1814078 - "Invalid Password" after retransmitting the client to the server since upgrading to Agentry (5.2.16) for SAP Work Manager
  4. 1816621 - Troubleshooting: Failed to acquire cryptography context and key container - Agentry.


As we continue to help customers with key troubleshooting guides, you may bookmark this article as we may add more into this landing page soon.


Best Regards,

Mark Pe
SAP Platinum Support Engineer

To All SAP Agentry/SMP 3.0 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 Mobile Platform/Agentry Products in a cluster, the following KBA articles will help users troubleshoot issues tied to SMP 3.0 (Agentry) cluster successfully. This SCN blog/article can be used as a check point for clustering issues in SMP 3.0 and Agentry.


Please review each listed Knowledge Base Article (KBA) below based on your use case (proper SAP access required):


KBAs/SAP Notes:


  1. 2196375 - Example of how to setup Agentry Work Manager 6.2 in SMP 3.0 SP08 cluster
  2. 2188862 - Problem of publishing Work Manager on an SMP 3.0 cluster environment.
  3. 2190759 - DMS Document download is not working for SAP Work Manager (in node 2) in a cluster setup - Agentry and SMP 3.0.
  4. 2142843 - SMP 3.0 SP04 Agentry: SAP Java Load Balance - badKey and No endpoint with name - SAP Work Manager 6.1
  5. Help doc - Virtual IP is not working in Cluster network with SMP Server (Agentry app)



The goal of SAP AGS mobility support is to share the knowledge on key areas to properly support the users and customers using the SAP mobile products. We may add more resolution to this incident as we see fit. You may bookmark as needed.



See Also (Other SCN/Wiki/Whitepaper/Notes discussions):




Best Regards,

Mark Pe
SAP Platinum Support Engineer

For existing customers with Agentry 6.0.x running against a Microsoft SQL Server backend, the migration to SMP 3.0 may be confusing.  Here is a document which provides clear steps to get your application migrated successfully.  This documents goes over the following:

  1. Exporting and moving the Agentry application to the SMP environment
  2. Creating the application in the SMP Cockpit
  3. Importing the Agentry application to the new Agentry Editor
  4. Configuring the backend for the SMP application
  5. Testing the migrated application

Document: http://wiki.scn.sap.com/wiki/x/KwViGQ

SAP Mobile Secure includes a mobile application management (MAM) feature known as SAP Mobile Place. Mobile Place is a brandable, localizable and secure enterprise app store that makes it easy for companies to simply and proactively push their mobile apps into the hands of employees, business partners and consumers. And it does a lot more too.


Our top priority is to make the mobile app experience as easy as possible for all mobile users. Mobile Place technology delivers apps, services and content in a simple way to both managed and unmanaged mobile devices.


The concept of serving both managed and unmanaged devices is very important and ensures that you provide the best mobile experience for consuming enterprise apps. For example, a large beverage company will use Mobile Place to make their mobile apps easily accessible to distributors, and a healthcare provider can provide a single mobile app to authorized patients. The discovery features of mobile place help ensure any corporate developed or 3rd party apps can be easily configured.


For managed users, Mobile Place identifies when their device is out of compliance and directs them to download the appropriate mobile device management (MDM) solution before they can download any apps (note that MDM solutions include SAP Mobile Secure's own cloud based MDM offering, our on-premise SAP Afaria product or other MDM vendor products). And for companies who don’t want to MDM manage their devices, unmanaged users can get the same apps installed and secured at the app level.


Mobile Place also provides a mobile app configuration service to simplify the deployment of mobile apps – and specifically SAP Fiori apps. The mobile app configuration service is a feature that is designed to help companies easily to build, configure, wrap and deploy mobile apps. Now, a Fiori app can be deployed to a mobile device by passing the Fiori endpoint URL to the configuration service which packages the URL into the configuration of a SAP Fiori Client application, builds and signs the app and finally makes it available for deployment through Mobile Place.

Without this build service, the process for deploying Fiori apps requires several steps for both end users at IT. Users started with the basic Fiori client app, which they downloaded from the App Store. They entered the URL and other parameters manually. This increased the probability of user error and potentially reduced usability. Also, Fiori apps were generic with the same icon and name; they could not be customized or personalized in any way. Finally app-level security policies could not be defined or enforced by default. I’m pleased to report that those days are over!


The mobile app configuration service makes it easier not only for IT, but also for end users. It enables the easy creation of multiple customized SAP Fiori apps for different functionalities - with different app names, splash screens and icons. It takes the burden off the end user, increasing adoption and giving IT more control of app customization, and it allows for app-level security policies to be defined and enhanced with SAP Mobile App Protection.


Want to learn more?


Mobile Place is included at no additional cost with the purchase of SAP Mobile Secure in the cloud. And that's only 1 euro per device per month.

As a Canadian, I love the 4th of July for many reasons. One of which is the ability to blog uninterrupted while my American colleagues are out of the office enjoying parades and fireworks.


I read today on usnews.com that “80% of Americans attend a barbecue, picnic or cookout” on the 4th of July. That’s exactly the same percentage of people who download SAP Fiori with the intent of accessing SAP systems from mobile devices. While a very high number, this statistic shouldn’t be surprising considering mobile is the preferred consumption method of millions of employees working across a wide variety of roles at companies globally.


We often refer to the concept of taking SAP Fiori web applications and enabling them to act as true mobile applications on a mobile device as the “SAP Fiori mobile experience”. Delivering the best possible mobile app experience requires more than a good app level user interface.


The mobile environment is full of challenges. Anyone who has tried to use a browser on a mobile device to access corporate content behind a firewall can tell you the issues. But there are many unique challenges inherent to mobile that should be considered, such as:

  • Optimizing the experience so users can be productive away from their desktops
  • Making it easy for users to complete small tasks quickly and easily
  • Providing the option to work both online and offline
  • Taking advantage of the unique capabilities available of mobile devices
  • Addressing security concerns that may impact user experience
  • Providing an app store experience that users have come to expect.


The US smartphone market surpassed 150 million devices a year and a half ago. This weekend alone, Americans are expected to chow down on 150 million hot dogs. As we consume both hotdogs and mobile data, lets keep in mind that the average mobile consumer checks their device 150 times a day. It is in this environment of rapid change and heavy mobile usage that we have to provide easy access for employees to be productive at work. And we can help you do this with the SAP Fiori mobile experience.


As you’re planning to take SAP Fiori to your mobile users, and you’ve started to consider the issues you’ll face, I encourage you to join my colleague Scott Steadman and I as we deliver a webinar on this topic on July 22nd. If you’re interested in learning more and registering, check out the invitations for either the 11am eastern session or the 8pm eastern session.


We’ll cover topics including the end-to-end development tooling and process, implementing security features like certificate provisioning, multi-factor authentication, and central policy management, and delivering a native, more responsive and better performing user experiences to Fiori mobile apps are top issues to consider.


While you’re enjoying your hotdog and fireworks display, think ahead to your plans to take SAP Fiori mobile in 2015. Join us as we help enable you to be successful in the mobile environment.

We are pleased to announce that SAP Mobile Platform 3.0 (SP08) was released for download on SAP Service Marketplace on 2015-06-28.

We are delivering new capabilities in the following three big areas:

  • Developer Experience
  • Security Enhancements
  • Administration enhancements


The enhancements for “Developer Experience” are around the integration Services and enhancements for retail scenarios.

For the Integration Services the performance and functionality was enhanced. This enables, for example, developers to do deep inserts to any level on the REST connector. With deep inserts the developer can now insert a parent with several children with a single REST call. Further the delta tokes for complex models are enabled for the JDBC connector. This will give mobile solutions, which integrate a Database the option to improve the runtime performance through the use of delta tokens.


The second enhancements for the retail scenarios include a Point of Sale (POS) optimized API, and Paypal integration. Through the POS API developers can now connect their remote POS system through the SMP to simplify the landscape for a specific solution. Through the Paypal integration developers can now leverage the Payment options in their mobile solutions through the SMP.

We also continue with our enhancements around Security.

With the new Service Pack 08, Administrators are enabled to now leverage the SMP3 as a SAP SSO2 provider. This allows Administrators to generate SAP SSO2 tickets for their mobile solutions. So the System Landscape can be optimized and no extra SAP Java stack is needed to generate such tickets anymore. Additionally the administrator can now validate with a single click if a security configuration which was just created. This saves the administrator testing and validation time to provide the expected services.

Screen Shot 2015-07-03 at 12.54.36.png

In the area enhancements for Administration we expanded the capabilities of the Solution Manager. Now the SAP Mobile Platform fully supports the System Landscape Directory, which gives Administrators easy access to the system information of the running mobile solutions.

Further we added the capability to import and delete certificates on the SAP Mobile Platform, which are deployed on a cluster. An Admin can now centrally manage the certificates.

Screen Shot 2015-07-03 at 12.51.14.png

Additional enhancements were made the SAP Mobile Platform Admin console, which is now unified with the Admin console for the Integration services. This Allows Administrators to easily drill into mobile solutions leveraging the Integration Services. Additionally we

You can consult the SMP PAM on Service Marketplace for details (SMP3 PAM (access to the Service Market Place is needed)).



Want more information?




We are inundated by the latest hype: Everyday, someone is launching a new wearable.  The Apple Watch sold out in its initial offering and of course, exceeded all expectations once again. Not to be outdone, Google is upgrading its own OS to create a better smartwatch that will rival the Apple Watch. In the automotive world, we are peppered by news stories about the “connected car” to the “fully autonomous self-driving car.”  That notwithstanding, we already enjoy many driving autonomous features such as adaptive cruise control, lane detection, and preventative braking. Already, Tesla is launching the first elements of its much anticipated “autopilot.”  Delphi recently completed a cross-country run of its self-driving technology and of course, Google thinks they can have an autonomous driving vehicle ready for the market in 5 years.


Mobile technology is not just about mobile phones anymore. Mobile means networks for access – you know the kind: 3G, LTE, LTE-Advanced, and beyond as well as Wi-Fi.  Mobile means connectivity and big data as well as communications and certainly a backbone for the Internet of Things (IoT). Mobile also means devices – but not just our favorite smartphone – but also wearables, automobiles, and things.


From today’s new wearables to connected cars, the technology – especially mobile-centric technology – that is taking root today will enable baby boomers as well as Gen-X’ers to live more independent lives as they age.  People want and need independence and mobility. The technology that is actively being tested now and starting to become mainstream will be the technology that frees many people from dependence and isolation.

Apple Watch Gallery-1.jpg


Let’s look at a few examples starting with wearables.  Wearables such as the new Apple Watch are becoming smarter and providing more capabilities to help people monitor their health.  While today these devices mainly are used for fitness tracking, as more functionality is added (and FDA approved), we’ll see these devices being to be used for more serious health monitoring with functionality including blood oxygenation (the Apple Watch actually contains photoplethysmography sensors to measure blood oxygenation; however, it is not yet activated), respiration rates, blood pressure and more.  With accelerometers already measuring movements discerning between riding in a bumpy car and actually walking, these are truly spectacular sensors.


Devices such as smart watches and other wearables are the new: Life Alert (“I’ve fallen and I can’t get up”). While today’s Apple Watch is still tethered to an iPhone, it is likely that future wearable devices from Apple will not require this.  With very sensitive accelerometers and the appropriate software, the ability to detect a fall is extremely likely.  In addition a smart wearable’s messaging and alerting capabilities (already available) can remind people to take medication
and perform other activities.  The current generation of wearables is very much geared toward fitness; however, I do expect we’ll see more and more applications that will cater to seniors to enable them to be more independent. Utilizing mobile connectivity as well as GPS and other sensors, the ability for a wearable user to gain greater independence through personal health monitoring will increase and likely become one of the dominant markets for wearable technology.


In the not too distant future, if you are older, living alone, you'll have some peace of mind as you are “connected” – your heart rate, O2 saturation, body temperature and even blood sugar are monitored. Your wearable knows where you are and reminds you of times to take medications and if you don’t an alert could be sent to a loved one or caregiver. If you fall, your wearable detects that and alerts someone to call you to see if you are okay and if not, alerts emergency responders. Does this seem to be an invasion of your privacy?  In a way, yes; however, it’s much better than complete loss of privacy by having to move to a full-time care facility.  In fact, as technologies within wearables improve, we should see improvements in capabilities to intervene before a medical emergency or even a devastating fall.


Now let’s discuss mobility – and I mean the ability to move around. As many people age, they lose the ability to drive. In  many communities, public transportation and transportation options for seniors is limited to abysmal. People are simply trapped in their homes. Today’s mobile-centric, ride-sharing companies such as Uber or Lyft would certainly be an option; however, many seniors just do not view this as a viable option. Additionally, for many, there is just too much drama around Uber and Lyft as many organizations are not endorsing them as many municipalities are not so friendly to either company. For many, taxis, if they can afford them, are their only option.


Technology will likely provide us with self-driving or at least semi-autonomous cars?  Some of these may be on the road and ready for sale by or before 2020 and will likely grow in popularity before 2030. Business Insider reports that a “fully autonomous vehicle that can drive from point A to point B and encounter the entire range of on-road scenarios without needing any interaction from the driver” will debut in 2019.   BI Intelligence - Installed base of autonomous vehicles.png


Image being able to hop into your car and ask it to take you to your medical appointment or to visit friends and family or to the local bar or restaurant for drinks and dinner!   Talk about independence! As these new generations of Fords, Chevrolets, and yes, Teslas, Land Rovers, BMWs, Toyotas, Hondas, Audis, and more proliferate; vehicles with more autonomous driving capabilities will become more affordable. Full autonomously-driving vehicles will help the coming generations of seniors achieve considerable mobility that they would not have otherwise had.  Additionally, as vehicles become more automated, they will also become more connected, sharing data with other automated vehicles around them as well as with/from “the road itself (likely sensors periodically spaced through connected roadways).” This data will be the ultimate in M2M and will very likely use LTE-A and yet-to-be-defined 5G standards (likely after 2020) to maintain safety and autonomous operation of multiple vehicles all communicating real-time situational awareness.


As people in their forties and fifties today, reach their sixties, seventies and beyond – from the way we use mobile to communicate today (texting, video-calling, leveraging messaging, social and purpose-specific apps as well as yes, talking) to the wearables we are starting to embrace to the hints of automation and connectivity in our cars today – are all setting the stage to lead much more independent lives as they age.  Think back to where we were in mobile technology only ten years ago vs. where we are today. I refer to mobile, because it is mobile that, in my opinion, has made the greatest strides in spearheading how we live and work today. There is no reason to believe that innovation and positive steps forward won’t continue with mobile leading the way and playing a central role in the technology that will help our golden years become significantly more independent and healthy.

Mutual Authentication using X.509 Certificate with SMP 3.0 is very interesting topic. In order to help engineers configure SMP, I am posting the following white paper that explains the following:


  1. Generating X.509 certificates and configuring the SAP Backend
  2. User Mapping and adjusting profile parameters
  3. Converting PFX certificate to PKCS #12 (.p12)
  4. Configuring SMP 3.0
  5. Troubleshooting


Document: http://wiki.scn.sap.com/wiki/x/zgtYGQ

For those working with SMP 3 and Gateway for push notifications:


if you want to use the push functionality of SMP 3 together with Gateway and a SAP backend and are wondering how to configure the Gateway / Backend / SMP 3 connection, I have published a series of blogs on how to configure Gateway (FND) and backend (BEP).


The blogs hosted on my site are following the steps outlined at SAP Help, but they contain screenshots and some comments :-) Follow the blog links to go to my site and see the step-by-step doc, or click the SAP Help link to go to the corresponding page at SAP Help. I am still publishing the blogs. I will update this blog here on SCN until all blogs are published.


Backend (BEP)


1. Settings for Idempotent services Blog / SAP Help

2. Defining a remote function call to SAP Gateway Blog / SAP Help

3. Connection settings to SAP Gateway Blog / SAP Help

4. Configure the bgRFC supervisor destination Blog / SAP Help



1.       Basic configuration activities: SAP Help

1.1   Set profile parameters to support SSO2 Blog / SAP Help

1.2   Activate ICF Services Blog / SAP Help

2.       User & Authorization SAP Help

3.       SAP Gateway to Consumer (FND to SMP3) SAP Help

3.1   Creating a bgRFC destination for outbound queues Blog /SAP Help

3.2   Registering bgRFC destination for the oubound queue Blog / SAP Help

3.3 Creating bgRFC supervisor destination Blog / SAP Help

4.       SAP Gateway to SAP Backend (FND to BEP) SAP Help

4.1   Create RFC on SAP Gateway (FND) to SAP backend (BEP) Blog / SAP Help

4.2   Define trust between SAP Gateway and SAP backend (FND <-> BEP) Blog / SAP Help

4.3   Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway Blog / SAP Help

4.4   Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) Blog / SAP Help

4.5   Configure SAP system alias for applications SAP Help

5.       Activate SAP NetWeaver Gateway Blog / SAP Help

More blogs on the push functionality, how to test it, etc will follow.

We are pleased to announce that the SAP Mobile Platform rapid-deployment solution (Direct Download) was released for download on SAP Service Marketplace on June 8, 2015. You can follow the included step-by-step guides yourself to get started directly or you can work with SAP Services or SAP Partners.  As usual for rapid-deployment solutions the download is free for SAP customers and partners.


What's new?


SAP's Mobile Platform Solution can now be deployed flexibly either on premise using SAP Mobile Platform 3.0 or in the cloud with SAP HANA Cloud Platform Mobile Services (HCPms). The deployments include run time and design-time setup, configuration, development environment setup, and validation with a sample SAP Fiori app to increase time to value. The updated solution package includes the following SAP Best Practices™ for a quick and simple start for your implementation:

  • Unified foundation for on premise and cloud deployment as well as for the development of SAP mobile solutions
  • Guided run time and design-time setup with pre-configuration scripts
  • Streamlined scenario to introduce different deployment choices
  • Accelerators to reduced platform and applications implementation time
  • Simplified deployment and integration complexity of SAP Mobile Platform/SAP HANA Cloud Platform Mobile Services (HCPms) with mobile applications
  • Deployment of an end-to-end enterprise platform solution that provides installation, configuration, security, and data integration




Deployment options


On Premise -  SAP Mobile Platform 3.0



In the Cloud -  SAP HANA Cloud Platform Mobile Services (HCPms)



Download the package simply by following the below few steps:


1) Go to SAP Mobile Platform rapid-deployment solution's page http://service.sap.com/public/rds-sup

2) Tab on the orange button on the right hand side Download package

3) Select the link Installation

4) You get to a new page to download a ZIP file

5) Extract the ZIP file on your local hard disk. All documentation assets will be available offline on your desktop

6) Chose Start.htm to open the Content Library to flexible select or deselect scope items as you need them and get the related Configuration Guides



Available Mobile Rapid Deployment Solutions


  • SAP Mobile Secure rapid-deployment solution

          (Service Marketplace Page | Direct Download)

  • SAP Mobile Platform rapid-deployment solution

          (Service Marketplace Page | Direct Download)

  • SAP Work Manager rapid-deployment solution

          (Service Marketplace Page | Direct Download)


Feel free to comment, give feedback or ask questions via the comment section below.

Apple's WWDC Developer Conference has kicked off this week. This is not only the event where Apple announces new services like Apple Music, but also introduces new desktop and mobile operating system versions.


Frederic Jacobs has blogged about his initial impressions, and there is one thing that caught my eye:


2015-06-09 12_53_59-Frederic Jacobs auf Twitter_ _Apple introduces HSTS for your apps in iOS9, they .png


You see, one of the ongoing threats to mobile applications are badly secured connections. This threat category comes in many flavours:


  • Plain http connections:


    • all data can be read in transport by any network it passes through
    • the server you're talking to may not be the one you want to talk to (IP spoofing, DNS attacks - google "Pineapple WiFi")
    • anyone can intercept the connection and inject data into your stream, attacking the server code (or the client)


  • Badly implemented SSL connections


           Implementing SSL is not trivial, and I've witnessed many insecure implementations. Here are some of the more common issues:


    • #1 - not validating the SSL Server certificate. You may be talking encrypted, but not necessarily to the right server. This also makes man in the middle attacks (MITM) just as easy as on plain http connections.
    • validating the certificate, but not handling the different errors (certificate expired, mismatched host name etc.). That would also allow you to be misdirected.
    • you get a valid certificate, but it's a rogue server. Yes, attackers buy valid certificates, too. The mitigation against this is called Certificate Pinning, which basically hard codes the expected server data (certificate, key) into your code for verification.
    • accepting connections to a misconfigured server, i.e. a server with low grade security (vulnerable hash algorithms or small key sizes)


There are many more such issues. Apple is now taking a stand and effectively deprecating http connections, and giving your code a mechanism to do so in an automated way. This is a message that will be heard loud and clear in the market, and I wouldn't be surprised to see them reject apps from the store that don't implement this properly.


What is your experience with mobile applications? Were you aware of these issues? If you're a developer, is this a change you welcome?


UPDATE: Gizmodo also has a detailed list of security changes from WWDC

As a proactive support to our SAP Work Manager IBM Maximo customers, we have setup a quick start guide on how to install and get the SAP Work Manager 8.0 for the IBM Maximo (Maximo 7.5.2 version of the backend) to sync with the typical Agentry Test Environment (ATE) or SAP Agentry WPF clients.


This SAP Work Manager for Maximo 8.0 or 8.1 is a standalone SAP product to support the IBM Maximo backend enterprise system (Maximo 7.5.x and 7.6.x).


Most of these created Quick Start Guides reviewed multiple support tickets, QA tricks and request for help from the SAP Community Network (SCN discussions) to enhanced our documentation. This means by following the steps outline in the guide, the user will not see the same common error as reported in SCN or SAP ticketing (incidents). This will help each user tremendously in setting our products.


Thanks for making our SAP Work Manager for IBM Maximo successful. We wanted to share more hands on guide to help you in setting this product easily for your project and the customers.


The Quick Start Guide is to demo Microsoft SQL Server Backend database - adjust accordingly for Oracle or DB2. The user is expected to still run the SQL Admin script in the backend to generate the needed Agentry (Syclo) tables, procedures, triggers and others. If more information is needed the user may review the main installation guide.


  1. Quick Start Guide to install SAP Work Manager 8.0 with SMP 3.0  - Agentry - See SAP KBA # 2174180 - Quick Start Guide to install SAP Work Manager 8.0 for IBM Maximo with SMP 3.0 (Maximo 7.5.x).


# Note: The Quick Start Guide above can be reused for SAP Work Manager 8.1 (For Maximo 7.6).


Additional References:



Best Regards

Mark Pe
SAP Platinum Support Engineer

Hi everyone,


This is the second part of the blog post to detail out the steps to build an X Code project for SAP Work Mgr. 6.2 with ESRI GIS libraries and SAP EAM SDK included. The first part of the blog is at the below link:

Integrate GIS libraries in SAP Work Mgr. - iOS - part 1



SAP EAM Mobile App SDK 1.0


1) Download the SAP EAM SDK from SAP Support Portal. You can find this under Installation and upgrades-> A-Z-> E


2) Now we need to include the SAP EAM libraries and resources in the X Code project. Right click in the blank area in X Code -> Show in Finder. Create a “Resources” folder in your project where the .xcodeproj file is located. Create 2 new folders under the “Resources” folder, CommonResources, GISResources

create folders.jpg


2 folders.JPG


3) Copy contents from the following path SDK/Common/Common.framework/Resources to the CommonResources folder that was created in step above. Copy contents from following path SDK/GIS/GIS.framework/Resources and past them in the GISResources folder just created




4) In the end, your “Resources” folder should look like this


assets folder.jpg




5) Right click in blank area in your X Code, add files to your project and add this newly created “Resources” folder. Current project structure is in thebelow screenshot.


add resources.jpg


proj struc.jpg


6) Now we need to add the Common. Framework and GIS. Framework to the project. Click on the “target” in the project navigation view in X Code and then click on “Build Phases”-> Link Binary. Click “+” button and choose add other


add common 1.jpg



add common 2.jpg


7) Navigate to the folder where you installed the Arc GIS SDK and add the common.framework file to the project (path SDK/Common/Common.framework). Repeat to add GIS.framework file to the project (path SDK/GIS/GIS.framework).


add gis and common.jpg


8) Add systemconfiguration.framework by navigating to build phases->Link Binary


system config.jpg


9) Build your project and run in simulator. You have now finished building a project with the ESRI and SAP EAM libraries included. IF ALL BACKEND CONFIGS(from a Syclo and GIS standpoint) are in place, you should start seeing asset data under the locations tab in the app.


Hope this helps.





Filter Blog

By author:
By date:
By tag: