Skip to Content

Introduction

In February Juan Reyes posted a blog to launch the idea to rebrand SAP Netweaver Administrator to “Basis General”. The blog received a good amount of comments but the conclusion of those comments was that rebranding would not be sufficient to actually change anything about the issues.

Issues described like double posting on the forum and community members that get confused about where they should post and end up posting in the wrong section. Besides those two issues there is also the fact that there are a lot of categories and that some are overlapping making it hard to find the right category to post in.

It was certainly visible that there are community members that care deeply about system administration. As a result of the blog and the comments we (Juan Reyes, Martin English and I) decided to put our heads together and talk about the rebranding and how we can get more awareness that there are system administrators active on SCN.

Our place on SCN

While SCN started out mainly as a place for developers, it has evolved and now also includes other community areas such as the BPX (Business Process Expert Community).

I tend to believe system administrators are an important part of the whole SAP ecosystem. They keep the SAP systems running, enhance the performance, perform troubleshooting, update the software etc. They perform multiple roles, system administrator, database administrator, operating system administrator, architect, designer etc. They have knowledge on different technologies and provide guidance to the customers how to implement the SAP products.

If they are so important where is the space for SAP system administrators on SCN then?

When I look at the content featured on events, hands-on sessions and so on I often see functional use and development topics but there is a need for technical content and hands-on sessions as well.

Many of my colleagues and fellow system administrators would love to attend a hands on session on how to configure Root Cause Analysis. While I can organize such event on a small scale there should be content like this in major SAP events such as TechED. I’m convinced those seats would be filled in no time.

Calling out

Because of the above reasons we are calling out to our colleagues all over the world to show that you are a SCN community member who wants to have a SAP System Administration space and post a comment to this blog, vote for the idea on idea place, react on twitter using hash tag #SAPADMIN and spread the word.

Martin created a dummy page to show how to space could look like.

The next step

If there is enough reaction we can get our own space on SCN and create content for it. It can also be the necessary wake-up call to show that there is a need and demand for more technical content. I have heard from other SAP system administrators that TechED doesn’t offer enough technical hands-on sessions and that they mainly go for networking purposes. It’s great that you do networking but the event should also handle the demand for more technical content.

In order to do that feedback is essential. If you don’t step up and let your voice be heard, things are not going to change. So please yell “This is IT!”. React to this call to join forces and change things.

You can use any or all of the available platforms to spread the message. Comment on this blog, vote for the idea on idea place, post your system administration blog with the #SAPADMIN hash tag, tweet using #SAPADMIN on twitter and even create additional initiatives you can come up with to spread the word.

You will find blogs tagged with #SAPADMIN appearing to launch the idea.

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Martin English
    I was discussing this with someone at the Sydney Mastering SAP conference today, and they pointed out that a medium scale SAP implementation might take 6 – 12 months to Go Live.  But that system will be in day-to-day support by Administrators / BASIS people and Development staff for, on average, five to seven years (depending which set of figures you listen to).

    In other word, a system can easily spend from 5 to 14 longer in support than it does in development / implementation.

    (0) 
    1. Tom Cenens Post author
      Hello Martin

      Indeed the support of those SAP systems can take years and years so it’s important to have knowledge sharing on all those product versions since the support will have a lifespan of years.

      There is no doubt about the fact that there is a need for technical content and hands-on. I would love to see a technical hands-on session how you integrate HANA into a part of an ERP solution for example.

      I did see a webinar on the topic and it was very interesting but there is a need to have system admins / basis persons up to date along with developers and functional persons. I don’t see the need addressed when I look at the announcements and content that is released with new products.

      The BI4 launch for example shows a lot of content in terms of what the possibilities are available for developers and what you can do with the applications from a functional point of view but a lack of content on how technical persons will get impacted by the products. The same is valid for other products that come out.

      Creating the content for technical persons should start at the same moment in time that the content for developers and functional persons is being created.

      Kind regards

      Tom

      (0) 
      1. Martin English
        ahhh, yes…. BI and BO (and BW). 

        Some things never change; In the 60’s and 70’s at various times IBM was pushing end user, interactive, SQL.  You have no idea how badly written some of this SQL was.  I often wonder if similar episodes and issues was the real reason behind the introduction of the Business Warehouse Accelerator, and (indirectly) HANA itself 🙂

        (0) 
  2. David Hull
    Sadly, I find that most System Administrators (Basis/DB/OS) are not involved in social media, but I’m doing all I can to help change that with the ones I know. This type of community would also be a great way to engage more of them!

    Cheers,
    David.

    (0) 
  3. Amish Patel
    Absolutely there is no place for the People who really maintain the SAP Systems on SDN.  I am sure we (The Basis Admins) know that anything that the functional or development or middleware guys cannot solve comes to Basis for resolution.  Even before a ticket is Opened with the HelpDesk folks, the Basis are notified of an issue which clearly is someone else’s ticket but we still end up helping them.  So doesn’t that show the importance of “The Basis Folks” ;-).

    We should have a place where we can throw in our ideas,thoughts, minds, etc to make our lives fun.

    (0) 
    1. Tom Cenens Post author
      Hello Amish Patel

      Thanks for your strong believe in a Admin Community space. It is of great importance that our voices are heard and that more system administrators emphasize the need for such a community and related content.

      You are welcome to use the #sapadmin hashtag on twitter to emphasize SAP Technical conversations and content.

      Kind regards

      Tom

      (0) 

Leave a Reply