Innowera Process Runner now introduces Live Support

Innowera Live Support

Innowera Process Runner now introduces Live Support, a step further in helping our valued customers to resolve their issues quickly.

Why Innowera Live Support?

Live Support enables reservation less, ad-hoc, on demand, installation-less, direct screen and voice integration on one-to-one or one-to-many basis. This translates in immediate and effective support that goes to the bottom of the issues quickly.

When users need assistance fast, they can connect with skilled engineer who is ready to spring into action and get the things done beyond e-mails and phone calls could explain.

Live Support also shows Innowera’s commitment to integrate and invest in the best of the technology for the benefit of our valued customer.

If a picture is worth thousand words. In this Googlera, we can extend that proverb and say a Live Support is worth tens of e-mails.

Process Runner & Identity Management APIs

 As part of the SAP identity management model, SAP provides set of application programming interfaces (APIs) that can be used by identity and access management (IAM) to manage SAP users and role assignments within their systems.  The APIs exist for both ABAP and Java systems. The ABAP APIs are provided as Business Application Programming Interfaces (BAPIs). The Java APIs are provided with the user management engine (UME) interfaces.

Identity Management Implementation in Process Runner: Process Runner provides many ready to use SAP Identity Management BAPI samples. Here are list of some of these BAPIs which are available implemented with sample data in Process Runner:

  • BAPI_USER_ACTGROUPS_ROLES_ASSIGN - Use this BAPI to assign roles.
  • BAPI_USER_ACTGROUPS_ROLES_DELETE - Use this BAPI to delete all role assignments.
  • BAPI_USER_CREATE1 - Use this BAPI to create users in the ABAP system.
  • BAPI_USER_DELETE - Use this BAPI to delete users.
  • BAPI_USER_GET_DETAIL - Use this BAPI to obtain information about a user, which includes the user’s role assignments.
  • BAPI_USER_LOCK - Use this BAPI to lock users.
  • BAPI_USER_PROFILES_ASSIGN - Use this BAPI to assign profiles to users.
  • BAPI_USER_PROFILES_DELETE – Use this BAPI to delete all profile assignments. 
  • BAPI_USER_UNLOCK - Use this BAPI to unlock users.

With these examples, Process Runner also demonstrates how can security team can efficiently manage users, roles and profiles without being dependent on Transaction, which could be difficult to record and playback, may not work same accross the various SAP systems and tends to run slower then APIs.

Download your free evaluation of Process Runner today and find out how to use these Business APIs from Excel without any scripting or coding.

Learn more on SAP Identity Management BAPIs:

https://ecohub.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/668e6629-0701-0010-7ca0-994cb7dec5a3?overridelayout=true

SAP desktop automation beyond Transaction - why should you care.

You want to automate SAP data maintenance and creation in your enterprise. There are some products in market that does only SAP transaction automation. There are few solution that offers SAP Transaction automation and much more. Question is, how limiting or effective are those transaction-only automation tools?  What are the performance implications of these solutions for your SAP landscape and for your desktops of today and tomorrow. What do you need to know before you select an SAP automation software.  This blog should answer some of these questions.

Let’s start with one of the questions: Is SAP Transaction-only automation software enough or I need more than that?

Let me ask you this - if you want to run, do you want to use one leg or both? SAP offers automation in many ways. Transaction, BAPI, RFM, GUI Scripts, etc.. If yo are using a software that does only Transaction dependent automation, you are using only one leg. You are bound to be slow and you will eventually get tired and stop running.

See the chart below. This chart lists number of objects and SAP processes that are available in each SAP releases.  Notice how SAP is releasing more and more BAPIs and RFMs.

Chart

Now the second part of the story - while Transaction automation is important, it doesn’t work well with many enjoy and extended transactions. On the other hand, BAPI and RFMs are specifically designed for program to program interfaces, tend to work well in these cases.

One would agree that humans (for which transactions are designed) and computer programs (for which BAPIs/RFMs are designed)  are two different animals and their interaction needs are different. SAP is rightfully designing many transactions for easier human interface and providing ALV Grids, drag and drop and many other neat features. All these new user elements are making it increasingly difficult for Transaction automation software to record and upload or download the data to those transactions.

To address the automation needs, SAP is providing BAPIs and RFMs which are not only designed for program to program interface but also provides much smoother performance to SAP infrastructure and to SAP client software.

Bottom line: One would wish that you need a tool that can automate not only transactions but also Business APIs (BAPIs), released RFMs and in some cases GUI scripted transactions so you can do more in SAP.  This very question was not answered by any other tool in SAP automation market place - that is before Innowera Process Runner was introduced.

Much had changed since I first wrote transaction shuttling software in 2000. Most SAP implementations were 3.1h, some were preparing for 4.0. We were still running on first generations of Pentiums. Average desktop computer memory size was about 256MB. Everyone had big CRT monitors. In short, if you look back, it purely looks like a classical legacy world.

If we look today and forward, we have multi core computing power on our desk (or lap), average desktop memory is 1GB, workplace real estate is reclaimed by flat screens. Unfortunately,  in SAP automation world, we didn’t make much progress.  We are still using only one legged transaction-only data management tools.

Here was my shopping list for the next generation enterprise grade SAP automation software:

  1. SAP desktop automation must go beyond transactions and include BAPIs, RFMs, GUI Scripting and much more.  This will enable more user to tap the vast but unexplored business logic locked in SAP.
  2. Harness the power of the computers of today and tomorrow and provide multi threading, multi processing - SAP was already designed for that since years and it was time for desktop application to catch up.
  3. Provide collaborative integration and tools and bring some of the Web 2.0 benefits to ERP world. We is better than Me. When team is sharing the resources and efforts, it’s more agile and responsive.

With Process Runner 2008, all these became reality. Process Runner supports SAP Transactions, BAPIs, RFMs and GUI Scripting from one seamless interface. It has built in auto Parallel Processing and is written in multi threads so application is always responsive. One click scheduling, built in Excel and  with Enterprise Sharing implementation, Process Runner allows effortless team collaboration and knowledge sharing, taking productivity to the next level.

SAP automation will never be same again with Process Runner. Not only you will be using your both legs but you will have some muscle power as well. After all, SAP is a trillion pound gorilla, you need an automation software that can harness and tame it.

If this sounds interesting, I invite you to download a copy of Process Runner and see it yourself why Process Runner should have a place on your desktop.

About the author:

Mickey Shah is an SAP techno-wizard. He mostly spent last 10 years implementing SAP for very large corporations in North America and Europe.  Mickey posses an outstanding SAP functional and technical knowledge and is well respected among his peers in SAP world. Implemented over 9 full life cycle go lives and upgrades, he knows exactly what it takes to deliver a good SAP automation product. Overall he is enjoying his 20th year in Information Technology, dating back from first program he wrote on Z80 in 1988.

Prior to starting Innowera in 2007, Mickey founded and created winshuttle in 2000.


Home | Products | Downloads | Support | Contacts | Blogs

© 2007-09 Innowera LLC. | Privacy Policy